flowstate-epic-flowstate-community-epicdm-flowstate-finance-core
Package-local agent skill for @epicdm/flowstate-finance-core.
Tags
Publisher
Versions
1 version published — latest: 0.1.7
- 0.1.7publishedInvalid Date
Skill
flowstate-finance-core Package Skill
Package: @epicdm/flowstate-finance-core
Repository: epic-flowstate-community
Path: packages/flowstate-finance-core
Version: 0.1.7
Use this published Dojo skill as the package-level entrypoint. For detailed workflows, use the package-local skills listed below.
Primary Package Workflow
Finance Core Maintenance
Purpose
Use this skill when changing the finance-core package boundary or keeping documentation, package-local skills, feature matrix records, and Dojo artifacts aligned with source code.
Read First
packages/flowstate-finance-core/src/index.tspackages/flowstate-finance-core/README.mdpackages/flowstate-finance-core/CHANGELOG.mdpackages/flowstate-finance-core/.flowstate/feature-matrix/packages/flowstate-finance-core/.flowstate/dojo/packages/flowstate-finance-core/.flowstate/skills/packages/flowstate-mcp/src/tools/FinanceTools.ts
Maintenance Checklist
When changing public behavior:
- Update source and tests first.
- Export new public functions/types from
src/index.ts. - Check downstream MCP wrappers in
flowstate-mcp. - Update README and CHANGELOG if the workflow or public surface changed.
- Update package-local
.flowstate/skillsif an agent workflow changed. - Rebuild package-local Dojo content from reviewed skills before publishing.
- Update feature inventory/status artifacts if feature coverage changed.
Known Drift
- README still frames posting, mapping, schema seeding, and batch orchestration as future work. Current source implements and tests those workflows.
- Existing
.flowstate/dojoartifacts are generated prototypes. They incorrectly state that no query-like public methods and no test behavior names were detected. - Generated Dojo artifacts over-list one-function skilllets instead of teaching workflows.
- Publisher metadata differs across Dojo artifacts.
Do not publish these generated Dojo artifacts as-is. Rebuild from reviewed local skills and course material.
Export Hygiene
For any new public function or type:
- Add it to
src/index.ts. - Confirm package build emits declarations.
- Check whether
flowstate-mcpshould expose it as a tool. - Add tests at the package layer before adding downstream tool tests.
For internal helpers:
- Keep helpers unexported unless downstream packages need them.
- Prefer testing through public workflows when possible.
Verification
Run package gates:
yarn workspace @epicdm/flowstate-finance-core test
yarn workspace @epicdm/flowstate-finance-core typecheck
yarn workspace @epicdm/flowstate-finance-core build
yarn workspace @epicdm/flowstate-finance-core lint
yarn nx build @epicdm/flowstate-finance-core
Run downstream checks when exports or MCP behavior changed:
yarn workspace @epicdm/flowstate-mcp typecheck
yarn nx test @epicdm/flowstate-mcp --passWithNoTests
Record known warnings separately from failures. Existing lint warnings are not a reason to weaken the skill content.
Package Skill Inventory
@epicdm/flowstate-finance-core Skill Inventory
Skill Set
| Skill | Purpose |
|---|---|
flowstate-finance-core | Orient agents to the finance-core package, choose the right workflow skill, and preserve accounting invariants. |
flowstate-finance-core-posting-engine | Use and modify the YNAB to GL posting pipeline safely. |
flowstate-finance-core-mapping-and-schemas | Seed finance schemas, seed YNAB mappings, resolve source accounts, and handle Suspense. |
flowstate-finance-core-report-builders | Use and maintain report/query builders with GL mode, tenancy, and aggregation rules. |
flowstate-finance-core-query-and-actions | Wire finance query builders and write actions through MCP/tooling without bypassing guards. |
flowstate-finance-core-maintenance | Keep exports, docs, tests, downstream MCP wrappers, feature inventory, and Dojo artifacts aligned. |
Design Notes
This package needs workflow skills rather than one skill per exported function. Most defects would come from breaking accounting invariants across modules: posting, mapping, schema setup, and reports depend on the same collection names, source ids, org/workspace scoping, and journal-entry contracts.
Each skill names the source files to read first, concrete commands to run, and the verification evidence agents should capture before changing downstream Dojo content.
Not Included
- Test fixtures are not taught as runtime APIs.
- Generated
.flowstate/dojoskilllets are not reused directly because they contain stale and misleading statements. - The skills avoid publishing instructions until package-local review passes and the Dojo content is rebuilt from these reviewed skills.
Review Gate
@epicdm/flowstate-finance-core Skills Review
Verdict
Pass with tracked follow-ups.
The authored skills are source-backed and workflow-oriented. They teach agents how the finance package is used in practice instead of listing individual features.
Coverage
- Posting engine: covered from
post-batch.ts, posting helpers, idempotency, source hash, transfer-pair logic, subtransaction expansion, and journal write shape. - Mapping and schemas: covered from schema definitions, schema seeding, mapping seeding, resolver, Suspense lifecycle, and YNAB type derivation.
- Reports: covered from report types, aggregate wrapper, filter/date helpers, mode checks, and report builders.
- Queries/actions: covered from query builders, manual journal-entry actions, voiding, reconciliation, close period, and explicit mapping updates.
- Maintenance: covered for public export hygiene, downstream
flowstate-mcpwrapper checks, README/Dojo drift, and verification commands.
Follow-Ups
- Rebuild package-local
.flowstate/dojocourse and skill manifests from the reviewed skills before publishing. - Update
README.mdto stop describing implemented posting/mapping/schema/report phases as future work. - Keep
flowstate-mcpfinance tool wrappers synchronized when adding, renaming, or changing exported finance-core functions. - Track existing lint warnings separately from skill quality.
Verification Results
LC_ALL=C rg -n "[^\\x00-\\x7F]" packages/flowstate-finance-core/.flowstate/skills
rg -n "^name:|^description:" packages/flowstate-finance-core/.flowstate/skills
yarn workspace @epicdm/flowstate-finance-core test
yarn workspace @epicdm/flowstate-finance-core typecheck
yarn workspace @epicdm/flowstate-finance-core build
yarn workspace @epicdm/flowstate-finance-core lint
yarn nx build @epicdm/flowstate-finance-core
Results:
- ASCII scan passed with no non-ASCII matches.
- Frontmatter scan found
nameanddescriptionon all six skills. typecheckpassed.buildpassed and emitted CJS, ESM, and DTS outputs.testpassed: 40 passed suites, 2 skipped suites, 334 passed tests, 29 skipped tests, 363 total tests.lintpassed with 84 existing@typescript-eslint/no-non-null-assertionwarnings.yarn nx build @epicdm/flowstate-finance-corepassed. Nx Cloud reported the existing unconnected-workspace 401 warning.
Usage
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-finance-core/package.json. Do not treat generated feature lists as lessons; use workflow evidence from CODE-REVIEW.md, SKILL-INVENTORY.md, and REVIEW.md.
Install
Run this in your project to install via CLI:
fscloud dojo skill install flowstate-epic-flowstate-community-epicdm-flowstate-finance-core --target <target> --out ./skillsReplace <target> with your agent target identifier. See the CLI docs for details.