c3-ref
Manage cross-cutting patterns and conventions as first-class architecture artifacts. Use when: "add a pattern", "document this convention", "create a ref", "update ref-X", "evolve this pattern", "what patterns...
Explorez les skills IA publiés de lagz0ne et consultez leurs instructions source.
Skills indexés
18Étoiles des dépôts des skills indexés
36Forks du dépôt
0Moyenne des étoiles par skill indexé
2Les étoiles d’un dépôt peuvent se répéter entre ses skills.
Manage cross-cutting patterns and conventions as first-class architecture artifacts. Use when: "add a pattern", "document this convention", "create a ref", "update ref-X", "evolve this pattern", "what patterns...
Makes architectural changes through ADR-first workflow with staged intent clarification. Use when the user asks to "add a component", "change architecture", "refactor X", "implement feature", "fix bug", "create...
Creates C3 architecture documentation from scratch using staged Socratic discovery. Use when the user asks to "adopt C3", "onboard me to architecture", "scaffold C3 docs", "init C3", "set up architecture docs",...
Routes C3 architecture requests and audits existing C3 documentation for consistency. Use when the user asks to "audit architecture", "validate C3", "check C3 docs", or when no .c3/ directory exists (routes to...
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"...
This skill should be used when the user asks to "add a component", "change architecture", "refactor X", "implement feature", "fix bug", "create new service", "update diagram", or "remove component". Requires .c...
Creates C3 architecture documentation from scratch using staged Socratic discovery. Use when the user asks to "adopt C3", "onboard me to architecture", "scaffold C3 docs", "init C3", "set up architecture docs",...
This skill should be used when the user asks to "adopt C3", "onboard me to architecture", "scaffold C3 docs", "init C3", "audit architecture", "validate C3", or "check C3 docs". Also triggers when no .c3/ direc...
This skill should be used when the user asks "where is X", "how does X work", "explain X", "show me the architecture", "find component", "what handles X", or references C3 IDs (c3-0, c3-1, adr-*). Requires .c3/...
Use when upgrading .c3/ documentation to current skill version - reads VERSION, applies transforms from migrations/ directory in batches
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
Use when exploring Context level impact during scoping - system boundaries, actors, cross-container interactions, and high-level concerns
Use when bootstrapping C3 documentation for any project - guides through Socratic discovery and delegates to layer skills for document creation
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
Use when verifying C3 documentation quality - checks methodology compliance (layer rules, structure, diagrams) and implementation conformance (docs vs code drift)
Use when making changes to diashort - new features, bug fixes, refactoring, or modifications. Guides through brainstorming, planning, and subagent-driven implementation with reviews.
Use when configuring project preferences in .c3/settings.yaml - diagram tools, layer guidance, guardrails, and handoff steps
Use when designing, updating, or exploring system architecture with C3 methodology - iterative scoping through hypothesis, exploration, and discovery across Context/Container/Component layers
Le classement utilise les étoiles du dépôt GitHub indexé. Plusieurs skills peuvent partager ce nombre : ce n’est ni un nombre d’installations ni une note de qualité.