Build your own Photoshop.

# Build an original app inspired by Photoshop

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: Desktop. Explicit customized Product & audience and Tech stack requirements take precedence over this starting target.

## Product & audience
Build an original raster image editor called Pixelbench, inspired by Photoshop. It is for editing owned photographs and composing layered graphics. Scope the first version to reliable raster layers, simple selections and masks, brushes, adjustments, and export. The main journey is opening an image, making reversible edits, and exporting a flattened image while retaining an editable project.

## Design
Create an original desktop interface with a central zoomable canvas, tools on the left, layers and properties on the right, and a status bar for zoom and document dimensions. Use a dark neutral palette and one clear accent. Distinguish an image layer from its mask, expose opacity and blend mode, and give every destructive operation an undo path.

## Features
1. Documents and layers: create a canvas or import PNG/JPEG; add raster and editable text layers; reorder, rename, hide, lock, duplicate, and transform layers. Implement normal and multiply blending first.

2. Painting: implement a brush and eraser with configurable size and opacity. Keep stroke coordinates correct at different zooms. Treat one stroke as one history operation; optional pressure support must be detected.

3. Selections and masks: create rectangular and elliptical selections, invert/clear selections, crop the canvas, and edit an alpha mask on a selected layer. Selections constrain paint and adjustments.

4. Adjustments: provide reversible brightness/contrast and hue/saturation adjustments with explicit parameters. Compute compositing consistently between the preview and output.

5. History and files: undo/redo document operations, autosave a versioned editable project, reopen it, and export a flattened PNG/JPEG. Handle large images with explicit dimension and memory limits.

## Tech stack
Use Rust for a new native editor, with a practical UI toolkit and an isolated raster/compositing engine. Use maintained image-decoding libraries and a command-based history model. Begin with a correct CPU renderer before introducing GPU acceleration. Persist metadata plus raster assets in an app-owned project format. Do not claim PSD compatibility or use Adobe code, UI assets, brushes, or templates. If the environment already has another suitable stack, preserve it and document the rendering and memory tradeoffs.

## Data & behavior
Document {id, width, height, colorSpace, revision}; Layer {id, type, name, rasterAssetId, text, transform, opacity, blendMode, visible, locked, maskId, order}; Mask {id, alphaAssetId}; Adjustment {id, layerId, kind, parameters}; HistoryCommand; AssetBlob. Maintain an sRGB working space for the MVP and define premultiplied-alpha behavior. Keep original pixels separate from adjustment parameters and use bounded history storage.

Acceptance checks and scope:
Verify a semitransparent image over another layer, brush strokes inside a selection, mask edits, crop/undo, project reopen, and export pixel dimensions. Test transparent edge compositing and memory limits. Exclude generative fill, advanced RAW development, professional CMYK, complete PSD interchange, plugin compatibility, and cloud collaboration.

## 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.