easi

MUST load when building a feature contract-first or frontend-before-backend in EASI — designing an API contract before code, mocking that contract, building a runnable frontend against the mock, then implementing the backend to the same contract. Load whenever you hear "frontend first", "stub/mock the API", "contract first".

MUST load when UI/frontend changes are completed, to verify functionality by running the app in a browser.

MUST load when writing or reviewing any UI component, dialog, form, button, layout, or styling in the EASI frontend. Load when picking a UI primitive, deciding how to lay out a component, when you would otherwise reach for `style={{}}` or a bare HTML element, or when adding any visual chrome. The single UI vocabulary in EASI is Mantine v8 — this skill enforces it.

MUST load when creating, updating, or reviewing any documentation in EASI — docs/, architecture canvases, READMEs, INDEX files, or pattern guides. Load when adding a new bounded context canvas, writing a pattern guide, restructuring docs, or reviewing existing documentation for bloat.

MUST load after completing a feature, bug fix, or any behavior-changing implementation, before declaring the work done. A deliberate cleanup pass over the affected area — files you modified AND files you read while doing the work — so the code is measurably better than you found it. Distinct from `easi-codehealth`: codehealth scores the change set; boyscouting decides what additional structural cleanups belong in this branch.

Load when implementing new features. Model software around the business domain. Use when designing bounded contexts, defining aggregates and value objects, mapping context relationships, or working with complex business logic. Apply before implementation to prevent model drift.

MUST load when the user asks to check code health, run codehealth, refactor for codehealth, run a pre-commit codehealth check, or assess code quality of pending/branch changes. Enforces a per-file 10.0 verification — passing CodeScene quality gates alone is NOT sufficient.

MUST load when creating, reviewing, or fixing database migrations in EASI. Load when adding new tables, altering columns, fixing migration errors, or working with the event store schema. Also load when configuring database users or reviewing RLS policies.

MUST load when writing or reviewing frontend code that talks to the backend in EASI — HATEOAS link gating, TanStack Query keys, mutation hooks, cache invalidation, multi-surface call-site audits. Load when building action buttons that depend on backend permissions, writing data-fetching hooks, setting up cache invalidation, or adding new mutation hooks.

Spec-driven development workflow for EASI. Use when starting new features or behavior-changing work. Defines how to find, read, create, and maintain specs in /specs.

MUST load when writing, running, or reviewing backend Go tests in EASI. Load when adding a new test file, choosing between unit and integration tests, running tests in CI, or checking test coverage.

Enforce RED-GREEN-REFACTOR cycle with hard gates. Use this skill whenever writing new code, fixing bugs, or adding features — any time implementation code will be written or modified. Prevents the common LLM failure mode of writing implementation first and tests later (or never). Also use when reviewing code to verify TDD discipline was followed.

MUST load when working on EASI's Architecture Canvas — any code under `frontend/src/features/canvas/`, `frontend/src/features/views/`, or `frontend/src/store/slices/dynamicModeSlice.ts`. Load when adding canvas nodes/edges, changing what appears on a view, building handle interactions, drag-drop, dynamic-view-mode drafts, save / discard flows, or anything that touches canvas state ownership.

MUST load when writing or reviewing any backend HTTP handler in EASI. Load when adding a new endpoint, writing response logic, generating HATEOAS links, checking DTO structure, or writing Swagger annotations.

MUST load when writing or reviewing any Go backend code in EASI. Load when adding error handling, event deserializers, field extraction, upcasters, or repository code.