发现 编程开发 相关 Skills，比较来源仓库和用途，查看适合你工作流的技能说明。
Use this skill group when the user wants to "setup NOMAD", "configure settings", "add crown jewels", "update profile", "change preferences", or mentions organization configuration, setup wizard, or profile mana...
Revisa la ortografía española en archivos del proyecto (acentos, eñes, signos de interrogación). Usar cuando el usuario diga "revisa ortografía", "busca faltas", "corrige acentos" o invoque /revisar-ortografia.
Guía completa para crear fichas de productos duraderos y reparables en QueDure. Usar cuando el usuario diga "crear ficha de producto", "crear producto", "nuevo producto", "añadir producto", "ficha de..." o invo...
Guía para crear artículos educativos sobre consumo consciente, obsolescencia y derecho a reparar. Usar cuando el usuario diga "crear articulo", "nuevo articulo", "escribir sobre", "artículo de..." o invoque /cr...
Skills para gerenciar clientes, contatos e relacionamento. Inclui CRUD, filtros, analytics e operações em lote.
Skills para gerenciar clientes, contatos e relacionamento. Inclui CRUD, filtros, analytics e operações em lote.
Helper skill to create new agent skills following the standard structure. Use this when you want to define a new capability or workflow for the agent.
Habilidades para gerenciamento de projetos arquitetônicos. Permite criar, consultar, atualizar e analisar projetos no ArchFlow ERP.
Skills para rastreamento de atividades, time tracking e produtividade. Inclui criação de atividades, logs de tempo, relatórios e analytics.
Conjunto de skills para gerenciamento de projetos arquitetônicos. Inclui criação, atualização, filtragem e análise de projetos.
Detailed guidelines for the ArchFlow project's visual identity, including color palettes, typography, and component styling. Use this when implementing or updating UI components.
Use after completing planning phase (superpowers:writing-plans). Links implementation plan document to task. Simple task - just save the link, nothing else. Handles post-planning workflow for beads tasks.
Use after completing brainstorming/design phase. Links design document to task, parses subtasks, shows preview for approval, implements smart merge with existing subtasks. Handles post-design workflow for beads...
Use when starting a work session or when user asks to begin working on a beads task. Handles task selection, branch management, and context display. Use after /clear, at session start, or when switching tasks.
Use after completing and verifying a task. Checks git branch (feature → suggests finishing-a-development-branch), closes task, recursively checks parents with confirmation, runs bd sync. Handles task completion...
Stage, commit, and push changes to the current branch. Use when asked to commit changes, push code, or after completing a task.
Review and fix docstrings to follow Google-style conventions. Use when asked to check docstrings, format docstrings, or lint docstrings.
Create a pull request for the current branch using GitHub CLI. Use after committing changes when ready to open a PR.
Review code for regressions, duplications, and spec compliance. Use after completing significant implementations, or when asked to verify work. Can be invoked proactively after major changes.
Format all user-facing output with consistent visual structure. Apply when displaying questions, results, progress, errors, or any message to the user. Use dividers, emojis, and clear sections.
Guide feature-based directory structure and file placement. Apply when creating new files or organizing code. Enforce naming conventions and import ordering for backend and frontend files.
Enforce 500-line file size limits. Warn at 400 lines. Guide splitting large files into focused modules. Apply when writing or editing code.
Proactively remind about Gabe-OS workflows when context may have been lost, especially after /compact operations. Prevent manual implementation by checking for existing specs first.
Require comprehensive WHY/WHEN/HOW documentation for all functions. Apply when writing functions, classes, or complex logic to explain purpose, usage context, and implementation approach.
默认按已收录数据中的 GitHub 仓库 Stars 排序。Stars 属于来源仓库，同一仓库的多个技能可能共享相同数值；它反映仓库关注度，不代表单个技能的安装量或质量评分。