Loading...
Loading...
Found 288 Skills
Write and maintain Architecture Decision Records (ADRs) following best practices for technical decision documentation. Use when documenting significant technical decisions, reviewing past architectural choices, or establishing decision processes.
Generate living documentation from git diffs — analyze branch comparisons or last N commits to automatically create or update Component Docs, Changelogs, ADRs, and Runbooks in Markdown with Obsidian-compatible YAML frontmatter. Use when asked to: (1) document changes from a branch diff, (2) generate release notes, (3) update service documentation, (4) analyze commits and produce docs, (5) create ADRs from architectural changes. Triggers: 'document the diff', 'generate docs from commits', 'update docs for [service]', 'release notes', 'what changed and document it', 'living docs', 'analiza el diff y genera documentacion'.
Create a new plugin for Claude Code marketplace with validation, ADR, and release automation. TRIGGERS - create plugin, new plugin, scaffold plugin, add plugin, plugin-dev create.
Map "Profit Growth × Financial Conditions (Financial Environment)" to the "Investment Clock" to determine the current quadrant, whether it has been rotating clockwise or counterclockwise recently, and the position difference compared to the previous cycle.
Create or evaluate an architecture decision record (ADR). Use when choosing between technologies (e.g., Kafka vs SQS), documenting a design decision with trade-offs and consequences, reviewing a system design proposal, or designing a new component from requirements and constraints.
Research best practices via MCP Ref/Context7/WebSearch and create documentation (guide/manual/ADR/research). Single research, multiple output types.
Create and maintain technical documentation including READMEs, API docs, architecture decision records (ADRs), and user guides. Use this skill when writing project documentation, documenting APIs, recording architectural decisions, creating how-to guides, or establishing documentation standards.
Creates and manages project artifacts (research, spikes, analysis, plans) using templated scripts. Use when asked to "create an ADR", "research topic", "spike investigation", "implementation plan", or "create analysis". Provides standardized structure, naming conventions, and helper scripts for artifact organization. Works with .claude/artifacts/ directory, Python scripts, and markdown templates.
Clarify or discuss a proposed task, plan, design update, or ADR by resolving the highest-value unresolved decisions, decision criteria, trade-offs, and option boundaries until the inputs are ready for task creation, task planning, task/design updates, ADR writing, or safe implementation continuation. Use this as the default path when the user asks to clarify, discuss criteria, compare options, stress-test a design, or otherwise resolve material unresolved questions before proceeding. When clarification ends, resume the invoking workflow. It may also be used for general grilling when explicitly selected or when no other default grilling skill is available.
Technical specification and design document expert. Use when writing design docs, RFCs, ADRs, or evaluating technology choices. Covers C4 model, system design, and architecture documentation.
Create an Architectural Decision Record (ADR) document for AI-optimized decision documentation.
Manage project todos in todo.md files with task states (pending, in_progress, completed). PROACTIVELY invoke when Claude detects need to create or update a todo during a session. Use when breaking down work into tasks, tracking progress across sessions, organizing complex multi-step projects, or coordinating task states. Supports refactor/migration tracking with ADR integration.