By name: implement-use-case description: Implement a use case from the spec/ folder. Use when asked to implement, build, or work on a use case. argument-hint: "[use-case-name or number]"
Use Case Implementation
Implement the use case specified by $ARGUMENTS.
A use case is the unit of work, not a view. A single use case may produce one view, several views, or no UI at all — let the spec drive that, and keep tests grouped per use case as defined by /use-case-tests.
Input
- The use case document itself (in
spec/use-cases/) - Related use cases
- Generic specification files in
spec/ - Any potential images or other resources provided for the use case
Implementation
The following steps are mandatory and sequential. Do not skip or reorder them. Each step must be completed before proceeding to the next.
Step 1: Write the code
- Whenever you are even slightly unsure about Vaadin API usage, component behavior, theme variables, styling, or best practices -- use the Vaadin MCP server to look it up before guessing. Do not rely on memory for Vaadin specifics.
Step 2: Visually verify with Playwright MCP
- This step is mandatory. Do not skip it, do not defer it.
- Follow the visual-verification workflow end-to-end: start the app, navigate every route, walk through the main flow, take screenshots, and validate the visual appearance.
- Fix any issues found before moving on.
Step 3: Write and run automated tests
- Follow the use-case-tests workflow and ensure all tests pass.
Step 4: Iterate
- Keep iterating until everything looks and works great. Prefer great results over finishing quickly.
Step 5: Commit
- Once all steps are complete and everything works, create a git commit with the changes.
All steps must be completed before a use case is considered implemented.