菜单
Runs the full admin-UI quality-gate battery for app/ehrbase-admin-ui: clippy on native AND wasm32 targets, nextest, leptosfmt + cargo fmt, and a cargo-leptos build. Use before committing any admin-UI change, when the user asks to "check the UI", or as the done-gate a ui-implementer task must pass.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Closes a tracker issue: verifies the work is genuinely done (exit criteria, gates, docs, changelog), writes the close narrative into the PR description, ensures the PR declares `Closes #N`, posts the handoff comment, and deletes the implemented plan file. Use when the user says a work item is complete or asks to close it out.
Runs the CNF 2.0 conformance pipeline (scripts/conformance.sh) — the reference runner over the committed machine-readable catalogue and the acceptance instrument — against the Docker-composed server (or any BYO SUT). Use when the user asks to check conformance, run the conformance/CNF suite, verify spec compliance, or at phase close for the zero-drift gate.
Audits an implemented subsystem, endpoint group, or diff against the vendored openEHR spec text and the CNF Platform Conformance Test Schedule (docs/specs/openehr/), producing a findings list of divergences with spec citations. Use when the user asks "are we following the spec", "audit X against the spec/CNF", before closing a spec-facing phase, or after a conformance failure.
Reads the tracker (GitHub Issues), picks the pinned/top open issue (or the issue the user names), and restates it as a concrete in-session work plan naming the files and crates involved. Use when the user asks "what's next" or "what should I work on".
Prints the tracker's open issues (pinned first), any linked plan file's unchecked tasks, and a short git status. Use when the user asks "where are we", "what's in flight", or at the start of a work session to orient.
Creates a new workspace crate directory (crates/, app/, or tools/) with a Cargo.toml wired to the workspace (inherited package fields, [lints] workspace = true, path deps per the docs/architecture.md dependency arrows), a doc-comment-only lib.rs/main.rs, and the crate's nested CLAUDE.md. Use when a plan calls for standing up a crate that does not exist yet.
| name | ui-gates |
| description | Runs the full admin-UI quality-gate battery for app/ehrbase-admin-ui: clippy on native AND wasm32 targets, nextest, leptosfmt + cargo fmt, and a cargo-leptos build. Use before committing any admin-UI change, when the user asks to "check the UI", or as the done-gate a ui-implementer task must pass. |
| allowed-tools | ["Bash","Read","Grep","Glob"] |
Run every gate the admin console must pass (defined in
.claude/rules/leptos-ui.md §10). Stop and report on the first hard
failure; run the cheap gates first.
app/ehrbase-admin-ui must exist; if it doesn't, say so and stop (it is the
shipped console crate; see tracker issue #152 for the open scope)../target, no
ad-hoc RUSTFLAGS, no flag variation between runs.rustup target list --installed | grep wasm32 (install
with rustup target add wasm32-unknown-unknown if missing);
cargo leptos --version; leptosfmt --version (report if missing —
install is cargo install --locked cargo-leptos leptosfmt, ask before
installing).# 1. Format (fast, catches drift)
cargo fmt -p ehrbase-admin-ui --check
leptosfmt --check app/ehrbase-admin-ui/src
# 2. Clippy — BOTH compilation targets (the wasm pass catches
# server-only deps leaking past the ssr feature gate)
cargo clippy -p ehrbase-admin-ui --all-targets
cargo clippy -p ehrbase-admin-ui --lib --target wasm32-unknown-unknown --no-default-features --features hydrate
# 3. Tests
cargo nextest run -p ehrbase-admin-ui
# 4. Full build (server bin + WASM + assets) — only when the change
# touches the build surface (Cargo.toml, styles, assets, features);
# otherwise report it as skipped-with-reason
cargo leptos build
# 5. E2E journeys (merge-gating in CI; local requires Docker) — Rust-native
# thirtyfour/WebDriver over the composed stack (.claude/rules/leptos-ui.md §10)
bash scripts/ui-e2e.sh
Stage 5 locally: run when Docker is available (docker info); otherwise
report SKIPPED(no docker) — but state explicitly that CI's ui-e2e job
WILL run it and gates the merge, so a skip here is not a pass.
Adjust the exact feature flags to the crate's Cargo.toml (read it first —
the ssr/hydrate feature names are the convention, not a guess).
One line per gate: PASS / FAIL / SKIPPED(reason), with the failing output excerpted verbatim on failure. Never mark a gate green you did not run. A FAIL is never fixed by weakening the gate (removing a lint, deleting a test, dropping the wasm pass) — fix the code.