'specification' 검색 결과

Comprehensive quality control for U.S. patent application filing documents. Use when the user asks to QC, check, validate, or review patent filing documents before submission to the USPTO. Performs 70+ automated and manual checks across specification, drawings, ADS, declaration, assignment, and power of attorney documents. Detects cross-document inconsistencies, formatting issues, missing required fields, and common errors.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Perform a dual-lens critical review of the specification and plan from both product strategy and engineering risk perspectives before implementation.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Create or update the feature specification from a natural language feature description.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Create or update the feature specification from a natural language feature description.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Adaption AI SDK for synthetic data augmentation and dataset adaptation. Use when building data pipelines with the Adaption Python SDK, uploading datasets (local files, Hugging Face, Kaggle), running augmentation/adaptation jobs, configuring brand controls (hallucination mitigation, safety categories, length), recipe specifications (reasoning traces, deduplication, preference pairs, prompt rephrase), evaluating dataset quality, downloading results, or any workflow involving `pip install adaption`, `from adaption import Adaption`, Adaptive Data, or the adaptionlabs.ai API. Also trigger when the user mentions synthetic data generation for fine-tuning, dataset augmentation pipelines, DPO preference pair generation, or grounding-based hallucination reduction on training data.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Check any artifact against an explicit specification and report adherence using the add-comments workspace format. Use when validating plans, scripts, docs, or code changes against a source-of-truth spec.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Generate sitemap and wireframe specifications from project-config.json and produce UX planning artifacts.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Prompt and workflow for generating conventional commit messages using a structured XML format. Guides users to create standardized, descriptive commit messages in line with the Conventional Commits specification, including instructions, examples, and validation. Use when writing commit messages for a repository that follows Conventional Commits.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Token architecture, component specifications, and slide generation. Three-layer tokens (primitive→semantic→component), CSS variables, spacing/typography scales, component specs, strategic slide creation. Use for design tokens, systematic design, brand-compliant presentations.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

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.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

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.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

AID Phase 2 - Technical Specification. Use for system architecture, API contracts, data models, security architecture, transitioning from PRD to 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.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

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.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Create or update the feature specification from a natural language feature description.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

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.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.