'specifications' 검색 결과

Develop behavior through one failing test and one minimal implementation at a time. Tests use agreed interfaces and expected results from specifications or documented examples, producing evidence of both failure and success, including for bug fixes.

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

• Adding behavior through small test-first steps
• Reproducing a bug before fixing it
• Checking results against specifications

Convert long Markdown specifications, reports, and plans into a single HTML document with a sticky table of contents, search, section tracking, and code-copy buttons. Apply previously configured brand colors and layout styles.

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

• Turn long specifications into navigable HTML documents
• Add search and a table of contents to reports
• Apply consistent brand styling to technical documents

Plan features before coding by defining requirements, acceptance criteria, and scope. Validate the specification, generate starter tests from expected behaviors, and guide implementation and review so each delivered feature can be checked against its agreed requirements.

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

• Define requirements before implementing a feature
• Turn acceptance criteria into starter tests
• Check specifications for missing requirements

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.

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

• Learning OpenSpec through a real code change
• Understanding proposals, specifications, designs, and tasks
• Practicing a complete change cycle with a small fix

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.

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

• Archive an implemented change
• Check unfinished documents and tasks before archiving
• Review specification differences before updating the main specifications

Write game interface specifications for individual screens, interaction flows, and the HUD, the information shown during play. Also document shared interaction patterns and project-wide accessibility requirements, with section depth guided by project settings.

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

• Writing specifications for game screens and navigation flows
• Designing the HUD information shown during play
• Documenting shared interaction patterns

Turn small game changes into concise specifications with clear reasons, rules, and acceptance criteria. Check existing design documents and earlier specifications, then document tuning adjustments, minor behavior changes, or small features before implementation.

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

• Documenting game balance adjustments
• Specifying minor behavior changes
• Defining a small mechanic for an existing system

Break a large game development feature into implementation tasks with clear acceptance criteria. Each task carries relevant requirements and design decisions, with test specifications added when the selected review mode includes a QA review.

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

• Break a game feature into implementation tasks
• Carry requirements and design decisions into task files
• Define acceptance criteria and test specifications

Turn json-render specifications into SolidJS interfaces. This skill guides component registration, connects inputs to application state, handles actions and validation, and helps troubleshoot how changing values update the screen, including streamed UI generation.

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

• Build SolidJS interfaces from JSON specifications
• Connect form inputs to application state
• Troubleshoot values that fail to update the screen

Add and troubleshoot the json-render inspection panel in SolidJS applications. This skill covers panel setup for examining specifications, editing state, reviewing action and stream timelines, browsing component catalogs, and selecting page elements for inspection.

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

• Add an inspection panel to a SolidJS app
• Inspect JSON specifications and edit application state
• Review action and stream timelines

Build multi-page Next.js applications from JSON specifications. This skill guides route setup, shared layouts, page metadata, and server-side rendering, which prepares pages on the server, with optional data loading before display.

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

• Build a multi-page app from JSON specifications
• Share navigation and layouts across pages
• Load server data before rendering a page

Build TanStack Start pages from JSON specifications. This skill connects URL routes, shared layouts, server-side data loading, page metadata such as titles, and client navigation, including loading, error, and missing-page displays.

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

• Build multiple pages from JSON specifications
• Share layouts across pages
• Connect dynamic URLs to page data loading

Build native mobile interfaces from JSON specifications with @json-render/react-native. Use standard or custom components, connect form inputs to application state, and update visible content in response to taps and other interactions.

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

• Building mobile screens from JSON specifications
• Connecting form inputs to application state
• Switching tab content in response to taps

Helps integrate YAML output into json-render, turning incoming text into incremental UI updates. Covers prompt generation, streaming parsing, and targeted edits to existing UI specifications through merge, patch, or diff formats.

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

• Render UI updates as YAML arrives
• Generate prompts for YAML output
• Apply partial edits to existing UI specifications

Build interactive terminal interfaces from JSON specifications with @json-render/ink. The skill covers standard and custom components, input handling, state connections, conditional display, and progressively rendering specifications generated by AI.

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

• Building a terminal dashboard from JSON
• Creating forms with input fields and selection menus
• Defining a catalog of custom terminal components

Design consistent API specifications with OpenAPI 3.0 and 3.1. Define requests, responses, authentication, and reusable data structures, then guide specification checks, documentation, and generation of client libraries or starter server code.

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

• Define an API contract before implementation
• Standardize authentication and error responses
• Check API specifications in CI

Design reusable Figma components, flexible layouts, and shared design systems. Get guidance on managing colors and spacing, supporting themes and screen sizes, and preparing clear specifications and assets for developers.

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

• Organizing reusable components and their variants
• Building layouts that adapt to different screen widths
• Managing shared colors, spacing, and light or dark themes

Review patent claims and specifications with an AI acting as a patent examiner. It identifies clarity, novelty, and disclosure issues, applies revisions, and conducts a second review, producing a report of changes and remaining concerns.

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

• Check claims and specifications before filing
• Find unclear terms and missing technical explanations
• Review novelty against known prior art

Build reusable Claude Skills from documentation, APIs, code, and specifications. Organize instructions and reference files, define clear activation conditions, add reproducible examples, and check new or existing skills against a delivery checklist.

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

• Creating a skill from documentation, code, or specifications
• Reorganizing an overly long SKILL.md
• Clarifying when a skill should activate

Carry out Docupost tasks through Rube MCP, an agent connection to external tools. Discover supported actions, check their required inputs and the service connection, then execute operations according to the specifications returned by tool search.

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

• Find supported Docupost actions and their inputs
• Check whether the Docupost connection is active
• Run a task using the discovered tool specifications

Read existing code to reconstruct system specifications, including architecture, data flows, APIs, and business rules. Produces documentation tied to code locations, separating observed behavior from inferences and questions that need clarification.

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

• Understand an undocumented legacy system
• Document existing APIs and business rules
• Map module dependencies and data flows

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.

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

• Defining requirements for a new feature
• Clarifying vague feature requests
• Writing testable acceptance criteria

Create and maintain code comments, API specifications, documentation sites, and user guides. Apply consistent formats, document parameters and errors, validate code examples, and report which parts of the code have been documented.

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

• Add explanations to public functions and classes
• Create API specifications and reference pages
• Build a documentation site

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.

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

• Model a distributed protocol before implementation
• Create a specification from existing concurrent code
• Investigate deadlocks and race conditions