메뉴
Generates test plans, writes unit/integration/E2E test files, identifies coverage gaps, flags common testing anti-patterns. Use when writing tests, creating test suites, planning test strategies, mocking dependencies, measuring code coverage, or test planning.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | testing-workflow |
| description | Generates test plans, writes unit/integration/E2E test files, identifies coverage gaps, flags common testing anti-patterns. Use when writing tests, creating test suites, planning test strategies, mocking dependencies, measuring code coverage, or test planning. |
| Rule | Detail |
|---|---|
| One suite per session | Never run all suites in one conversation |
| Max 3 screenshots | Per session |
evaluate_script() over take_snapshot() | Returns less data |
| Reload between flows | Clears state |
| Log results | Append to .opencastle/logs/e2e-results.md |
Suite files: see .opencastle/project.instructions.md.
| Category | What to cover |
|---|---|
| Initial state | Page loads with defaults; components in expected state |
| User interactions | Buttons, dropdowns, filters (URL params + refetch), form validation |
| State transitions | Filter changes produce different results; loading states; backend sync |
| Edge cases | Empty results, min/max boundaries, invalid input, network errors |
| Integration | Data flow server→UI, URL params↔state, server vs client filtering |
| Responsive (MANDATORY for UI) | All breakpoints per browser-testing skill / validation-gates Gate 3 |
| Layer | Minimum |
|---|---|
| Unit (functions, components, hooks) | 95% |
| Integration (boundaries, URL sync) | All boundaries |
| E2E (journeys, interactions, errors) | All critical paths |
| Anti-Pattern | Correct Approach |
|---|---|
| Testing only initial page load | Test filter changes, different results |
| Assuming filters work because they render | Verify each option changes results |
| Client-side only | Verify server requests are triggered |
| Single scenario | Test urban, rural, edge, out-of-range |
| Visual inspection only | Verify data values programmatically |
# Unit / integration
npx vitest run --coverage # all tests + coverage
npx vitest run src/utils.test.ts # single file
# E2E (Playwright)
npx playwright test # all E2E suites
npx playwright test --ui # interactive mode
// Unit test with mock
import { describe, it, expect, vi } from 'vitest';
import { fetchItems } from './api';
describe('fetchItems', () => {
it('returns filtered results', async () => {
vi.spyOn(global, 'fetch').mockResolvedValue(
new Response(JSON.stringify([{ id: 1, name: 'test' }]))
);
const items = await fetchItems({ category: 'active' });
expect(items).toHaveLength(1);
expect(fetch).toHaveBeenCalledWith(expect.stringContaining('category=active'));
});
});
// E2E test (Playwright)
import { test, expect } from '@playwright/test';
test('filter updates results and URL', async ({ page }) => {
await page.goto('/items');
await page.getByRole('combobox', { name: 'Category' }).selectOption('active');
await expect(page).toHaveURL(/category=active/);
await expect(page.getByRole('listitem')).not.toHaveCount(0);
});
| Resource | Purpose |
|---|---|
| browser-testing skill | Chrome DevTools automation for E2E |
| validation-gates Gate 3 | Responsive breakpoint checks |
project.instructions.md | Suite files, project-specific test config |
Scaffolds production-ready monorepo projects using the backbone CLI: configures workspace packages, wires build tooling, sets up CI pipelines, and initializes framework/backend/CMS integrations. Use when creating, bootstrapping, or initializing a new application, project, starter template, or monorepo from scratch. Trigger terms: scaffold, bootstrap, init, new repo, new app, boilerplate, starter, greenfield.
Resolves task dependencies, generates machine-actionable delegation specs, structures phased subtask plans for multi-agent work. Use when writing delegation specs, resolving task dependencies, building phased subtask plans for multi-agent work, assigning work to sub-agents, or partitioning a feature into parallelizable phases.
Reviews mature LESSONS-LEARNED.md entries, rewrites them as permanent rules in skill/instruction files, archives graduated lessons. Use when graduating lessons into skills, promoting validated lessons, updating skills from past learnings, archiving mature lessons, codifying repeated patterns, or cleaning up a crowded LESSONS-LEARNED.md.
Logs sessions, tracks activity, records delegation decisions, and stores review/dispute outcomes as NDJSON audit trails. Use when logging session activity, tracking work, recording decisions, building audit trails, capturing delegation history, or running pre-response verification checklists. Trigger terms: log, track activity, audit trail, session record, delegation log, NDJSON
Enforces React-specific patterns: functional components with hooks, TypeScript prop interfaces, CSS Modules co-location, React Testing Library behavioral tests. Use when creating React components, writing custom hooks, structuring component folders, applying RTL test patterns, or wiring TypeScript prop types. Trigger terms: React, .tsx, component, hook, RTL, jsx, useState, useEffect, prop interface
Implements technical SEO: meta tags, JSON-LD structured data, sitemaps, crawlability fixes. Use when adding schema markup, JSON-LD, robots.txt updates, canonical URLs, Open Graph tags, or improving crawlability.