docs(coding): files 1000 lines max, functions 200 lines max, no earlier split point

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
BluscreamandClaude Opus 5.5 committed 2026-10-18 21:52:48 +02:00
1 parent e385e01993
commit 44c2d1502c
4 files changed
+26 -25

No files matched your search

+3 -3
View File
@@ -139,9 +139,9 @@ Attach an `AbortController` to every long-lived `fetch` and abort it in cleanup.
- **Imports**: prefer the configured alias (`@/…`) over relative climbs.
- Indentation and quote/semicolon style: **match the file you are editing**. Do not introduce
a new formatter or lint config into a project that already has one.
- **One file until it earns a split** — around 250 lines for a self-contained plugin/feature,
or when a second file is genuinely reusable (`utils.ts`, `types.ts`, `components/`).
Hard limits from the general rules still apply: ESLint's `max-lines` and
- **One file until it earns a split** — when it nears the 1000-line limit, or when a second
file is genuinely reusable (`utils.ts`, `types.ts`, `components/`).
The limits from the general rules (1000 lines per file, 200 per function) apply: ESLint's `max-lines` and
`max-lines-per-function` cover both natively, so prefer those over a separate test here.
---