[Project Name]

Project Overview

Profile: standard

Tech Stack

Critical Rules

Commands

# Filled by /bootstrap with detected commands:
# dev:       <dev server command>
# test:      <test command>
# lint:      <lint command>
# format:    <format command>
# build:     <build command>
# typecheck: <typecheck command>

Architecture

Architecture Rules

• Before proposing any architectural change, check @docs/adr/ for prior decisions.

Git Workflow

• Default branch: <!-- Detected by /bootstrap (main, master, develop, etc.) -->
• Flow: Modified GitHub Flow (sprint branches → squash merge to main)
• Branches: <type>/<description> (feat, fix, hotfix, refactor, docs, test, chore) or sprint-<N>
• Commits: Conventional Commits: <type>(<scope>): <description> — atomic, one logical unit each
• PRs: ≤400 LOC (target ≤200). Squash merge to main. Delete branch after merge.
• Safety: Force push, reset --hard, clean -f, branch -D, --no-verify, checkout . — all blocked by hooks
• Rollback: /rewind → reset --soft → stash → revert → (reset --hard blocked)
• Reference: See docs/reference/GIT_WORKFLOW.md for full guide

Current Focus

Backlog

• Index: @docs/reference/BACKLOG_INDEX.md
• Epics: @docs/reference/backlog/E##-name.md (load only current epic)
• Progress: @docs/progress.md

Testing

TDD mandatory for feature, bug fix, and refactoring stories. See docs/reference/TESTING_STRATEGY.md.

Skills — Exosuit v5.0

See .claude/skills/SKILLS_INVENTORY.md for full inventory.

Core Workflow

/sprint-start → /story-cycle (repeat) → /sprint-end

Important Files

• docs/reference/CODING_STANDARDS.md — Code conventions
• docs/reference/TESTING_STRATEGY.md — Testing practices
• docs/reference/STORY_SIZING.md — Project sizing policy (sizing is by cohesion, not file count)
• docs/architecture/ARCHITECTURE.md — System architecture
• docs/reference/GROUND_RULES.md — Architectural principles
• docs/adr/ — Architecture decision records (prior decisions and rejected alternatives)
• docs/reference/MCP_INTEGRATION.md — MCP server selection and integration guide
• docs/testing/UAT_COVERAGE.md — UAT test cases

Compaction Directive

When compacting context, use this structured key-value format. Items are tagged by priority — drop LOW first, CRITICAL must survive all compactions verbatim.

## Compacted Context

### [CRITICAL — preserve verbatim across all compactions]
goal: "[Current objective — what story/task is in progress]"
sprint_goal: "[Current sprint goal — one sentence from sprint spec]"
sprint_spec: "docs/sprints/sprint-[N].md"
commands: {test: "[cmd]", lint: "[cmd]", build: "[cmd]", typecheck: "[cmd]"}
active_plan: |
  [Any in-progress plan, verbatim if possible]

### [HIGH — preserve if space allows]
branch: "[name]"
sprint: [number]
phase: "[current phase or status]"
decisions:
  - choice: "[decision]" | reason: "[rationale]"
in_progress: "[current task and its state]"

### [NORMAL — summarize if needed]
completed: ["[item1]", "[item2]"]
blocked_by: "[blocker or null]"

### [LOW — drop first, these are recoverable]
<files-read>[paths of all files explored this session, one per line]</files-read>
<files-modified>[paths of all files changed this session, one per line]</files-modified>

When multiple compactions occur:

• MERGE new file paths into existing <files-read> and <files-modified> lists — never discard previous entries
• Drop LOW items first if space is tight (files can be re-read)
• CRITICAL items must survive every compaction — never summarize or drop them