rubentalstra

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.

Regenerates the openEHR spec + ITS layer from the vendored specs (emit / emit-xml / emit-rest) and checks for drift. Use after changing the openehr-codegen emitter or bumping a vendored spec, or when asked to regenerate the generated crates or run the codegen drift check.

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.

Stage and commit the current changes as a single Conventional Commit that passes this repo's commit-msg rules. Use when the user asks to commit work in OpenWorkspace.

Scaffold a new workspace crate or app the OpenWorkspace way — edition 2024, inherited lints, thiserror error type, thin facade lib.rs. Use when adding a new member under crates/ or apps/.

Scaffold and apply a sqlx database migration the OpenWorkspace way, then refresh the offline query cache. Use when adding or changing the PostgreSQL schema in crates/db.

Run the full OpenWorkspace quality gate and report pass/fail per check before opening or updating a PR. Use when the user wants to verify a branch is green, or is about to push or open a PR.

Comprehensive Rust coding guidelines with 265 rules across 26 categories. Use when writing, reviewing, or refactoring Rust code. Covers ownership, error handling, async patterns, concurrency, unsafe code, API design, memory optimization, performance, numeric safety, conversions, serde, pattern matching, macros, closures, observability, testing, and common anti-patterns. Invoke with /rust-skills.

Query CDISC standards definitions (SDTM, ADaM, SEND, CT)

Export SDTM domains to XPT or XML format

Run tests for a specific crate or domain

Run CDISC validation checks on a domain DataFrame

Zod v4 best practices, patterns, and API guidance for schema validation, parsing, error handling, and type inference in TypeScript applications. Covers safeParse, object composition, refinements, transforms, codecs, branded types, and v3→v4 migration. Baseline: zod ^4.0.0. Triggers on: zod imports, z.object, z.string, z.infer, safeParse, mentions of "zod", "schema validation", "zod v4", or "z.enum".