Coding-assistant prompts (excerpt) Taken from the product files

### 1. Turn an idea into a project brief

**When to use:** You have a rough app idea and nothing written down yet.

```text
I want to build a small web app. Here is my idea in my own words:
[APP IDEA]

Turn it into a one-page project brief with these headings:
- One sentence: what it does, for whom, and why
- User journey: 4 to 7 steps, each starting with a verb
- Version 1 scope: must have / later / not planned
- Data: one realistic example record and a rule for each field
- Screens and states: empty, no results, invalid input, error
- Constraints: [TECH CONSTRAINTS, e.g. plain HTML, CSS, and JavaScript, no build step, data in localStorage]

Keep version 1 small enough to build in [AVAILABLE TIME].
Mark every assumption you made with "(assumption)" so I can check it.
Do not write any code.
```

### 2. Find the gaps in my plan

**When to use:** You have a brief and want problems found before any code exists.

```text
Here is the project brief for my app:
[PROJECT BRIEF]

Act as a careful reviewer before any code is written. List up to [NUMBER] questions or gaps
that would make this app hard to build, confusing to use, or risky (for example: missing
states, unclear rules, data that could be lost).
Order them by importance and say in one sentence why each matters.
Do not suggest new features and do not write code.
```

Files in the ZIP 10 files · 321 KB

• README.txt3 KB
• ai-coding-workbook.pdf295 KB
• checklists/debugging-checklist.md3 KB
• checklists/launch-checklist.md3 KB
• checklists/security-basics.md3 KB
• prompts/coding-assistant-prompts.md25 KB
• starter-project/README.md27 KB
• starter-project/app.js22 KB
• starter-project/index.html4 KB
• starter-project/styles.css9 KB