Documentation

Use when ranking backlogs, deciding what to do first based on effort vs impact (quick wins vs big bets), prioritizing feature roadmaps, triaging bugs or technical debt, allocating resources across initiatives, identifying low-hanging fruit, evaluating strategic options with 2x2 matrix, or when user mentions prioritization, quick wins, effort-impact matrix, high-impact low-effort, big bets, or asks "what should we do first?".

Use when content must be translated between audiences with different expertise, context, or goals while preserving accuracy but adapting presentation. Invoke when technical content needs business framing (engineering decisions → executive summary), strategic vision needs tactical translation (board presentation → team OKRs), expert knowledge needs simplification (academic paper → blog post, medical diagnosis → patient explanation), formal content needs casual tone (annual report → social media post), long-form needs summarization (50-page doc → 1-page brief), internal content needs external framing (roadmap → public updates, bug tracking → known issues), cross-cultural adaptation (US idioms → international clarity, Gen Z → Boomer messaging), medium shifts (written report → presentation script, detailed spec → action checklist), or when user mentions "explain to", "reframe for", "translate this for [audience]", "make this more [accessible/formal/technical]", "adapt for [executives/engineers/customers]", "simpl

Rule 07: Testing. Use when writing tests, reviewing test coverage, or setting up testing.

Stratégie de Tests React. Use when writing tests, reviewing test coverage, or setting up testing.

Testing Flutter - Stratégie Complète. Use when writing tests, reviewing test coverage, or setting up testing.

Use when writing or reviewing career documents including research statements, teaching statements, diversity statements, CVs, or biosketches. Invoke when user mentions research statement, teaching philosophy, diversity statement, biosketch, academic CV, faculty application, or needs help with career narrative, positioning, or professional documents for academic advancement.

Plan, generate, and validate documentation using Prompt Architect clarity patterns and routing to doc-generator subskills.

FrankenPHP Documentation - Modern PHP application server built on Caddy

Compare a GitHub repository with connectrpc-axum. This skill should be used when the user provides a GitHub repository URL and wants to compare it with the current project. Analyzes user features, technical implementation, architecture patterns, code quality, tests, and documentation. Outputs comparison to docs/guide/compare/ directory.

Create docstrings for functions and classes. Use when documenting code APIs.

Use when analyzing failures, outages, incidents, or negative outcomes, conducting blameless postmortems, documenting root causes with 5 Whys or fishbone diagrams, identifying corrective actions with owners and timelines, learning from near-misses, establishing prevention strategies, or when user mentions postmortem, incident review, failure analysis, RCA, lessons learned, or after-action review.

Use when explaining concepts at different expertise levels, moving between abstract principles and concrete implementation, identifying edge cases by testing ideas against scenarios, designing layered documentation, decomposing complex problems into actionable steps, or bridging strategy-execution gaps. Invoke when user mentions abstraction levels, making concepts concrete, or explaining at different depths.

Comprehensive PR review that synthesizes security, performance, correctness, style, and documentation findings with actionable fixes.

Create weekly software meeting agenda in the wiki repo.

Documentation lifecycle skill for API, code, and system guides with continuous validation.

Estrategia de Testes React. Use when writing tests, reviewing test coverage, or setting up testing.

Estrategia de Testing React. Use when writing tests, reviewing test coverage, or setting up testing.

Map workflows, extract SOPs, and identify automation opportunities through systematic process capture and AI tractability assessment. Use when documenting workflows, creating SOPs, conducting process discovery interviews, or analyzing automation opportunities. Grounds the SOP-first doctrine in tacit knowledge documentation and structured analysis.

Ollama API Documentation

Comprehensive cryptocurrency market research and analysis using specialized AI agents. Analyzes market data, price trends, news sentiment, technical indicators, macro correlations, and investment opportunities. Use when researching cryptocurrencies, analyzing crypto markets, evaluating digital assets, or investigating blockchain projects like Bitcoin, Ethereum, Solana, etc.