Design Philosophy & Aesthetic
Extracted from anonymous reference. The Anonymous Study design system applies Anonymous Study Geist's monochrome precision to developer workflows. It pairs ultra-sharp typefaces, mathematical gray scales, zero-dependency structural simplicity, and high-contrast terminal code windows.
Color Tokens & Semantic Scale
Click any swatch to copy its hex value to the clipboard.
Typography & Type Scale
Terminal Preview & Traffic Lights
High-contrast, macOS 3-dot traffic light terminal windows demonstrate side-by-side agent interactions.
brain/pages/auth.md: Electron + SQLite, local-first. Picking up session strategy.Workflow Chain & Spatial Arrows
update-truth atomically rewrites truth and appends decision timeline.brain/ first with zero re-explanation.Feature Cards Grid
$ npm i -g @mindmux/brain-md
↳ rewrites compiled_truth
$ brain lint-links ✓
[[page-id]] syntax.Protocol Entry Points Table
| File | Audience | Purpose |
|---|---|---|
| README.md | Humans | Quick start, installation, high-level intro |
| AGENTS.md | AI coding agents | Execution rules, build commands, test instructions |
| BRAIN.md | Any reasoning agent | Protocol entry point — guides how to read & write the brain |
| brain/ | Agents & humans | Decisions, tradeoffs, architecture, flow, stack, roadmap |
FAQ Accordion Disclosures
What is BRAIN.md?
BRAIN.md is a plain-file convention for storing project knowledge in a repository. It gives agents and humans a predictable place to find decisions, rationale, constraints, and current project context.
Why does it separate compiled_truth and timeline?
compiled_truth records the current best understanding of a topic. timeline records the evidence, decisions, reversals, and notes that led there. The split lets agents read the current answer quickly while preserving the reasoning history.
How does it differ from MCP?
MCP is a runtime protocol integration layer. BRAIN.md is a repository-local Markdown convention plus a small CLI, so the project knowledge remains readable, reviewable, and versioned in git.
Do's and Don'ts
✓ Do
- Keep terminal surfaces high-contrast and dark (#171717) regardless of light/dark theme.
- Use Geist Mono strictly for commands, prompts, file trees, and code snippets.
- Use negative letter-spacing on bold headings (-2.4px on hero, -0.96px on sections).
- Use pill border-radius (9999px) for primary and secondary action buttons.
✗ Don't
- Don't introduce colorful gradient fills across body backgrounds.
- Don't use saturated primary colors for body text; keep ink at #171717 / #ededed.
- Don't use heavy drop shadows on cards; prefer subtle borders and 2px raised elevations.
- Don't mix non-monospace fonts inside terminal preview windows.