docs(agents): prefer cleaner code shape

This commit is contained in:
Peter Steinberger
2026-05-18 13:46:22 +01:00
parent c32878d1b7
commit d29f77bece
+5
View File
@@ -111,6 +111,11 @@ Skills own workflows; root owns hard policy and routing.
- No `@ts-nocheck`. Lint suppressions only intentional + explained.
- External boundaries: prefer `zod` or existing schema helpers.
- Runtime branching: discriminated unions/closed codes over freeform strings. Avoid semantic sentinels (`?? 0`, empty object/string).
- If formatter output becomes a jagged staircase, refactor the expression instead of accepting the formatted shape.
- For function calls with config objects, compute complex fields above the call; keep object fields simple.
- Avoid dense inline plumbing: no nested ternaries, long `??` chains, or repeated `params.foo?.bar` inside argument objects.
- Prefer named intermediate values when a value has domain meaning, e.g. `channel`, `parentSessionKey`, `selectedModelRef`, `sourceProvider`.
- Code should read top-down: gather inputs, normalize/resolve, then call helpers.
- Dynamic import: no static+dynamic import for same prod module. Use `*.runtime.ts` lazy boundary. After edits: `pnpm build`; check `[INEFFECTIVE_DYNAMIC_IMPORT]`.
- Cycles: keep `pnpm check:import-cycles` + architecture/madge green.
- Classes: no prototype mixins/mutations. Prefer inheritance/composition. Tests prefer per-instance stubs.