lagz0ne
@lagz0ne
Public Skills
c3-sweep
by lagz0ne
Sweeps architecture for impact before a change — spawns agents per C3 entity for constraint-checked analysis. Advisory only — does NOT make changes (route to c3-change for implementation). This skill should be used when the user asks to: - "assess C3 impact of X", "what would break in C3 if..." - "check C3 constraints for X", "is this change safe per C3 docs" - "affected C3 components", "which C3 containers are impacted by X" - "sweep C3 architecture", "impact assessment against C3 architecture" <example> user: "assess C3 impact if I replace the auth system" assistant: "Using c3-sweep to assess architectural impact." </example> DO NOT use for: "what is X" / "explain X" (c3-query), implementation (c3-change), patterns (c3-ref). Requires .c3/ to exist.
c3-change
by lagz0ne
Orchestrates architectural changes through Agent Teams with ADR-first workflow. This skill should be used when the user asks to: - "add a component", "add feature", "add X to Y", "new component", "create new service" - "add endpoint", "add API", "add middleware", "add handler", "add route" - "change architecture", "modify X", "update component", "refactor X" - "fix X", "fix bug", "fix issue", "implement X", "implement feature" - "remove component", "delete component", "deprecate X" - "provision X", "design the architecture for X", "plan X architecture" - "replace X with Y", "migrate X", "upgrade X" DO NOT use for: "what is X", "how does X work", "explain X" (route to c3-query). DO NOT use for: "add pattern", "create ref", "update ref" (route to c3-ref). DO NOT use for: "audit C3", "validate docs" (route to c3-audit). Requires .c3/ to exist. All changes flow through ADR process with Agent Teams.
c3-onboard
by lagz0ne
Creates C3 architecture documentation from scratch using staged Socratic discovery. This skill should be used when the user asks to: - "adopt C3", "init C3", "initialize C3", "start C3", "bootstrap C3" - "scaffold C3 docs", "create C3 docs", "create .c3", "set up .c3" - "set up architecture docs", "create architecture documentation" - "document this project", "document the codebase", "document the architecture from scratch" - "new C3 project", "first time with C3", "never used C3", "getting started with C3" - "onboard", "onboard this project", "C3 onboarding" DO NOT use when .c3/ already exists (route to c3-audit, c3-change, or c3-query). DO NOT use for updating existing docs (route to c3-change). Implements 3-stage workflow: Inventory → Details → Finalize.
c3-audit
by lagz0ne
Audits C3 architecture documentation for consistency, drift, and completeness. This skill should be used when the user asks to: - "audit C3", "validate docs", "check architecture", "verify C3 docs" - "run C3 audit", "check documentation", "are docs up to date", "docs out of sync" - "validate architecture", "check for drift", "verify docs match code" DO NOT use for: "update docs", "change docs" (route to c3-change for changes). Requires .c3/ to exist. Routes navigation to c3-query, changes to c3-change, patterns to c3-ref.
c3-query
by lagz0ne
Navigates C3 architecture docs and explores corresponding code to answer architecture questions. Use when the user asks: - "where is X", "how does X work", "explain X", "show me the architecture" - "find component", "what handles X", "diagram of X", "visualize X" - "describe X", "list components", "trace X", "flow of X" - References C3 IDs (c3-0, c3-1, adr-*) <example> Context: Project with .c3/ directory user: "explain what c3-101 does and how it connects to other components" assistant: "Using c3-query to navigate the architecture docs." </example> <example> Context: Project with .c3/ directory user: "show me a diagram of the C3 architecture" assistant: "Using c3-query to generate an architecture overview." </example> DO NOT use for changes (route to c3-change). DO NOT use for pattern artifact management — listing, creating, updating refs (route to c3-ref). Requires .c3/ to exist.
c3-ref
by lagz0ne
Manages scoped patterns and conventions as first-class architecture artifacts. This skill should be used when the user asks to: - "add a pattern", "document this convention", "create a ref", "update ref-X" - "evolve this pattern", "what patterns exist", "which components use ref-X" - "list refs", "show refs", "list patterns" - "standardize this approach", "make this a convention", "document this as a standard" <example> Context: Project with .c3/ directory user: "list all C3 refs and show which components cite each" assistant: "Using c3-ref to list patterns and their citings." </example> DO NOT use when "pattern" or "ref" is merely descriptive (e.g., "explain the auth flow pattern" → c3-query). DO NOT use for removing/deprecating refs (route to c3-change with ADR). Requires .c3/ to exist. Refs apply where their scope states — violations require explicit override.