Shared source map
This site and the README are rendered from the same content map, so the guidance stays in sync as the repo grows. Use it to see which files matter, what each one should contain, and where to add new context without making the tree noisy.
Shared source: src/data/steering-data.js
Agent-Agnostic Files
These files should stay useful no matter which assistant is reading the repo.
AGENTS.md
The vendor-neutral operating manual for coding agents.
Use it for: repo-specific agent behavior, safe defaults and guardrails, commands that are reliable in this repo, review and merge expectations
PRODUCT.md
Product context that keeps implementation choices aligned with the business.
Use it for: target users, the problem being solved, major workflows, business objectives and success criteria
TECH.md
The technical source of truth for stack and implementation constraints.
Use it for: frameworks and libraries, runtime versions, build and test commands, deployment targets and integration points
STRUCTURE.md
A map of the repository that helps agents put changes in the right place.
Use it for: top-level directory layout, naming conventions, import patterns, module boundaries
VISION.md
The durable product and taste direction that should change less often than product specs.
Use it for: long-term product vision, non-goals, design and product taste, the kind of future you are trying to create
DESIGN.md
A design-system source of truth for AI-generated interface work.
Use it for: design tokens, typography, spacing, color principles, component patterns, accessibility expectations
Agent-Specific Files
These files should exist when a tool needs its own memory, syntax, or scope rules.
CLAUDE.md
The Claude Code instruction file.
Use it for: Claude-specific guidance, repo conventions that should persist across Claude sessions, build/test/verify expectations for Claude, workflow notes that are useful for Claude but not all tools
GEMINI.md
The Gemini CLI / Gemini agent context file.
Use it for: Gemini-specific instructions, repo conventions that should persist across Gemini sessions, project context and response preferences, custom commands or tool usage hints
.github/copilot-instructions.md
The repository-wide GitHub Copilot instructions file.
Use it for: instructions that should apply to Copilot across the repo, build/test/validation guidance, repo-specific coding standards, review and safety expectations
.cursor/rules/*.mdc
Path-scoped Cursor rules for workflows that should only apply in specific places.
Use it for: file-specific or workflow-specific rules, path-scoped instructions, rule sets that should only apply in certain parts of the repo, agent behavior that needs to be narrower than a repo-wide file
Writing checklist