gateway-specs Package Skill

Package: @epicdm/gateway-specs Repository: flowstate-platform Path: packages/gateway-specs 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

Gateway Specs OpenAPI Bundle Workflow

Status: Active Purpose: Keep bundled OpenAPI specs generated from worker-owned source specs. Scope: packages/gateway-specs Trigger: Worker OpenAPI changes, SDK codegen inputs, manifest drift, or spec consumption. Input: Worker source specs, package manifest, and target consumer. Output: Valid specs/*.json, regenerated manifest.json, and stable package API usage.

Workflow

1. Do not hand edit manifest.json or bundled specs/*.json for source changes. Regenerate from worker specs.
2. If route/schema changes happened in worker packages, run the repo OpenAPI generation first: yarn generate:openapi.
3. Run yarn workspace @epicdm/gateway-specs bundle. The script in scripts/bundle-specs.mts validates OpenAPI 3.1, copies each source spec, counts paths/operations, and writes manifest.json.
4. Use index.js for programmatic consumption: manifest, services, and loadSpec(name).
5. Add or remove services by changing the SOURCES table in scripts/bundle-specs.mts, then update package.json exports and README service docs.

Example

import { loadSpec, services } from '@epicdm/gateway-specs'

const marketplace = loadSpec('marketplace')
console.log(services.map(service => service.name), marketplace.openapi)

Verification

• yarn workspace @epicdm/gateway-specs bundle
• yarn workspace @epicdm/gateway-specs typecheck
• yarn workspace @epicdm/gateway-specs lint

Composition

• Use worker package skills for the source route/schema changes.
• Use gateway-routes-route-table-workflow when gateway path prefixes change with the spec.

Package Skill Inventory

Skill Inventory: @epicdm/gateway-specs

Created Skills

Candidate Future Skills

Source Evidence

• scripts/bundle-specs.mts validates and copies worker specs.
• README.md documents regeneration, consumption, publishing, and semver policy.
• index.js and index.d.ts define the package API.

Review Gate

Review: @epicdm/gateway-specs Skills

Result: Pass for source-backed package-local workflow guidance.

Checks

• The skill names generated artifacts and tells agents not to hand edit them.
• It cites scripts/bundle-specs.mts, index.js, manifest.json, and specs/*.json.
• It stays focused on bundle and consumption workflow rather than listing every service path.
• Generated .flowstate/dojo files were not modified.

Residual Risk

SDK codegen is referenced but not fully documented in this package-local shard.

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