Loading...
Loading...
Found 2,598 Skills
Senior-engineer coding standard for Bun/TypeScript, Next.js, and Java (Quarkus) repos. Enforces strict TDD (primary-port SUT, hand-written fakes, no mocks), Clean Architecture (`src/{domain,use-cases,infra,presenter,composition}`), `Result<T, E>` at IO boundaries, branded types at trust boundaries, Bun-only or Maven toolchains (no `class`/`function` declaration/`interface`/`console.*` in TS), Atomic Design, a logic-free design system (no Tailwind in app code), and production disciplines covering privacy (no PII in logs/URLs), tenant isolation, IO deadlines, soft-delete, expand-contract migrations, optimistic locking, observability, AI ports with evals, delivery, accessibility. Use for ANY code task in a Bun, Next.js, or Java repo, covering writing, scaffolding, testing, refactoring, review, React components, APIs, persistence, debugging, security. Consult even when conventions are not mentioned; rules are non-negotiable; violations are rewritten.
Use when testing GitHub Actions workflows locally with act. Covers act CLI usage, Docker configuration, debugging workflows, and troubleshooting common issues when running workflows on your local machine.
Use, debug, or maintain `@wot-ui/cli` and the open-wot repository. This Skill covers wot CLI commands, Agent/MCP integration, doctor/usage/lint, component knowledge queries, client adapters, offline data extraction, build testing, release package inspection, and repository development; if a task directly involves writing wd-* component pages or explaining component APIs, use the wot-ui-v2 Skill instead.
Test a macOS app at three levels, from Swift Testing unit tests and an in-app self-test to a debug bridge that lets an agent drive the running app and read its state, plus computer use for real clicks. Use when adding logic, fixing a bug, before a release, or when the user asks for tests, end-to-end checks, or "make sure it works".
Trigger this skill when the task is to assess "how the legal outcome would differ if a given fact, conduct, or condition did not exist or were changed." Typical trigger scenarios include causation analysis (whether the harm would still have occurred but for the conduct), allocation of fault and degree of liability, determination of the scope of damages, calculation of contractual breach losses, hypothetical legality testing of administrative acts, assessment of intervening causes in criminal causation, legislative impact assessment, and more. The core method is to construct a "counterfactual world" that differs from the real world only with respect to the target variable, compare the outcomes of the two worlds, and thereby determine the target variable's contribution to the outcome.
Guide for creating effective skills. This command should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations. Use when creating new skills, editing existing skills, or verifying skills work before deployment - applies TDD to process documentation by testing with subagents before writing, iterating until bulletproof against rationalization
Create and configure git hooks with intelligent project analysis, suggestions, and automated testing
Test REST and GraphQL APIs for authentication bypasses, authorization flaws, IDOR, mass assignment, injection attacks, and rate limiting issues. Use when pentesting APIs or testing microservices security.
Build websites with Bascik, the zero-runtime HTML component build tool. Use whenever a project depends on @bascik/bascik, has a bascik.config.ts, or keeps components in src/components/*.html, or when the user mentions Bascik. Covers pages, components, slots, props, attribute inheritance, the bascik CLI (dev, --build, --server, --check, add), project layout, verifying compiled dist/ output, building a new site, and copying tested example components. Start here; companion skills cover components, compatibility, scripts, SEO, config, testing, and migration.
Systematically isolate and fix frontend bugs using reproduction, instrumentation, hypothesis testing, and regression prevention.
Test quality guard - prevents testing mock behavior, production pollution with test-only methods, and mocking without understanding dependencies.
Agent testing methodology - run agents with test inputs, observe outputs, iterate until outputs are accurate and well-structured.