agentleFS
pando-bpando-b/summer-solstice/AGENTS.md

summer-solstice

AGENTS.md0 starsChanged 46 days agoMITView on GitHub

This is the public Summer Solstice plugin: a generic product factory. It must never contain live intel. - No live intel here. No product names, slugs, or domains of products in flight, no competitor names in live use, no records, no event files, no workspace config, no account IDs, and no secrets. Tests and fixtures use synthetic data only, and every file under cli/tests/fixtures/ carries the marker solstice-fixture: synthetic. Build secret-shaped test strings at runtime. - Knowledge work about live…

  • Commits and pushes

The file

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

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

  • ≈1

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Common:

    No live intel here: No product names, slugs, or domains of products in flight, no competitor names in live use, no records, no event files, …

    line 6
  2. Very specific:

    Run the CLI tests with cd cli && uv run pytest -q.

    line 28

≈ “Common” is an estimate: at least 1 in 5 of the 41,581 AGENTS.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
AGENTS.md

Agent rules for this repo

This is the public Summer Solstice plugin: a generic product factory. It must never contain live intel.

  • No live intel here. No product names, slugs, or domains of products in flight, no competitor names in live use, no records, no event files, no workspace config, no account IDs, and no secrets. Tests and fixtures use synthetic data only, and every file under cli/tests/fixtures/ carries the marker solstice-fixture: synthetic. Build secret-shaped test strings at runtime.
  • Knowledge work about live products runs from the private workspace checkout, not this one. ce-plan, ce-compound, and similar work about a real product write into the workspace's own docs_root. In this checkout, compound-engineering writes to .ce-artifacts/, which is gitignored and must stay untracked.
  • Never run git push --no-verify on this repo. The pre-push hook in .githooks/pre-push scans every pushed commit (contents, paths, and messages) against the private denylist and secret patterns, and it fails closed. If it blocks a push, remove the leak from the commits; do not bypass it.
  • Confirm the hook is armed with solstice doctor (the pre-push hook line must be ok). Arm it with solstice hooks install <this checkout> --workspace <private workspace>.
  • v1 skills under skills/ stay untouched until they are removed in the v2 release.

Run the CLI tests with cd cli && uv run pytest -q.

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.