- Python 99.3%
- Shell 0.7%
Flip Surface A dev-verb routing to `ward exec` / .ward/ward.yaml. coily ops cloud passthroughs stay on coily (no ward ops surface yet). closes #23 Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> |
||
|---|---|---|
| .agents/skills | ||
| .claude | ||
| .coily | ||
| .ward | ||
| apps/bsky-scorer/docs | ||
| docs | ||
| ideas | ||
| reference | ||
| .gitignore | ||
| .pre-commit-config.yaml | ||
| AGENTS.md | ||
| CLAUDE.md | ||
| pyproject.toml | ||
| README.md | ||
atmosphere
Incubator monorepo for AT Protocol / Bluesky Atmosphere apps and experiments.
Why a monorepo
This is the undefined frontier. Atmosphere apps share a lot of plumbing - lexicon definitions, identity and auth, a PDS client, a Jetstream firehose consumer. While everything here is experimental, a lexicon change should ripple through every app that reads it in one atomic commit. That is the monorepo's whole job.
The coilysiren/cli-* family is the opposite pattern: one repo per tool, because those tools are stable and well-bounded. Atmosphere is not there yet. When an app here proves itself and stops sharing churn with the rest, it graduates out into its own repo.
Monorepo for the frontier. Polyrepo for the settled tools.
Layout
ideas/ idea dumps, one file per idea, no ceremony
packages/ shared code - lexicons, atproto-core (identity, auth, PDS client, Jetstream)
apps/ the actual Atmosphere apps, one directory each
packages/ and apps/ fill in as real things take shape. ideas/ is the front door.
Dumping ideas
Drop a markdown file into ideas/. Name it whatever. Do not overthink it. See ideas/README.md.
References
- atproto.com - the canonical protocol spec, lexicons, identity.
- docs.bsky.app - Bluesky developer docs, feed generator guide.
- bluesky-social/feed-generator - official feed generator starter.
See also
- AGENTS.md - agent instructions.
- docs/FEATURES.md - inventory of what ships today.
- .coily/coily.yaml - allowlisted commands.
Cross-reference convention from coilysiren/agentic-os#59.