'build' 검색 결과

Critical-path smoke gate before QA hand-off — runs the automated suite. A failed check means the build is not QA-ready.

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

Pre-release checklist — build verification, certification requirements, store metadata, launch readiness.

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

Concept prototype before PRDs — throwaway HTML, Engine or Paper build, PROCEED/PIVOT/KILL/NOT ASSESSED. After /saas-brainstorm and /saas-setup-stack.

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

Implements one story in code with tests, following its ADRs. Use when the user says to build, implement or start working on a story. Not for checking readiness beforehand or closing the story after.

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

Breaks one epic into implementable stories with acceptance criteria. Use when the user wants stories for an epic or the next batch of work to build. Not for turning the whole design into epics.

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

Builds a short list of must-do and never-do coding rules per system from accepted ADRs. Use when the user wants programmer rules or a quick reference sheet from the ADRs, or needs it regenerated after ADR changes.

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

Propose a new change with all artifacts generated in one step. Use when the user wants to quickly describe what they want to build and get a complete proposal with design, specs, and tasks ready for implementation.

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

Writes, fixes and red-teams prompts — system prompts, templates, meta-prompts, agent or bot instructions — as copy-paste-ready artifacts, and picks the model tier for a prompt, task or plan's subtasks. Trigger to write, improve, debug or rewrite a prompt; which model should run this; a prompt that costs too many tokens, to cut with behavior held; or say promptwright (model, optimize — tune against test cases, slim, refresh). Not for a fan-out's units (dispatchwright), installed local models (lmstudiorunner), skills or their slim (skillwright), sourced comparisons (researchscribe), handoffs (handoffwright) or a pre-build interview (grillwright).

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

Finds what changed in Claude — docs, release notes, changelogs, GitHub and community posts on Claude Code, claude.ai, Cowork, the API and models — and turns each change into adopt rows for your setup, plus a fit card for a new model or feature and a monthly bench of your skills against public skill and plugin repos (build, adopt or skip). Trigger on what changed since a date or version, a weekly sweep, features worth adopting, a feature that broke unannounced, a stale model table, what a new model or feature is good for, or how your skills compare with popular or little-known skill and plugin repos; or say scoutwright (sweep, since, watch, adopt, fit, bench, sources, refresh). Outside research is researchscribe's; applying a row, skillwright's; config, rigwright's; schedules, agentwright's; tier picks, promptwright's.

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

Runs a session's fan-out — splits a large request into tiered, recoverable units, dispatches and reconciles them against the repo. Trigger when work needs many agents or spans many repos or files (rebuild, re-architect, sweep, migrate, 'do all of this'); when subagents would launch with no model or effort set; for the plan table (units, models, tokens, meters) before launch; to resume a unit that died or hit a usage limit; when units would share a repo; or say dispatchwright (plan, dispatch, resume, audit, refresh). Tiers come from its own table (scoutwright flags it stale); pacing, pacewright's; hooks, rigwright's; schedules, agentwright's.

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

Keeps a fiction story bible and checks text against it. Trigger to build, extend or extract (from a manuscript) a story, lore or world bible; to check chapters, game strings or generated drafts for contradictions or timeline breaks; to track a world timeline with branches and who is alive, or chart it; to brief a local model from canon; for naming rules; to share canon across repos; or say lorescribe (bible, manuscript, check, timeline, names, brief, audit). Research is researchscribe's; line edits commscribe's; real-data charts dataviz's; art pixelsmith's; audio soundsmith's; model runs lmstudiorunner's or comfyrunner's; no prose drafting.

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

Answers plain-word questions from a repo's CSV, JSON, Parquet and YAML files, or a .duckdb file, with DuckDB, and shows the SQL it ran. Read-only. Trigger to query, count, join, filter or summarise data files, including analytics CSVs exported from a video platform; to build a Parquet or DuckDB cache; to check no .duckdb, .wal or .parquet cache is committed or stale; when a query hits a locked database file; or say duckrunner (ask, cache, check, refresh). Needs the user-installed duckdb Python package; never a database server. DuckDB docs, S3 and MotherDuck are the duckdb-skills plugin's; outside research researchscribe's.

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

Runs Docker Desktop and its WSL2 layer, checking RAM and disk before container work. Trigger when Docker Desktop or a container won't start, vmmem eats RAM or the Docker disk keeps growing; to set a WSL memory cap in .wslconfig; to list or install WSL distros; to bring a compose stack up or down; to prune images and build cache; to run a command in a container; to log in to a registry; or say dockerrunner (audit, check, up, down, prune, status, refresh). Local LLMs (Docker Model Runner too) are lmstudiorunner's; images comfyrunner's; VMs and sandboxes hypervrunner's; Docker's MCP catalog its MCP Toolkit's; registry tokens keywarden's.

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

Proves a Godot 4.x build is actually green and holds its project conventions. Trigger when a GUT or GDScript result needs believing (a suite green while a script failed to parse, a one-file run that ran the whole suite, drifted CI guard counts, a coverage claim, a gate figure, a failing check someone wants softened); to review scenes, signals, awaits, threads, determinism, saves, imports or .uid files, or the upgrade rule (not the migration); to prove a simulation or balance rule; for import settings and the pixel-art render precondition; or say godotsmith (check, guard, gate, review, intake). API reference is the Godot docs'; art reads pixelsmith's; audio direction soundsmith's.

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

Publish the current Convex app to a live *.convex.app URL (deploy backend + upload web build).

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

Create distinctive, production-grade frontend interfaces with high design quality. Generates creative, polished code that avoids generic AI aesthetics. Use when the user asks to build web components, pages, artifacts, posters, or applications, or when any design skill requires project context.

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

Extract and consolidate reusable components, design tokens, and patterns into your design system. Identifies opportunities for systematic reuse and enriches your component library. Use when the user asks to create components, refactor repeated UI patterns, build a design system, or extract tokens.

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

Check the current app's pinned Convex components against recommended versions and upgrade them behind a build gate.

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

Convex UI component patterns from the live Storybook preview. Use when building React components, forms, modals, navigation, feedback states, or app layouts that should match the current Convex design system. Applies to both shared primitives and dashboard style product UI.

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

Design and generate Convex database schemas with proper validation, indexes, and relationships. Use when creating schema.ts or modifying table definitions.

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

Agent Ready project design context for navigation, docs links, and interface tone. Use when building or reviewing UI in this repo so patterns match the documented product feel.

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

Full-stack Convex development guidelines covering React, Vite, TypeScript, mutations, auth, design system, and documentation practices. Use when building features, writing Convex functions, or making code changes in this project.

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

Builds reusable Convex components with isolated tables and app-facing APIs. Use for new components, reusable backend modules, integrations, or component boundary work.

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

Design and build reactive, type-safe, production-grade backends on Convex. Covers schema, queries/mutations/actions, indexes, auth, file storage, scheduling, real-time multiplayer, mobile backends, and LLM/agent workflows on Convex's one-platform stack.

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