Learning Claude

Product Requirements Document

What exactly are we building?

• What the app does — its main purpose and why it is worth building.
• Who it is for — the target users and stakeholders.
• Every feature that is in scope for this build.
• An explicit list of what is out of scope, so the project does not creep.
• Success criteria — measurable targets that define "done".

App Flow Document

A complete map of the app from the user’s point of view.

• What does a user see when they first land?
• Where do they go after signing up?
• What happens when they click Settings?
• What does the error state look like?

Tech Stack Document

A version-locked list of every dependency the app will use.

• Frontend and backend frameworks
• Database, auth library, and CSS framework
• API clients, payment processor, file storage, and email service

Content Guidelines Document

A lightweight design system.

• Colour palette
• Typography choices
• A spacing system
• Component aesthetics
• Tone of voice

Backend Schema Document

A complete technical spec of the data and access layer.

• How the data is structured
• How the system handles identity and access

• Every database table, with every column
• Relationships between tables
• Authentication flows
• Authorization rules
• API endpoints

Implementation Plan Document

Give Claude a clear build sequence.

• The order things get built in, step by step, so each piece has what it depends on already in place.