Loading...
Loading...
Found 10,419 Skills
Investigates and analyzes an idea or codebase area before committing to changes. Pure research, no writes. Trigger: /sdd-explore <topic>, explore, investigate codebase, research feature, analyze before changing.
Creates a change proposal with clear intent, defined scope, and technical approach. Trigger: /sdd-propose <change-name>, create proposal, define change scope, sdd proposal.
Authors and consumes feature-level domain knowledge files in ai-context/features/. Reference guide for bounded-context business rules, invariants, integration points, and known gotchas.
Morning preparation. Calendar lookahead, meeting context loading, open threads from yesterday, active task review. Extends briefing with actionable prep.
Decomposes a spec or architecture into buildable tasks with acceptance criteria, dependencies, and implementation order for AI agents or engineers. Produces `.agents/tasks.md`. Not for clarifying unclear requirements (use discover) or designing architecture (use system-architecture). For code quality checks after building, see review-chain. For packaging and PRs, see ship.
Auto-detect project tech stack and configure language-specific references
Turn any CLI tool into a fully typed JavaScript/TypeScript API using cli-to-js
Explore requirements and approaches through collaborative dialogue before writing a right-sized requirements document and planning implementation. Use for feature ideas, problem framing, when the user says 'let's brainstorm', or when they want to think through options before deciding what to build. Also use when a user describes a vague or ambitious feature request, asks 'what should we build', 'help me think through X', presents a problem with multiple valid solutions, or seems unsure about scope or direction — even if they don't explicitly ask to brainstorm.
Route multi-step marketing, product, or business challenges to the right sequence of ClawFu skills. Recommends which frameworks to combine, in what order, with handoff outputs between steps. Use when: planning a product launch end-to-end, combining positioning + offers + launch skills, running a customer-validation sprint, creating a content strategy pipeline, deciding which skills to chain for a complex project, or orchestrating a sales-enablement playbook.
Follow this sub-process when fixing bugs—turn the verbal description of "discovered a problem" into a closed loop of verification and repair, leaving three documents in the middle: issue report, root cause analysis, and repair record. This process adds a buffer between "seeing the problem" and "starting to modify code", avoiding several common pitfalls: the problem description in your mind disappears after modification, fixing only the surface without analyzing the root cause, uncontrollable expansion of repair scope that cannot be traced, and not knowing if the fix is correct without verification after modification. This skill only acts as a router, deciding which of report / analyze / fix to proceed with based on existing outputs. For simple problems that can be identified at a glance, a fast track will be taken, skipping the two middle steps and only keeping the fix-note.
Organize reusable programming patterns, library usages, and technical techniques that address "This is the correct way to do such tasks" into a prescriptive reference library, which can be retrieved and reused on demand during feature-design and issue-analyze phases. There are three types: pattern (design patterns, programming idioms), library (usage and pitfalls of a specific library/framework), technique (specific operation skills / command recipes). Trigger scenarios: when users say "Record a trick", "This usage is worth noting", "tricks", "Record library usage", or when valuable techniques worth documenting and archiving are discovered during feature-design / issue-analyze phases and actively pushed. For how to distinguish it from learning / decisions / explore, refer to the root skill of `easysdd`.
Integrate markstream-angular into an Angular app. Use when Codex needs standalone component imports, signal-based examples, CSS wiring, custom HTML tags or customComponents setup, or optional peer integration in an Angular repository.