# Solo Builder Project Context Brief

AI Usage Playbook / Studio Nani

Purpose: give an AI assistant the product, user, constraints, current state, and decision rules in one reusable brief so you do not restart from zero every session.

## How to use it

- Paste this brief at the start of a new AI project, chat, or coding-agent session.
- Update it whenever the real project state changes.
- Do not include passwords, API keys, private user data, or raw customer records.

## Project Brief Template

```text
# Project Context Brief

## 1. Product
- Name: [product name]
- One-line promise: [who gets what result]
- Current stage: [idea / prototype / private MVP / public beta / launched]
- Primary platform: [web / iOS / Android / PWA / content site / other]

## 2. Target user
- Primary user: [who uses it]
- Urgent problem: [why it matters now]
- Existing alternatives: [competitors/substitutes]
- What we will not do: [clear exclusions]

## 3. Business goal
- 30-day goal: [30-day goal]
- 90-day goal: [90-day goal]
- Monetization hypothesis: [ads / subscription / one-time sale / affiliate / other]
- Main acquisition loop: [search / sharing / content / community / app store / other]

## 4. Product rules
- P0 must work: [non-negotiable core]
- P1 nice to have: [next layer]
- P2 later: [later]
- Quality bar: [what counts as good]
- Anti-goals: [product directions to avoid]

## 5. User experience / taste
- Tone: [calm / playful / premium / practical / other]
- Visual references: [sites/apps/images]
- Avoid style: [what it must not feel like]
- Copy style: [short / warm / expert / direct]

## 6. Technical context
- Stack: [framework/language/hosting]
- Important paths: [files/folders]
- Local commands: [build/test/dev]
- Constraints: [cost, API, deployment, performance, security]
- Do not touch: [sensitive files or forbidden scope]

## 7. Current state
- What is already done:
  - [done 1]
  - [done 2]
- Known issues:
  - [issue 1]
  - [issue 2]
- Next likely task:
  - [next task]

## 8. Decision rules
- If a tradeoff appears, prefer: [speed / quality / cost / SEO / maintainability / other]
- Ask before: [payment, deployment, deletion, public publishing, sensitive data access]
- Verify by: [tests, browser QA, user feedback, logs, etc.]

## 9. Output request
For this session, help with: [what you want now]
Return:
- conclusion
- recommended next action
- risks / assumptions
- verification steps
```

## What makes a good brief

- The AI can understand the product in 30 seconds.
- Avoid-list and constraints are explicit.
- Current state is separate from the next task.
- Verification method is included.
- No sensitive information is embedded.

## Limit

This brief helps project memory. Current metrics, deployment state, API behavior, competitor pricing, legal claims, and financial decisions still require separate verification.