Loading...
Loading...
Found 865 Skills
Optimizes raw idea descriptions into structured prompts ready for the brainstorming workflow. TRIGGER when: user says "optimize for brainstorm", "prepare idea for brainstorm", "enhance this idea", "make this ready for brainstorming", "imposta per brainstorm", or wants to improve a feature idea before using /specs.brainstorm. DO NOT TRIGGER for code optimization, refactoring, or general prompt engineering tasks.
Crea o actualiza tareas técnicas (TK-XXX) asociadas a una historia de usuario existente. Activar cuando el usuario solicite planificar implementación, descomponer trabajo, definir alcance técnico, estructurar subtareas o documentar especificaciones técnicas sin generar código ni pruebas. Activar también — por defecto — cuando el usuario solo entregue una referencia a una historia (p. ej. «US-004», «planifica US-007», «tareas para esta historia») — en ese caso el propósito es proponer stubs agrupados por unidad de trabajo que cubran los escenarios (SC-XX) y consideren las reglas de negocio (BR-XX) de la US, sin redactar TKs completas.
Review reusable project knowledge and decide what belongs in project memory, notepad, or durable docs
Use when documenting an HTTP API, message payloads, queue contracts, DTOs, file formats, or webhooks - or when writing the api-reference of a legacy campaign, or when callers keep asking what a field means or which errors an endpoint returns. Encodes the four detail levels, the DTO-first catalog, wire types with source anchors, the generated-spec one-home rule, and omitted-versus-null semantics. Use whenever a machine interface needs documenting for its callers, even if nobody says "API docs".
Proxy2.0 数据库设计与操作规范：表设计命名、字段类型、索引规则、DO 对象、Mapper 接口、 SQL 安全、性能优化、MyBatis Plus 使用。Use when: (1) Creating database tables or SQL, (2) Writing DO classes, (3) Creating Mapper interfaces, (4) Reviewing database code, (5) Optimizing queries, (6) Working with MyBatis Plus.
Supabase's UI design system. Use when building interfaces inspired by Supabase's aesthetic - dark mode, Inter font, 4px grid.
Write structured product requirements documents (PRDs) with problem statements, user stories, requirements, and success metrics. Use when speccing a new feature, writing a PRD, defining acceptance criteria, prioritizing requirements, or documenting product decisions.
This skill must be used before any creative work—creating features, building components, adding functionality, or modifying behavior. Explore user intentions, requirements, and designs before implementation.
Research, discuss, and write specs. Use this when creating or refining specs.
Use when you need to generate "page list → function points → business processes → business rules" with evidence from frontend code, and the project has non-unique routing entries, complex dynamic routes/permissions/backend menus, and the team is prone to making assumptions or missing evidence chains.
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.
Arc's UI design system. Use when building interfaces inspired by Arc's aesthetic - light mode, Inter font, 4px grid.