flowstate-desktop Package Skill

Package: @epicdm/flowstate-desktop Repository: flowstate-desktop Path: . 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

FlowState Desktop Workspace

Use this skill for the root @epicdm/flowstate-desktop package.

Start Here

Read:

• package.json
• packages/desktop/package.json
• packages/desktop/.flowstate/skills/SKILL-INVENTORY.md

Rules

1. Exclude .worktrees, generated builds, node_modules, dist, and coverage from package scans.
2. Treat packages/desktop as the only source workspace package unless new packages are added intentionally.
3. Keep generated .flowstate/dojo out of source-of-truth skill decisions.
4. Run package-specific checks from packages/desktop when changing app behavior.
5. Check root scripts after dependency or workspace layout changes.

Verification

npm run typecheck
npm test
npm run format:check

Known Drift

Root lint-staged references packages/apple/.swiftlint.yml, which does not match the current packages/desktop/macos Swift layout.

Package Skill Inventory

@epicdm/flowstate-desktop Skill Inventory

Review Gate

@epicdm/flowstate-desktop Skill Review

Verdict

Pass with existing test drift.

Skill is source-backed and focuses on root workspace operations and package-boundary pitfalls.

Verification

• ASCII and skill frontmatter checks passed.
• Package-root coverage passed: 2 package roots, 0 missing inventories.
• npm run typecheck passed.
• npm test failed existing desktop app tests in TauriDrivePage.test.tsx; 9 files and 79/87 tests passed.
• packages/desktop npm run build passed with existing large chunk warnings.

Follow-Ups

• Reconcile lint-staged SwiftLint path with current packages/desktop/macos layout.
• Rebuild generated Dojo content from reviewed local skills before publishing.
• Reconcile TauriDrivePage tests/mocks with the current drive service API, especially missing service.cacheStatus.

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