New Project Checklist

When starting a new project, this sequence ties together the patterns documented across Field Notes into a single bootstrap workflow. Each step links to the relevant documentation.

The Bootstrap Sequence

Step 0: Make Stack Decisions

Before creating any files, decide on the technology stack. Record each choice with its rationale so the team can revisit decisions later without starting from scratch.

Key decisions: package manager, build system, framework, TypeScript strictness, styling approach, testing tools.

Read Stack Decisions

Step 1: Set Up Project Structure

Create a directory structure with living documents at the root (DECISIONS.md, PERSONAS.md, PRINCIPLES.md, CLAUDE.md), sprint records in docs/, and a _meta/PROJECT_CONTEXT.md describing the project's purpose, users, and constraints.

See Synthesis & Validation for living document templates.

Once the structure is in place, run the scaffold commands to install tooling and wire up the workspace.

Read Bootstrap Commands

Step 2: Connect to Field Notes

Add the Field Notes index to your project's CLAUDE.md so AI agents can look up specific patterns as needed. Use the index, not the full dump — agents fetch individual pages when relevant rather than loading everything into context at once:

## Reference

See https://bysixteen.github.io/field-notes/llms.txt for design engineering pattern index.

Read the Documentation Hub Pattern

Step 3: Configure Claude Code

Set up your AI agent configuration following the Claude Code Setup guide:

• Create CLAUDE.md at project root (under 150 lines)
• Add build/test/lint commands and git conventions
• Create .claude/rules/ for file-type-specific conventions
• Test: can a fresh agent clone and run tests on first try?

Step 4: Choose Architecture Patterns

Review the Platform Patterns domain. Key decisions:

• Data: Will you split transactional and editorial data? → Data Architecture
• Auth: Do you need row-level security? → Auth & RLS
• Audit: Do you need state transition history? → Audit-First
• Structure: Monorepo or single-repo? → Monorepo Architecture

Step 5: Audit Your Inputs

For greenfield projects there is no codebase to audit — instead, audit the inputs that will shape the project: design briefs, requirements documents, stakeholder assumptions, competitive analysis, and any prior research. For existing projects, also audit the codebase.

Document findings in docs/audit/gap-analysis.md. Map each gap to a concrete remediation action.

Step 6: Run the First Sprint

Target the highest-priority user journey. The first sprint produces the first real entries in DECISIONS.md, PERSONAS.md, and PRINCIPLES.md — transforming them from empty templates into living documents.

Step 7: Start Compounding

After the first sprint, living documents are no longer empty templates. Let CLAUDE.md grow from real corrections, not predictions.

Read about Compounding Engineering

Quick Reference

Copy this checklist into your project kickoff document:

## Project Bootstrap

- [ ] Make stack decisions and record in DECISIONS.md
- [ ] Write `_meta/PROJECT_CONTEXT.md`
- [ ] Set up directory structure with living documents at root
- [ ] Run bootstrap commands (scaffold, tooling, workspace)
- [ ] Add Field Notes llms.txt index URL to CLAUDE.md
- [ ] Configure Claude Code (CLAUDE.md, rules, first-try test)
- [ ] Set up git conventions (branch prefixes, commit format)
- [ ] Choose architecture patterns from Platform domain
- [ ] Audit inputs (briefs, designs, requirements, assumptions)
- [ ] Run first sprint targeting highest-priority journey
- [ ] Update living documents (DECISIONS, PERSONAS, PRINCIPLES)