| name | readme-guidelines |
| description | Review or write README content for open-source projects. Enforces progressive disclosure, jargon-free language, and single-concept code examples. Use when asked to "write README", "review README", "update README", or "check docs". |
| argument-hint | <file-or-section> |
| metadata | {"author":"Celesto Team","version":"1.0.0"} |
README Guidelines
Review or write README content following these principles. The goal is easy onboarding for both newcomers and advanced users.
Core Principles
1. Progressive disclosure of complexity
Structure content so readers can stop at any point and still have a working mental model. Each section should be usable on its own:
- Lead with the simplest outcome (one-liner, quickstart)
- Add detail in subsequent sections
- Advanced topics (integrations, internals, performance) come last
- Never require reading ahead to understand what's in front of you
2. One concept per code example
Each code block should demonstrate exactly one idea. If a snippet requires the reader to understand two or more new things simultaneously, split it.
Wrong — introduces sandbox creation AND environment variables at the same time:
with SmolVM(env={"API_KEY": "secret"}) as vm:
vm.run()