'specs' 검색 결과

Git-native issue tracking (beads), coding guidelines, knowledge injection, and spec-driven planning for AI agents. Drop-in replacement for bd/Beads with simpler architecture. Use for: tracking issues/beads with dependencies, creating bugs/features/tasks, planning specs, implementing features from specs, code reviews, committing code, creating PRs, loading coding guidelines (TypeScript, Python, TDD, golden testing, Convex, monorepo patterns), code cleanup, research briefs, architecture docs, agent handoffs, and checking out third-party library source code. Invoke when user mentions: tbd, beads, bd, shortcuts, issues, bugs, tasks, features, epics, todo, tracking, specs, planning, implementation, validation, guidelines, templates, commit, PR, pull request, code review, testing, TDD, test-driven, golden testing, snapshot testing, TypeScript, Python, Convex, monorepo, cleanup, dead code, refactor, handoff, research, architecture, labels, search, checkout library, source code review, or any workflow shortcut.

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

Write a comprehensive product or engineering specification before implementation. Use when the user asks for `/spec`, PRDs, feature specs, API specs, refactor specs, acceptance criteria, user stories, edge cases, or open decision tracking before code is written.

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

Tend the Allium garden. Use when the user wants to write, edit, update, add to, improve, clarify, refine, restructure, fix or migrate Allium specs. Covers adding entities, rules, triggers, surfaces and contracts, fixing syntax or validation errors, renaming or refactoring within specs, migrating specs to a new language version, and translating requirements into well-formed specifications. Pushes back on vague requirements.

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

Weed the Allium garden. Find where Allium specifications and implementation code have diverged, and help resolve the divergences. Use when the user wants to check spec-code alignment, compare specs against implementation, audit for spec drift or violations, sync specs with code or code with specs, or verify whether the implementation matches what the spec says.

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

Design and write QA test artifacts - test cases, test plans, acceptance criteria, API test specs, and PR testability reviews. Use this skill whenever a QA engineer or SDET needs to translate requirements, user stories, or feature specs into structured test documentation. Trigger on phrases like "write test cases", "create a test plan", "define acceptance criteria", "review this PR for testability", "write API test specs", "test coverage for this feature", "what should we test", "how do we test this", or any request to structure what and how to test before execution begins. Also trigger when a developer asks "is this testable?" or a PM asks "what are the edge cases?".

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

Use when orchestrating Loop Factory specs from factory/specs/inbox or factory/specs/active, dispatching work, generating implementation prompts, or deciding next loop state.

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

Use when orchestrating Loop Factory specs from factory/specs/inbox or factory/specs/active, dispatching work to Codex or Claude agents, generating implementation prompts, or deciding next loop state.

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

Use when auditing a repository for evidence-backed gaps between code, SPECs, architecture, and documentation — before a release, after a review, or when the user asks what is missing or divergent. Confirmed gaps become Draft SPECs via write-specs, a tracked GitHub Epic via create-issues, and orchestrated execution via orchestrator, with an explicit approval gate before any external action.

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

テスト仕様生成エージェント - AIエージェントがテストコードを実装可能なBDDシナリオ・ユニットテスト・統合テスト仕様を生成。Gherkin形式のシナリオとJUnit/Jest形式のテストケースを策定。/generate-test-specs [対象パス] で呼び出し。

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

제안서와 명세서를 배경 정리부터 절별 작성, 독자 검증까지 대화로 완성합니다. 작성 대화를 모르는 별도의 Claude로 설명 부족과 모호한 부분을 확인합니다.

• 흩어진 배경 메모로 제안서 작성
• 명세서와 의사 결정 기록 작성
• 절별 구성과 문장 다듬기

Convert a Notion specification into a linked implementation plan and manageable tasks. Extract requirements and acceptance criteria, record uncertainties, and keep task statuses, checklists, blockers, and milestone updates aligned as the work progresses.

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

• Turn a Notion feature specification into a plan
• Break implementation work into one- or two-day tasks
• Link specifications, plans, and task pages

Share Markdown specs, plans, and drafts through Proof, a collaborative document editor. Read shared documents, add comments or tracked suggestions, edit text, and pull documents into local files, with confirmation of each requested operation.

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

• Sharing a Markdown plan through a Proof link
• Commenting on a shared specification
• Suggesting or applying changes to a draft

Review changed test specifications for cases where broken behavior could still pass. Report concrete gaps supported by the changes and implementation, with a minimal fix and an observable condition for resolving each advisory finding.

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

• Reviewing whether changed tests prove their stated behavior
• Finding UI tests that bypass the interaction being tested
• Checking whether save tests observe newly saved data

Expose REST APIs as tools for AI agents through Google Cloud API Gateway using MCP, a protocol for connecting agents to tools. Covers OpenAPI migration, authentication, client connections, validation, and troubleshooting.

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

• Expose existing REST APIs as agent tools
• Migrate OpenAPI 2.0 specifications for MCP
• Protect tool listings with JWTs or API keys

Helps build custom code exporters from json-render UI specifications. Covers walking the UI tree, collecting components, state references, and actions, and formatting property values for JSX, the markup syntax used in React.

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

• Build a custom exporter for Next.js or Remix
• List components and actions used in a UI specification
• Convert property values into JSX attributes

Turn JSON layout definitions into SVG or PNG images with Satori. Use this skill to create social sharing previews and cards, assemble standard layout and text components, or define custom components for image specifications.

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

• Creating social sharing preview images from JSON
• Building social cards with standard components
• Rendering AI-generated JSON image definitions

Turn JSON specifications into React interfaces using a catalog of available components. This skill helps connect component implementations, shared data, form inputs, conditional display, and user actions to render interactive screens, including AI-generated designs.

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

• Render AI-generated JSON as a React interface
• Define a catalog of reusable UI components
• Connect form inputs to shared data

Generate PDF documents from JSON definitions with headings, tables, images, and page numbers. Use file, in-memory, or streaming output, and extend document layouts with custom components and externally managed application state.

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

• Generate invoice PDFs from JSON definitions
• Build documents containing tables and images
• Stream generated PDFs through an HTTP response

Build Vue 3 interfaces from JSON specifications, including AI-generated layouts. The skill covers component registration, named content areas, synchronized form values, conditional visibility, validation, actions, and connections to external state management.

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

• Display AI-generated JSON interfaces in Vue 3
• Build forms with synchronized values and validation
• Switch visible content based on application state

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 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

Turn JSON screen descriptions into Svelte 5 interfaces. This skill covers component catalogs, registration, shared state, form bindings that keep inputs and data synchronized, conditional display, and streaming AI-generated interfaces as they arrive.

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

• Render a Svelte interface from JSON
• Define and register reusable screen components
• Synchronize form inputs with shared state

Create HTML or plain-text emails from JSON specifications with React Email. This skill guides reusable email components, conditional content, server-side rendering, and browser previews for transactional messages such as signup notifications and marketing emails.

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

• Create signup notifications and other transactional emails
• Build marketing emails from JSON specifications
• Vary email content using state and conditions

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