forked from retoor/devplacepy
feat: add six specialized Claude agent definitions under .claude/agents for audit, devii, docs, dry, fanout, and frontend maintenance
This commit is contained in:
@@ -0,0 +1,13 @@
|
||||
---
|
||||
description: Scaffold a new prose docs page - create the template under templates/docs/ and register it in routers/docs/pages.py, then validate.
|
||||
argument-hint: <slug> "<title>" [section] [admin]
|
||||
allowed-tools: Read, Grep, Edit, Write, Bash(python *)
|
||||
---
|
||||
Add a new prose docs page: **$ARGUMENTS**
|
||||
|
||||
Follow the docs convention exactly (confirm against `devplacepy/routers/docs/pages.py` and `devplacepy/routers/docs/views.py` first):
|
||||
|
||||
1. Create `devplacepy/templates/docs/<slug>.html` as a prose page: one `<div class="docs-content" data-render> ... </div>` containing GitHub-flavored markdown. The page is rendered server-side. Any example component markup INSIDE the data-render block must be HTML-escaped (`<dp-...>`); a live demo, if any, goes in a SEPARATE block OUTSIDE the data-render div with its own `<script type="module">`.
|
||||
2. Register it in `DOCS_PAGES` in `devplacepy/routers/docs/pages.py`: `{"slug": "<slug>", "title": "<title>", "kind": "prose", "section": SECTION_*}`. Add `"admin": True` for an admin-only page. If a new section is needed, add a `SECTION_*` constant and place it in the correct `AUDIENCES` group.
|
||||
3. Write accurate, professional content - confirm every factual claim against the source. No em-dashes, no AI disclaimers, dates as DD/MM/YYYY.
|
||||
4. Validate: run `python -m agents.validator` on the new template and on `pages.py`, run `python -c "from devplacepy.main import app"`, and confirm the slug is registered with no duplicate.
|
||||
Reference in New Issue
Block a user