47 engineering skills for Claude Code across the SDLC — shared principles injected at session start. Works with Codex, Cursor, Cline & other markdown agents.
A guided conversation for turning a vague creative idea into a clear proposal. It asks one question at a time and checks what you want, who it is for, how success will be measured, and what limits apply.
A guide for deciding how an open-source project should grow and make money. Open source means the code is available for others to inspect, use, and often modify; open core keeps a free core while selling additional features or services.
A skill for writing a structured specification before building a new project, feature, or major change. A specification records the goal, structure, commands, coding and testing expectations, and boundaries.
A design-review skill for finding places where a codebase could be reorganised into modules with clear boundaries and useful interfaces. A codebase is the full collection of a project's source files and related code.
A guide to defining and testing the important concepts and relationships in a software project's subject area, then recording the agreed vocabulary and decisions.
A skill for generating design-reference images for brand identity, website sections, or mobile-app screens. It produces images only, not frontend code.
A guide for designing prompts and evaluations for features that use large language models. It treats the prompt, model choice, safety rules, and tests that measure quality as one engineering task.
Use when a design question is best answered by a throwaway prototype — a single shareable HTML file for state/logic, or several toggleable UI variations to compare. Triggers on "prototype", "throwaway", "mockup", "compare layouts", "validate the interaction", "sketch out", "try this quickly", "build a demo", "原型"…
A skill for turning an approved plan or specification into small, ordered work tickets. Each ticket describes a complete slice of work and what must be decided or finished first.
A method for giving a coding agent the most relevant project information at the right time. It organizes persistent rules, feature specifications, architecture notes, code conventions, and current task details.
A guide to preparing software for multiple languages and regional settings. This includes translated text, date and number formats, plural rules, and right-to-left layouts.
Use when implementing the work described by a spec or tickets — drives TDD within each slice, runs typechecks and tests regularly, and closes with code-review before committing. Also covers lightweight changes (small edits, mechanical renames, project scaffolding) that don't need a full spec. Triggers on "implement"…
Use when executing work through subagents — dispatching independent tasks to parallel isolated-context agents, or driving a plan as a sequence of implementer-subagents with review checkpoints. Scales beyond a single context window. Triggers on "parallel agents", "subagent execution", "dispatch tasks", "fan out", "并行…
A workflow for reducing cloud spending by measuring the current bill, finding its main cost driver and verifying changes. It treats spending as a metric alongside performance.
A workflow for making software run faster by measuring first, finding the actual bottleneck and then checking the result. It uses profiling and performance measurements rather than guesswork.
3 14d agoA60 tokens
originalMIT
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: