alkdev/storage
2
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs: add AGENTS.md and fix agent role defs for deno-first project

Browse Source 
- Add AGENTS.md with project overview, conventions, commands, and heritage notes
- Fix all npm→deno command references in coordinator, implementation-specialist, poc-specialist
- Fix project name in coordinator spawn template (@alkdev/operations→@alkdev/storage)
- Remove hub-specific content (future model, hub operations) from coordinator
- Add project-specific conventions to implementation-specialist (no comments, TypeBox, slow types, etc.)
- Add deno-specific review checks to code-reviewer
- Fix file path examples in implementation-specialist (packages/core→src/graphs)
- Update sdd_process.md to remove hub-specific references and architecture doc list
- Update architect examples to use storage component names
This commit is contained in:
glm-5.1
2026-05-28 12:29:39 +00:00
parent 8c68dd6b07
commit 351fc98ec1
7 changed files with 141 additions and 54 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
.opencode/agents/architect.md
View File

@@ -29,7 +29,7 @@ Before writing architecture:
### 2. Identify Documentation Scope
Determine the appropriate scope for each document:
- **Component-level**: One document per major component (e.g., `call-graph.md`, `spoke-runner.md`)
- **Component-level**: One document per major component (e.g., `graphs-schema.md`, `sqlite-host.md`)
- **Cross-cutting**: Shared patterns in overview documents
- **Decision records**: Significant decisions in separate ADR files
@@ -145,4 +145,4 @@ Send exploration work to Research Specialist:
3. **Implementation details**: Don't describe HOW at the code level
4. **Outdated sections**: Remove or update stale content immediately
5. **Missing context**: Always explain WHY decisions were made
6. **Consumer dispatch in library docs**: When writing a library's architecture, describe what consumers need (graph construction, analysis, security constraints) — not how they dispatch it (tool registry mapping tables, CLI→action tables). That belongs in the consumer's own architecture.
6. **Consumer dispatch in library docs**: When writing a library's architecture, describe what consumers need (graph construction, analysis, security constraints) — not how they dispatch it (tool registry mapping tables, CLI→action tables, hub coordination calls). That belongs in the consumer's own architecture.