Loading...
Loading...
Found 144 Skills
Knowledge base for designing, reviewing, and linting agentic AI infrastructure. Use when: (1) designing a new agentic system and need to choose patterns, (2) reviewing an existing agentic architecture ADR or design doc for gaps/risks, (3) applying the lint script to an ADR markdown file to get structured findings, (4) looking up a specific agentic pattern (prompt chaining, routing, parallelization, reflection, tool use, planning, multi-agent collaboration, memory management, learning/adaptation, MCP, goal setting, exception handling, HITL, RAG, A2A, resource optimization, reasoning techniques, guardrails, evaluation, prioritization, exploration/discovery). All rules and guidance are grounded in the PDF "Agentic Design Patterns" (482 pages).
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", "diagram of X", "visualize X" - "describe X", "list components", "trace X", "flow of X" - References C3 IDs (c3-0, c3-1, adr-*) <example> Context: Project with .c3/ directory user: "explain what c3-101 does and how it connects to other components" assistant: "Using c3-query to navigate the architecture docs." </example> <example> Context: Project with .c3/ directory user: "show me a diagram of the C3 architecture" assistant: "Using c3-query to generate an architecture overview." </example> DO NOT use for changes (route to c3-change). DO NOT use for pattern artifact management — listing, creating, updating refs (route to c3-ref). Requires .c3/ to exist.
Use for high-stakes technical decisions, system design (Microservices/Monolith), cloud infrastructure, or generating ADRs/RFCs.
Bootstrap AGENTS.md as a short table-of-contents plus a structured docs/ directory (architecture, product specs, acceptance tests, ADRs, exec plans, quality grades). Use when AGENTS.md is missing, when asked to "create AGENTS.md", "bootstrap project for agents", or "set up agent context".
[WHAT] Universal content intake system for URLs (GitHub repos, YouTube videos, articles, PDFs) and skill packages (skills.sh, skill:// protocol) [HOW] Phase 1: Clone repos/fetch transcripts/scrape content/resolve skills to ~/lev/workshop/intake/. Phase 2-3: Load workshop/intake.md for full analysis [WHEN] Use when user provides a URL to analyze, says "intake/download", wants to evaluate external content, or references a skill package [WHY] Systematically evaluates external content and skill packages for adoption/adaptation with tier classification and ADR creation Triggers: "intake", "download", "analyze this url", "check out this repo", "review this video", "evaluate content", "install skill", "skill://"
Automated SYS generation from ADR decisions - generates system requirements with REQ-Ready scoring
Expert in designing high-level enterprise solutions. Specializes in TOGAF adaptation, trade-off analysis, and aligning technology with business strategy.
Generate technical design documents with proper structure, diagrams, and implementation details. Default language is English unless user requests Chinese.
Use when designing system architecture, choosing between monolith/microservices/serverless, planning scalability, or making technology decisions. Covers microservices, event-driven, CQRS, modular monoliths, distributed systems, and reliability patterns for production-grade software.
Draft stakeholder updates tailored to audience — executives, engineering, customers, or cross-functional partners. Use when writing weekly status updates, monthly reports, launch announcements, risk communications, or decision documentation.
Creates 4 core project docs (requirements.md, architecture.md, tech_stack.md, patterns_catalog.md). L3 Worker invoked by ln-110-project-docs-coordinator. ALWAYS created.
arc42 architecture documentation template and guidance