Appendix A — Prompt cheat sheet

Use Dr JSkill to create a new <app-name>.

Use Dr JSkill to create a new <app-name>.

- Features: <one-line feature list>
- Front-end: Vue (or React / Angular / Vanilla JS)
- Database: PostgreSQL with Hibernate ddl-auto
- No security
- Include: Docker, tests, dotfiles

Use Dr JSkill to create a new <app-name>. Use the versions specified in
versions.json — do not override.

Add a <field-or-feature> to <entity-name>. Update:
- the JPA entity and migration of the schema
- the REST controller (expose it on existing endpoints)
- the Vue component that renders <entity-name>
Keep existing behavior; do not add new dependencies.

Add a search field above the todo list.

Acceptance:
- Typing filters the list in real time
- Empty search shows everything
- No API call per keystroke — debounce to 300ms
- The search also works with the user filter

Do not add any new Maven or npm dependencies; use what's already in the
project.

Keep the current project layout — no new packages, no file renames, no
refactoring beyond the change described.

Use Spring Data JPA, not JDBC. Use MockMvc, not RestAssured. Use Bootstrap
utility classes, not custom CSS.

Only modify files under frontend/src/components/. Do not touch the backend.

Do not edit any files yet. Describe the changes you would make to implement
<X>, file by file. I'll say "go" once I approve.

Walk me through what you changed, file by file, and why.

The change compiles but I think <Y> is wrong. Re-check <specific claim> by
reading the file and the test.

The previous change broke <behavior>. Expected: <what should happen>.
Observed: <what actually happens>. Fix it without reverting the rest of
the changes.

Revert the last change completely — use git. Don't try to "fix" it in place.

Run ./mvnw test. If any test fails, show me the failing test and the
exception stack trace before attempting a fix.

The /api/todos endpoint returns 500 when called with a userId that doesn't
exist. Find the root cause using the LSP tool to trace the call chain, then
propose a fix.

Show me the last 50 lines of the Spring Boot log and identify anything that
isn't a healthy startup message.

Rename the "name" field on AppUser to "login" across the codebase — entity,
repository methods, DTOs, controllers, front-end. Use LSP rename where
possible. Update all tests.

TodoController has business logic creeping in. Move the per-user filtering
logic to TodoService and keep the controller thin. Update the relevant
tests.

Add @WebMvcTest unit tests for <controller>. Cover success, not-found, and
bad-request paths for every endpoint. Mock the service with @MockitoBean.
Follow Dr JSkill's testing conventions.

Add a *IT test that walks through the full create-read-delete lifecycle
against a real Postgres container via @ServiceConnection. Follow
Dr JSkill's testing conventions.

Add a Micrometer counter on <action> so I can see it in /actuator/metrics.
Don't change the behavior.

Apply <specific recipe, e.g. "virtual threads"> from references/SPRING-BOOT-4.md.
Quote the exact property added and show me the one-line diff.

Update the project README.md to reflect the current feature set: users,
filters, toasts, etc. Keep it under 80 lines.

Commit the current staged + unstaged changes with a Conventional Commit
message summarizing what's in the diff. Do not push.

Read SKILL.md and references/DATABASE.md before answering.

Apply the pattern described in references/<FILE>.md — quote the relevant
section in your response.

Dr JSkill prefers Hibernate ddl-auto over Flyway. Summarize the rationale
from the references, then tell me under what conditions I should reconsider
that choice for this project.