'specifications' 검색 결과

Review specifications, plans, and tasks together before implementation. Identify missing task coverage, duplicate requirements, unclear wording, and conflicting decisions, then receive a prioritized report with recommendations without changing project files.

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

• Reviewing specifications and plans before implementation
• Finding requirements with no corresponding tasks
• Checking compliance with project principles

Review specification files to see the current phase, completion levels, and remaining tasks. Get a progress report that identifies next steps, blockers, dependencies, and related specifications that may need checking after changes.

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

• Check a specification’s progress and remaining tasks
• Identify next steps and blockers
• Review related work that may need checking after changes

Extract structured specifications from electronic component datasheet PDFs — pinouts, electrical characteristics, peripherals, topology, and features. Cache extractions per project for consumption by schematic and PCB analyzers. Primary consumer infrastructure for `kicad`, `emc`, `spice`, and `thermal` analyzers. Use this skill whenever the user asks to extract, verify, or read specs from a component datasheet; when analyzers need verified IC knowledge (EN pin thresholds, PG presence, USB peripheral speed); or when a review mentions datasheet coverage, extraction quality, or per-MPN specifications. Also triggers on "extract this datasheet", "what are the specs for MPN X", "verify datasheet extraction", or "check pin functions for part Y".

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

Extract structured specifications from electronic component datasheet PDFs — pinouts, electrical characteristics, peripherals, topology, and features. Cache extractions per project for consumption by schematic and PCB analyzers. Primary consumer infrastructure for `kicad`, `emc`, `spice`, and `thermal` analyzers. Use this skill whenever the user asks to extract, verify, or read specs from a component datasheet; when analyzers need verified IC knowledge (EN pin thresholds, PG presence, USB peripheral speed); or when a review mentions datasheet coverage, extraction quality, or per-MPN specifications. Also triggers on "extract this datasheet", "what are the specs for MPN X", "verify datasheet extraction", or "check pin functions for part Y".

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

Write detailed feature specifications with functional requirements, edge cases, data models, API contracts, and UX flows. Create comprehensive technical specifications that enable clear implementation.

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

Write comprehensive Product Requirements Documents with user stories, acceptance criteria, technical specifications, wireframe descriptions, and prioritization frameworks (RICE, MoSCoW). Create clear specifications for product teams.

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

Establish explicit traceability between formal specifications (preconditions, postconditions, invariants) and verified code components with their correctness proofs. Produce structured Markdown mapping reports showing verification coverage and proof evidence. Use when auditing formal verification, documenting verified systems, establishing traceability for certification, or when the user asks to map specifications to code, generate verification reports, or analyze verification coverage in Coq, Dafny, Isabelle, or other proof assistants.

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

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.

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

Automatically generate TLA+ specifications from source code (C/C++, Python) for formal verification of distributed systems. Use when users need to: (1) Generate TLA+ specs from program implementations, (2) Model distributed systems, consensus protocols, or concurrent algorithms, (3) Extract state variables, actions, and invariants from code, (4) Create formal specifications for model checking with TLC, (5) Verify safety and liveness properties of distributed systems. Particularly effective for message-passing systems, replication protocols, consensus algorithms, and distributed transactions.

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

Transforms natural language requirements (user stories, verbal descriptions, business rules) into formal specifications and constraints. Use when converting informal requirements into structured, testable specifications with explicit constraints. Outputs in multiple formats including BDD-style Given-When-Then, JSON Schema, and structured plain text requirements documents.

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

Iteratively enhance user requirements into clear, complete, actionable specifications through analysis and clarification. Use when: (1) Users provide initial requirements that need refinement, (2) Requirements are vague, incomplete, or ambiguous, (3) Creating formal specifications from informal descriptions, (4) Identifying missing constraints, edge cases, or acceptance criteria, (5) Clarifying assumptions and implicit dependencies, or (6) Preparing requirements for design, implementation, or verification. Operates interactively: analyze → ask clarifying questions → refine based on responses.

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

Converts pseudocode descriptions and algorithm specifications into complete, executable Java code. Use this skill when you need to implement algorithms from pseudocode, translate algorithm descriptions to Java, generate Java code from specifications, convert textbook algorithms to working code, or create executable implementations from high-level descriptions. Preserves logic and control flow while handling Java idioms, data structures, and includes test cases for verification.

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

Generate complete, production-ready functions and classes from formal specifications, design descriptions, type signatures, or natural language requirements. Use this skill when implementing APIs from specifications, creating data structures from schemas, building classes from UML diagrams, generating code from contracts, or translating design documents into code. Supports multiple programming languages and follows language-specific best practices.

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

Generate formal specifications (definitions, predicates, invariants, pre/post-conditions) in Isabelle/HOL or Coq from informal requirements, source code, pseudocode, or mathematical descriptions. Use when users need to: (1) Formalize algorithms or data structures, (2) Create function specifications with contracts, (3) Generate predicates and properties for verification, (4) Translate informal requirements into formal logic, (5) Specify invariants for loops or data structures, or (6) Create formal definitions for mathematical concepts. Supports both Isabelle/HOL and Coq equally.

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

Create ACSL (ANSI/ISO C Specification Language) formal annotations for C/C++ programs. Use this skill when working with formal verification, adding function contracts (requires/ensures), loop invariants, assertions, memory safety annotations, or any ACSL specifications. Supports Frama-C verification and generates comprehensive formal specifications for C/C++ code.

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

Detects and analyzes ambiguous language in software requirements and user stories. Use when reviewing requirements documents, user stories, specifications, or any software requirement text to identify vague quantifiers, unclear scope, undefined terms, missing edge cases, subjective language, and incomplete specifications. Provides detailed analysis with clarifying questions and suggested improvements.

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

Plan game UX, UI, and HUD design specifications. Use when the user says "lets create game UX", "design the HUD", "create UI specifications", or "help me plan the game UX"

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

Apply requirement quality principles when generating or validating feature specifications. Enforces feature completeness, scenario structure, AC verifiability, feature independence, and implementation slice quality. Use when writing feature specs, validating existing requirements, or when the user mentions 'validate this spec', 'check this feature', 'requirement quality', 'is this spec complete', or 'requirement-quality'. This skill governs the craft of writing individual feature specifications — not technical design (see design-blueprint), not implementation (see code-forge).

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

Retrieve Amazon product details by ASIN, including price, title, main image, listing date, material, weight, variant monthly sales, and up to 12 months of monthly sales history. Triggered when users query Amazon product details, ASIN lookup, product pricing, sales rank history, monthly sales trends, product dimensions, FBA fees, product specifications, batch ASIN query, Nexscope product details, ASIN detail lookup, monthly sales data, pricing info, product specifications, FBA fees, batch ASIN query. Even if users do not explicitly mention "Nexscope", this skill should be triggered whenever the task involves obtaining structured product data for one or more Amazon ASINs.

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

Plan UX patterns and design specifications. Use when the user says "lets create UX design" or "create UX specifications" or "help me plan the UX"

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

Technical writing, engineering specifications, reports, presentations, and documentation standards for engineering practice. Covers document types (requirements documents, test reports, design rationale, operations manuals), writing style, data visualization, engineering drawing standards, and oral presentation techniques. Use when writing engineering documents, presenting technical results, creating specifications, or learning documentation best practices.

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

Engineering design cycle covering requirements elicitation, specifications writing, constraint identification, iterative prototyping, and design communication. Spans the full loop from problem definition through ideation, analysis, prototyping, testing, and redesign. Includes morphological charts, TRIZ, Pugh matrices, design reviews, and the distinction between functional and non-functional requirements. Use when framing engineering problems, generating design alternatives, writing specifications, or running design reviews.

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

Advanced motion designer with decades of After Effects and motion graphics experience, specialized in creating engaging video specifications for Remotion. Use when creating video specs, planning motion graphics, designing animations, or when asked to "create a video", "design motion graphics", "plan video content", or "spec out a video". Produces detailed scene-by-scene specifications with timing, audio, sound effects, and animation descriptions.

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

Expert product specification and documentation writer. Use when creating PRDs, user stories, acceptance criteria, technical specifications, API documentation, edge case analysis, design handoff docs, feature flag plans, or success metrics. Covers the full spectrum from high-level requirements to implementation-ready specifications.

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