flowstate-dojo-platform-epicdm-flowstate-admin

Use this skill when a task touches packages/admin, imports @epicdm/flowstate-admin, or needs to teach humans/agents how this package works.

Package identity:

• Package: @epicdm/flowstate-admin
• Repository: flowstate-platform
• Version authority: package.json (0.1.0)
• Dojo course: flowstate-dojo-platform-epicdm-flowstate-admin

How to use the package:

• Purpose: Centralized admin dashboard for FlowState platform
• Start with package-local docs when present.
• Verify details against source and tests before changing behavior.
• Use the Dojo course lessons as the teaching path: setup, mental model, core workflow, integration, feature labs, maintenance.

Public surfaces discovered:

• GET
• metadata
• dynamic
• Providers
• Layout
• Pagination
• TeardownButton
• PlanBadge
• TenantStatusBadge
• PaymentStatusBadge
• JobStatusBadge
• ControlStatusBadge
• VerificationBadge
• AvailabilityBadge
• AdminUserMenu
• buildAuditEvent
• AdminIdentity
• getAdminSession
• requireAdmin
• getIdentityDb
• getLmsDb
• getTemplatesDb
• getDirectoryDb
• getComplianceDb
• getPlatformDb
• escapeLike
• getAuthClient
• SESSION_COOKIE_NAME
• SessionData
• invalidateUserSessions

Composable feature skilllets:

• Admin User Menu: use feature labs for workflow, source anchor, and regression risk.
• Availability Badge: use feature labs for workflow, source anchor, and regression risk.
• Build Audit Event: use feature labs for workflow, source anchor, and regression risk.
• Config: use feature labs for workflow, source anchor, and regression risk.
• Control Status Badge: use feature labs for workflow, source anchor, and regression risk.
• Dynamic: use feature labs for workflow, source anchor, and regression risk.
• Escape Like: use feature labs for workflow, source anchor, and regression risk.
• GET: use feature labs for workflow, source anchor, and regression risk.
• Get Admin Session: use feature labs for workflow, source anchor, and regression risk.
• Get Auth Client: use feature labs for workflow, source anchor, and regression risk.
• Get Compliance Db: use feature labs for workflow, source anchor, and regression risk.
• Get Directory Db: use feature labs for workflow, source anchor, and regression risk.
• Get Identity Db: use feature labs for workflow, source anchor, and regression risk.
• Get Lms Db: use feature labs for workflow, source anchor, and regression risk.
• Get Platform Db: use feature labs for workflow, source anchor, and regression risk.
• Get Templates Db: use feature labs for workflow, source anchor, and regression risk.
• Invalidate User Sessions: use feature labs for workflow, source anchor, and regression risk.
• Job Status Badge: use feature labs for workflow, source anchor, and regression risk.
• Layout: use feature labs for workflow, source anchor, and regression risk.
• Metadata: use feature labs for workflow, source anchor, and regression risk.
• Middleware: use feature labs for workflow, source anchor, and regression risk.
• Pagination: use feature labs for workflow, source anchor, and regression risk.
• Payment Status Badge: use feature labs for workflow, source anchor, and regression risk.
• Plan Badge: use feature labs for workflow, source anchor, and regression risk.
• Providers: use feature labs for workflow, source anchor, and regression risk.
• Require Admin: use feature labs for workflow, source anchor, and regression risk.
• SESSION_COOKIE_NAME: use feature labs for workflow, source anchor, and regression risk.
• Teardown Button: use feature labs for workflow, source anchor, and regression risk.
• Tenant Status Badge: use feature labs for workflow, source anchor, and regression risk.
• Verification Badge: use feature labs for workflow, source anchor, and regression risk.

Agent operating rules:

• Treat package.json as the Dojo version authority.
• Do not turn feature inventory into user-facing lessons without workflow context.
• Update this Dojo package when package behavior, docs, examples, or feature inventory changes.
• Verify downstream packages when package use and connection metadata shows inbound dependencies or references.
• Never mark publish status passed without successful cloud publish and catalog lookup.

Use this Dojo skill with package human docs, package-local feature inventory, agent-skillset.md, and the generated course.json in this folder. Keep this manifest version aligned with package.json.