Build your own Figma.

# Build an original app inspired by Figma

You are an experienced product designer and full-stack engineer. Build a working, polished MVP from the brief below. Implement the core journeys end to end; a static mockup is not sufficient. Inspect the current environment, make sensible implementation decisions, and get started. Ask a question only if a missing answer genuinely blocks implementation.

Starting platform: Web. Explicit customized Product & audience and Tech stack requirements take precedence over this starting target.

## Product & audience
Build an original browser-based interface design tool called Framekit, inspired by Figma. It is for individuals sketching interface mockups. Scope the first version to a practical 2D editor, not a full professional replacement. The main flow is creating a frame, adding and styling objects, and exporting the result.

## Design
Use a neutral editor with a compact top toolbar, layer tree on the left, infinite canvas in the center, and property inspector on the right. Keep selection outlines and handles precise and consistent. Use an original violet accent and minimal chrome.

## Features
1. Document and canvas: create design documents and frames; pan and zoom; select one or multiple objects; fit the canvas to selection; preserve view state.

2. Objects: add rectangles, ellipses, text, and user-uploaded raster images. Move, resize, rotate, and edit fill, stroke, corner radius, opacity, and text properties.

3. Layers: name, reorder, hide, lock, and group objects. Support nesting within frames and intuitive z-order. Align and distribute multi-selections.

4. Reusable elements: turn a group into a local component, insert instances, and propagate basic style changes with explicitly supported overrides.

5. History and output: undo/redo grouped operations, autosave documents, export selected frames as PNG and SVG, and download/import a versioned JSON document.

## Tech stack
Use the existing repository and conventions if there is one. If starting from scratch, use React with TypeScript and a practical, lightweight styling approach. Pick well-maintained libraries only when they materially help. Keep components, domain logic, and data access separate. Explain your chosen stack briefly, then begin implementation.

Follow the persistence requirements in Data & behavior. Personal tools may use IndexedDB. Products with public submission, bookings, permissions, or shared messaging require an authenticated backend with server-side authorization and durable storage. Use infrastructure already available in the environment. Do not put secrets in frontend code. If external infrastructure is unavailable, build a clearly labeled local demo, provide the schema and setup instructions, and state which shared features need configuration. Do not present simulated sharing or authentication as production functionality.

## Data & behavior
Document {id, name, version}; Node {id, documentId, parentId, type, name, x, y, width, height, rotation, style, visible, locked, order}; Component {id, sourceNodeId}; Instance {id, componentId, overrides}; Asset {id, blob, mimeType}; HistoryCommand. Use an established canvas library if appropriate, with its scene model adapted to a serializable schema. Persist documents and blobs in IndexedDB.

Acceptance checks and scope:
Verify transformed nested objects, zoom-independent pointer coordinates, selection on locked layers, undo after resizing, component propagation, and export dimensions. Sanitize imported SVG or restrict uploads to raster images. Provide keyboard equivalents to core canvas actions. Exclude live multiplayer, plugins, advanced auto-layout, code generation, and external design imports.

## Originality and assets
The named product is a reference for general workflows only. Use an original product name, visual identity, wording, layout, and assets. Do not copy proprietary code, branded logos, distinctive screens, private APIs, paid templates, or protected media. Use original or appropriately licensed sample data and assets. Build from this brief rather than scraping the reference service. Do not imply affiliation with the referenced company.

## Implementation quality
- Make every visible control work, with clear loading, success, empty, validation, and failure states. Remove controls for unimplemented features.
- Support the target platform and responsive or resizable layouts where appropriate. Use platform-appropriate accessibility semantics, labels, keyboard operation, visible focus, sufficient contrast, and reduced-motion preferences. Provide alternatives for drag-only interactions.
- Validate inputs at the relevant boundary. Treat imported or user-generated content as untrusted; render it safely. Confirm destructive actions or offer undo.
- Keep state changes reliable across navigation and reloads. Never silently lose edits. Handle persistence and network errors with an actionable message.
- Keep the scope realistic. Prioritize the complete primary journey. If a custom Features section differs from the baseline, update the data model, design, and acceptance checks to match it; explicit custom requirements take precedence over baseline assumptions.
- Provide realistic original sample content and a useful empty state. Keep sample data clearly separate from user-created data.

## Delivery and verification
1. Inspect the repository and outline the implementation in a few sentences.
2. Implement the app and connect its actual data flow. Continue until the primary journey works.
3. Run appropriate checks and test the acceptance cases above on the target platform. Verify responsive layouts and keyboard navigation when browser tools are available. For native projects, build with the available SDK and test an emulator or device when possible; report any missing native verification honestly. For games, verify the rules and gameplay loop, not only the menus.
4. Fix observed failures, then provide the runnable result, setup/run instructions, a brief explanation of what is implemented, and any specific configuration or verification limits.

This is a focused MVP. Do not add billing, AI services, or unrelated features unless explicitly requested in the brief. Start building now.