nobodyonlyc/harness-skills - 2페이지

design-database

Phase 2 data design — model entities, relationships, keys, indexes, and migrations from the requirements and architecture. Use when: modeling a schema, designing entities/relationships/keys, planning indexes for query patterns, or defining a migration…

원문 언어: 영어

design-detailed

Phase 2 detailed design — component-level structure, key algorithms, and applicable design patterns before code is written. Use when: producing the dev-facing blueprint before code, breaking a component into modules/classes, specifying a non-obvious…

원문 언어: 영어

design-ui

Phase 3 UI design — produce a visual mockup per screen using the generate-image capability, falling back to static HTML/CSS when image generation is unavailable. Use when: mocking up screens before frontend code, visualizing a UI per the UX flow, defining…

원문 언어: 영어

design-ux-flow

Phase 3 UX flow — map screen-to-screen navigation, user journeys, and per-state transitions before UI mockups are finalized. Use when: mapping screen-to-screen navigation, defining user journeys per US, specifying per-screen state transitions, or identifying…

원문 언어: 영어

check-pr-review

Phase 6 PR review — review an integration pull request in team mode before merge, covering the full change set, tests, and migration safety. Use when: reviewing an integration PR in team mode, the pre-merge gate, evaluating a feature branch for merge, or…

원문 언어: 영어

check-refactor

Phase 6 refactor pass — improve reuse, simplification, and clarity of the changed code without changing behavior. Quality only; does not hunt for bugs. Use when: cleaning up a change after review, reducing duplication/complexity in the current task's code,…

원문 언어: 영어

plan-ba-analysis

Phase 1 business analysis — elicit goals, users, and scope and produce a PRD-style requirements doc, with depth branched by user_role. Use when: starting a new project, scoping a new capability, turning a vague prompt into requirements, a BA/PRD pass before…

원문 언어: 영어