main
md 38 lines 1.76 KB
Rendered Raw
1 # A0 Development References DOX
2
3 ## Purpose
4
5 - Own focused reference files loaded by the `a0-development` skill on demand.
6 - Keep detailed framework-development guidance grounded in current source files and nearest DOX contracts.
7
8 ## Ownership
9
10 - `architecture-runtime.md` owns runtime, path, discovery-order, and port-boundary guidance.
11 - `dox-workflow.md` owns the edit and closeout workflow for DOX-governed changes.
12 - `tools.md` owns core and plugin tool development contracts.
13 - `extensions.md` owns backend and frontend extension contracts.
14 - `api-webui.md` owns HTTP API, WebSocket, and WebUI extension guidance.
15 - `agents-prompts-skills-projects.md` owns profiles, prompt fragments, skills, and project metadata guidance.
16 - `plugins-workflow.md` owns plugin-first placement and handoff guidance.
17
18 ## Local Contracts
19
20 - Every reference file must list source anchors or DOX anchors that can be checked in the repository.
21 - Prefer pointing to narrower `AGENTS.md` files instead of copying long subtree contracts.
22 - Keep examples minimal and compatible with the current helper classes.
23 - Do not include hardcoded default WebUI ports or environment-specific credentials.
24
25 ## Work Guidance
26
27 - Update the focused reference file when source or DOX changes make its guidance stale.
28 - If a reference starts duplicating a specialist skill, shorten it and hand off to that skill instead.
29 - Treat checked-in examples as examples, not authority, when they conflict with current discovery code.
30
31 ## Verification
32
33 - Manually read changed references for broken relative paths, stale source anchors, and duplicated specialist-skill material.
34 - After changing reference names, load `a0-development` and confirm the file tree exposes the new paths through `skills_tool`.
35
36 ## Child DOX Index
37
38 No child DOX files.