a4e667de10
Single-commit clean baseline after security scrub of niche-tells, project codenames, internal jargon, and contributor-email leaks. Contents: - 100 Rust crates (_primitives/_rust/) - 37 agent manifests (_manifests/) + generated specs (_generated/) - 67 user-invocable skills (skills/) - 33 hooks (hooks/) - Composition blocks (_blocks/) - Documentation (docs/, README.md) - TS adapter packages (_ts_packages/) - Assembler (_assembler/) - Roles (_roles/) - Templates (_templates/) - Forgejo CI (.forgejo/) Author: Denis Parfionovich <info@greendragon.info> License: see LICENSE.
25 lines
1 KiB
Markdown
25 lines
1 KiB
Markdown
## Constructor Pattern — size limits
|
|
|
|
You MUST keep every file you write or edit under 200 lines of code,
|
|
and every function under 30 lines of code. These are hard limits,
|
|
not guidelines.
|
|
|
|
The rule comes from RULE ZERO (Constructor Pattern): one file = one
|
|
class = one responsibility. Files that breach 200 LOC should be
|
|
decomposed into sibling modules. Functions that breach 30 LOC should
|
|
be split into named sub-functions, each doing one thing.
|
|
|
|
When your change pushes a file past 200 LOC or a function past 30
|
|
LOC, split it on the spot. Do not commit with `TODO: refactor later`.
|
|
|
|
Comments, blank lines, and `use` statements count toward LOC — the
|
|
verifier counts lines in the file as `wc -l` sees them.
|
|
|
|
Exceptions:
|
|
- Auto-generated code (e.g. `include!(...)` expansions) is skipped.
|
|
- Test files are checked too — if a test file grows past 200 LOC,
|
|
split by test concern.
|
|
|
|
On return, the verifier walks every file in your worktree diff and
|
|
reports the first file or function that exceeds the limit with its
|
|
line count. No partial credit.
|