flowstate-epic-flowstate-apps-epicdm-flowstate-app-sales
Package-local agent skill for @epicdm/flowstate-app-sales.
Tags
Publisher
Versions
1 version published — latest: 1.0.0
- 1.0.0publishedInvalid Date
Skill
flowstate-app-sales Package Skill
Package: @epicdm/flowstate-app-sales
Repository: epic-flowstate-apps
Path: packages/flowstate-app-sales
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 Sales App
Status: Active
Purpose: Guide changes to @epicdm/flowstate-app-sales without drifting from host plugin contracts.
Scope: packages/flowstate-app-sales.
Trigger: Use when changing Sales routes, exports, plugin metadata, sidebar surfaces, or multiple sales workflows.
Input: src/index.ts, src/plugin.ts, flowstate.plugin.json, src/App.tsx, touched hooks/components.
Output: A source-backed Sales package change with verification notes.
Workflow
1. Check Host Integration
Compare salesPlugin in src/plugin.ts with flowstate.plugin.json: id sales, route /apps/sales, base path /sales, and sidebar links for dashboard, pipeline, deals, clients, contacts, quotes, invoices, payment plans, and settings.
2. Pick The Domain Skill
Use sales-crm-records for clients, contacts, and deals. Use sales-pipeline-configuration for pipelines and stages. Use sales-commercial-documents for quotes, invoices, line items, and payment plans.
3. Keep Public Exports Honest
When adding a public hook, schema, component, or utility, update src/index.ts. Do not export private page-only helpers unless downstream callers need them.
Verification
Run yarn workspace @epicdm/flowstate-app-sales typecheck and yarn workspace @epicdm/flowstate-app-sales build. Record that yarn workspace @epicdm/flowstate-app-sales test currently does not run src/__tests__/App.test.tsx.
Composition
Composes with collection/model skills from @epicdm/flowstate-collections because persisted model types are imported from that package.
Pitfalls
- Do not infer all behavior from
flowstate.plugin.json; it only declaressales.newDeal. - Keep Zod form schemas aligned with collection model expectations.
- Do not edit
.flowstate/dojo.
Done When
The plugin, manifest, exports, domain hooks, and verification notes all match the changed workflow.
Package Skill Inventory
Package Skill Inventory: @epicdm/flowstate-app-sales
Package Context
Sales has several user-facing feature groups, but most agent work repeats three patterns: app/plugin integration, collection CRUD, and financial document/pipeline workflows.
Skill Map
| Skill | Type | Trigger | Teaches | Evidence | Depends On | Dojo |
|---|---|---|---|---|---|---|
flowstate-app-sales | orchestrator | Maintaining Sales app package | Routing, plugin, sidebar, exports, verification | src/index.ts, src/plugin.ts, flowstate.plugin.json | app framework | ready-after-review |
sales-crm-records | workflow | Changing clients, contacts, or deals | useRecords selectors and mutations | src/hooks/useClientCRUD.ts, useContactCRUD.ts, useDealCRUD.ts | collections | ready-after-review |
sales-commercial-documents | workflow | Changing quotes, invoices, line items, or payment plans | Zod forms, totals, statuses, collection names | src/hooks/useQuoteCRUD.ts, useInvoiceCRUD.ts, useLineItemCRUD.ts, usePaymentPlanCRUD.ts, src/utils/calculations.ts | collections | ready-after-review |
sales-pipeline-configuration | workflow | Changing sales pipelines or stages | Pipeline/stage hooks and kanban surfaces | src/hooks/usePipelineCRUD.ts, src/components/pipeline/* | collections | ready-after-review |
Anti-Sprawl Decision: Four skills cover all major Sales workflows without creating one skill per component.
Feature Coverage
| Feature Group | Source Evidence | Covered By | Notes |
|---|---|---|---|
| App/plugin/sidebar | src/plugin.ts, flowstate.plugin.json | flowstate-app-sales | Host integration. |
| Clients/contacts/deals | CRUD hooks and components | sales-crm-records | Deal filters include client, pipeline, and stage. |
| Quotes/invoices/payment plans | hooks, schemas, utils | sales-commercial-documents | Watch collection name paymentplans. |
| Pipeline stages | usePipelineCRUD.ts, pipeline components | sales-pipeline-configuration | Includes default pipeline lookup. |
Composition Model
Start with flowstate-app-sales. Use a workflow skill for the touched domain, then return to orchestrator for exports and package verification.
Deferred Skills
- Dashboard analytics skill deferred until dashboard calculations become richer than current utilities.
- Command skill deferred because only
sales.newDealis declared.
Review Questions
- Should
package.jsontest run the existing App test? - Are quote/invoice number generators sufficient for persisted records?
Review Gate
Package Skills Review: @epicdm/flowstate-app-sales
Verdict
Pass with fixes
Findings
| Severity | Skill | Issue | Evidence | Required Fix |
|---|---|---|---|---|
| Important | All | Test script drift limits verification. | package.json says "No tests yet"; src/__tests__/App.test.tsx exists. | Fix test script before publishing. |
Coverage
| Feature Group | Status | Skill | Notes |
|---|---|---|---|
| App/plugin/exports | Covered | flowstate-app-sales | Source-backed. |
| CRM records | Covered | sales-crm-records | Clients, contacts, deals. |
| Commercial docs | Covered | sales-commercial-documents | Quotes, invoices, line items, payment plans. |
| Pipeline | Covered | sales-pipeline-configuration | Pipelines and stages. |
Drift and Contract Risks
| Area | Risk | Evidence | Decision |
|---|---|---|---|
| Tests | Existing test not run by script. | package.json, src/__tests__/App.test.tsx. | Record as existing drift. |
| Dojo | Generated prototype content. | .flowstate/dojo/*. | Leave untouched. |
Dojo Publication Decision
Defer until test-script drift is resolved or publication notes explicitly mark local-only verification limits.
Follow-Up Work
- Add focused tests for calculations and CRUD hook selectors.
- Decide whether
sales.newDealneeds a source command handler.
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-app-sales/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-apps-epicdm-flowstate-app-sales --target <target> --out ./skillsReplace <target> with your agent target identifier. See the CLI docs for details.