'specifications' 검색 결과

업무와 일상의 반복 작업을 질문으로 구체화하고 시작 조건, 사람의 확인, 판단용 요약을 정리해 구현 담당자가 추가 질문 없이 만들 수 있는 워크플로 명세로 작성합니다.

• 위임할 수 있는 반복 작업 찾기
• 워크플로 시작 조건 정리
• 사람이 확인할 시점 결정

Co-write proposals, specifications, and decision documents through a guided process. Gather background, draft and refine each section, then test the document with a fresh Claude conversation to find unclear explanations and missing context.

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

• Turning scattered background notes into a proposal
• Drafting specifications or decision documents
• Refining structure and wording section by section

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

Turn specifications into pseudocode, a language-independent outline of program logic. Define data structures, handle edge cases, analyze time and memory requirements, and document design patterns and optimization opportunities before implementation.

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

• Turning specifications into clear processing steps
• Comparing data structures and computational costs
• Planning error handling and edge cases before coding

Turn specifications and designs into working code using test-driven development: write failing tests, implement enough code to pass, then refactor. The workflow also covers error handling, performance improvements, documentation, and coordinated changes across components.

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

• Implementing a feature from specifications and designs
• Developing authentication or APIs with tests
• Refactoring code while checking test results

Turn specifications and algorithm outlines into a system architecture. Define components, interfaces, data structures, and deployment plans, then document technology choices, security measures, failure handling, and plans for supporting increased usage.

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

• Turn specifications into a system design
• Define component responsibilities and API interfaces
• Plan for increased traffic and component failures

Compare an implementation with its OpenSpec specifications, tasks, and design decisions before archiving the change. Get a report on completion, requirement coverage, and consistency, with prioritized issues, actionable recommendations, and explicit limits where evidence is missing.

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

• Check for unfinished tasks before archiving a change
• Find gaps between specifications and implementation
• Review scenario tests and adherence to design decisions

Update main OpenSpec specifications from a change's delta specs, which describe specification changes. The skill merges requirement additions, edits, removals, and renames while preserving unrelated content, validates the results, and leaves the change active.

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

• Update specifications while keeping a change active
• Merge new scenarios into existing requirements
• Sync only selected specification files

Plan the visual and narrative direction of HyperFrames videos, including colors, fonts, composition, narration, and scene rhythm. The skill helps apply existing design specifications, choose a style, and check whether the finished work follows that direction.

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

• Match a video's appearance to existing design specifications
• Choose colors and fonts to suit a mood
• Plan scene rhythm and narration pacing

Create HeyGen avatar videos with a chosen presenter, voice, exact script, and backgrounds for each scene. Use photos as presenters, generate transparent WebM files for compositing, or produce batches of videos with consistent specifications.

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

• Have a chosen avatar read an exact script
• Create multiple scenes with different backgrounds
• Generate transparent WebM files for compositing

Turn a math or science video idea into a detailed scene plan. Research the topic, clarify the audience, and outline visuals, narration, transitions, and implementation notes for Manim, an animation tool.

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

• Turn a rough explainer idea into a scene plan
• Plan intuitive math and science visuals
• Adapt video depth to the audience

Consult Sally, a UX and UI specialist, to translate user needs into interaction designs and UX specifications. The role considers unusual situations as well as everyday use, helping communicate clear design intent to architecture and implementation work.

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

• Discuss interaction flows based on user needs
• Clarify UX specifications for implementation
• Consider unusual situations in interface design

Record durable Cherry Studio engineering decisions in Agent Notes. Determine which changes need a note, prepare specifications with verifiable acceptance criteria, and manage approval, implementation, rejection, and replacement while preserving the reasoning behind decisions.

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

• Deciding whether a change needs a lasting decision record
• Documenting bug fixes with significant tradeoffs
• Preparing specifications for approval before implementation

Assess Airflow Improvement Proposals by comparing Confluence specifications with pull requests, commits, and codebase files. Produce evidence-backed progress reports showing delivered items, remaining work, and specification updates needed across one or more proposals.

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

• Check implementation progress for an Airflow proposal
• Compare specification deliverables with shipped code
• Compile a progress report across multiple proposals

Generate API documentation from source code, including OpenAPI/Swagger specifications. Describe endpoints, the addresses used to access API operations, with parameters, responses, errors, authentication guidance, and examples in cURL, JavaScript, and Python.

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

• Creating API documentation from source code
• Preparing OpenAPI/Swagger specifications
• Documenting parameters, responses, and errors

Create or update API documentation from source code. The skill produces OpenAPI/Swagger specifications, descriptions of API operations, parameter and response references, authentication guidance, and practical examples for developers integrating an API.

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

• Creating API documentation from source code
• Generating OpenAPI/Swagger specifications
• Preparing API request and response examples

Design and review REST and GraphQL APIs with consistent naming, data structures, error responses, pagination for large result sets, and versioning strategies. Helps teams define shared standards and plan changes that existing clients can adopt gradually.

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

• Designing a new REST or GraphQL API
• Reviewing API specifications before implementation
• Establishing shared API design standards

Organize features, bug fixes, and refactors as Conductor tracks, units of related work. Create specifications and task plans, maintain status and dependency records, and preserve completed work with verification details and commit references.

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

• Creating a work unit for a feature or bug fix
• Writing and reviewing specifications and task plans
• Recording task status, dependencies, and commits

Research products against a budget and required features, then compare prices, specifications, and review findings in a table. Get one recommendation with its tradeoff, plus a price history check for deals when available.

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

• Build a product shortlist within a budget
• Compare prices, specifications, and reviews
• Check whether a discount is a good deal

Compare project documentation with existing code to identify missing core features. Rank the gaps and create GitHub issues with practical specifications, implementation plans, acceptance criteria, effort estimates, and dependencies.

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

• Find documented features missing from the implementation
• Prioritize gaps in core product functionality
• Turn feature gaps into actionable GitHub issues

Create structured Markdown specifications that AI agents can read and use. Organize requirements, constraints, interfaces, acceptance criteria, and testing plans into a self-contained document with clear definitions and examples.

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

• Writing specifications for AI-assisted implementation
• Defining requirements and acceptance criteria
• Documenting APIs and data contracts

Build an llms.txt file, a navigation guide for AI models, from a repository's structure. Summarize the project and organize links to essential documentation, specifications, examples, and configuration resources.

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

• Creating an AI-readable guide to a repository
• Organizing links to documentation and specifications
• Prioritizing essential project information

Write or revise instructions, specifications, tickets, and skill files so an agent can act without prior chat history. Make rules checkable, explain their reasons, define completion criteria, and keep authoritative information in one place.

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

• Clarifying instructions in CLAUDE.md
• Making specifications and tickets actionable
• Adding completion criteria to skill procedures

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