test-fixtures-factory
Test Fixtures Factory
Generates a typed builder-pattern factory system for test entities — defaults that read like real data, overrides that don't require reconstructing the whole object.
Phase 1: Discovery
Extract before writing:
- Entity shapes — what types/interfaces need factories? Get their definitions.
- Language + test runner — TypeScript with Jest/Vitest, or plain JS?
- ORM/persistence — does the factory need a
.create()method that persists to DB, or just.build()for in-memory objects? - Related entities — do any entities reference others (e.g.,
Posthas anauthor: User)? Need to know nesting depth. - Existing tooling — is
fishery,@anatine/zod-mock, or similar already installed? Or building from scratch? - Unique field constraints — are any fields unique in the DB (email, slug)? These need sequence counters.
If the user pastes entity types, extract shape and relationships directly.
More from blunotech-dev/agents
anti-purple-ui
Enforce a strict monochrome UI with a single high-contrast accent color, removing generic tech gradients and “AI-style” palettes. Use when the user wants minimal, anti-AI, or non-generic aesthetics, or says the UI looks too techy or generic.
9harmonize-whitespace
Align all spacing (padding, margins, gaps) to a consistent 4pt/8pt grid. Use when spacing feels off, inconsistent, cramped, or unbalanced, or when the user asks for a spacing scale or alignment fix.
9typographic-hierarchy
Improve typography by adjusting font sizes, weights, spacing, and contrast to create clear visual hierarchy and readability. Use when text feels flat, unstructured, or when the user asks to refine headings, type scale, or overall readability.
7micro-interaction-adder
Add polished CSS micro-interactions like hover effects, transitions, and feedback states to improve UI feel. Use when the user asks for animations, better UX, or when the interface feels static, plain, or unresponsive.
4consistent-border-radius
Normalizes rounded corners across a file so buttons, inputs, cards, modals, badges, and all UI elements share the exact same curvature. Use this skill whenever the user mentions inconsistent border radii, wants to unify rounded corners, asks to make UI elements look more cohesive, or says things like "make the corners match", "fix the rounding", "unify border radius", "standardize my rounded corners", or "buttons and cards don't match". Also trigger when the user pastes a CSS/HTML/JSX/TSX file and asks for a design consistency pass, border radius is one of the first things to normalize.
4component-split
Analyze a component and determine when and how to split it based on size, responsibility, and reuse signals, producing a refactored structure with clear boundaries. Use when users share large, mixed-concern, or hard-to-test components, or ask about splitting, refactoring, or improving component architecture.
3