Menü
Cross-domain coordinator — use when work spans 2+ agent domains (opt-in)
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Basierend auf der SOC-Berufsklassifikation
Marketing specialist — changelog entries, release notes, harvous.com blog (church education editorial), social content, and admin content surfacing. Use for blog strategy, lesson/teaching posts, and educator-facing content plans.
Harvous design-system guardian — tokens, prototype CSS, native DesignSystem views, gallery scenes, visual QA, and cohesion reviews. Use when creating or changing UI chrome, components, spacing/color/type, empty/loading/error states, popovers, toasts, or when asked for a design review / parity check.
Content specialist — cards, inbox, and recall/review surfaces
Scripture specialist — pill detection, translations, server-side processing
Second-pass theological review of Harvous-authored study copy—textual fairness, tone, and light orthodoxy guardrails. Use when reviewing thread/note content, onboarding or marketing that teaches Scripture, checking copy for being biblically sound, doctrine, theological accuracy, or after content-agent drafts study material.
Data layer specialist — Supabase, Drizzle, API endpoints, offline sync
| name | coordinator |
| description | Cross-domain coordinator — use when work spans 2+ agent domains (opt-in) |
| allowed-tools | Read, Write, Edit, Glob, Grep, Bash, Agent |
| argument-hint | <task description> |
Use the coordinator only when:
For single-domain work, invoke the specialist directly (/editor-agent, /scripture-agent, etc.) — it's faster and cheaper.
Read .claude/agents/coordinator.context.md for the cross-domain dependency map.
Read .claude/agents/manifest.json.
For the task: $ARGUMENTS
Match the affected files against owns arrays in the manifest. List which agents are involved.
Read the context files for each involved agent:
.claude/agents/editor.context.md.claude/agents/scripture.context.md.claude/agents/content.context.md.claude/agents/sharing.context.md.claude/agents/data.context.md.claude/agents/design.context.mdLoad only the ones relevant to this task.
The primary agent is the one whose domain contains most of the work. The others are reviewers.
Use the dependency map in coordinator.context.md to determine review order:
data changes are reviewed last (foundation — others depend on it)design reviews UI chrome/tokens before editor/sharing polish when both touch the same surfacePerform the primary implementation using the primary agent's context and rules.
For each reviewer agent, check the implemented changes against their invariants:
For complex reviews, use the Agent tool to launch a specialist review: "Review these changes for compliance with your domain's invariants: [changes summary]"
Update the context file for every agent whose domain was touched, with new lessons or state changes and an updated "Last Updated" date.