prototype-builder
Build representative screens or a state-complete interactive mobile prototype from approved direction specifications using an existing authorized prototype environment. Use after direction generation; never use to begin production Flutter UI or to invent missing runtime tooling.
- License 许可
- Apache-2.0
- 最近更新
- 2026-08-12
- Stars
- ★ 1
- Forks
- 0
01 前言 Front Matter
- name
- prototype-builder
- description
- Build representative screens or a state-complete interactive mobile prototype from approved direction specifications using an existing authorized prototype environment. Use after direction generation; never use to begin production Flutter UI or to invent missing runtime tooling.
03 SKILL.md 正文
Prototype Builder
Purpose
Turn approved direction logic into deterministic interactive design evidence while keeping prototype code separate from production Flutter UI.
When to use
Use first in representative-screen mode for every candidate direction, then in expansion mode only after a human selects one direction.
When not to use
Do not use without an approved prototype environment, before direction work, for production Flutter implementation, or as proof of visual quality merely because screens render.
Required inputs
- Validated design brief.
- Candidate direction specification or human-approved chosen direction.
- Representative-screen problem or full prototype scope.
- Realistic content and state requirements.
- Relevant Design OS pattern, typography, spacing, color, motion, accessibility, and platform guidance.
- An existing repository-approved prototype runtime and write boundary.
Permitted evidence sources
- Validated product artifacts and owner-approved content.
- Design OS knowledge and templates.
- Existing local prototype components whose ownership and license are clear.
Expected outputs
- Representative mode: one comparable screen per direction with the same content/task conditions.
- Expansion mode: the main flows, navigation, interactions, realistic fixtures, and relevant state variants.
- Token use, state coverage, and unresolved runtime limitations documented for review.
Ordered workflow
- Confirm the prototype runtime and target paths exist and are approved.
- Select representative or expansion mode; do not mix their gates.
- Load only the knowledge relevant to the screens being built.
- Use realistic content and deterministic state inputs.
- Apply the direction's composition, navigation, type, density, color, surfaces, geometry, icons, and motion coherently.
- Implement required interaction and recovery paths.
- Inspect all relevant states and supported mobile viewports available in the repository.
- Capture screenshots only when an existing approved capture capability is available; otherwise report screenshot evidence unavailable and stop before sign-off.
- Record deviations between the specification and prototype.
Tools allowed
- Existing local prototype/runtime tools already approved by the product repository.
- Local file editing inside the approved prototype/design boundary.
- Existing local browser or capture tools when already installed and authorized.
Tools forbidden
- Dependency installation, network access, external assets without provenance, production Flutter editing, secrets, installer creation, and claims that absent screenshot/QA tooling ran.
File boundaries
Write only inside the product repository's approved prototype or design workspace and approved design-artifact locations. Protect production source, CI, publishing configuration, and frozen artifacts unless the active task explicitly authorizes an update.
Non-negotiable rules
- No fake metrics or generic domain content.
- No default Material-looking scaffold as the visual direction.
- No universal card-grid dashboard without workflow evidence.
- No full expansion before representative-screen review and human selection.
- No sign-off based only on runtime success.
Stop conditions
Stop if the prototype environment or required route/state capability does not exist, the write boundary is unclear, realistic content is unavailable, or full mode lacks a human-selected direction.
Failure conditions
- The prototype changes product requirements for layout convenience.
- Direction integrity drifts across screens.
- Key states or recovery paths are omitted.
- Rendering depends on uncontrolled remote resources.
- Production Flutter files are changed.
Acceptance criteria
- The output is deterministic within the available runtime, direction-coherent, realistic, interactive, and state-aware.
- Representative screens are comparable across directions, or the chosen prototype covers the approved flows and states.
- Missing later-phase screenshot or QA capability is explicitly reported.
Handoff to the next skill
- Representative mode: return to the master workflow for human selection.
- Expansion mode: hand off to
accessibility-auditorandvisual-fidelity-reviewer.
Required human-review points
- Representative-screen comparison, direction selection, workflow realism, interaction clarity, emotional fit, and any visual/runtime deviation.
04 同仓库更多 Skills
valid-skill
Validate a small local skill fixture with one declared reference and one local schema.
visual-release-gate
Make a strict evidence-based decision on redesign, refinement, design freeze, Flutter implementation, or release-candidate eligibility using the canonical rubric, hard gates, accessibility findings, unresolved debt, and mandatory human review.
visual-fidelity-reviewer
Review mobile UI evidence for product fit, hierarchy, composition, polish, distinctiveness, consistency, direction integrity, realistic content, state completeness, and generic-AI patterns. Use before design freeze and after material visual revisions.
visual-direction-lab
Generate and compare at least three materially different mobile visual directions from a validated product design brief. Use when Codex must explore structural visual alternatives instead of defaulting to one generic composition.
mobile-product-interpreter
Derive an evidence-backed mobile product design brief from repository documents, product requirements, user flows, and explicit owner input before visual styling begins. Use when product context must be clarified, normalized, or validated for Design OS work.
flutter-ui-handoff
Prepare precise Flutter implementation guidance from an approved design freeze, including token mapping, screen behavior, component variants, states, platform adaptation, assets, semantics, and risks. Use after freeze; do not generate production Flutter UI in this skill.