mirror of https://github.com/TechNomadCode/AI-Product-Development-Toolkit.git synced 2026-10-20 08:39:44 +02:00

Files

T

History

TechNomadCodeandClaude Opus 5.5 30b9b8cf55 Give each planning step one name and make the guides easier to follow

- Rename prompt-templates/ to planning-prompts/ with numbered step
  folders, so GitHub lists them in workflow order. Folder, prompt file
  and skill now share one name per step (2-prd/prd.md is /prd).
- Merge the full and ultra-lean MVP plan prompts into 5-mvp-plan/, as
  the /mvp-plan skill already did.
- Rename the /mvp skill to /mvp-scope; the installer removes an earlier
  mvp install and tells the owner about the new name.
- Rename agent-configs/claude-code-desktop/ to agent-configs/claude-code/,
  since the rules apply to the terminal too.
- Rewrite each prompt guide in one short layout with previous and next
  links, drop outdated model and temperature advice, and fix the copied
  "final PRD draft" lines and the claimed v0.dev section.
- Point to GitHub's Copy raw content button for copying a prompt.
- Move the AI App Starter details from the root README into the starter
  guide, add the skills to the top table, and align the test plan
  wording with what the prompt produces.
- Add issue forms, a Discussions link and a short contributing guide.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

2026-10-12 14:57:27 +02:00

README.md

Give each planning step one name and make the guides easier to follow

2026-10-12 14:57:27 +02:00

ux.md

Give each planning step one name and make the guides easier to follow

2026-10-12 14:57:27 +02:00

README.md

UX and user flow prompt

Step 3 of the planning prompts. The AI turns your PRD into UX and interface specs: the screens, how people move through them, and how each one behaves. Detailed enough for a developer, or an AI design tool, to build from.

Prompt: ux.md

What you get

UX specs in seven parts:

Information architecture: the screen map, navigation and layout zones
Core user flows, including decision points and error paths
Screen layouts and their states: empty, loading, filled and error
Interaction patterns and feedback
Design system notes: components, grid and spacing
Accessibility: keyboard paths, screen readers, contrast and focus
Technical notes for the frontend

During the interview it sketches layouts in plain text, so you can react to them before anything is written up.

What to bring

Your PRD (required): the full text, from the PRD prompt or your own.
Constraints (optional): fill in the bracketed line under TONE & CONSTRAINTS, such as a design system, devices and browsers, or an accessibility standard, or delete it.

How to use it

Open ux.md and copy it with the copy button at the top right of the file (Copy raw content).
In a text editor, paste your PRD over the placeholder between --- PRD START --- and --- PRD END ---.
Paste it into a new AI chat and answer its questions. It checks its understanding with you before each new section.
When it offers to write the specs, say yes. Review them and save them as a Markdown file.

In Claude Code or Codex? The /ux skill runs this same prompt and fills it in from your files.

Good to know

Text sketches aren't designs. Try the key screens in a visual prototype before you build them.
The PRD and the interview make a long conversation, so use a model that keeps it all in view.
The specs are a draft. Check them against what you know about your users.

Next step

MVP scope: pick the smallest first version worth building, using your PRD and these specs.

← Previous: PRD · All planning prompts