trailblaze
CLAUDE.md327 starsChanged 8 months agoApache-2.0View on GitHub
This file captures conventions for AI coding assistants (Claude Code, Cursor, Aider, etc.) working in this repo. Humans are welcome to read it too. Public-facing docs (docs/**/*.md, examples/*/README.md) refer to the CLI as trailblaze — the binary an installed user has on their PATH. This is the audience the docs are written for. Framework developers working out of a source checkout of this repo should mentally swap trailblaze → ./trailblaze (the wrapper script at the OSS repo root that rebuilds…
In this repository4 other files it gives its agents.
- devlogSkill
- trailblaze-authorSkill
- trailblazeSkill
- trailblaze-validate-oobSkill
The file
Files
Working with AI Agents in this Repository
This file captures conventions for AI coding assistants (Claude Code, Cursor, Aider, etc.) working in this repo. Humans are welcome to read it too.
CLI invocations in docs
Public-facing docs (docs/**/*.md, examples/*/README.md) refer to the CLI as
trailblaze — the binary an installed user has on their PATH. This is
the audience the docs are written for.
Framework developers working out of a source checkout of this repo should
mentally swap trailblaze → ./trailblaze (the wrapper script at the OSS repo
root that rebuilds + dispatches to the source-built CLI). Don't bake ./ into
docs or example READMEs — that's a dev-loop detail, not a contract for the
audience we're writing for.
The same convention applies to commands an AI assistant suggests to the
developer in this repo: if you're walking a contributor through driving a
device from this checkout, use ./trailblaze. If you're updating user-facing
docs, use trailblaze.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.