Explore skills

QA testing for Streamlit applications — locally or on Hugging Face Spaces. Covers app startup, UI rendering, Streamlit-specific checks (session state, widgets, forms, caching), clinical content accuracy, HF Spaces compatibility, and accessibility. Produces a structured QA report with PASS/FAIL/PARTIAL status.

Clinical safety code review against DCB0129/DCB0160 and NHS Digital standards. This is NOT a general code review — it is a clinical safety audit for tools handling clinical data, calculations, decision support, or patient-facing information. Produces a hazard register, required mitigations, and a release recommendation.

TypeScript and Angular coding best practices. Use when working with TypeScript, Angular, or Node.js files: implementation, testing, refactoring, RxJS Observables, type system, strict mode, generics, and async patterns.

Turn a product problem, idea, observation, or business goal into a clear testable experiment hypothesis. Use this skill when the user has an idea or problem but not yet a properly structured hypothesis for an A/B test or product experiment.

Check and strengthen the alignment between team-level goals (OKRs, KPIs) and company strategy. Use this skill when goals have been set but their connection to strategy is unclear, inconsistent, or contested.

Deploy code to production via feature branch → test → staging → PR → merge. Use when deploying changes, pushing to production, or when the user says "deploy", "push to prod", "merge to main", "stage this", or "ship it".

Help address review/issue comments on the open GitHub PR for the current branch using gh CLI; verify gh auth first and prompt the user to authenticate if not logged in.

Use when a user asks to debug or fix failing GitHub PR checks that run in GitHub Actions; use `gh` to inspect checks and logs, summarize failure context, draft a fix plan, and implement only after explicit approval. Treat external providers (for example Buildkite) as out of scope and report only the details URL.

Use when Code implementation and refactoring, architecturing or designing systems, process and workflow improvements, error handling and validation. Provide tehniquest to avoid over-engineering and apply iterative improvements.

Full QA pass: run all tests, check types, catch regressions, write missing tests. Use when the user says "run tests", "QA", "verify changes", "check for regressions", "test everything", or "make sure it works".

Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.

Write tests for the Travmaskinen codebase — backend (pytest, async, FastAPI), frontend (Vitest + React Testing Library), or E2E (Playwright). Use this skill whenever writing new tests, adding test coverage, implementing TDD red-green-refactor cycles, or when the user says "write tests", "add tests", "test this", "cover this", "TDD", or asks for test coverage on any module. Also triggers when imple