nanakura/moeka-project
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs: keep ADRs in the main repository

Browse Source
This commit is contained in:
RainbowBird
2026-09-12 19:23:23 +08:00
parent 938c9d6b88
commit 827b692b15
2 changed files with 9 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files
AGENTS.md
+7
View File
@@ -91,6 +91,13 @@ Concise but detailed reference for contributors working across the `moeru-ai/air
## Before You Start
## Architecture decisions
- Put project-wide and client ADRs directly in `docs/ai/`.
- Put hosted backend ADRs directly in `server/docs/ai/`.
- Both paths are relative to the repository root.
- Keep ADRs in this repository and include them in the related commits and pull requests.
## Enforced Repository Skills
- For testing, Vitest, regression reproduction, mocks, or test import-boundary work, always use [`enforce-rules-for-vitest` skill](.agents/skills/enforce-rules-for-vitest/SKILL.md).
server/AGENTS.md
+2 -3
View File
@@ -12,9 +12,8 @@
## Architecture decisions
- Put server ADRs in `../airi-docs/adr/`.
- For an ADR task, write or update the ADR only. Do not stage, commit, push, or open a PR for ADR files.
- The user owns ADR commits and pushes.
- Put server ADRs directly in `server/docs/ai/`, relative to the repository root.
- Include ADRs in the related commits and pull requests in this repository.
- Create or update the ADR before you change a server boundary.
- A server boundary includes an HTTP contract, provider contract, persistence model, or cross-module lifecycle.
- Add a module dependency graph, an affected-file tree, and a sequence diagram to every implementation ADR.