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

Update

Browse Source
This commit is contained in:
retoor
2026-07-07 16:09:28 +02:00
parent 32c8bbe0a9
commit 5083efb150
42 changed files with 2556 additions and 2806 deletions
Download Patch File Download Diff File Expand all files Collapse all files
.claude/commands/explain.md
+3 -3
View File
@@ -1,5 +1,5 @@
---
description: Explain a DevPlace subsystem, route, or file - read the relevant AGENTS.md section and the code, then summarize architecture, data flow, invariants, and entry points. Read-only.
description: Explain a DevPlace subsystem, route, or file - read the relevant nested CLAUDE.md and the code, then summarize architecture, data flow, invariants, and entry points. Read-only.
argument-hint: <area, route, or file>
allowed-tools: Read, Grep, Glob, Bash(git log:*)
---
@@ -8,13 +8,13 @@ Orient me on: **$ARGUMENTS**
Investigate before explaining; confirm every claim against the source.
1. Locate the code: the router under `devplacepy/routers/`, the template under `devplacepy/templates/`, data helpers in `devplacepy/database.py`, schemas in `devplacepy/schemas.py`, and any service under `devplacepy/services/`.
2. Read the matching domain section in `AGENTS.md` (the long-form companion) and the relevant part of `CLAUDE.md`.
2. Read the matching nested `CLAUDE.md` for the subsystem (e.g. `devplacepy/services/devii/CLAUDE.md`), plus the relevant cross-cutting part of the root `CLAUDE.md`.
3. Trace the data flow: input model (`models.py`) -> router handler + guard -> data helper -> response (HTML via `respond` + template, JSON via the `*Out` schema), plus the Devii action (`catalog.py`) and API docs (`docs_api.py`) where present.
Then give a tight explanation:
- What it does and where it lives, with `file:line` references.
- The request pipeline and data flow.
- Key invariants and gotchas (pull these from AGENTS.md).
- Key invariants and gotchas (pull these from the nested CLAUDE.md).
- The fan-out: which of the nine feature layers exist for it.
Do not modify anything.
.claude/commands/maintenance.md
+1 -1
View File
@@ -8,7 +8,7 @@ You are orchestrating the DevPlace maintenance fleet. Each dimension is a projec
## Dimension to subagent map
| Dimension | Subagent | Enforces |
|-----------|----------|----------|
| style | `style-maintainer` | CLAUDE.md/AGENTS.md coding rules (context-aware names, em-dash, typing, pathlib, headers) |
| style | `style-maintainer` | CLAUDE.md (root/nested) coding rules (context-aware names, em-dash, typing, pathlib, headers) |
| dry | `dry-maintainer` | duplication and reuse of canonical shared utilities |
| security | `security-maintainer` | auth guards, project visibility, read-only guards, input validation, XSS |
| audit | `audit-maintainer` | audit-log coverage and event catalogue |
.claude/commands/service.md
+1 -1
View File
@@ -12,5 +12,5 @@ Mirror an existing service - read `devplacepy/services/base.py` (BaseService) an
3. Register it in `main.py` startup: `service_manager.register(YourService())`, under the same `DEVPLACE_DISABLE_SERVICES` guard as the others. It then auto-appears on `/admin/services`.
4. If it calls an LLM, default its endpoint to `config.INTERNAL_GATEWAY_URL` and authenticate with the internal gateway key, like the other AI consumers.
5. Emit audit events via `record_system` for any state change it makes.
6. Document it in `AGENTS.md` (Background services section) and in `README.md` if user-visible.
6. Document it in `devplacepy/services/CLAUDE.md` (Background services base machinery section, or the service's own nested `CLAUDE.md` if it has one) and in `README.md` if user-visible.
7. Validate with `hawk` on the touched files and `python -c "from devplacepy.main import app"`.