lagz0ne/c3-skill

Routes C3 architecture requests and audits existing C3 documentation for consistency. Use when the user asks to "audit architecture", "validate C3", "check C3 docs", "verify docs", "check documentation", "are docs up to date", or when no .c3/ directory exists (routes to onboarding). Routes navigation to c3-query, changes to c3-alter, patterns to c3-ref, design to c3-provision.

Audit an ADR for C3 principle violations before approval. Use when reviewing ADRs or when c3-alter needs pre-approval validation. Checks abstraction boundaries, composition rules, context alignment, and ref compliance.

Documents architecture WITHOUT implementation. Creates ADR and component docs with status: provisioned. MUST use this skill when user wants to DESIGN or PLAN without implementing: - "provision X", "provision a component", "provision new service" - "design the architecture for X", "design a component" - "plan X", "plan a new service", "plan the architecture" - "document X architecture", "architect X" - "envision X", "sketch X architecture" DO NOT use this skill if prompt contains: - "pattern", "patterns" → route to c3-ref - "ref", "refs" → route to c3-ref - "convention", "standard" → route to c3-ref Key indicator: User wants documentation/design output, NOT code changes. Requires .c3/ to exist. Creates ADR with status: provisioned. For implementation requests, route to c3-alter.

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", "what constraints apply to X", or references C3 IDs (c3-0, c3-1, adr-*). Requires .c3/ to exist. For changes, route to c3-alter instead.