Loading...
Loading...
Found 9,865 Skills
Turn an idea into a well-structured Linear project ready for hands-off parallel execution. Conversational — asks clarifying questions before scaffolding. Outputs a Linear project, per-scope-item tickets, and `.handoffs/<slug>/tickets.yaml` — the machine contract /project-start consumes (with file surface and per-ticket dependencies). Reads `.claude/conventions.yaml` for Linear team / ticket-prefix conventions. Requires the `/grilling` and `/domain-modeling` skills (mattpocock/skills).
Generate a design document (design proposal) from a PRD, following the style of Go's official design proposals — structured with Abstract / Background / Design / Rationale / Compatibility / Implementation sections, with a strong focus on the 'why' behind decisions and tradeoffs. Trigger keywords: to-design, prd-to-design, PRD to design document, generate design document, write design document, design doc, design proposal, design proposal, technical design document.
Internal planning gate: consumes the normalized repository state and makes the ONE final architectural classification, using a two-stage contract that allows a lightweight NRS read during planning and a full architectural classification after the plan is cut. Used by plan-feature, plan-feature-from-issue, plan-feature-scaffold, and plan-fix. Not a menu entry.
Use when turning a requirement, spec, or feature brief into a single self-contained HTML design document in a fixed house style — one styled HTML page with a table-of-contents, architecture/sequence SVG diagrams, code/SQL/YAML blocks, callout boxes, an aligned-decisions (已对齐结论) panel, test cases, and a code index. Reuse for any new 需求/设计文档 that should look identical every time.
Illustrate an article (Markdown, HTML, etc.) with animated-style icons from itshover.com/icons. Fetches icons as clean inline SVG and places them at section headings, key concepts, lists, and callouts. Triggers on: /article-icons, 配图, 给文章配图标, add icons to article, illustrate with icons.
Simplify an already-bounded code or documentation area without changing intended behavior. Use for deletion, direct-flow refactors, wrapper or branch reduction, clearer data models, reduced mutable state, or concrete simplification findings; use improve-architecture when the opportunity or design is still unclear.
Internal contract: one compact frozen ACCEPTANCE.md per delivery unit, its validation ladder, anti-weakening rules, and blob-bound execution receipt. Consumed by planners, execute-phase, review-change, and loop-review-fold.
Internal step of plan-feature: turn a feature-request issue into a scoped, sized, roadmap-mapped SPEC **product half** (capability closure satisfied) with Closes #N traceability.
Review a change with only applicable internal axes, classify every finding, persist fix-now work, and return one evidence-backed decision. Findings only; --adversarial N uses isolated reviewers; --synthesize fuses supplied reviewer tables. Triggers: "review-change", "review this change", "adversarial review".
Internal scope/classification engine composed by review-change (and reused by the audit skills): consumes the synthesized findings table, verifies every applicable axis is represented, and classifies each finding into a decision table (fix-now / replan-in-unit / decision-required / proposal / ignore). Findings only — never refactors.
Reduce token waste by 40-60% through anti-sycophancy rules, tool-call budgets, one-pass coding, task profiles, and read-before-write enforcement. Inspired by drona23/claude-token-efficient.
Generate or optimize figure/table captions for academic papers. Geography-aware: study area, CRS notation, data source. Writes output to .tex file. 图表标题生成与优化。