Loading...
Loading...
Found 46 Skills
Use this skill for Makefile audit and optimization. Use when auditing Makefiles, reviewing build system, checking portability, eliminating recipe duplication. Do not use when creating new Makefiles - use abstract:make-dogfood. DO NOT use when: architecture review - use architecture-review.
Use this skill when orchestrating multiple review types. Use when general review needed without knowing which specific skill applies, full multi-domain review desired, integrated reporting needed. Do not use when specific review type known - use bug-review, test-review, etc. DO NOT use when: architecture-only focus - use architecture-review.
Use this skill for mathematical code verification. Use when reviewing math-heavy code, verifying algorithm correctness, checking numerical stability, aligning with mathematical standards. Do not use when general algorithm review - use architecture-review. DO NOT use when: performance optimization - use parseltongue:python-performance.
Generate layered architecture diagrams as self-contained HTML with inline SVG icons, CSS Grid containers, and connection overlays. Triggers on: "architecture diagram", "infra diagram", "system diagram", "deployment diagram", "topology", "draw architecture". NOT for architecture reviews, use architecture-reviewer.
Idiomatic Go design patterns: functional options, builder, factory, strategy, middleware chain, pub/sub, and other patterns adapted for Go's type system. Use when: "design pattern", "functional options", "builder pattern", "factory pattern", "strategy pattern", "middleware chain", "option pattern", "how to structure this". Do NOT use for: interface design principles (use go-interface-design), package layout (use go-architecture-review), or concurrency patterns (use go-concurrency-review).
Coordinate a cross-functional star-team workflow (Product Manager, Principal Engineer, Backend, Frontend, QA/Security, DevOps) with mandatory architecture and code-review checkpoints. Use when a request needs end-to-end product delivery, multi-role collaboration, or explicit role-based outputs (PM/PE/Backend/Frontend/QA/DevOps), or when the user asks for "star team", "cross-functional", "full lifecycle", or "multi-role" planning.
When the user wants a comprehensive technical analysis of a codebase or project. Also use when the user mentions 'analyze this codebase,' 'technical overview,' 'document this architecture,' 'what does this codebase do,' 'summarize this repo,' 'code audit,' 'architecture review,' 'codebase walkthrough,' or 'analyze this project.' Performs a multi-phase analysis covering architecture, code quality, testing, and infrastructure, producing a detailed markdown report targeting engineers. For quick code searches or single-file reviews, see standard editor tools.
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).
Analyze code quality, security, performance, and architecture. Use when user asks to analyze code, review codebase health, or identify issues.
Analyze the source code of GitHub open-source repositories and generate structured analysis reports. Supports generating reports such as project architecture overview, code quality analysis, core module description, etc., and optional synchronization to Notion.
Auto-generates code flow diagrams from Python module analysis. Detects when architecture diagrams become stale (code changed, diagram didn't). Use when: creating new modules, reviewing PRs for architecture impact, or checking diagram freshness. Generates mermaid diagrams showing imports, dependencies, and module relationships.
Generate an LLM-optimized project profile for any git repository. Outputs docs/{project-name}.md covering architecture, core abstractions, usage guide, design decisions, and recommendations. Trigger: "/project-profiler", "profile this project", "為專案建側寫"