القائمة
Use before changing Enoch Dashboard V2 UI, routes, cards, tables, command results, detail pages, navigation, dashboard copy, read-model presentation, or dashboard assets. Prevents page sprawl, raw backend-state exposure, and non-operator dashboard clutter.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Fix SonarQube and SonarLint issues using the user-sonarqube MCP server together with IDE Problems/Linter diagnostics. Use when the user mentions SonarQube, SonarLint, quality gates, rule keys (e.g. S3776, S5852), code smells, cognitive complexity, security hotspots, or asks to clear Sonar errors in Problems.
Use when running an Enoch autonomous research project on a worker machine. Explains the expected artifacts, decision schema, negative/positive paper gate, follow-up rules, and operator-safety boundaries for Codex-native Enoch runs.
| name | enoch-dashboard-operator-design |
| description | Use before changing Enoch Dashboard V2 UI, routes, cards, tables, command results, detail pages, navigation, dashboard copy, read-model presentation, or dashboard assets. Prevents page sprawl, raw backend-state exposure, and non-operator dashboard clutter. |
Use this skill before making any Enoch Dashboard V2 UI or dashboard read-model presentation change.
Dashboard V2 is an operator command center, not a data explorer.
Do not add a page, panel, card, table column, badge, route, metric, or visible JSON field unless it answers a concrete operator question.
The first screen must answer:
If the proposed UI does not answer one of those, move it below the fold, put it inside collapsed debug details, merge it into an existing route, or remove it.
Before writing code, produce this short design review:
What operator pain or failure is being fixed?
Pick the question the change answers:
Choose exactly one by default:
Avoid new routes unless the route has a distinct operator job that cannot fit an existing route.
List what will be removed, hidden, collapsed, or demoted to secondary text. Every addition should usually be paired with a deletion or demotion.
State the deterministic invariant that prevents regression. Examples:
details.raw-detailsproject:, run:, paper:, or event:Pick the smallest tests that enforce the invariant.
Frontend:
cd dashboard
npm test -- --run
npm run typecheck
npm run lint
If dashboard source changes affect committed assets:
./scripts/rebuild_dashboard_v2_assets.sh
git add enoch_control_plane/control_plane/dashboard_v2/
python3 scripts/check_dashboard_v2_source_asset_pair.py --base origin/main
python3 scripts/validate_dashboard_v2_assets.py --skip-npm-ci
Backend/read-model semantics:
uv run pytest tests/test_control_plane_router.py -k "overview or dashboard or movement or lane" -q
uv run ruff check enoch_control_plane/control_plane/read_models.py enoch_control_plane/control_plane/router.py tests/test_control_plane_router.py
Above the fold, the command center may show only:
Yes, Check readiness first, Action available, or BlockedEverything else goes below the fold or into route-specific pages.
Red means operator risk only. Do not use red for normal active work, idle lanes with no queued work, historical counts, completed no-paper items, or archived blocked rows that do not affect current readiness.
Raw JSON is debug evidence only and must be inside collapsed details.raw-details.
Do not show giant visible JSON blocks, raw backend field names as primary labels,
or detail pages that only display an ID plus raw payload.
Every route must earn its existence. If a route only displays a title, ID, raw object, or backend state dump, improve it into a structured operator page or redirect to the nearest useful list/detail route.
Tables prioritize human-readable title, operator state, lane/target, next action or blocker, updated age, and compact ID copy. IDs are never the main content.
At the end of dashboard work, report: