agentleFS
SmolevichSmolevich/pet-project-atlas/CLAUDE.md

pet-project-atlas

CLAUDE.md2 starsChanged 17 days agoMITView on GitHub

Public reference site (Astro + Starlight): how to get a side project found — demand, indexing, AI search, content, distribution, analytics, money. Live at https://atlas.smolevich.com, deployed from main by CI. The site is public on purpose: no Cloudflare Access in front of it. Two things live here and they are not the same job. Content is what the site publishes (src/content/docs/**). The plugin is what a reader's Claude Code runs (plugin/skills/*/SKILL.md). A page explains; a skill runs a check and…

  • In this repositoryOne other file it gives its agents.

The file

We split this CLAUDE.md into the rules it gives an agent

2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  • could be automatic: a setting could enforce it
  1. Distinctive:

    No manual deploy: Never build locally and copy to the host.

    line 27
  2. Distinctive:

    Nothing about the host in this repo: Not the provider, not what else runs on it.

    line 29

≈ “Common” is an estimate: at least 1 in 5 of the 28,029 CLAUDE.md files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
CLAUDE.md

Pet Project Atlas — notes for agents

Public reference site (Astro + Starlight): how to get a side project found — demand, indexing, AI search, content, distribution, analytics, money. Live at https://atlas.smolevich.com, deployed from main by CI. The site is public on purpose: no Cloudflare Access in front of it.

Two things live here and they are not the same job. Content is what the site publishes (src/content/docs/**). The plugin is what a reader's Claude Code runs (plugin/skills/*/SKILL.md). A page explains; a skill runs a check and points back at the page. If a human reads it, it is a page. If it returns a result, it is a skill.

Specifics live in docs/. Read the file when its topic comes up, not up front.

TopicFileOne line
Writing contentdocs/content.mdfour H2s in order, numbers need sources, both languages move together
The plugindocs/plugin.mdno audit engine of our own; command names and install paths break quietly
Checks before a commitdocs/checks.mdfive commands, all must pass, check:links only after build
Commit messagesdocs/commits.mdEnglish, one line, imperative, prefixed by area
DeployDEPLOY.mdCI only; build and deploy are separate jobs on purpose
Voice rules in fullSTYLE.mdwhat the linter enforces and why
ContributionsCONTRIBUTING.mdworkflow and editorial policy for outside pull requests

Not negotiable

  • No manual deploy. Never build locally and copy to the host. Push to main and let the workflow do it.
  • Nothing about the host in this repo. Not the provider, not what else runs on it. The origin sits behind a tunnel, and a public repo is the wrong place to narrow the search.
  • No secrets in the tree, including in example configs and drafts.
  • The checks pass before the commit, not after the push.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.