486건 · 관련도순
Create a single-column HTML email for a product launch, with a centered brand wordmark, hero image block, headline, copy, action button, specifications, and footer. Table-based layout and inline colors support compatibility with email clients.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Create a detailed specification for a dashboard, covering its purpose, panels, data sources, refresh schedules, and interactions. Use a reusable structure to document what each panel shows and how users and external systems interact with it.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Create dictionaries of keywords and identifying byte sequences for fuzzing, or testing with generated inputs. Extract useful entries from code, binaries, or specifications, then configure fuzzers to explore parsing paths beyond initial input validation.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Turn cryptographic code or specifications into sequence diagrams showing who sends each message, which cryptographic operations occur, and where failures stop the exchange. Outputs include Mermaid source, a plain text diagram, and a protocol summary.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Review smart contract projects against Trail of Bits development guidelines. Examines architecture, upgrade mechanisms, implementation, dependencies, and tests, then provides system documentation, identifies gaps, and recommends improvements in priority order with code references.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Extract structured product records from Amazon URLs across regional sites, including price, stock, specifications, rating breakdowns, sellers, and visible variants. Use the records for competitor research, catalog audits, or tracking product prices and availability.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Extract details from an open eBay listing into JSON, a structured data format. Collect prices, availability, sales counts, seller feedback, specifications, and image links for product comparisons and catalog checks across regional eBay sites.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Develop and fix Nexent features by connecting written specifications, acceptance criteria, implementation, and verification evidence. Plan unit tests and appropriate staged checks, maintain their links to requirements, and fill confirmed test gaps after development.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Learn the complete OpenSpec workflow through a small task in an actual codebase. The agent explains each stage while creating a proposal, specifications, design, and tasks, then implements the change and archives its records.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Archive an OpenSpec change after checking its documents, task completion, and specification differences. The skill offers a choice about updating the main specifications, then moves the change into a dated archive and reports the result.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
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 comprehensive Product Requirements Documents with user stories, acceptance criteria, technical specifications, wireframe descriptions, and prioritization frameworks (RICE, MoSCoW). Create clear specifications for product teams.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Write detailed feature specifications with functional requirements, edge cases, data models, API contracts, and UX flows. Create comprehensive technical specifications that enable clear implementation.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.