956 个 · 按相关度排序
Generates a complete, working application from an OpenAPI specification using the active framework's conventions: models, routes, validation, and tests. Use when scaffolding a service from an existing OpenAPI/Swagger spec rather than hand-writing endpoints.
中文简介正在准备中。当前显示原文说明。
SOP for formal mathematical domain modeling. Trigger when: - Creating new formal models or applying mathematical lenses to analyze existing specifications. - Navigating phases: Identify, Select, Construct, Validate, Record, Connect. - Prompt contains: /form, form workflow, categorical, coalgebraic, linear logic, information-theoretic, validation.
中文简介正在准备中。当前显示原文说明。
SOP for normative specification and behavioral contracts. Trigger when: - Defining invariants, permitted transitions, and forbidden states. - Navigating steps: Identify, Formalize, Verify, Record, Connect. - Prompt contains: /spec, spec workflow, normative constraint, invariant, BCP 14.
中文简介正在准备中。当前显示原文说明。
Mathematical foundations, logical structures, and formal verification guidance. Trigger when: - Designing protocol contracts, formal specifications, verifying state spaces, or using proof assistants. - Tasks involve: TLA+, Alloy, Lean, Coq, model checkers, invariants, temporal logic. - Prompt contains keywords: formal verification, alloy, tla+, lean, coq, invariant, state machine, model checker, liveness, safety.
中文简介正在准备中。当前显示原文说明。
AID Phase 2 - Technical Specification. Use for system architecture, API contracts, data models, security architecture, transitioning from PRD to implementation.
中文简介正在准备中。当前显示原文说明。
Senior System Architect for SaaS specifications. Security-first design with ISO 27001 compliance. Use for system architecture, tech specs, API design, technology choices, distributed systems, cloud infrastructure.
中文简介正在准备中。当前显示原文说明。
Cucumber BDD integration for AID methodology. Gherkin-first acceptance criteria with executable specifications. Use for writing feature files, step definitions, and running acceptance tests.
中文简介正在准备中。当前显示原文说明。
Create detailed specifications by iteratively clarifying unclear points for Plan mode. Use when: After completing a plan when detailed requirements need clarification before implementation.
中文简介正在准备中。当前显示原文说明。
Master REST and GraphQL API design principles to build intuitive, scalable, and maintainable APIs that delight developers. Use when designing new APIs, reviewing API specifications, or establishing API design standards.
中文简介正在准备中。当前显示原文说明。
Runs a bounded spec-build-review development loop with explicit scope, stop conditions, and human approval gates for risky or ambiguous work.
中文简介正在准备中。当前显示原文说明。
Discover and inventory shadow API endpoints that operate outside documented specifications using traffic analysis, code scanning, and API discovery platforms.
中文简介正在准备中。当前显示原文说明。
Deploy a Software-Defined Perimeter using the CSA v2.0 specification with Single Packet Authorization, mutual TLS, and SDP controller/gateway configuration to enforce zero trust network access.
中文简介正在准备中。当前显示原文说明。
Create or update feature specifications from natural language descriptions. Use when starting new features or refining requirements. Generates spec.md with user stories, functional requirements, and acceptance criteria following spec-driven development methodology.
中文简介正在准备中。当前显示原文说明。
Create or update the feature specification from a natural language feature description.
中文简介正在准备中。当前显示原文说明。
Generate technical implementation plans from feature specifications. Use after creating a spec to define architecture, tech stack, and implementation phases. Creates plan.md with detailed technical design.
中文简介正在准备中。当前显示原文说明。
Formally verify programs by writing Lean 4 proofs. Trigger this skill whenever the user wants to formally verify code, generate Lean 4 proofs, prove properties about algorithms or smart contracts, verify invariants, convert program logic into formal specifications, or anything involving Lean 4 and formal verification. Also trigger when the user mentions "qedgen", "lean proof", "formal proof", "verify my code", "prove correctness", "formal verification", or wants mathematical guarantees about their implementation.
中文简介正在准备中。当前显示原文说明。
Drafts a nonconformance report from inspection notes, test results and the governing specification or procedure: what was observed, where, the evidence with references, the requirement cited quoted verbatim with the departure from it, and containment proposals for the quality lead to decide. Never classifies severity, dispositions the item, names a root cause or closes the report. Use when the user asks to "write up this nonconformance", "draft an NCR from my inspection notes", "formalise this deviation" or "turn this snag into a defect report". Do not use for tracking the actions an NCR raises, use corrective-action-tracker instead. Drafts for human review; never approves, authorises or signs off.
中文简介正在准备中。当前显示原文说明。
Proposes the piping content a P&ID adds to an accepted PFD process model: line inventory with off-page continuity and required ancillary lines, line identification elements per the project line numbering procedure, connection items at nozzles matched to a quoted schedule, per quoted standards, specification break questions and observations. Every proposal cites its source and revision; no source, no proposal; never sizes a line or selects a class. Use when the user asks to "run the piping enrichment", "start the discipline enrichment", "list the lines the P&ID adds to this PFD" or "fill the line identifiers from the numbering procedure" after gate G2. Do not use for instruments, loops or instrument tags, use instrumentation-and-control-enrichment instead; do not use before gate G2, use process-model-check. Drafts for human review; never approves, authorises or signs off.
中文简介正在准备中。当前显示原文说明。
Design new Claude skills from structured idea specifications. Use when the skill auto-generation pipeline needs to produce a Claude CLI prompt that creates a complete skill directory (SKILL.md, references, scripts, tests) following repository conventions.
中文简介正在准备中。当前显示原文说明。
Translate a fuzzy analytical question into a rigorous investigation plan. Interrogates the ask, grounds the plan in the available data dictionary, applies analytical best practices, and produces a structured brief of query specifications for a downstream query-writing skill. Plans, does not write SQL. Use when: "why did X drop", "is there a relationship between A and B", "who are our highest-value customers", "what's driving the change in Y", "investigate this trend", "design an analysis for", "scope this analytical question". (narrative-common)
中文简介正在准备中。当前显示原文说明。
Reconstructed reference notes on US NRC software assurance guidance for digital computer software in nuclear power plant safety systems, built from seven public-domain sources (Regulatory Guide 1.168 Revision 2, July 2013; Regulatory Guides 1.169, 1.170, 1.171, 1.172, and 1.173 Revision 1, July 2013; NUREG-0800 Branch Technical Position 7-14 Revision 6, August 2016; pinned 2026-10-12). Use for software life cycle process questions, software requirements specifications, software configuration management plans, verification and validation with reviews and audits, test documentation and unit testing, and what NRC staff examine in a BTP 7-14 software review of plans, implementation, and design outputs. SCOPE LIMITS: NRC Regulatory Guides and the BTP 7-14 staff review position only; the endorsed IEEE standards (IEEE Std 603-1991, 7-4.3.2-2003, 828-2005, 829-2008, 830-1998, 1008-1987, 1012-2004, 1028-2008, 1074-2006), IEC 60880, IEC 61513, IEC 62138, and IAEA guides are cited by designation and edition only, with no standard text; RG 1.152 Rev 4, BTP 7-18, BTP 7-19, other SRP Chapter 7 sections, and NUREG/CR contractor reports are outside the pack; reflects the pinned 2013 and 2016 editions, not later agency actions; synthesized reference notes, not legal or licensing advice and not a substitute for the source documents. LICENCE: Public Domain (US Government work, 17 U.S.C. § 105).
中文简介正在准备中。当前显示原文说明。
Load for EF Core entities/configurations, semantic value persistence, portable constraints, DbContext/query filters, repositories/specifications, migrations, model snapshots, transactions, or seeded lookup tables; use query-optimization specifically for N+1 or slow SQL diagnosis.
中文简介正在准备中。当前显示原文说明。
Load for native CQS commands, queries, immutable request/result contracts, handlers (ICommandHandler, IQueryHandler), validators, cache invalidation, idempotency, or specification-driven reads in Explore.Application; not for controller-only or repository-only edits.
中文简介正在准备中。当前显示原文说明。
Crystallize shared understanding into a reviewable spec, or update an existing one. Use when the problem needs a written specification, when assumptions or decisions have changed, or when the user says 'write a spec'.
中文简介正在准备中。当前显示原文说明。