Skill Claude CodeCodex
Discover, prepare, capture, or generate evidence-based Architecture Decision Records under docs/adr/. Use when architectural choices need to be surfaced, discussed, or recorded without inventing historical rationale.
Skill Claude CodeCodex
Inspect a repository and create or refresh concise, evidence-based architecture documentation under docs/archdoc/. Use for repository orientation, static architecture, interface surfaces, and operational/runtime documentation.
Skill Claude CodeCodex
Generate or refresh selective C4-style architecture documentation for a repository using evidence-based GitHub-renderable Mermaid views. Use when the user explicitly wants C4 system, container, component, deployment, or dynamic views.
Skill Claude CodeCodex
Review repository boundaries for responsibility drift, knowledge leakage, boundary bypasses, and change amplification using concrete repository evidence. Use for a focused Cockburn-style architecture critique.
Skill Claude CodeCodex
Discover and document repository-specific business and domain language from a Domain-Driven Design perspective. Use when asked to identify ubiquitous language, domain terminology, bounded-context vocabulary, ambiguous business terms, or to create or refresh docs/GLOSSARY.md.
Skill Claude CodeCodex
Create or update one focused Mermaid diagram when a repository document benefits from a visual explanation. Use as a helper for specific flow, structure, dependency, or interaction diagrams; do not create a separate documentation model by default.
Skill Claude CodeCodex
Review a repository for accidental or unjustified implementation complexity and propose simpler alternatives when evidence supports them. Use for evidence-based overengineering and complexity reviews.
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: