Delegate independent tasks to specialized agents working concurrently with isolated context.
295.4K 206.3K
View 
Test Discipline
test-discipline
Update tests when changing APIs — no exceptions
SKILL.md
Full skill instructions
Context
When APIs or public interfaces change, tests must be updated in the same commit. When test assertions reference file counts or expected arrays, they must be kept in sync with disk reality. Stale tests block CI for other contributors.
Patterns
- API changes → test updates (same commit): If you change a function signature, public interface, or exported API, update the corresponding tests before committing
- Test assertions → disk reality: When test files contain expected counts (e.g.,
EXPECTED_FEATURES,EXPECTED_SCENARIOS), they must match the actual files on disk - Add files → update assertions: When adding docs pages, features, or any counted resource, update the test assertion array in the same commit
- CI failures → check assertions first: Before debugging complex failures, verify test assertion arrays match filesystem state
Examples
✓ Correct:
- Changed auth API signature → updated auth.test.ts in same commit
- Added
distributed-mesh.mdto features/ → added'distributed-mesh'to EXPECTED_FEATURES array - Deleted two scenario files → removed entries from EXPECTED_SCENARIOS
✗ Incorrect:
- Changed spawn parameters → committed without updating casting.test.ts (CI breaks for next person)
- Added
built-in-roles.md→ left EXPECTED_FEATURES at old count (PR blocked) - Test says "expected 7 files" but disk has 25 (assertion staleness)
Anti-Patterns
- Committing API changes without test updates ("I'll fix tests later")
- Treating test assertion arrays as static (they evolve with content)
- Assuming CI passing means coverage is correct (stale assertions can pass while being wrong)
- Leaving gaps for other agents to discover
More Other skills
Other
brand-guidelines
Applies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply.
179.7K 100.1K
View Other
theme-factory
Toolkit for styling artifacts with a theme. These artifacts can be slides, docs, reportings, HTML landing pages, etc. There are 10 pre-set themes with colors/fonts that you can apply to any artifact that has been creating, or can generate a new theme on-the-fly.
179.7K 89.5K
View Other
internal-comms
A set of resources to help me write all kinds of internal communications, using the formats that my company likes to use. Claude should use this skill whenever asked to write some sort of internal communications (status reports, leadership updates, 3P updates, company newsletters, FAQs, incident reports, project updates, etc.).
179.7K 76.1K
View Fundamental design principles for writing maintainable, testable Python code.
40.2K 21.9K
View 
Other
responsive-design
Modern responsive layouts using container queries, fluid typography, CSS Grid, and mobile-first strategies.
40.2K 20K
View Generate Playwright tests from scenarios using interactive browser exploration and validation.
39.7K 18.2K
View Automated website exploration and test case generation using Playwright.
39.7K 14.9K
View Modern React state management with Redux Toolkit, Zustand, Jotai, and React Query for every state category.
40.2K 14.7K
View Other
gdpr-data-handling
GDPR-compliant data handling with consent management, data subject rights, and privacy controls.
40.2K 14.3K
View Python error handling patterns including input validation, exception hierarchies, and partial failure handling. Use when implementing validation logic, designing exception strategies, handling batch processing failures, or building robust APIs.
40.2K 13.5K
View 
Other
refactor-plan
Detailed multi-file refactor planning with safety checks and rollback guidance.
39.7K 13K
View