القائمة
MUST load when UI/frontend changes are completed, to verify functionality by running the app in a browser.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | easi-frontend-e2e-testing |
| description | MUST load when UI/frontend changes are completed, to verify functionality by running the app in a browser. |
| compatibility | opencode |
EASI's full stack (backend + Postgres + Dex OIDC) runs locally via Docker Compose at the repo root. Use podman compose up --build -d if it's not running already.
| Service | URL | Purpose |
|---|---|---|
| Frontend (Vite) | http://localhost:5173 | What the user sees. Started via npm run dev from frontend/. |
| Backend (Go API) | http://localhost:8080 | REST API + OIDC callback. |
| Dex (OIDC) | http://localhost:5556/dex | Local OIDC provider with seeded users. |
| Postgres | localhost:5432 | DB (user/pass easi/easi, db easi). |
Defined in dex-config.yaml at the repo root. Password for all users is password.
| Role | |
|---|---|
architect@acme.com | architect |
admin@acme.com | admin |
stakeholder@acme.com | stakeholder (read-only) |
nono@acme.com | persona-non-grata (deny test) |
podman compose up -d --build backend. Verify with curl before browser testing.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 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.