flowstate-dojo-community-epicdm-flowstate-extension-core

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

Package identity:

• Package: @epicdm/flowstate-extension-core
• Repository: epic-flowstate-community
• Version authority: package.json (1.0.7)
• Dojo course: flowstate-dojo-community-epicdm-flowstate-extension-core

How to use the package:

• Purpose: Core TypeScript SDK for VS Code extension compatibility — manifest types, adapters, VSIX scanner, compatibility scoring, and Open VSX API client
• 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:

• x
• Platform
• SupportStatus
• ContributionPointScore
• CompatibilityScore
• SUPPORT_WEIGHTS
• PLATFORM_SUPPORT
• getPlatformSupport
• scoreExtension
• generateRecommendations
• ExtensionNode
• DependencyEdge
• DependencyGraph
• DependencyResolutionSuccess
• DependencyResolutionError
• DependencyResolution
• normalizeExtensionId
• extractDependencyNode
• buildDependencyGraph
• resolveDependencies
• FederationMode
• FederationFilter
• FederationConfig
• FederationCacheKey
• FederatedSearchResult
• FederatedExtensionResult
• generateCacheKey
• matchesFilter
• isDeclarativeExtension
• FederationClient

Composable feature skilllets:

• Build Compatibility Report: use feature labs for workflow, source anchor, and regression risk.
• Build Dependency Graph: use feature labs for workflow, source anchor, and regression risk.
• Classify Declarative: use feature labs for workflow, source anchor, and regression risk.
• DECLARATIVE_CONTRIBUTION_POINTS: use feature labs for workflow, source anchor, and regression risk.
• Detect Api Namespaces: use feature labs for workflow, source anchor, and regression risk.
• Enumerate Contribution Points: use feature labs for workflow, source anchor, and regression risk.
• Extract Dependency Node: use feature labs for workflow, source anchor, and regression risk.
• Federation Client: use feature labs for workflow, source anchor, and regression risk.
• Flow State To Vs Code: use feature labs for workflow, source anchor, and regression risk.
• Generate Cache Key: use feature labs for workflow, source anchor, and regression risk.
• Generate Recommendations: use feature labs for workflow, source anchor, and regression risk.
• Get Platform Support: use feature labs for workflow, source anchor, and regression risk.
• Is Declarative Extension: use feature labs for workflow, source anchor, and regression risk.
• Map Activation Events: use feature labs for workflow, source anchor, and regression risk.
• Map Category: use feature labs for workflow, source anchor, and regression risk.
• Map Extension Kind: use feature labs for workflow, source anchor, and regression risk.
• Matches Filter: use feature labs for workflow, source anchor, and regression risk.
• Normalize Extension Id: use feature labs for workflow, source anchor, and regression risk.
• Open VSXClient: use feature labs for workflow, source anchor, and regression risk.
• PLATFORM_SUPPORT: use feature labs for workflow, source anchor, and regression risk.
• Resolve Dependencies: use feature labs for workflow, source anchor, and regression risk.
• Reverse Activation Events: use feature labs for workflow, source anchor, and regression risk.
• Reverse Category: use feature labs for workflow, source anchor, and regression risk.
• Reverse Extension Kind: use feature labs for workflow, source anchor, and regression risk.
• Scan Vsix: use feature labs for workflow, source anchor, and regression risk.
• Score Extension: use feature labs for workflow, source anchor, and regression risk.
• SUPPORT_WEIGHTS: use feature labs for workflow, source anchor, and regression risk.
• Vs Code To Flow State: use feature labs for workflow, source anchor, and regression risk.
• Vsix Scan Error: 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.