flowstate-app-launcher Package Skill

Package: @epicdm/flowstate-app-launcher Repository: epic-flowstate-community Path: packages/apps/flowstate-app-launcher Version: 0.1.0

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

Primary Package Workflow

FlowState App Launcher E2E

Use this skill when modifying launcher behavior that must hold in a browser host.

Start Here

Read:

• packages/apps/flowstate-app-launcher/demo/App.tsx
• packages/apps/flowstate-app-launcher/playwright.config.ts
• packages/apps/flowstate-app-launcher/e2e/fixtures.ts
• packages/apps/flowstate-app-launcher/e2e/helpers.ts
• the relevant packages/apps/flowstate-app-launcher/e2e/*.spec.ts

What The Tests Protect

The E2E suite covers:

• page load and launcher visibility
• app grid rendering
• navigation to app routes
• responsive layouts
• accessibility expectations

Treat the demo app as the test host. Do not assert behavior that only works in the full desktop/web shell unless the demo host is updated to model that dependency.

Adding Coverage

1. Prefer shared fixtures for app definitions and host setup.
2. Use user-visible app names, routes, and controls instead of implementation selectors when possible.
3. Add navigation assertions when changing handleAppSelect, route paths, or manifest route metadata.
4. Add responsive coverage when changing card layout, group layout, or status/header placement.
5. Add accessibility coverage when changing keyboard selection, focus behavior, or button roles.

Verification

Run:

yarn workspace @epicdm/flowstate-app-launcher test:e2e

If Playwright browser binaries are missing, install them using the workspace's documented Playwright setup before rerunning.

Package Skill Inventory

@epicdm/flowstate-app-launcher Skill Inventory

Skill Set

Coverage

The skill set covers:

• manifest-to-app adaptation
• suite grouping
• dynamic Lucide icon lookup
• runtime mode/server/org display
• org/workspace selector placement
• route navigation callbacks
• host integration boundaries
• E2E launcher smoke, navigation, grid, responsive, and accessibility coverage

Out Of Scope

• Publishing generated Dojo artifacts.
• Reworking visual design.
• Adding missing rebuild package script.

Review Gate

@epicdm/flowstate-app-launcher Skill Review

Review Verdict

Pass with follow-ups.

The local skills are source-backed and describe how agents should operate the package, not just what symbols exist. The generated Dojo artifacts remain prototype content and should be rebuilt from these skills before publication.

Verification

Completed:

• ASCII and skill frontmatter checks passed.
• yarn workspace @epicdm/flowstate-app-launcher test passed with no unit test files found and exit code 0.
• yarn workspace @epicdm/flowstate-app-launcher typecheck passed.
• yarn workspace @epicdm/flowstate-app-launcher build passed with existing package export-condition warning for types after import/require.
• yarn nx build @epicdm/flowstate-app-launcher passed with dependent tasks cached and existing Nx Cloud 401/unconnected-workspace notice.

Optional E2E:

• yarn workspace @epicdm/flowstate-app-launcher test:e2e

Follow-Ups

• Decide whether root rebuild:apps should call build or this package should add a rebuild script.
• Refresh generated .flowstate/dojo content from reviewed package-local skills.
• Update old README naming and package metadata drift when touching docs.

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/apps/flowstate-app-launcher/package.json. Do not treat generated feature lists as lessons; use workflow evidence from CODE-REVIEW.md, SKILL-INVENTORY.md, and REVIEW.md.