Loading...
Loading...
Found 5,531 Skills
17 developer utilities via MCP — base64, UUID, hash, JWT decode, cron, timestamps, JSON, regex. Use for common dev utility tasks.
Use when creating or modifying Angular components in WebV2 (Angular 19) with proper base class inheritance, state management, and platform patterns.
Information collection and exploration before Spec creation. Invoked by the role spec-explorer. Trigger conditions: (1) The spec-explorer role needs to collect background information before Spec creation, (2) Need to retrieve historical experience (exp-search), (3) Need to explore the project codebase, external documents or third-party libraries, (4) TeamLead notifies the spec-explorer to start working.
Convert raw plugin analysis results into actionable improvement recommendations for agent-scaffolders and agent-skill-open-specifications. Trigger with "synthesize learnings", "generate improvement recommendations", "what should we improve in our scaffolders", "update our meta-skills based on these findings", or after completing a plugin analysis.
Semantic search skill for retrieving code and documentation from the ChromaDB vector store. Use when you need concept-based search across the repository (Phase 2 of the 3-phase search protocol). V2 includes L4/L5 retrieval constraints.
Use AST parsing and code graph indexing for deep codebase analysis — refactoring, dead-code detection, dependency tracing, impact analysis, and safe symbol renaming
macOS Reminders: create tasks, due dates, priorities, lists, location-based, iCloud sync
Foundry is a Rust-based toolkit for developing, testing, and deploying Ethereum smart contracts using Solidity.
Advanced git workflows including worktrees, bisect, interactive rebase, hooks, and recovery techniques
Update documentation based on lessons learned. Use after completing work to capture learnings and prevent future issues.
Strict Red-Green-Refactor workflow for robust, self-documenting code. Discovers project test setup via codebase exploration before assuming frameworks. Use when: (1) Implementing new features with test-first approach, (2) Fixing bugs with reproduction tests, (3) Refactoring existing code with test safety net, (4) Adding tests to legacy code, (5) Ensuring code quality before committing, (6) When tests exist but workflow unclear, or (7) When establishing testing practices in a new project. Triggers: test, tdd, red-green-refactor, failing test, test first, test-driven, write tests, add tests, run tests.
Use this when you are exploring the codebase. It lets you ask the AI who wrote code questions about how things work and why they chose to build things the way they did. Think of it as asking the engineer who wrote the code for help understanding it.