Skill UI

A five-axis code review checklist covering correctness, security, readability, performance, and test coverage to produce actionable comments instead of style nitpicks. Use for reviewing code, diffs, or pull requests.

This skill develops and verifies mathematical proofs using the Lean theorem prover. It handles creating new proofs, continuing incomplete projects, and auditing existing formalizations to ensure they match original statements. It connects inputs to lemmas, assembles theorems, and checks axioms for reproducibility. Use it for formal verification tasks rather than ordinary drafting.

Edit mathematically, empirically, or technically dense papers for readers outside the author's specialty, including empirical legal scholarship, law-and-economics models, and legal-technology research. Clarifies terminology, antecedents, study design, and claim-statistic relationships while checking equations, numbers, quotations, and citations against the source. Use to clarify exposition or de-jargonize a technical draft; not to rewrite briefs or doctrinal arguments. Produces an edited draft and audit memo. Full integrity checks and original-format rendering require suitable extraction, c...

Standardized audit register for Soroban Rust smart contracts on Stellar: tracks authorization checks, panic pathways, integer overflows, storage footprint and remediation status, exporting CSV, SQL DDL and JSON Schema compliance artifacts.

Proofreads English technical writing such as READMEs, API references, tutorials and blog drafts for typos, grammar, punctuation, terminology consistency and structure. Returns an itemized Original → Suggestion → Reason checklist with statistics, never rewriting the document.

A browser runtime skill that provides isolated WPE WebKit sessions, native input, screenshots, and ordered JSONL automation. Supports docker-based container lifecycle, deterministic testing, and GitHub Actions verification. Useful for reproducible browser checks and self-hosted runtime integration.

Build or fix frontends to look designed, not AI-generated. Includes taste direction, craft floor checklists, and browser-based quality gate that renders pages at phone and desktop widths, catching overlap, low contrast, and AI-slop defaults. Proof before calling work done.

Perform evidence-backed impact analysis before changing code, data, interfaces, or governance documents, and compare planned impact with actual diff after implementation. Covers call paths, data/schema, API contracts, tests, docs, ADRs, deployment, migration, and rollback. Use for cross-module or high-risk changes, database migrations, authentication, public interfaces, blast-radius questions, pre-change checks, and post-implementation alignment.

A step-by-step workflow for UI work: understand the project, choose the right plan (new screen, dashboard, polish, simplify, review), then render, fix, and re-check until the result looks right. It helps agents build real, polished interfaces and avoid AI slop.

Safely rebase the checked-out feature branch onto the latest upstream default branch, detecting main or master and handling conflicts without discarding work.

This tool builds, tests, upgrades, deploys, and verifies Power Apps Component Framework (PCF) controls for model-driven apps and Power Pages. It handles quality gates, deployment, registration verification, and troubleshooting for field and dataset controls. Supports canvas app setup and inventory checks.

Write Quarkus application code including REST APIs, validation, OpenAPI, CDI, Hibernate ORM, and reactive messaging. Configure extensions, manage security with OIDC, and implement observability features like health checks and metrics. Use this skill for implementing or modifying features in existing Quarkus projects, ensuring proper build-time resolution and virtual thread usage.