kreek
UserEngineering quality focused skills for AI coding agents that keep humans in the loop.
Categories
Indexed Skills (25)
ship
Run Consult's guarded maintainer flow for commit, merge, version bump, validation, and push.
accessibility
Use for accessible UI, WCAG, ARIA, keyboard, focus, contrast, inclusive states.
api
Use for REST API contracts: endpoints, fields, evolution, status codes, errors, pagination, idempotency.
architecture
Use for architecture decisions, module boundaries, coupling, layering, system shape.
async-systems
Use for async systems, concurrency, queues, streams, pub/sub, ordering, backpressure.
code-review
Use to review diffs and PRs for bugs, regressions, edge cases, proof, merge readiness.
commit
Use for staging reviewed work, commit splits, messages.
database
Use for databases, schemas, migrations, indexes, transactions, query plans, locking.
debugging
Use to debug failures, reproduce symptoms, isolate causes, inspect evidence, fix bugs.
documentation
Use for docs describing existing code: READMEs, runbooks, API docs, module docs, comments.
domain-modeling
Use for domain modeling, data shapes, invariants, state transitions, parsing, effects.
error-handling
Use when failure contracts matter: error types, propagation, retries, recovery, user-facing messages.
git-workflow
Use for branches, history edits, conflicts, rebases, recovery, force-push, gh.
observability
Use for production observability: logs, metrics, traces, health, dashboards, alerts, SLOs; not debug prints.
performance
Use for performance, profiling, latency, throughput, allocation, caching, hot paths.
proof
Use for proof and tests, claims, invariants, behavior specs, edge cases, evidence.
refactoring
Use for refactoring, behavior-preserving change, tests, safe rewrites.
release
Use only on request/approval for release prep, or when validation requires release artifact sync.
scaffolding
Use for scaffolding, new projects, package setup, quality tooling, CI, repo structure.
security
Use when auth, secrets, crypto, trust boundaries, dependency risk, or untrusted input are at stake.
specify
Use to design before building: discovery, tradeoffs, ADRs, RFCs, tech specs, and decisions needing user agreement.
ui-design
Use for frontend UI, layouts, components, responsive behavior, accessibility, WCAG, keyboard, focus.
workflow
Use first for any feature, bug fix, refactor, debug, test, or config task to route risks, pick skills, define proof.
technical-writing
Use for forward-looking docs: design docs, ADRs, RFCs, tech specs, PRDs, requirements, system analyses, strategy.
official-source-check
Use for version-sensitive framework, library, SDK, or platform behavior: upgrades, deprecations, current APIs.
Bio shown is the top-scored skill's repo description as a fallback — real GitHub bios land in a future update.