11건 · 관련도순
Design, refine, or review web and iOS interfaces using the product’s existing components and visual style. Consult relevant screen examples when useful, then inspect the result for layout problems, inaccessible controls, and broken interactions.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Stop coding agents from shipping generic UI. Use UIZZE's 800,000+ real web and iOS screens to build product-specific interfaces, define a design contract, cover required states, and run a hard finish gate. Use for web or iOS UI design, implementation, redesign, critique, and pre-ship review in Codex, Claude Code, Cursor, Copilot, and other coding agents.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Release-gate sequence: validate → review → push → tag. Wraps kernel:git mechanics with the pre-ship safety chain. Triggers: ship, release, push to main, ready to merge, deploy.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Pre-ship gate — runs detector, verifies brief and tokens, applies the 10-pass finish bar, ranks findings by feedback hierarchy. Use when the user wants to ship, merge, or finalize a surface and needs a verdict (READY / NOT READY / BLOCKED) before committing. Invoke when the user asks for finalize on their UI, or mentions 'finalize' alongside design / UI / frontend work.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Independent review loop run before delivery in code work. An independent reviewer (Codex, or fresh Codex-style subagents) reads the whole PR against the approved outcome; the lead fixes in-scope functional findings and re-reviews until none remain. Its differentiator is independence and exhaustiveness — a reviewer that fails differently from the authors, run to clean — distinct from the recursive-refinement ladder. Invoked by the team lead from the unified pre-ship gate (code-mode and /swarm:refine) after the ship steps.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Reviews a whole deliverable (talk, course module, paper, chapter, or referee report) against its manifest without rewriting it. Runs a deterministic gate for build, citations, numbers, facts, and leaks and stops on failure, then runs a finder over each section and a strong-model pass over the whole work, and adjudicates into checks/<date>/findings.json and report.md with anchored findings, severities, and honest NOT CHECKED coverage within a dollar budget. Use when asked to lint or review the whole talk, module, or paper, for a pre-ship review, or for the night shift. Revision stays serial and author-led.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Review or polish a product UI for accessibility, brand fidelity, hierarchy, rhythm, responsive behavior, themes, interaction states, and generic AI-template patterns. Use for visual audits, accessibility checks, UX polish, UI critique, or pre-ship design review. Do not use for generic code review, backend review, or API design.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Unified verification: build→lint→test→type-check→coverage. Use for 'is everything green', 'run all checks', 'verify build'. Auto-called by mk:cook. NOT for lint/format only (see mk:lint-and-validate); NOT for test-to-requirement coverage mapping (see mk:nyquist).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Before finishing any code (endpoint, query, migration, render, file, infra, dependency, test) — the senior pre-ship checklist of invisible cross-cutting controls AI omits, with backstop greps
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Pre-ship framing and the technical release gate, with approvals under the go-gate rules. Generated from plugin-commands.json; invoke as $bdb-aos:shipping.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Pre-ship safety proof for replacing a live implementation with a canonical one. Use when repointing nodes, tools, or services to a new contract, superseding a schema, retiring a legacy or parallel system, or any 'new way replaces the old way' change. NOT for greenfield or unconsumed additive work.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.