Loading...
Loading...
Found 113 Skills
Clarify the user’s intent for vague, incomplete, or ambiguous clauses, statements, and requirements before modifying the code.
Canonical Zener HDL semantics, package rules, manifests, and high-value stdlib APIs. Covers `Module()`, `io()`, `config()`, imports, `pcb.toml`, `pcb.sum`, stdlib interfaces and units, and package APIs.
Interactive guide for creating new skills (or updating existing skills) that extend Claude's capabilities. Walks the user through use case definition, frontmatter generation, instruction writing, and validation. Use when users want to create a new skill, build a skill, update an existing skill, or ask "help me make a skill for X". Always clarifies requirements before generating.
Mandatory only on the task-file path of `spec-loop-plan-task`. Use when an active task file already exists and the next user-facing action would otherwise present that task for evaluation, feedback, review, or implementation approval.
Manage tasks via dex CLI. Use when breaking down complex work, tracking implementation items, or persisting context across sessions.
This skill should be used when demonstrating skill structure and format. Provides example patterns for creating new skills.
Guide users through a structured workflow for co-authoring documentation, articles, or long-form content. Use when user wants to write documentation, proposals, articles, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting articles, or using "co-authoring" workflow.
tRPC router architecture, procedure design, and Vertical Slice Architecture patterns. Use when building tRPC APIs, designing procedures, or structuring backend slices.
Improve an existing skill in diegocanepa/agent-skills based on conversation learnings and submit the changes via a Pull Request.
Researches how the industry solves a defined issue, collects references from engineering blogs, open-source projects, and technical articles, then produces a design document with industry baseline, research summary, design goals, non-goals, and proposed design. Use when an issue definition exists in docs/issues/ and a concrete design is needed before implementation begins.
Execute approved implementation plans phase by phase with automated and manual verification. Use when the user explicitly says "implement the plan", "execute the plan", or "start implementing" and has a plan file ready. Do not use for ad-hoc coding tasks without a plan.
Add multiple functional specs to the ***functional specs*** section of a ***plain spec file in a single batch. Use whenever more than one new functional spec is being added — whether the user explicitly asks, or another skill/workflow (e.g. forge-plain, add-feature) needs to author several specs in one pass. Bulk-writing or hand-authoring functional specs without invoking this skill is forbidden; for adding a single spec, use add-functional-spec instead.