Loading...
Loading...
Found 621 Skills
Paper Reader for Non-Academics. It takes a research paper and extracts actionable ideas for personal use. Focuses on comprehension rather than academic critique. Activate when users share an arXiv link, paper URL, PDF, or request to analyze a research paper. Trigger words: 'read paper', 'analyze paper', 'paper', or when users share an academic paper.
Shared scripts, fragments, and bundled files used by all RootSpec skills — not meant to be invoked directly
Transforms a rough idea into a detailed design document with implementation plan. Follows Prompt-Driven Development — iterative requirements clarification, research, design, and planning.
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.
Write a feature spec or PRD from a problem statement or feature idea. Use when turning a vague idea or user request into a structured document, scoping a feature with goals and non-goals, defining success metrics and acceptance criteria, or breaking a big ask into a phased spec.
Structured clarification and requirements gathering through focused dialogue. Use when a task is ambiguous, underspecified, or requires user input before any action can be taken. Do not plan or implement anything—only ask questions to collect the information needed.
Activate for business cards, flyers, invitations, packaging, posters, and any physical media design.
You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, designing systems, or making architectural decisions. Enters plan mode, reads all available docs, explores the codebase deeply, then interviews the user relentlessly with ultrathink-level reasoning on every decision until a shared understanding is reached. Produces a validated design spec before any implementation begins. Triggers on feature requests, design discussions, refactors, new projects, component creation, system changes, and any task requiring design decisions.
Obsidian's UI design system. Use when building interfaces inspired by Obsidian's aesthetic - dark mode, Inter font, 4px grid.
Upstash's UI design system. Use when building interfaces inspired by Upstash's aesthetic - light mode, Inter font, 4px grid.
This skill should be used when the user asks "what is Stratum v2", "mining protocol v2", "binary mining protocol", "encrypted mining", "job declaration protocol", or needs to understand Stratum v2 for BSV mining infrastructure.
SDD workflow: specs, designs, implementation plans, quality gates.