Skill Creator
lagz0ne
11 published skills · 18 GitHub stars across the catalog. View on GitHub ↗
c3
Use when working with C3 architecture docs - navigating, understanding, designing, or auditing.Triggers: "C3", "architecture", "where is X documented", "impact of changing X".
c3-alter
Use when project has .c3/ and user intends to change code or architecture.Triggers: "add", "change", "modify", "update", "fix", "refactor", "remove", "implement", "create new", "rename", "new feature", "bug fix".
c3-query
Use when project has .c3/ and user asks about architecture or code location.Triggers: "explain", "where is", "look for", "how does", "what is", "find", "show me", C3 IDs (c3-0, c3-1, adr-*).
c3-adopt
Use when bootstrapping C3 documentation for any project - guides through Socratic discovery and delegates to layer skills for document creation
c3-audit
Use when verifying C3 documentation quality - checks methodology compliance (layer rules, structure, diagrams) and implementation conformance (docs vs code drift)
c3-component-design
Use when documenting component implementation patterns, internal structure, or hand-off points - enforces NO CODE rule and diagram-first approach for leaf-level C3 documentation
c3-config
Use when configuring project preferences in .c3/settings.yaml - diagram tools, layer guidance, guardrails, and handoff steps
c3-container-design
Use when changes affect component organization, technology stack, or cross-container communication - triggered by new components, pattern changes, or needing to map external interfaces to internal components
c3-context-design
Use when exploring Context level impact during scoping - system boundaries, actors, cross-container interactions, and high-level concerns
c3-design
Use when designing, updating, or exploring system architecture with C3 methodology - iterative scoping through hypothesis, exploration, and discovery across Context/Container/Component layers
c3-migrate
Use when upgrading .c3/ documentation to current skill version - reads VERSION, applies transforms from migrations/ directory in batches