packages-flowstate-cli-templates-plugin-extension Package Skill

Package: packages-flowstate-cli-templates-plugin-extension Repository: epic-flowstate-community Path: packages/flowstate-cli/templates/plugin/extension 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 Plugin Extension Template

Status: Active Purpose: Maintain the extension plugin scaffold template safely. Scope: packages/flowstate-cli/templates/plugin/extension. Trigger: Use when changing template manifest, source, tests, README guidance, or generated plugin behavior. Input: Template files, parent CLI scaffolding behavior, and generated plugin expectations. Output: A scaffold that still generates a working plugin package.

Workflow

1. Preserve Template Placeholders

Keep {{pkgName}} and other scaffold placeholders intact unless the parent CLI template renderer changes. This directory is not a real package identity.

2. Update Manifest And Source Together

When flowstate.plugin.json changes, check matching source exports in src/index.ts and src/plugin.ts. For app templates, also check app/page entrypoints. For theme templates, check src/tokens.css.

3. Verify Generated Behavior

Run parent CLI tests and, when possible, generate a sample plugin and run its test, typecheck, and build scripts.

Verification

yarn workspace @epicdm/flowstate-cli test

Composition

Use parent CLI package skills for create-app/plugin command behavior. This template skill only covers scaffold files.

Pitfalls

• Do not publish this template as {{pkgName}}.
• Do not hardcode a concrete plugin ID into template files.
• Do not edit generated plugin examples instead of the template source when the scaffold is wrong.

Done When

Template placeholders, manifest, source entrypoints, tests, and generated plugin expectations agree.

Package Skill Inventory

Package Skill Inventory: flowstate-cli template extension

Package Context

This is a CLI scaffold template package with placeholder metadata. It should teach template maintenance and remain local-only for Dojo publish.

Skill Map

Anti-Sprawl Decision: One skill is enough because this is a scaffold template, not an independently used package.

Feature Coverage

Composition Model

Use this skill with parent @epicdm/flowstate-cli package skills when changing scaffold commands.

Deferred Skills

No additional skills until template behavior diverges into independent workflows.

Review Questions

• Should generated plugin smoke tests instantiate each template during CLI CI?

Review Gate

Package Skills Review: flowstate-cli template extension

Verdict

Pass with publish caveat

Findings

Coverage

Drift and Contract Risks

Dojo Publication Decision

Local-only. Do not publish to Cloud Dojo unless converted into a real generated package with a real package name.

Follow-Up Work

• Add generated-template smoke coverage in CLI tests if template drift becomes frequent.

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