Version 01 archive · View the current site
← All chapters
CHAPTER 07 / 12

Be clear, then be clearer.

You can correct the AI. You can also ask a separate AI to organise a complicated request before returning to your coding partner.

Organise a rough idea

TRY THIS PROMPT

Reorganise the following rough idea into a clear brief: purpose, audience, context, main user actions, boundaries and questions. Do not invent features or change my intention. Mark any ambiguity for me to answer. Here is my idea: [use fictional examples].

Correct a layout

TRY THIS PROMPT

The current layout is [describe]. I intended [describe]. On [screen size], the user needs to [task]. Change these specific elements: [list]. Preserve working behaviour. Explain your interpretation before changing the layout.

Correct a data model

TRY THIS PROMPT

The current relationships do not match the workflow. Here are fictional examples of the people, records and relationships: [examples]. Explain a corrected data model first. Do not delete records or reset a database. Propose how to preserve existing data and wait for my review.

Ask for a useful review

TRY THIS PROMPT

Review the app against its purpose, audience, context, usability, layout, permissions, reliability and maintainability. Check the main task, empty states and failure cases. State what you actually checked and what remains uncertain. Prioritise suggestions; do not implement them yet.

Continue in a new conversation

TRY THIS PROMPT

Prepare a continuation handover with purpose, audience, working features, source folder, hosting target, commands for preview/build/checks, known issues and next priorities. Separate completed work from ideas. Include no credentials, secrets or personal records. Explain any database and file storage separately.