superlite
AGENTS.md249 starsChanged 14 days agoMITView on GitHub
Instructions for any agent (or human) changing this repository. A lean build-lifecycle plugin: 10 skills in skills/, 7 agents in agents/, and one manifest or extension per supported harness. Keep it lean; process is the cost superlite exists to remove.
Where files are headingNew AGENTS.md files have more rules about keeping secrets out of the code, and fewer about code style.
Of the AGENTS.md files we read, the 31,774 first seen in the last six months, against the older ones: the kind of rule that gained most share, and the kind that lost most. About files like this in general, not this one, and an estimate, since a kind is a pattern in the words.
In this repository15 other files it gives its agents.
- commands/agents.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .cursor/rules/feature-worktrees.mdcCursor rule
- .cursor/rules/no-cursor-commit-notes.mdcCursor rule
- diagnosisSkill
- draftingSkill
- feature-prototypeSkill
- inventingSkill
- mvp-prototypeSkill
- proofSkill
- shippingSkill
- swarmSkill
- testingSkill
- using-superliteSkill
- writing-specsSkill
The file
We split this AGENTS.md into the rules it gives an agent
4 rules. About 0 are common, 0 are distinctive, and 4 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 13
Every harness integration must load using-superlite at session start.
- Very specific: line 16
Keep LF line endings. hooks/session-start uses printf, never a heredoc.
- Very specific: line 17
Do not touch bench/ results or docs/plans/ when working on a harness integration.
- Very specific: line 19
No Cursor agent notes on commits: Do not add Co-authored-by: Cursor … (or similar agent trailers).
≈ “Common” is an estimate: at least 1 in 5 of the 40,246 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.
Files
Superlite - Contributor Guidelines
Instructions for any agent (or human) changing this repository.
What this repo is
A lean build-lifecycle plugin: 10 skills in skills/, 7 agents in agents/, and one manifest or extension per supported harness. Keep it lean; process is the cost superlite exists to remove.
Rules
- While a superlite run is in progress, superpowers (and anything with the same lifecycle skills) is suspended.
superlite-cli finishreleases it. See the README note. skills/using-superlite/SKILL.mdis injected into every session. Keep it at most 2,000 characters.- Every harness integration must load
using-superliteat session start. Acceptance test: open a clean session and sendLet's make a react todo list;inventingmust trigger before any code is written. Manually copied skills or per-session opt-in do not count. - Per-harness tool mappings live in
skills/using-superlite/references/<harness>-tools.md. Each says how to runagents/*.mdwhere plugin agents do not exist. - Versions are declared in
.version-bump.json. Change them only withscripts/bump-version.sh <version>; runscripts/bump-version.sh --auditto catch missed files. - Keep LF line endings.
hooks/session-startusesprintf, never a heredoc. - Do not touch
bench/results ordocs/plans/when working on a harness integration. - One feature, one worktree. Never develop two features in the same checkout. Before writing code for a feature (including feature-mode integration), cut a dedicated branch and git worktree — e.g.
git worktree add -b superlite/<topic> .superlite/worktrees/<topic> <base>— move the agent root there, and keep other features' trees untouched. Prototype sandboxes (.superlite/sandboxes/<topic>-proto) stay separate from the integration worktree. The flow that cut a worktree removes it when the flow finishes; a keep with uncommitted work stays. Trivial one-line fixes on the current branch are exempt. - No Cursor agent notes on commits. Do not add
Co-authored-by: Cursor …(or similar agent trailers). After clone, runbash scripts/install-git-hooks.shonce socore.hooksPath=.githooksand thecommit-msghook strips them automatically.
Harness files
| Harness | Files |
| Claude Code, Factory Droid, Copilot CLI, Qwen Code | .claude-plugin/, hooks/hooks.json |
| Codex | .codex-plugin/plugin.json, .agents/plugins/marketplace.json |
| Cursor | .cursor-plugin/plugin.json, hooks/hooks-cursor.json |
| Devin | .devin-plugin/plugin.json |
| Gemini CLI | gemini-extension.json, GEMINI.md |
| Kimi Code | .kimi-plugin/plugin.json, docs/README.kimi.md |
| Muse | .muse-plugin/ |
| Hermes Agent | .hermes-plugin/ |
| OpenCode | .opencode/, index.js, package.json |
| Pi | .pi/extensions/superlite.ts, package.json |
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
Reviews can't be read right now.
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.