Loading...
Loading...
Found 2,894 Skills
Use when generating PDFs from markdown with Pandoc - covers differences from Python-Markdown, blank line rules, fix scripts for labels/anchors/metadata, and visual testing workflow
Research codebase comprehensively using parallel sub-agents to answer user questions. Use when the user asks to "research the codebase", "understand how X works", or "investigate Y".
Meta-skill for internal codebase exploration at varying depths (quick/deep/architecture)
Generate comprehensive implementation tutorial documents with deep background, context, rationale, and step-by-step milestones. Use when the user wants to learn by building—creating detailed guides instead of making direct code changes. Triggers on requests like "create a tutorial for", "implementation guide", "teach me how to implement", or explicit /tutorial invocation.
Systematic three-phase approach to feature development using Requirements, Design, and Tasks phases. Transforms vague feature ideas into well-defined, implementable solutions that reduce ambiguity, improve quality, and enable effective AI collaboration.
Processes meeting notes or transcripts to extract structured information. Use after meetings to quickly generate action items, capture decisions, and create follow-up tasks. Extracts: action items with owners, decisions made, key discussion points, follow-up tasks with priorities.
Manage project rules and standards in docs/rules/. Use when creating coding standards, git conventions, style guides, or any enforceable project rules. Routes to specialized sub-skills for code, git, and infrastructure rules.
Create feature definition documents with phased delivery, MVP scope, and definition of done. Use when specifying new product features, user-facing capabilities, or system enhancements that require planning and incremental delivery.
This skill should be used when the user asks to "document discussion", "save meeting notes", "record conversation", "capture meeting", or mentions needing to document team discussions with participants, decisions, and action items.
Generates module specifications following amplihack's brick philosophy template. Use when creating new modules or documenting existing ones to ensure they follow the brick & studs pattern. Analyzes code to extract: purpose, public contract, dependencies, test requirements.
Review a single file or all files in a folder for data inconsistencies, reference errors, typos, and unclear terminology using parallel sub-agents
Use when developing or documenting trading strategies - guides edge hypothesis formation, validates statistical significance, documents strategy rules systematically (entry, exit, risk management). Activates when user says "research this strategy", "document my approach", "test this idea", mentions "trading strategy", "edge", or uses /trading:research command.