Loading...
Loading...
Found 865 Skills
Deep interview process to transform vague ideas into detailed specs. Works for technical and non-technical users.
Railway's UI design system. Use when building interfaces inspired by Railway's aesthetic - dark mode, Inter font, 4px grid.
Lemonsqueezy's UI design system. Use when building interfaces inspired by Lemonsqueezy's aesthetic - light mode, Inter font, 4px grid.
Use when you need to turn a vague idea into a confirmed design spec before implementation (new feature/component/behavior change). First check project context, then ask one question at a time, provide 2-3 options with trade-offs, finally output design in segments (~200-300 words each) with confirmation after each. Triggers: brainstorm, clarify idea, design spec, refine concept, requirement clarification.
Specify micro-interactions with trigger, rules, feedback, and loop/mode definitions.
Agent eXperience Interface (AXI) — ergonomic standards for building CLI tools that agents use via shell execution. Use when building, modifying, or reviewing any agent-facing CLI.
Focuses on reviewing, maintaining, and generating project documentation (located in the docs/ directory).
End-to-end UI/UX design skill that takes a feature from vague idea to production-ready UI by moving sequentially through research, requirements, information architecture, wireframing, and visual design without skipping steps.
Use this when you need to initialize a new Spec Pack in the AI SDLC workflow of this repository (create a three-digit numbered branch and the `.aisdlc/specs/{num}-{short-name}` directory), or when you are unsure about input parsing, short name rules, UTF-8 BOM file path parameter passing, script invocation methods, or output artifacts when executing `spec-init`.
Convert between Skill (SKILL.md) and Prompt (chat box instruction) formats. Supports two-way conversion between Skill→Prompt and Prompt→Skill with zero loss of core information. Use this when users mention Skill to Prompt conversion, Prompt to Skill conversion, format mutual conversion, or SKILL.md conversion.
This skill should be used when the user explicitly says "Nothing style", "Nothing design", "/nothing-design", or directly asks to use/apply the Nothing design system. NEVER trigger automatically for generic UI or design tasks.
Use when a technical question needs a real experiment to answer, to generate a structured spike spec before executing it in a separate session