# Wireframe Gen Agent Guide

This workspace implements a hybrid documentation-to-wireframe system:

1. Normalize scattered product documentation into traced product data.
2. Convert normalized data into UX architecture, flows, screen inventory, and screen blueprints.
3. Build or update mid-fi editable Figma wireframes through native Figma MCP.
4. Coordinate user requests, artifact lifecycle, open questions, and decision logs.

Use repo-local skills from `.agents/skills/` when a task matches them. Keep schema keys in English for tooling stability. Default generated narrative, UX rationale, and user-facing summaries to Russian unless the source material or user asks otherwise.

This workspace is the origin template. Do not store client-specific project context, copied Figma content, client names, or run outputs here, except generic additions to the UX research registry.

Client-copy work data lives under `workspace/`, which is preserved during Hot Update and is never part of the transferable system package. Legacy `artifacts/` may exist only for migration and is excluded from updates.

Primary local artifacts live under `workspace/artifacts/wireframe-gen/`:

- `source_inventory.json`
- `normalized_project.json`
- `normalized_project.summary.md`
- `ux_spec.json`
- `ux_spec.summary.md`
- `screen_blueprints.json`
- `figma_build_manifest.json`
- `figma_validation.md`
- `decision_log.md`

System files that may be pushed from Origin to client copies are declared in `wireframe-system.manifest.json`. Hot Update scripts must copy only manifest allowlist paths and must preserve `workspace/`, `artifacts/`, `maintenance/`, and `dist/`.

Internal depersonalized bug reports created during client work live under `workspace/system-feedback/bug-reports/`. Origin-only bug analysis and fix notes live under `maintenance/`; never copy `maintenance/` into client projects.

Before UX construction or Figma generation, surface unresolved blocking `open_questions` to the user and record answers in `decision_log.md`. Before writing to Figma, ensure `screen_blueprints.json` exists and is validated. After writing to Figma, update `figma_build_manifest.json` with every created, mutated, or annotation node ID and screenshot/validation notes.

Figma product screen frames must contain only final-product UI. Put metadata, comments, requirement traceability, UX rationale, and other annotations in a separate notes frame inside the same Figma Section, outside the screen frame.