Your build starts here
Replace bracketed details with your own goal, context, and checks. Keep the first build small enough to inspect.
Implement [document workflow] in the existing desktop app. Users should [create or open], edit [content], save to [supported destination], and reopen the same result.
Inspect current window, document, and file-access conventions. Define unsaved-change behavior and useful handling of cancellation, unsupported files, and unwritable destinations. Keep document state distinct from window lifetime when required. Use appropriate system dialogs and accessible keyboard interaction.
Verify the saved file by reopening its actual bytes. Check multiple windows if supported, text or display scaling, and the packaged application environment. Report tested paths, recovery behavior, relevant checks, and distribution-specific setup that remains necessary.Make this prompt yours
Replace bracketed fields with your goal, current behavior, and relevant evidence. Keep requirements that affect the task. Check the result against the acceptance criteria you supplied.
The docs behind it
These references explain the underlying concepts and APIs. The prompt templates and project plans are original examples to adapt to your own setup.
- Apple — NSDocument document architecture
- Electron — Native open and save dialogs
- Node.js — File system operations
Documentation links checked .
Editorial review · October 28, 2026
Supported: Original, unexecuted document template. Native selection and actual filesystem writes are distinct; cancellation and failed-save draft preservation are sensible proposed acceptance rules.