Name: _workflow-base
Author: ZanderCowboy

Prompt file imported from ZanderCowboy/multichoice (.cursor/commands/_workflow-base.md). Copyright stays with the author.

Shared Workflow Base

Include these steps in feature, fix, and similar implementation commands.

Before editing

Read relevant .cursor/rules/ files (not all — pick by area: ui-rules, api-rules, testing-rules, code-organization).
Read .cursor/references/ when product or UX context is needed.
Search for existing implementations; match nearby architecture, naming, and folder layout.

Implementation

Keep changes scoped to the ticket or user request.
Ask before new dependencies, packages, service boundaries, state management, persistence, or UX pattern changes.
Preserve shipped behavior unless the ticket requires a change and the user confirms risk.
Mocks/codegen: check mocks.dart first; run make db via Melos — never hand-edit generated files.

Validation

Narrowest relevant test (melos test:core / melos test:multichoice).
Scoped analyze: melos exec --scope=<touched-package> -- flutter analyze.
melos analyze / melos test:all only for cross-package changes.
Fix introduced lints and test failures; state skipped validation and risk if blocked.

Completion

Summarize what changed and why; list validation run.
Do not commit or push unless the user explicitly asks.

# Shared Workflow Base Include these steps in feature, fix, and similar implementation commands. ## Before editing 1. Read relevant `.cursor/rules/` files (not all — pick by area: `ui-rules`, `api-rules`, `testing-rules`, `code-organization`). 2. Read `.cursor/references/` when product or UX context is needed. 3. Search for existing implementations; match nearby architecture, naming, and folder layout. ## Implementation - Keep changes scoped to the ticket or user request. - Ask before new dependencies, packages, service boundaries, state management, persistence, or UX pattern changes. - Preserve shipped behavior unless the ticket requires a change and the user confirms risk. - Mocks/codegen: check `mocks.dart` first; run `make db` via Melos — never hand-edit generated files. ## Validation 1. Narrowest relevant test (`melos test:core` / `melos test:multichoice`). 2. Scoped analyze: `melos exec --scope=<touched-package> -- flutter analyze`. 3. `melos analyze` / `melos test:all` only for cross-package changes. 4. Fix introduced lints and test failures; state skipped validation and risk if blocked. ## Completion - Summarize what changed and why; list validation run. - Do not commit or push unless the user explicitly asks.

Install _workflow-base and it becomes one more candidate the router can pick - when it fits.

A listing is a routing target with a manifest: what it does, which domains it covers, what it costs and who publishes it. Once installed it sits beside your own models and tools, is scored like any other candidate for each request, and shows up in the trace when it wins. Ratings come from workspaces that installed it, one per account.

{ "prompt": "# Shared Workflow Base\n\nInclude these steps in feature, fix, and similar implementation commands.\n\n## Before editing\n\n1. Read relevant `.cursor/rules/` files (not all — pick by area: `ui-rules`, `api-rules`, `testing-rules`, `code-organization`).\n2. Read `.cursor/references/` when product or UX context is needed.\n3. Search for existing implementations; match nearby architecture, naming, and folder layout.\n\n## Implementation\n\n- Keep changes scoped to the ticket or user request.\n- Ask before new dependencies, packages, service boundaries, state management, persistence, or UX pattern changes.\n- Preserve shipped behavior unless the ticket requires a change and the user confirms risk.\n- Mocks/codegen: check `mocks.dart` first; run `make db` via Melos — never hand-edit generated files.\n\n## Validation\n\n1. Narrowest relevant test (`melos test:core` / `melos test:multichoice`).\n2. Scoped analyze: `melos exec --scope=<touched-package> -- flutter analyze`.\n3. `melos analyze` / `melos test:all` only for cross-package changes.\n4. Fix introduced lints and test failures; state skipped validation and risk if blocked.\n\n## Completion\n\n- Summarize what changed and why; list validation run.\n- Do not commit or push unless the user explicitly asks.", "variables": [], "notes": "Include these steps in feature, fix, and similar implementation commands.", "metadata": { "source": { "provider": "github-cursor-commands", "repository": "https://github.com/ZanderCowboy/multichoice", "path": ".cursor/commands/_workflow-base.md", "ref": "5425568a3ddc186c48fac1415f70b70b8d1d4cfc", "url": "https://github.com/ZanderCowboy/multichoice/blob/5425568a3ddc186c48fac1415f70b70b8d1d4cfc/.cursor/commands/_workflow-base.md", "key": "ZanderCowboy/multichoice/.cursor/commands/_workflow-base.md" } } }

_workflow-base

About

Shared Workflow Base

Before editing

Implementation

Validation

Completion

Use it

Install _workflow-base and it becomes one more candidate the router can pick - when it fits.

Manifest

Reviews