retoor/devplacepy
1
0
Fork 1
Code Issues 44 Pull Requests 4 Actions Packages Projects Releases Wiki Activity

feat: add six specialized Claude agent definitions under .claude/agents for audit, devii, docs, dry, fanout, and frontend maintenance

Browse Source
This commit is contained in:
retoor
2026-06-13 18:34:47 +00:00
parent ede7a863b7
commit de745f7a75
107 changed files with 2611 additions and 517 deletions
Download Patch File Download Diff File Expand all files Collapse all files
devplacepy/templates/docs/architecture-workflow.html
+4 -4
View File
@@ -2,7 +2,7 @@
{% raw %}
# Development workflow
How a change moves from understanding to shipped. The workflow is ordered by data flow because every feature is one data source fanning out into several consumers, and the failure mode is updating one consumer while forgetting a connected one. See also [Architecture overview](/docs/architecture.html) and [Conventions and rules](/docs/architecture-conventions.html).
How a change moves from understanding to shipped. The workflow is ordered by data flow because every feature is one data source fanning out into several consumers; the failure mode is updating one consumer while forgetting a connected one. See also [Architecture overview](/docs/architecture.html) and [Conventions and rules](/docs/architecture-conventions.html).
> Audience: administrators and maintainers. These pages are hidden from members and guests, in the sidebar, the search index, and the documentation export.
@@ -17,7 +17,7 @@ How a change moves from understanding to shipped. The workflow is ordered by dat
## The four faces
Because one handler is HTML, JSON, a Devii tool, and an API-docs entry at once, after touching a route ask of each face whether it needs updating:
One handler is HTML, JSON, a Devii tool, and an API-docs entry at once. After touching a route, ask of each face whether it needs updating:
| Face | Where | Most-forgotten symptom |
|------|-------|------------------------|
@@ -34,7 +34,7 @@ Three files are kept current, each with a distinct role:
- **`AGENTS.md`** is the deep companion: every domain-specific mechanic, helper, pitfall, and cross-layer wiring, plus the full feature relationship map.
- **`CLAUDE.md`** holds the rules and conventions. Update it only when a new architectural rule, convention, or workflow step is introduced, not per feature.
This Architecture section in the in-app docs is the browsable, admin-facing reflection of those three: it explains the design and the process, while the trio remains the source of truth in the repository.
This Architecture section in the in-app docs is the browsable, admin-facing reflection of those three: it explains the design and the process, while the trio remains the repository source of truth.
## Validation gates
@@ -46,6 +46,6 @@ Run these before considering a change done:
## Testing
Correctness is verified by the suite in `tests/`, and load behavior by Locust. Every user-facing feature requires an end-to-end Playwright test. The full rules, the fixture stack, and the `make` targets are documented in the [Testing overview](/docs/testing.html) section. Do not run the test suite as part of routine development unless it is explicitly requested; validate with a clean import and per-language checks instead.
Correctness is verified by the suite in `tests/`, and load behavior by Locust. Every user-facing feature requires an end-to-end Playwright test. The rules, the fixture stack, and the `make` targets are documented in the [Testing overview](/docs/testing.html) section. Do not run the test suite during routine development unless explicitly requested; validate with a clean import and per-language checks instead.
{% endraw %}
</div>