brogeby
c48b6e9c94
Add AGENTS.md, CLAUDE.md, and the agents-docs/ tree (workflow, lessons, engineering standards, context map, ADR seed, feature template) plus a domain-bearing CONTEXT.md for each of the six subdomains: toju-app, electron, server, e2e, website, docs-site. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
27 lines
1.4 KiB
Markdown
27 lines
1.4 KiB
Markdown
# Feature Areas
|
|
|
|
This index represents the known feature areas in the system.
|
|
|
|
It must stay accurate as new features are introduced, renamed, merged, or removed.
|
|
|
|
---
|
|
|
|
## Feature list (alphabetical)
|
|
|
|
_No cross-context feature docs have been written yet._
|
|
|
|
The product client already documents its bounded contexts at `toju-app/src/app/domains/<name>/README.md` (Access Control, Attachment, Authentication, Chat, Direct Call, Direct Message, Experimental Media, Game Activity, Notifications, Plugins, Profile Avatar, Screen Share, Server Directory, Theme, Voice Connection, Voice Session). Those domain READMEs cover internal product-client behavior.
|
|
|
|
`agents-docs/features/<slug>.md` is for **cross-context** contracts and feature areas that span more than one subdomain — WebSocket envelopes, IPC channels, plugin manifests, end-to-end flows that touch client + server + Electron together. Add an entry here the first time you write one.
|
|
|
|
---
|
|
|
|
## Rules for agents
|
|
|
|
- Introducing a new feature area requires:
|
|
- creating `agents-docs/features/<feature>.md` (use `agents-docs/features/feature-template.md`)
|
|
- adding it to this list (alphabetical)
|
|
- Renaming or merging features requires updating links and notes
|
|
- If the change is fully contained inside one product-client domain, prefer updating `toju-app/src/app/domains/<name>/README.md` over adding a top-level feature doc
|
|
- This file should remain concise and navigable
|