13.5K skills · sorted by relevance
Turn a feature idea into a specification through structured questions about users, business goals, and technical constraints. Produce requirements, user stories, testable acceptance criteria, and an implementation checklist, including performance, security, and error handling.
Prepare an AI-SPEC.md design agreement for an AI development phase. The skill coordinates framework selection, documentation and domain research, and evaluation planning so the phase has a defined technical direction and assessment strategy.
Model distributed systems and concurrent algorithms in TLA+ or PlusCal, then check possible states with TLC. Use the results to investigate deadlocks, broken rules, and differences between specifications and implementation code.
Turn rough feature ideas into a clear SPEC.md through focused questions. Define target users, business rules, current scope, and acceptance criteria based on observable results, giving developers or AI agents concrete requirements to implement.
Review feature plans before development from business strategy, user experience, and engineering perspectives. Receive scored assessments, specific gaps tied to requirements, and prioritized actions that clarify what must change before the team starts building.
Turn Notion product requirements and feature specifications into linked implementation plans and manageable tasks. Extract requirements, flag ambiguities, and keep task status, milestones, blockers, and decisions aligned as work progresses.
Design specialized assistants that work with their own separate context. Define responsibilities, delegation conditions, working steps, and report formats for reusable subagents handling verification, debugging, security audits, or code reviews.
Review changes from a chosen Git reference against both project coding standards and issue or specification requirements. Separate parallel reviews report rule violations, possible design problems, missing requirements, and changes beyond the intended scope.
Review whether a proposal, specification, or design decision addresses the right problem and follows from its goals and constraints. Receive prioritized findings with supporting evidence, confidence, and concrete alternatives or questions that would resolve each concern.
Run a build-and-evaluation pipeline from a natural-language specification. Generate scenarios, implement the project, test scenarios withheld during implementation, and report scores against a target with failures and suggested next steps.
Build a planned feature by following an existing task list and technical plan. The skill respects task dependencies, runs tests before related implementation where applicable, records progress, and checks the completed work against the specification.
Process mass spectrometry data in Python with PyOpenMS. Read common file formats, smooth and normalize signals, detect peaks, align samples, and process peptide identification results for protein and metabolite quantification workflows.
Clarify a development request through structured questions and choose a practical next step: update an existing specification, create new ones, or implement directly. For new specifications, record scope, approach, and dependencies in planning files.
Coordinate defect image generation, augmentation, and labeling for circuit board, metal surface, and glass inspection on OSMO. Select workflows that create initial board datasets from CAD scenes, process real images, or fine-tune NVIDIA Cosmos AnomalyGen models.
Sync delta specs from a change to main specs. Use when the user wants to update main specs with changes from a delta spec, without archiving the change.
The English summary is being prepared. Showing the original description.
Writes Specific Aims pages for grant applications. Use when drafting or revising the Specific Aims page (NIH R01/R21/R03), NSF Project Summary, or equivalent for any major funding agency. Also triggers on "write my specific aims", "help me draft specific aims for NIH", "what should a specific aims page include", "NSF project summary", "write my grant aims", or "how do I structure an R01".
The English summary is being prepared. Showing the original description.
Continue a multi-phase engineering spec from its progress table. Use when the user says /continue-spec, "continue the spec", "continue the operations feature", or asks what the next phase is. Runs the next step (plan, implement, review) in this session on the model the spec names, stopping at the spec's gates. Never uses subagents.
The English summary is being prepared. Showing the original description.
Read-only drift detector. Diffs SPEC.md against current code and reports violations grouped by severity. Writes nothing — suggests remedies via the spec or build skills but never invokes them. Triggers when the user asks to check drift, audit the spec, verify invariants, or ask whether code still matches the spec. Phrasings: "check drift", "audit the spec", "does the code still match §V", "check invariants", "spec vs code".
The English summary is being prepared. Showing the original description.
A first step in the data analysis of Mass Spectrometry (MS) based proteomics data is to identify peptides and proteins. With this respect the huge number of experimental mass spectra typically have to be assigned to theoretical peptides derived from a sequence database. Search engines are used for this purpose. These tools compare each of the observed spectra to all candidate theoretical spectra derived from the sequence data base and calculate a score for each comparison. The observed spectrum
The English summary is being prepared. Showing the original description.
This skill should be used when the user asks to "build a feature", "create a spec", "start spec-driven development", "run research phase", "generate requirements", "create design", "plan tasks", "implement spec", "check spec status", "triage a feature", "create an epic", "decompose a large feature", or needs guidance on spec-driven development workflow, phase ordering, or epic orchestration.
The English summary is being prepared. Showing the original description.
Use when creating or updating OpenSpec artifacts from an issue, plan, approved design, ADRs, existing OpenSpec, or a valid combination. The workflow assesses reviewable scope, records source authority and derivation, handles conflicts, and prevents silent synchronization. Triggers include Create OpenSpec from an issue; Convert a plan into OpenSpec; Update an OpenSpec change; Split broad requirements into reviewable changes. Part of Plinth Toolkit
The English summary is being prepared. Showing the original description.
Sync delta specs from a change to main specs. Use when the user wants to update main specs with changes from a delta spec, without archiving the change.
The English summary is being prepared. Showing the original description.
Guides preparation for supervisory authority (DPA) inspections and investigations including document readiness checklists, interview preparation for key personnel, technical demonstration procedures, on-site logistics, response protocols, and post-inspection follow-up. Covers unannounced inspections, formal audits, and complaint-triggered investigations. Keywords: DPA inspection, supervisory authority, investigation, readiness, interview preparation, response protocol.
The English summary is being prepared. Showing the original description.
Generate implementation code and tests from written specifications. Use when the user provides specifications (natural language descriptions, formal specs, requirements documents, API specs) and asks Claude to implement the described functionality. Supports data structures, algorithms, classes, functions, and includes automatic test generation to validate implementation against specification.
The English summary is being prepared. Showing the original description.