archgen-skill 0.0.7 → 0.1.1

package/vendor/skills/archgen/archgen.config.json

@@ -1,5 +1,5 @@
 {
-  "version": "0.0.7",
+  "version": "0.1.1",
   "skillName": "archgen",
   "markers": {
     "start": "<!-- archgen:start (managed block - do not edit between markers) -->",

package/vendor/skills/archgen/references/code-standards.md

@@ -1,70 +1,54 @@
 # Code standards — contractual, verifier-enforced
 
-Workers and planners follow these. The verifier rejects tasks whose plan or
-output violates them. Every rule exists because its absence produced real
-production incidents somewhere.
+Workers and planners must follow these rules. The verifier rejects plans or outputs that violate them.
 
 ## Typing (TypeScript projects)
 
-- NO ANY: `any` is BANNED — including implicit anys and `as any` casts. Enable `"strict": true` plus
-  `noImplicitAny`, `strictNullChecks`, `noUncheckedIndexedAccess`.
-- No unhandled `undefined`/null: validate at boundaries (env parsing, API
-  input) with a schema; inside the codebase use non-optional types + explicit
-  result objects for fallible operations.
-- Prefer discriminated unions over boolean-flag parameters.
-- Generated Python/Rust/Go equivalents: type hints mandatory / no `unwrap()` on
-  fallibles / handle errors explicitly — same discipline per language.
+- **NO `any`:** Explicit `any`, implicit `any`, and `as any` casts are BANNED. Enforce `"strict": true`, `noImplicitAny`, `strictNullChecks`, and `noUncheckedIndexedAccess`.
+- **No unhandled `undefined`/`null`:** Validate external boundaries (env vars, API payloads) with schemas; internally use non-optional types and explicit result unions for fallible operations.
+- **Discriminated unions:** Prefer discriminated unions over boolean-flag parameters.
+- **Other languages:** Mandatory type hints in Python; no `.unwrap()` on fallible types in Rust; explicit error handling in Go.
 
 ## File & module limits
 
-- HARD CEILING: files < 1000 LOC. Split well before — when a file gains a
-  second responsibility, that IS the split signal.
-- One public purpose per module. If the docstring needs "and", split.
+- **Hard ceiling:** Files MUST stay `< 1000 LOC`. Split immediately when a file acquires a second responsibility.
+- **Single responsibility:** One public purpose per module. If its summary requires `"and"`, split it.
 
 ## Folder structure (planned in architecture.yaml BEFORE coding)
 
 ```
 src/
-  features/<name>/        # feature-first: everything a feature owns
-    api/                  #   inbound contracts (routes/handlers)
-    internal/             #   private implementation
-    tests/                #   colocated tests mirror structure
-  shared/                 # cross-feature ONLY; may not import features/
-  config/                 # typed env + constants
+  features/<name>/   # Feature-first: everything a feature owns
+    api/             # Inbound contracts (routes/handlers)
+    internal/        # Private implementation
+    tests/           # Colocated tests mirroring structure
+  shared/            # Cross-feature utilities ONLY; MUST NOT import features/
+  config/            # Typed env parsing + constants
 ```
 
-- Feature modules may import `shared/`; `shared/` imports NOTHING from features.
-- Tests live beside code (mirrored path), never a distant `/tests` desert.
+- `features/*` may import `shared/`; `shared/` imports NOTHING from `features/`.
+- Colocate tests beside the code they test—never in a disconnected root `/tests` directory.
 
 ## File naming
 
-Per-language conventions (professional, descriptive, consistent):
-
-| Language | Source files | Components/classes | Tests |
+| Language | Source files | Components / Classes | Tests |
 |---|---|---|---|
-| TypeScript | `kebab-case.ts` | `PascalCase.tsx` components, `PascalCase` classes | `<subject>.test.ts` colocated |
-| Python | `snake_case.py` modules | `PascalCase` classes, `snake_case` functions | `test_<subject>.py` mirrored |
-| Rust | `snake_case.rs` modules | `PascalCase` types/traits | `#[cfg(test)] mod tests` inline or `tests/` |
-| Go | `snake_case.go` packages | `PascalCase` exported / `camelCase` internal | `<subject>_test.go` same dir |
+| TypeScript | `kebab-case.ts` | `PascalCase.tsx` components, `PascalCase` classes | `<subject>.test.ts` (colocated) |
+| Python | `snake_case.py` | `PascalCase` classes, `snake_case` functions | `test_<subject>.py` (mirrored) |
+| Rust | `snake_case.rs` | `PascalCase` types/traits | `#[cfg(test)] mod tests` or `tests/` |
+| Go | `snake_case.go` | `PascalCase` exported, `camelCase` internal | `<subject>_test.go` (same dir) |
 
-- Descriptive > clever: `rate-limiter.ts` not `rl.ts`; `parse-config.ts` not
-  `utils2.ts`.
-- BANNED names: `utils.ts`, `misc.ts`, `helpers.ts`, `temp*`, `final*`,
-  `copy*`, numbered duplicates (`auth2.ts`) — split by responsibility instead.
+- **Descriptive over terse:** Use `rate-limiter.ts` (not `rl.ts`) and `parse-config.ts` (not `utils2.ts`).
+- **BANNED names:** `utils.*`, `misc.*`, `helpers.*`, `temp*`, `final*`, `copy*`, or numbered duplicates (`auth2.ts`). Split by specific responsibility.
 
 ## Comments
 
-- WHY at decision points: tradeoffs taken, non-obvious constraints, links to
-  decisions ("see ADR D3"). 
-- Public APIs get doc comments: purpose, params, failure modes.
-- NO noise: no `// increment i`, no commented-out code, no change-log comments
-  (git remembers).
+- **Document WHY:** Explain trade-offs, non-obvious constraints, and ADR references (`see ADR D3`) at decision points.
+- **Public APIs:** Document purpose, parameters, and failure modes.
+- **Zero noise:** No restating code (`// increment i`), no commented-out code, no inline changelogs.
 
 ## Enforcement hooks
 
-- tasks.yaml acceptance criteria MUST include at least one objectively
-  checkable statement (command exit, observable output).
-- The verifier runs `archgen_plan{action:'verify'}` AND reads plans against this
-  file; violations = ISSUES, not warnings.
-- Workers receive this reference in their prompt contract; "I didn't know" is
-  not available to them.
+- Every `tasks.yaml` acceptance list MUST include $\ge 1$ objectively verifiable check (exit code or observable output).
+- The verifier runs `archgen_plan{action:'verify'}` and audits plans against this file; violations trigger `ISSUES`.
+- Workers receive this file path in their prompt contract and are strictly bound by it.