flowstate-app-content Package Skill

Package: @epicdm/flowstate-app-content Repository: epic-flowstate-apps Path: packages/flowstate-app-content Version: 1.0.0

Use this published Dojo skill as the package-level entrypoint. For detailed workflows, use the package-local skills listed below.

Primary Package Workflow

Content Collection Hooks

Status: Active
Purpose: Keep Content Studio collection access scoped and consistent.
Scope: src/hooks/*CRUD.ts in packages/flowstate-app-content.
Trigger: A task changes list/detail/mutation hooks or introduces a content collection.
Input: Collection name, filters, and mutation needs.
Output: Scoped hook behavior using FlowState collection helpers.

Workflow

1. Start from the nearest existing hook in src/hooks: content pieces, pillars, hook templates, conversion codes, funnels, calendar, persuasion templates, or audiences.
2. Use useDatabase() and useOrgWorkspace() to get db, currentOrgId, and currentWorkspaceId.
3. Include orgId in selectors. Add workspaceId when present. Keep workspace optional where existing hooks do.
4. Use useRecords for collection-backed CRUD. Return entity-specific names such as contentPieces, pillars, or funnels.
5. For mutation object compatibility, follow the local pattern: some hooks return raw create/update/remove, while calendar and persuasion templates expose mutateAsync wrappers.

Collection Names

Verification

yarn workspace @epicdm/flowstate-app-content typecheck

When adding filters, inspect both the list component and detail route to ensure field names match stored records.

Package Skill Inventory

Skill Inventory: @epicdm/flowstate-app-content

Composition

Start with the orchestrator for app structure. Use collection hooks for data access and form schemas for validation changes. Most feature work in this package needs both subskills.

Review Gate

Review: @epicdm/flowstate-app-content Skills

Status: Passed for local package use
Reviewed: 2026-06-30

Checks

Residual Risk

Several imports in src/App.tsx point to nested component directories not covered by the initial shallow file list. Future changes should inspect the exact component before editing.

Start with this skill to understand the package purpose, then use the package-local focused skills for specific workflows. Keep this Dojo version aligned with packages/flowstate-app-content/package.json. Do not treat generated feature lists as lessons; use workflow evidence from CODE-REVIEW.md, SKILL-INVENTORY.md, and REVIEW.md.