Unit Testing

Coordinates adaptive QA testing across behavioral, contract, and regression dimensions. Routes to specialized sub-agents based on context and depth.

Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup

Validates Jupyter notebook execution, outputs, and educational quality metrics

This skill should be used when Claude needs to determine what to test, design test structures, follow TDD practices, or decide when to skip tests. Trigger phrases include "write tests", "TDD approach", "test coverage", "what should I test", "testable vs non-testable".

Perform a code review focused on bugs, risks, regressions, and missing tests.

Workspace-first R statistics suite with subskills and agent-run metaskills (including run-demo for guided onboarding, explain-statistics for concept explanations, explain-results for interpreting outputs, format-document for NLSS format alignment, screen-data for diagnostics, check-assumptions for model-specific checks, and write-full-report for end-to-end reporting) that produce NLSS format tables/narratives and JSONL logs from CSV/SAV/RDS/RData/Parquet. Covers descriptives, frequencies/crosstabs, correlations, t-tests/ANOVA/nonparametric, regression/mixed models, SEM/CFA/mediation, EFA, power, reliability/scale analysis, assumptions, plots, missingness/imputation, data transforms, and workspace management.

Testing guide for GRE projects covering pytest-django (backend) and Vitest (frontend).Use when: writing tests, debugging test failures, setting up test fixtures, mocking.Triggers: test, pytest, vitest, unittest, mock, fixture, TestCase, assert, coverage, TDD

This skill should be used when working on Obsidian plugins, testing plugin changes, verifying plugin UI, debugging plugin behaviour, or running automated tests against Obsidian. Also triggers on "start Obsidian", "take Obsidian screenshot", "test plugin", "run plugin command", "execute in Obsidian", or any Obsidian automation task. Use proactively during plugin development to verify changes visually.

Update a Raycast extension to the latest version

Level 1 patterns - test-watch, integration-test, complexity, loc, duplicates, slowtests

PolicyEngine period handling - converting between YEAR, MONTH definition periods and testing patterns

Write async tests with tokio::test and configure multi-threaded test runtimes. Use when testing async code.

Checklist for finishing work, pushing a branch, and opening a ready-for-review PR with tests and tracker updates.

Standards and best practices for writing effective tests including the testing pyramid, test structure patterns, and coverage guidelines

Frontend-Entwicklung für Claude Code Archive Backoffice UI.Next.js 16, React 19, Tailwind CSS 4, shadcn/ui, Better Auth.Feature Slices Architektur mit Dependency Injection.Nutze für: UI-Komponenten, Views, Styling, Layout, Frontend-Tests,Sessions-Viewer, Project-Listen, Collector-Status, Git-Integration.Hohe Informationsdichte, professionelles Business-App Design.

Database access layer guidelines for Quantum Skincare's Prisma-based data-access library. Covers Prisma schema design, DAO patterns, UUID primary keys, PostgreSQL role-based access control (RBAC), migration workflows, type-safe queries, transaction handling, soft deletes, and testing strategies. Use when working with Prisma schema, DAOs, database migrations, or data access patterns in libs/data-access.

Autonomous GitHub repository discovery and integration agent that hunts relevant open-source projects for BidDeed.AI (foreclosure auctions) and Life OS (productivity/ADHD). Searches GitHub for repos matching domain keywords, evaluates relevance via README/tech stack analysis, auto-adds as submodules or archives to target repos, and alerts Ariel with actionable summaries. Use when (1) User requests "find relevant GitHub repos", (2) Exploring new integrations for BidDeed.AI workflows, (3) Discovering productivity tools for Life OS, (4) Keeping repositories updated with latest open-source innovations.

Generate step-by-step walkthrough guides for testing features or bug fixes. Use when the user asks to create testing instructions, QA guides, walkthrough documentation, or says something like "write a walkthrough" or "create testing steps" after implementing a feature.

Critical fix for backtest capital accounting when equity curves are inflated or drawdown metrics are meaningless

Use when tests/test_code_patterns.py fails - fixes recurring anti-patterns with documented root causes and verification