Skip to main content

Prompt Generator

As easy as filling a form. You do not need to understand any technical term — beginner-friendly defaults are already selected. Just describe your goal and features, and you get a prompt Codex will understand.

Not sure what to write? Start from a template

Beginner-friendly noteThe technical words in the generated prompt are there for Codex, not you. Focus on the goal and features — sensible defaults take care of the rest.

1. What kind of software?

Most offices use Windows, so this is pre-selected.

2. How should it be built (pick a direction)

3. What should it look like

4. Where should data live?

Goal (one or two sentences)

Features (one per line, be specific)

7. Extra requests (optional)

The prompt to copy

Copy the whole block. Open Codex Desktop, start a new task, paste it in. No edits needed.

Please fill in the goal before copying.

English prompts tend to work a bit better. If you are unsure, try both.

You are a senior engineer experienced with Windows desktop apps, with strong product and interaction design sensibilities. Build a local desktop application for a business colleague who does NOT code. Technology choices, packaging, error messages, and UX affordances should all be beginner-friendly.

[Platform]
Windows desktop app (Windows 10 / 11)

[Stack]
Pick the lightest sensible stack yourself (prefer Electron + React). Use mature, well-documented, actively maintained libraries. Avoid obscure or abandoned dependencies.

[Visual Style]
Minimal: white background, generous whitespace, rounded cards, large type. Follow the system light/dark preference. Keep animations subtle and transitions smooth. Give clear visual feedback on key actions. Use system fonts only (Segoe UI / Microsoft YaHei / San Francisco / PingFang). No web fonts.

[Data]
Persist to local files (Excel / CSV / JSON) — simple and portable. All data stays local; do not upload anything to external services.

[Goal]
(Please fill in: who is the app for, and what problem does it solve? One or two sentences.)

[Features]
(Please fill in: what should it do? One item per line, as specific as possible.)

[Additional Requirements]
- Must run fully offline; no internet required
- Key results can be exported as PDF / Excel

[Robustness & Error Handling]
- Show friendly messages for every error — never expose raw stack traces.
- On bad input, prompt and guide the user rather than crashing.
- Handle empty data, edge cases, and large volumes (10k+ rows) gracefully.
- All critical actions are undoable; snapshot important data on every save and let the user roll back to the last 3 versions.

[Delivery Steps]
1. First, outline the project structure and the role of each key file, plus a simple wireframe (ASCII or text) of the main views. Wait for my confirmation before writing code.
2. Deliver in phases per feature module. After each module, run it and tell me what you built and what is still missing.
3. Final step:
   - build a Windows .exe installer.
   - Write a user guide for non-technical colleagues (<= 500 words, plain language, sections for "install", "first run", "FAQ").
   - List known limitations and future improvements.

[Working Style]
- Advance one thing at a time. Ask me if something is unclear rather than assuming.
- For company-specific details (company name, field names, brand colors) use placeholders like {{COMPANY_NAME}} and summarize the items I need to fill in at the end.
- Communicate in English, with English code comments.

Please start with step 1: project structure and wireframe.

Recent prompts

No history yet. Prompts are stored in your browser only; nothing is uploaded.