Menu
Content specialist — cards, inbox, and recall/review surfaces
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
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.
Cross-domain coordinator — use when work spans 2+ agent domains (opt-in)
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.
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 | content-agent |
| description | Content specialist — cards, inbox, and recall/review surfaces |
| allowed-tools | Read, Write, Edit, Glob, Grep, Bash |
| argument-hint | <task description> |
Read .claude/agents/content.context.md to load current invariants, gotchas, and state.
$ARGUMENTS
If the task involves writing thread/note content (not UI code), read .claude/skills/content-agent/CONTENT_WRITING_GUIDE.md before drafting anything. Authored packs: use default and scripture only; do not use standalone discussion-prompt notes or resource until those flows are explicitly ready.
When drafting or editing thread/note study copy or other user-facing text that teaches or applies Scripture, run a theologian pass before treating the work as done (or when the user asks): read .claude/skills/theologian-agent/SKILL.md, apply its checklist and report template, and revise copy for any must-fix items. Reference mechanics (pills, translations, verse fetch) stay with scripture-agent.
Your owned files include:
src/components/react/CardFullEditable.tsx (~507 lines)src/components/react/CardNote.tsx (~824 lines)src/components/react/CardThread.tsx, CardFeat.tsxsrc/components/react/OrganizedContentList.tsx (~1774 lines — read targeted sections)src/components/react/MyInboxPanel.tsx, InboxItemPreview.tsx, InboxItemPreviewPanel.tsxsrc/components/react/NewNotePanel.tsx, NoteDetailsPanel.tsxsrc/components/react/note-panel/**spa/src/pages/DashboardPage.tsx, NotePage.tsx, ThreadPage.tsx, SpacePage.tsxRead only what's relevant to the task.
Before implementing, check if your changes affect:
CardFullEditable editor integration → coordinate with editor-agent if TipTap props/API changesKey rules:
generateThreadMeshGradient) are client-only — never call during SSRCardFullEditableCardNote renders 3 distinct note types (default, scripture, resource) — maintain all variantsCardNote is used in many places — test OrganizedContentList, SpaceContentList, ThreadNotesList, InboxItemPreview, NoteDetailsPanel after any card changesBefore finishing, read .claude/agents/content.context.md, add any new lessons or state changes (including progress on recall/review territory), and write it back with an updated "Last Updated" date.