readable index of all skills (auto-generated by `scripts/generate-registry.js`)
- `evals/` — test cases
- `docs/` — contributor documentation
## CLI tool: affiliate-check
Persistent Bun daemon querying the openaffiliate.dev API. Port 9500, 5min cache
voice of Louis Rossmann, for general prose. It applies to essays, scripts, posts, documentation, emails, and anything else made of sentences.
It is NOT tied to any wiki
authoring then sweeping is much higher than the cost of internalizing the rule.
## Documentation Rules
### Public vs Private Files
- Some internal working material is gitignored (for example `_NOTES/`, `_LOCAL
owner corrects these on sight if wrong), `from: roadmap` when it comes from planning documents (durable intent, backloggable); omit when neither
- new work NEVER creates a component by default
word for a source file and for a 150-byte JSON stub naming a
document that lives in Drive. Anything routing on the modality alone reads the
stub and reports
boundary conditions and error states
5. **User experience** - Accessibility, performance, and usability considerations
6. **Documentation** - Add comments for complex logic, but prefer self-documenting code
---
Most formatting and common issues
always-on rule). **A daily-note entry alone is NEVER the documentation** — anything new gets a proper contextual home too: an existing note first, a new note in the right
lines of comment, fix the code.
- A doc comment longer than the body it documents is wrong. The usual cause is writing it to justify a
review fix rather than
when I need code generation, library installation, setup or configuration steps, or library/API documentation. This means you should automatically use the exa MCP tools get library docs without me having
crystal clear you MUST ask
## MANDATORY: Read These First
You MUST ALWAYS read these documents before ANY work:
- **`docs/PROJECT.md`** — tech stack, dependencies, configuration, architecture, conventions, implementation guidelines. This
infer current behavior or standards status from archived, staged, private, or randomly sampled documents.
## Critical
- **This repo is PUBLIC.** Everything tracked is world-readable. Business, strategy, GTM, investor, fundraising, outreach
class root `lint` script or automated `test` script in `package.json`. There is also no documented single-test command at the repository root, so validation is primarily targeted manual smoke testing
A file Claude Code reads at the start of every session. It holds the commands, conventions and warnings the agent needs for this project.
Where does it go?
At the repository root. Claude Code also reads CLAUDE.md files in subdirectories when it works there.
What should it contain?
Build and test commands, the project's layout, conventions that aren't obvious from the code, and mistakes to avoid. Short files tend to work better than long ones.
CLAUDE.md or AGENTS.md?
Claude Code reads CLAUDE.md; most other agents read AGENTS.md. Many projects keep one and point the other at it.