176 skills · sorted by relevance
Keep comparison answers readable in a terminal about 100 columns wide. Limits Markdown tables to four columns with short phrases, and switches to lists or per-item headings when the content needs longer explanations.
Add a new exchange integration to CCXT using TypeScript and established exchange templates. Follow guidance for unified methods, data conversion, authentication, sandbox settings, recorded API test data, documentation, and checks across generated language implementations.
Evaluate how Chatbox answers questions about large attachments using synthetic and real documents. Check whether the model retrieves file content when needed, skips retrieval for unrelated requests, and investigate failures through the actual application flow.
Create and organize Python tests with pytest. Use reusable setup, mock replacements for external services, controlled test time, and coverage reports to check normal behavior, failures, retries, and interactions between application components.
Write JavaScript and TypeScript tests with Jest, Vitest, and Testing Library. Covers functions, UI components, and APIs, including mock replacements for external services, reusable test data, and setup for automated testing.
Write focused C# unit tests with XUnit, including tests that run against multiple input datasets. Apply consistent naming, setup, assertions, shared fixtures, and mock dependencies to keep tests readable, independent, and organized.
Reproduce Mastra Code bugs with a real model and compare timestamped logs across network, streaming, execution, and terminal interface layers. Use the evidence to locate timing problems, incorrect token rates, flicker, or stuck status displays.
Creates test starters for React and Next.js applications and analyzes coverage reports to find untested code. Supports unit, integration, and browser-based tests, simulated API responses, reusable test data, and test runner configuration.
Create unit test scaffolds, sample data, and mocks from code or specifications. Analyze coverage reports to prioritize missing tests, and guide test-driven development through failing tests, minimal implementation, and refactoring.
Capture before and after screenshots of Lite UI changes on a local machine, compare the images, and publish changed screens to a pull request. It also guides screenshot coverage checks and updates to an existing comment.
Create, update, run, and debug shell-based performance scenarios for the but CLI. It separates repository setup from the operation being measured, uses Hyperfine for timing, and guides focused validation and inspection of test output.
Maintain LangBot skill assets by organizing operating rules, reference guides, test cases, fixtures, and troubleshooting entries. Check existing material before adding files, keep detailed instructions in one place, and verify that indexes stay current.
Create Playwright tests that check user journeys in a browser. The skill organizes reusable page interactions, configures test environments, investigates intermittent failures using execution traces, and supports API mocking, visual comparisons, and automated pipeline integration.
Change a running OpenRig setup by adding or removing agent seats, connecting existing sessions, or attaching terminals. Guides checks for roles, startup context, permissions, and session identity so the setup reflects each change correctly.
Opinionated Rails conventions: rich models, concerns, CRUD-everything, state-as-records, minimal dependencies, Minitest with fixtures. Load this skill BEFORE any code-level thinking, not only before editing a file. It is required the moment a task touches Rails code in ANY way: designing or even just discussing a data model, schema, migration, entity, association, field, validation, class, or method name; writing, planning, reviewing, analyzing, testing, debugging, or refactoring; or proposing any model, table, column, route, or code snippet inline in chat. If you are about to name a model or sketch a column you are already in scope, even in an exploratory back-and-forth where no file is written yet. Do not let a "we're just discussing" framing defer it. Do NOT use for non-Rails backends, NestJS, or general architecture (use nestjs-modular-monolith or coding-guidelines).
The English summary is being prepared. Showing the original description.
Test a playable browser game end to end with deterministic fixtures and real browser evidence. Use for gameplay QA, regression testing, controls, accessibility, responsive/mobile testing, save flows, console checks, performance smoke tests, and release verification.
The English summary is being prepared. Showing the original description.
Design, implement, tune, or test Three.js action-game encounters. Use for arena layout, enemy composition, spawn pacing, objectives, boss phases, reward cadence, encounter fixtures, and difficulty validation.
The English summary is being prepared. Showing the original description.
Build or refactor reusable, data-driven enemy archetype and moveset systems for Three.js action games. Use for enemy content schemas, model and rig conventions, combat move timing and contact contracts, runtime state boundaries, placeholder fallbacks, deterministic fixtures, or production playthrough validation.
The English summary is being prepared. Showing the original description.
Build, integrate, audit, or refactor rigged monsters for Three.js and web action games. Use for monster asset contracts, procedural or imported creature rigs, semantic joints and sockets, hurtboxes and attack volumes, combat animation states, enemy-runtime adapters, LODs, deterministic review fixtures, and validating that every monster follows one shared system.
The English summary is being prepared. Showing the original description.
Vitest fast unit testing framework powered by Vite with Jest-compatible API. Use when writing tests, mocking, configuring coverage, or working with test filtering and fixtures.
The English summary is being prepared. Showing the original description.
Maintain model-routing audit golden fixtures and expected outputs.
The English summary is being prepared. Showing the original description.
Review pull requests to code-graph-rag, a multi-language code graph parser. Focuses on graph-edge correctness in language parsers, cross-language consistency, and test fixtures that actually exercise the fix.
The English summary is being prepared. Showing the original description.
Page Object Model patterns for Playwright — when to use POM, how to structure page objects, and when fixtures or helpers are a better fit.
The English summary is being prepared. Showing the original description.
Battle-tested Playwright patterns for E2E, API, component, visual, accessibility, and security testing. Covers locators, assertions, fixtures, network mocking, auth flows, debugging, and framework recipes for React, Next.js, Vue, and Angular. TypeScript and JavaScript.
The English summary is being prepared. Showing the original description.