Menu
Test planning, generation, and execution -- unit, integration, and end-to-end testing workflows
The review-first prompt is selected by default. You can switch to a direct command or download a local copy.
Read SKILL.md and any companion files shown by SkillsMP before deciding whether to install.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
A direct command skips the review prompt. Inspect the source before running it.
npx skills add https://github.com/InugamiDev/ultrathink-oss --skill testThe command stays on one line. Scroll horizontally to inspect it before copying.
Prefer a local copy? Download the files currently available to SkillsMP.
Unified design foundations — design system architecture, tokens, component specs, visual principles, creative vision, figma integration, plus brand design system loader (66 real brands via DESIGN.md). Absorbs design, design-system, design-systems, design-principles, design-router, creative-vision, figma, design-md.
Render, summarize, and present markdown documents and structured content in multiple output modes
Ultra UI skill - combines Google's DESIGN.md spec (machine-readable design tokens) with the ui-ux-pro-max knowledge base (91 styles, 161 palettes, 73 font pairings, 161 products, 104 UX guidelines, 25 chart types). Generates lint-clean DESIGN.md files, validates token references and WCAG contrast, exports Tailwind/DTCG tokens, and diffs design systems version-over-version.
Based on SOC occupation classification
Showing SKILL.md
| name | test |
| description | Test planning, generation, and execution -- unit, integration, and end-to-end testing workflows |
| layer | hub |
| category | workflow |
| triggers | ["/test","write tests","test this","add test coverage","run the tests","check if tests pass"] |
| inputs | [{"target":"Code, feature, or file(s) to test"},{"testType":"unit | integration | e2e | all (optional, defaults to appropriate type)"},{"framework":"Test framework to use (optional, auto-detected from project config)"}] |
| outputs | [{"testPlan":"Strategy document listing what to test and why"},{"testFiles":"Generated test file(s) with complete test cases"},{"testResults":"Output from running the tests"},{"coverageReport":"Coverage summary for the tested area (if available)"}] |
| linksTo | ["scout","debug","fix","code-review"] |
| linkedFrom | ["fix","refactor","optimize","cook","team","ship"] |
| preferredNextSkills | ["code-review","fix"] |
| fallbackSkills | ["debug","scout"] |
| riskLevel | low |
| memoryReadPolicy | selective |
| memoryWritePolicy | selective |
| sideEffects | ["Creates or modifies test files","Runs test commands","May install test dependencies"] |
Plan, generate, and execute tests that verify code correctness, prevent regressions, and document expected behavior. This skill covers the full testing lifecycle from strategy through execution.
Tests are not bureaucracy. Tests are executable documentation that proves your code works.
Use when you need to decide WHAT to test before writing tests.
tests/ directory, __tests__ folders)# Test Plan: [Target]
## Target
[What is being tested]
## Test Infrastructure
- **Framework**: [name + version]
- **Runner command**: [command]
- **Test location**: [where tests should go]
## Unit Tests
| Test | Input | Expected Output | Edge Case? |
|------|-------|----------------|------------|
| [function] handles valid input | [input] | [output] | No |
| [function] handles empty input | [] | [] or error | Yes |
| [function] handles null | null | throws TypeError | Yes |
## Integration Tests
| Test | Components | Scenario |
|------|-----------|----------|
| [feature] happy path | A + B + C | [description] |
| [feature] error propagation | A + B | [description] |
## Edge Cases to Cover
- [edge case 1]
- [edge case 2]
[thing]: [reason -- e.g., "covered by upstream tests"]
Use when you need to WRITE tests.
Read the target code thoroughly.
Read existing tests in the same area to match conventions.
Generate tests following these principles:
it('returns 404 when user does not exist')Test file structure:
describe('[ModuleName]', () => {
describe('[functionName]', () => {
// Setup shared across this function's tests
beforeEach(() => { /* ... */ });
it('does X when given Y', () => {
// Arrange
const input = createTestInput();
// Act
const result = functionName(input);
// Assert
expect(result).toEqual(expectedOutput);
});
it('throws when given invalid input', () => {
expect(() => functionName(null)).toThrow(ValidationError);
});
it('handles edge case: empty array', () => {
const result = functionName([]);
expect(result).toEqual([]);
});
});
});
Mocking strategy:
Write the test file using the Write tool (new file) or Edit tool (adding to existing).
Use when you need to RUN tests and interpret results.
npm test -- path/to/test.tsnpm test -- --testNamePattern="test name"npm testnpm test -- --coveragefix)/test Plan tests for the authentication module
/test Write unit tests for src/lib/utils/formatDate.ts
/test Run the test suite and report results
/test Write a regression test for the bug fixed in src/lib/orders.ts
/test Improve test coverage for the payment processing module
Target: formatCurrency(amount: number, currency: string): string
Generated tests:
formatCurrency(10.5, 'USD') returns '$10.50'formatCurrency(0, 'USD') returns '$0.00'formatCurrency(-5, 'USD') returns '-$5.00'formatCurrency(1000000, 'USD') returns '$1,000,000.00'formatCurrency(10.5, 'EUR') returns 'EUR10.50' (or locale-appropriate)formatCurrency(10.5, 'INVALID') throws UnsupportedCurrencyErrorformatCurrency(NaN, 'USD') throws InvalidAmountErrorformatCurrency(Infinity, 'USD') throws InvalidAmountErrorTarget: User registration flow (API endpoint + database + email)
Generated tests:
/api/register with valid data creates user and sends welcome email/api/register with existing email returns 409 Conflict/api/register with invalid email returns 400 with validation errors/api/register when email service is down creates user but logs email failureit('does not crash when API returns error without items field (fixes #123)').