Give your AI a clear task. Then check the result.

Start with a project your AI can read

Open your app folder in your coding tool. These examples assume it can inspect and edit the project. Ghoststack includes AGENTS.md and the referenced files; in another starter, replace the filenames with your own. Fill in the square brackets before using a prompt.

A useful request explains who needs the feature, what should happen, and how you will check it. For a substantial change, review a short plan before asking the agent to implement it. The tools guide explains how to choose a coding workspace.

1. Turn an idea into one useful feature

Use this when your idea is still broad. For example, “help freelance designers” becomes “let a signed-in designer save a client brief and find it again.”

My app helps [AUDIENCE] with [PROBLEM].
The first feature should let a user [ACTION] and get [RESULT].
Example input: [EXAMPLE]. Expected output: [EXAMPLE].

Read AGENTS.md and inspect the relevant files. Propose the smallest
complete version, explain which services it needs, and give me a
short checklist to verify it. Explain unfamiliar terms in plain
language. Wait for my feedback before implementing.

Check before continuing: the plan describes one usable interaction, identifies where data will live, and explains what happens for invalid input. Correct assumptions now, then ask the agent to implement the agreed plan.

2. Make an existing page look like your app

Use a specific page and a visible result. This keeps a small branding change from turning into a redesign of the whole project.

Read AGENTS.md and app/page.tsx. Change the headline to
"[YOUR HEADLINE]" and the supporting text to "[YOUR DESCRIPTION]".
Keep the existing DaisyUI theme, layout, navigation, and checkout
behavior. Follow the nearby component patterns.

Run the relevant checks and explain how I can view the change
on desktop and mobile. Tell me which files changed.

Check before continuing: open the preview, read the new text, and try the page's buttons. Look at a narrow screen too. Save a Git checkpoint when the result works.

3. Fix a bug with a reproducible example

Tell the agent what you did and what you expected. Share the relevant error text with credentials and personal information removed.

Read AGENTS.md. I can reproduce this problem by:
1. [FIRST STEP]
2. [SECOND STEP]
Expected: [EXPECTED RESULT]
Actual: [ACTUAL RESULT]
Relevant error: [ERROR TEXT]

Inspect the relevant code, identify the cause, and make a focused
fix. Run appropriate checks, repeat the reproduction steps, and
tell me what you verified and what you could not test.

Check before continuing: repeat the original steps yourself. For login or private data, also try another account and a logged-out visit. A successful build alone does not demonstrate that an email arrived or a payment completed.

What the included prompt library adds

Ghoststack's prompts sit inside guides for real tasks: adding database records, connecting services, creating a waitlist or blog, changing onboarding, and publishing the app. The surrounding instructions explain prerequisites, where to work, and how to check the result. A written tutorial takes you through your first feature.

These are features you build when needed. Your purchase includes the starting code and those guides; it does not include every optional feature already installed. Read the workspace guide or launch checklist to inspect more of the approach before buying.