Production-grade software delivery for coding-agent teams on Multica — dynamic planning, deterministic execution, verifiable delivery.
This repository also configures its own agents. See what oh-my-multica tells them →
Skill Claude CodeCodex
A method for creating or reviewing a detailed technical architecture diagram: a concrete description of how an approved system design will be built. It covers technical components, their connections, runtime collaboration, stability, operations, and security.
Skill Claude CodeCodex
A method for creating or reviewing a system functional architecture diagram: a high-level picture of what the system does and how its capabilities are grouped. It focuses on user and business capabilities, not code, deployment, or step-by-step runtime behavior.
Skill Claude CodeCodex
Use when an architect must run the overview-design portion of technical design, preserve the full lifecycle-stage doctrine for shared technical-design entry and overview design, and define goals, alternatives, functional layering, system structure, risk, and overview-level design boundaries before detailed design…
Skill Claude CodeCodex
A guide for architects who draw or review system architecture diagrams during overview design. It explains subsystems, outside dependencies, communication links, and system boundaries without going into every technology detail.
Skill Claude CodeCodex
Grill the user relentlessly about a plan or design. Use when the user wants to stress-test a plan before building, or uses any 'grill' trigger phrases.
Skill Claude CodeCodex
Use when architecture or backend work needs pre-code structural guidance from design patterns, or post-code cleanup guidance from refactoring and code-smell-driven improvement.
Skill Claude CodeCodex
Manage software complexity through deep modules, information hiding, and strategic programming. Use when the user mentions "module design", "API too complex", "shallow class", "complexity budget", "strategic vs tactical", "deep module", "information leakage", or "pass-through method". Also trigger when reviewing…
Skill Claude CodeCodex
Design scalable distributed systems using structured approaches for load balancing, caching, database scaling, and message queues. Use when the user mentions "system design", "scale this", "high availability", "rate limiter", "design a URL shortener", "system design interview", "capacity planning", or "distributed…
Skill Claude CodeCodex
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
Skill Claude CodeCodex
Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies.
Skill Claude CodeCodex
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup.
Skill Claude CodeCodex
Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation.
Skill Claude CodeCodex needs its repo
Use when executing implementation plans with independent tasks in the current session.
Skill Claude CodeCodex
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
Skill Claude CodeCodex
Use when implementing any feature or bugfix, before writing implementation code.
Skill Claude CodeCodex
Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always.
Skill Claude CodeCodex
Behavioral guidelines to reduce common LLM coding mistakes. Use when writing, reviewing, or refactoring code to avoid overcomplication, make surgical changes, surface assumptions, and define verifiable success criteria.
Skill Claude CodeCodex
Use when writing, reviewing, or refactoring code in any language to apply industrial-grade development norms abstracted from the Alibaba Java Development Handbook. Covers naming, type safety, exceptions, logging, concurrency, databases, project structure, testing, and security with language-agnostic principles and…
Skill Claude CodeCodex
Apply meta-principles of software craftsmanship: DRY, orthogonality, tracer bullets, and design by contract. Use when the user mentions "best practices", "pragmatic approach", "broken windows", "tracer bullet", "software craftsmanship", "technical debt prevention", "prototype vs tracer bullet", or "code ownership".…
Skill Claude CodeCodex
Throwaway HTML mockups: 2-3 design variants to compare.
Skill Claude CodeCodex
Top-level entry point for the software development skill family. Routes to the right sub-skill for design patterns, refactoring, DDD, worktree governance, kanban splitting, container supervision, project governance, runtime ops, and web routing.
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: