Loading...
Loading...
Found 867 Skills
When the user needs to define a product feature, write a product requirements document, or translate an idea into a structured spec.
Phase d'architecture systématique AVANT le code (TDD). Use when starting a new feature that touches multiple files, designing a new module, or making non-trivial architectural choices.
Write one model-agnostic video prompt spec, then compile it to whichever video model you can actually call. Use for cross-model prompt work, model comparison matrices, reusing one brief across providers, or when the target model is not yet available and the work must proceed on another one.
You MUST use this, and not the upstream superpowers brainstorming skill, before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation. The spec review is a quick inline self-check, and the next step is the sp-writing-plans skill.
Reference for any XRPL Standard (XLS-N) when implementing or reviewing XRPL protocol features. Trigger on: XLS number (XLS-30, XLS-70), amendment name (AMM, Credentials, MPT, DID, NFToken, Batch, Escrow, Clawback, Firewall, Permissioned DEX), transaction type (AMMCreate, CredentialCreate, NFTokenMint, DelegateSet, PermissionedDomainSet, BatchSubmit), or ledger object name (Credential, AMM, MPToken, Delegate, Oracle, Bridge).
When the user wants to plan, create, or repurpose visual content (images, infographics, social post images) across channels. Also use when the user mentions "content images," "social media images," "infographic," "visual content," "post image," "image specs," "visual repurposing," "content visuals," or "image for social post."
Define a new task with structured requirements before implementation. Use when the user says "define task", "new task", "spec this", or wants to formalize a feature/bug/refactor before planning.
Optional AI SDLC user-experience workflow. Use when an AI assistant needs to define actors, goals, user journeys, interaction steps, loading/empty/error/success states, recovery behavior, content intent, accessibility requirements, or UX acceptance evidence and route them into traceable human and machine artifacts. Supports `--quick-flow` for a focused journey slice and `--full-flow` for strict state, accessibility, and acceptance coverage.
Promote a quick-and-dirty prototype to an lgtm-hq-standard repo - commit WIP lint-clean, grill the design, spec the backlog as milestone/epic/issue tree, then implement issue by issue. Use when asked to properize, productionize, or turn a prototype into a proper project.
Explore user intent, requirements, and design options through collaborative dialogue before implementation. Use before building new features, components, or systems — whenever the user describes something to build and design decisions are involved. Triggers: "brainstorm", "help me design", "think through the requirements", "头脑风暴", "设计方案", "梳理需求". Not for bug fixes, config changes, or tasks with an obvious implementation path.
Create a new feature/bug track with spec and implementation plan. Interactive interview generates requirements spec, then phased TDD plan. Use when starting work on a new feature, bug fix, or chore.
Shared scripts, fragments, and bundled files used by all RootSpec skills — not meant to be invoked directly