Build your own Premiere Pro.

# Build an original app inspired by Premiere Pro

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 non-linear video editor called Cutroom, inspired by Premiere Pro. It is for editing a short narrative from owned footage with separate source and program monitors. Scope the MVP to reliable ingest, timeline operations, basic titles and audio mixing, project persistence, and a rendered video. Preview-only timelines do not satisfy the brief.

## Design
Use an original dockable-style desktop workspace with media bins, source and program viewers, transport controls, a multitrack timeline, and a clip inspector. Distinguish source in/out markers from timeline range selection. Provide a readable frame/timecode display, zoom controls, and keyboard actions for common edits.

## Features
1. Media and sequences: import and organize video/audio assets in bins; inspect codecs, frame rate, dimensions, and duration; create a sequence with explicit dimensions and timebase; support proxy/relink workflows.

2. Editing: mark source in/out points, insert or overwrite clips, trim and split, ripple-delete a gap, link/unlink video and audio, and snap edits to frame boundaries. Define collision behavior rather than silently overlapping clips.

3. Preview and sound: play the composited sequence, show a source monitor, mute/solo tracks, set gain and fades, and add a simple title. Use one consistent sample-rate and frame-conversion policy.

4. History and projects: undo/redo editing commands, save and reopen a versioned project with media references, detect missing sources, and relink without losing timing.

5. Rendering: export a documented supported format via a real media engine. Show progress, allow cancellation, clean up temporary files, and verify the output with a separate player.

## Tech stack
Use Rust for a new desktop editing engine and an appropriate native UI toolkit. A thin TypeScript/Tauri interface is acceptable if the environment already uses it. Use a properly licensed media engine for decode/encode; do not implement codecs from scratch or assume a bundled encoder is available. Use rational frame/time arithmetic and separate editing commands from preview and rendering. Document installation and supported input/output formats.

## Data & behavior
Project; Sequence {id, dimensions, fpsNumerator, fpsDenominator, sampleRate}; Bin; Asset {id, path, hash, duration, mediaInfo, proxyPath}; Track; TimelineClip {id, trackId, assetId, sourceIn, sourceOut, sequenceStart, linkedClipId}; Effect; Title; ExportJob. Store time as exact rational/integer units, not accumulated floating-point seconds. Snapshot a sequence for a render so later edits cannot mutate a running job.

Acceptance checks and scope:
Verify a one-minute sequence with several cuts, linked audio, a title, and a fade. Compare preview and export sync, reopen with missing assets, and test ripple edits and cancellation. Document behavior for mixed frame rates. Exclude Adobe project interchange, multicam, advanced grading, plugin ecosystems, cloud review, and professional codec parity.

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