docs: audit and tidy legacy agent workspaces and historical records
This commit is contained in:
1 parent
809f420fe4
commit
1ce711d960
3 files changed
+38
No files matched your search
@@ -0,0 +1,32 @@
|
||||
# Agent System & Workspaces Directory
|
||||
|
||||
> **Agent Infrastructure & Historical Provenance:** This directory houses both active multi-agent skills and historical subagent run workspaces. The platform identity is **DBK Platform**, with **HomAroma** as the reference tenant.
|
||||
|
||||
---
|
||||
|
||||
## 1. Active Skills (`.agents/skills/`)
|
||||
The `.agents/skills/` directory contains active domain skill definitions loaded on demand by Antigravity and orchestrator agents. Each skill contains a `SKILL.md` specifying role responsibilities, routing logic, and verification rules:
|
||||
|
||||
- **`orchestrator`**: Central project planning, task routing, delegation, and verification.
|
||||
- **`frontend-lead`**: React 19 SPA & Tailwind CSS development.
|
||||
- **`frontend-code-auditor`**: Review gate for bug risks, contracts, and regressions.
|
||||
- **`nextjs-seo-architect`**: Next.js 15 SSR, metadata, canonical URLs, and performance.
|
||||
- **`backend-mcp-lead`**: Elysia API endpoints, server architecture, and MCP tools.
|
||||
- **`database-architect`**: Prisma schema, PostgreSQL migrations, and data safety.
|
||||
- **`cms-architect`**: Dynamic page builder payloads and headless CMS schemas.
|
||||
- **`cms-content-manager`**: Content management and MCP blackbox testing.
|
||||
- **`product-manager`**: Product scope, roadmap, and business impact analysis.
|
||||
- **`ux-ui-designer`**: Design system, interaction models, and responsive layouts.
|
||||
- **`qa-product-auditor`**: User flows, regression checks, and release readiness.
|
||||
- **`brand-strategist`**: SEO copywriting, brand voice, and positioning.
|
||||
- **`theme-compliance-auditor`**: CMS dynamic theme token compliance (avoid hardcoded colors).
|
||||
|
||||
*Note: Changes to `.agents/skills/` directly affect agent behavior and should follow the operational rules defined in [`AGENTS.md`](../AGENTS.md).*
|
||||
|
||||
---
|
||||
|
||||
## 2. Historical Subagent Workspaces
|
||||
Directories matching `auditor_*`, `worker_*`, `explorer_*`, `reviewer_*`, `challenger_*`, `teamwork_preview_*`, `sentinel`, and `sub_orch_*` are historical workspaces and artifact directories generated during previous autonomous multi-agent sprint sessions.
|
||||
|
||||
- **Status:** Historical records preserved for provenance, auditability, and debugging.
|
||||
- **Usage:** Do not edit active platform rules within historical folders. Refer to [`AGENTS.md`](../AGENTS.md) and [`docs/PLATFORM_OVERVIEW.md`](../docs/PLATFORM_OVERVIEW.md) for current standards.
|
||||
Reference in new issue
Block a user