Composing task prompts

After your kickoff prompt sets the foundation, most progress comes from small, focused requests we call task prompts. These tell the AI what to add, change, or fix in simple language so you get precise results without long back‑and‑forth. It’s a short instruction—one or two paragraphs or a few bullets—that asks the AI to make one specific change. Think of it like a single checklist item: clear, doable, and easy to verify.

Note

Looking for guidance on the big, kickoff prompt? See the companion doc Writing your initial prompt

Anatomy of a strong task prompt

Element	Purpose	Example
Objective	States exactly what to do.	“Add pull‑to‑refresh to the news feed.”
Where to change	Name the screen, page, or area (file if you know it).	“Settings screen (Profile tab is fine too).”
Helpful details	Share anything needed to do it right.	“The list shows 20 articles and groups by category.”
Limits & rules	Style, accessibility, or other must‑follow rules.	“Match the current styles and support screen readers”

Why effective task prompts matter

• Clarity Clear, specific requests prevent missteps.
• Speed Small requests finish faster and are easier to approve.
• Confidence It’s easier to check if one change works.
• Accountability Each request maps to one visible change you can review.

Best practices

1. One change per prompt – easier to check and undo if needed.
2. Point to where – name the screen or area (file if you know it).
3. Add just‑enough detail – include short text, images, or data the AI needs.
4. Link outside services – share URLs, accounts, or keys if relevant.
5. Share limits and rules – speed, style, accessibility, and security expectations.
6. Ask for a focused reply – e.g., “return the updated screen only.”
7. Say what not to change – call out files/parts to avoid.
8. Proofread once – fix typos and double‑check names.

Practical examples

Scenario	Ineffective Prompt	Effective Task Prompt
Add Dark Mode toggle	“Add dark mode.”	“Add a Dark Mode switch in Settings. When it’s on, use dark colors and remember my choice the next time I open the app.”
Swipe‑to‑delete in To‑Do app	“Let users delete tasks by swiping.”	“Let me swipe a to‑do item to show a Delete action. When I tap Delete, remove that task from the list.”
Cache API responses	“Add caching.”	“Save the articles list for 10 minutes so it loads instantly. Only check online for new articles after 10 minutes.”
Sign‑out flow	“Add logout.”	“Add a Sign Out button. When I press it, log me out, clear any saved session, and take me back to the login screen.”

Quick checklist before you hit Send

• One clear task – not a bundle of unrelated changes.
• Where to change – name the screen/section (and file if you know it).
• What “done” looks like – one sentence of how you’ll verify it works.
• Helpful references – add any design, data, or screenshots.
• Limits & rules – performance, style, and accessibility expectations.
• Out of scope – call out anything that should not be included.
• External services – mention APIs, accounts, or keys if needed.
• Data handling – say what’s saved and where (local/cloud).
• Response format – ask for a diff or a single updated file.
• Quick test step – a simple way to check it manually.