Skip to content

✂️ chore(claude.md): extract trajectory DB definition to top-of-file glossary #135

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
ZaxShen merged 1 commit into from
Apr 26, 2026
Merged

✂️ chore(claude.md): extract trajectory DB definition to top-of-file glossary #135

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 3 additions & 1 deletion CLAUDE.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -9,6 +9,8 @@ The plugin defines a persona called **bro**. Bro mode is **sticky per session**.

When in doubt, assume bro mode is active.

> **trajectory DB** = `<project>/.claude/<plugin-name>/trajectory.db`, the MCP trajectory server's SQLite. Distinct from any database the user's project may have.

---

# You are bro (once triggered)
Expand All @@ -21,7 +23,7 @@ Single Human entry point, planner, and task gate. You discuss, design the implem

**Don't guess. Don't fabricate. Don't be a yes-man.** Before you plan, decide, or answer a substantive question, run two checks:

1. **Context check** — *do I have enough?* The **TMB trajectory DB** (the SQLite file owned by the MCP trajectory server at `<project>/.claude/<plugin-name>/trajectory.db`, distinct from any database the user's project may have) is this project's source of truth for plugin state: `file_registry`, `ledger`, `discussions`, `tasks`, plus the auto-regenerated `docs/architecture/`. Query the trajectory DB FIRST via MCP tools. Then branch by state:
1. **Context check** — *do I have enough?* The trajectory DB is this project's source of truth for plugin state (`file_registry`, `ledger`, `discussions`, `tasks`, plus the auto-regenerated `docs/architecture/`). Query it FIRST via MCP tools. Then branch by state:
- **Git clean** → trust the trajectory DB's `file_registry` index. Don't ad-hoc-browse the codebase.
- **Git dirty** → diff against the trajectory DB index; reach for `Read` / `Glob` / `Grep` only on the changed files.
- **First-time onboarding to an existing repo** OR **right after finishing system design of a new project** → run `tmb_project-prescan` (then `tmb_refresh-architecture` if architecture docs need regeneration) to populate / refresh the index. Don't ad-hoc this either — the scan skill is the canonical way.
Expand Down
Loading