flowstate-extension-core Package Skill

Package: @epicdm/flowstate-extension-core Repository: epic-flowstate-community Path: packages/extension-core Version: 1.0.7

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

Primary Package Workflow

Extension Core Compatibility Scoring

Status: Active Purpose: Produce a platform-aware compatibility score and recommendations for a VS Code extension manifest. Scope: src/compatibility-scorer.ts. Trigger: A workflow needs to decide whether an extension can run on desktop, web, or mobile FlowState surfaces. Input: VSCodeExtensionManifest, target Platform, optional API namespace list. Output: CompatibilityScore.

Workflow

1. Choose platform: desktop, web, or mobile.
2. Call scoreExtension(manifest, platform, apiNamespaces).
3. Inspect:
   • score
   • level
   • breakdown
   • report
   • recommendations
4. Use getPlatformSupport(platform) when explaining support status to callers.

Scoring Semantics

• Contribution points are weighted by SUPPORT_WEIGHTS.
• Unknown contribution points are unsupported.
• desktop has the broadest support and has an extension host.
• web and mobile apply an entry-point penalty when a manifest has main or browser.
• Levels derive from numeric score:
  • >= 90: full
  • >= 50: partial
  • > 0: declarative-only
  • 0: unsupported

Recommendation Rules

Recommendations should stay actionable:

• Warn when an extension requires an extension host on a platform that lacks one.
• Suggest desktop when unsupported contribution points are present on other platforms.
• Note partial support by contribution point.
• Provide an all-clear only when all contribution points are natively supported and entry-point requirements are acceptable.

Verification

yarn workspace @epicdm/flowstate-extension-core test src/__tests__/compatibility-scorer.test.ts
yarn workspace @epicdm/flowstate-extension-core typecheck

Package Skill Inventory

Skill Inventory: @epicdm/flowstate-extension-core

Package path: packages/extension-core

Skill Map

Why This Split

The feature inventory lists 29 public features, but they compose into six durable workflows. The split keeps generated constants and helpers inside the workflow where agents actually need them.

Publication Notes

• Existing .flowstate/dojo files are generated prototypes.
• Rebuild Dojo artifacts from these reviewed skills before publishing.

Review Gate

Package Skill Review: @epicdm/flowstate-extension-core

Package path: packages/extension-core

Review Result

Status: source-backed and verified for local package-skill use; Dojo publication deferred until reviewed skill content is packaged for the Dojo API.

The skillset is organized around real caller workflows: manifest translation, VSIX scanning, compatibility scoring, dependency resolution, and Open VSX/federation access.

Checks

• Source review: completed from package metadata, source exports, tests, changelog, feature matrix, generated Dojo artifacts, and package review subagent output.
• Skill inventory: completed.
• Skill files: completed.
• Verification: completed with lint warnings below.
• Generated Dojo replacement: deferred; existing .flowstate/dojo files are generated prototypes.
• Cloud Dojo publication: deferred until reviewed skills are packaged into Dojo manifests.

Verification Commands

Verification completed before publication:

yarn workspace @epicdm/flowstate-extension-core test
yarn workspace @epicdm/flowstate-extension-core typecheck
yarn workspace @epicdm/flowstate-extension-core build
yarn workspace @epicdm/flowstate-extension-core lint
yarn nx build @epicdm/flowstate-extension-core

Results:

• ASCII validation passed for .flowstate/skills.
• typecheck passed.
• test passed: 8 files, 318 tests.
• build passed.
• lint passed with 23 warnings, mostly forbidden non-null assertions in tests and dependency-resolver.ts, plus one unused test type import.
• yarn nx build @epicdm/flowstate-extension-core passed; Nx Cloud reported the existing unconnected-workspace 401.

Publication Gate

Do not publish generated .flowstate/dojo artifacts until they are rebuilt from reviewed package skills.

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