Team roles & agent modes
CoreX is built by people and AI agents, and it is used to build real client sites. Four gates keep framework work and client work from colliding:
Role Gate decides where you work · Spec Kit decides what to build · Guard Gate decides whether code/docs are safe to ship · UI/UX ProMax decides whether visible UI is good enough.
Classify the session into one mode before editing. Copy/paste start prompts for each mode live in the handbook:
docs/en/04-team-workflow/ai-agent-start-prompts.md.
The four modes
Section titled “The four modes”| Mode | Edits | Must not |
|---|---|---|
| CoreX Framework | plugins/, addons/, packages/, root theme//specs//docs/, docs-app/, ROADMAP.md, root PROGRESS.md, framework UI, release | edit sites/<client>/ (unless authorized) |
| Client Site | sites/<client>/ only | continue the CoreX roadmap; edit framework dirs (unless authorized) |
| Deployment | dist builder, azure-pipelines.yml, deploy/rollback | client-design or framework-product changes beyond packaging |
| Docs/Planning | docs, specs, roadmap, decisions, prompts | ship runtime code (unless authorized) |
Source layout
Section titled “Source layout”# framework source (repo root)plugins/ addons/ packages/ theme/ specs/ docs/ docs-app/
# client sourcesites/<client>/ <client>-site/ # client plugin (app/business code) <client>-theme/ # client theme (presentation) AGENTS.md CLAUDE.md README.md PROGRESS.md DECISIONS.md specs/ docs/Never edited as source: wp/wp-content/ and dist/ (runtime/build output). dist/ is generated by the
shared-host builder and is git-ignored — never committed. The server receives only the contents of dist/.
Build & deploy split
Section titled “Build & deploy split”- GitHub Actions = PR / code-quality gates.
- Azure Pipelines = build
dist/+ deploy to hosting.
npm run build:dist -- --client=acme # assemble a flat dist/npm run verify:dist # the package loads the framework; no dev or host-owned files; manifest validSee Deploy & distribute and the handbook deployment pages
(docs/en/05-deployment/shared-host-dist.md, azure-pipelines.md).
Required handoff format
Section titled “Required handoff format”Every working response ends with SUMMARY / WORKSPACE / MODE / SPEC KIT STATUS / VERIFICATION / BLOCKERS / RECOMMENDED NEXT STEP and a --- NEXT STEP --- block — see AGENTS.md / ../../../../../docs/internal/COREX-WORKING-GUIDE.md §G.5.