Repository navigation
Quality, Testing, and Roadmap
A feature is complete only when its end-to-end behavior works, relevant tests pass, limitations are documented, and the project’s protected integration boundaries remain intact. UI presence is not evidence of implementation.
- Inventory stack, dependencies, state, renderer, data model, save/open flow and public contracts.
- Document existing working functionality.
- Identify protected integration zones.
- Establish baseline tests and a prioritized gap analysis.
- Validate the riskiest renderer, layout, persistence and packaging choices.
Exit gate: the team understands the current implementation and has an approved plan before feature refactoring.
- Application shell and workspace panels
- Canonical document schema and scene graph
- Canvas, shapes, text, frames and selection
- Move, resize, pan and zoom
- Layers and property inspector
- Command/transaction engine and undo/redo
- Platform-aware shortcut registry
- Save, reopen and recovery
Exit gate: a user can create, edit, save, reopen and recover a design without data loss.
- Auto layout and constraints
- Variables, tokens and styles
- Components, variants and instances
- Asset management
- Responsive preview and supported import/export
Exit gate: layout and component semantics survive save/reopen and remain consistent across canvas and preview.
- Typed IR
- React/TypeScript and style emitters
- Token and asset packaging
- Diagnostics and build validation
- Repeatable export fixtures
Exit gate: representative fixtures compile into runnable projects with known limitations reported.
- Model gateway and context retrieval
- Typed plan schema
- Safe command executor
- Preview/diff and approval
- Evaluation and repair tests
Exit gate: AI performs scoped, reversible edits on real document objects and passes integrity tests.
- Interaction graph and runtime
- Preview/player and navigation
- Animation, variables and conditions in supported scope
- Diagnostics and scenario tests
- Responsive website preview
Exit gate: tested prototype journeys behave consistently, and unsupported behavior is reported.
- Shared libraries and access controls
- Comments and collaboration where approved
- Plugin SDK, scripting and CLI
- Expanded deployment/model-serving controls
Exit gate: permissions, concurrency, offline behavior and recovery have defined tests.
- Unit: geometry, hierarchy rules, layout, expressions, serialization, command reducers, compiler emitters.
- Integration: canvas ↔ layers ↔ inspector, AI ↔ commands, project store ↔ schema migrations, prototype runtime ↔ document.
- End-to-end: create/edit/save/reopen/export and complete prototype journeys.
- Visual regression: representative frames and responsive layouts.
- Performance: large documents, layer trees, selection/hit testing, pan/zoom, and repeated edits.
- Accessibility: keyboard navigation, focus, labels, contrast, and reduced motion.
- Security/robustness: malformed imports, invalid AI plans, missing assets, interrupted saves and unsupported export semantics.
- All visible controls in scope work or are intentionally unavailable with a clear reason.
- Mutations are validated and undoable where appropriate.
- Save/reopen and recovery tests pass.
- Cross-surface state stays synchronized.
- AI edits pass through validation and commands.
- Exported projects build and run independently.
- Prototype behavior is tested in the player.
- Unsupported features produce diagnostics.
- Documentation, changelog, parity matrix and known limitations are updated.
- Protected-zone integrity checks pass.