From blueprint
Create tests following project conventions with proper factories and real implementations. Triggers on "/bp-test", "/test", "write tests", "create tests", "add tests for", or any request to create new test files. Also triggers on "test this", "write a test for", "feature test", "unit test", or any request to generate test code. Uses the project's test runner and conventions detected from configuration.
npx claudepluginhub skaisser/blueprint-pluginThis skill uses the workspace's default tool permissions.
Read `blueprint/.config.yml` → `language`. If `auto`, detect from the user's messages. All generated content MUST be in the detected language. Skill instructions stay in English — only output changes.
Provides UI/UX resources: 50+ styles, color palettes, font pairings, guidelines, charts for web/mobile across React, Next.js, Vue, Svelte, Tailwind, React Native, Flutter. Aids planning, building, reviewing interfaces.
Fetches up-to-date documentation from Context7 for libraries and frameworks like React, Next.js, Prisma. Use for setup questions, API references, and code examples.
Analyzes competition with Porter's Five Forces, Blue Ocean Strategy, and positioning maps to identify differentiation opportunities and market positioning for startups and pitches.
Share bugs, ideas, or general feedback.
Read blueprint/.config.yml → language. If auto, detect from the user's messages. All generated content MUST be in the detected language. Skill instructions stay in English — only output changes.
Create tests for: $ARGUMENTS
NEVER mock what you can test. Use real implementations, real database, real factories. Mocks hide bugs — real integrations catch them.
Only mock when you literally cannot use the real thing:
Everything else — models, services, repositories, jobs, events, notifications, components — test with real implementations.
blueprint/.config.yml or project files (Pest, Jest, pytest, etc.)blueprint/.config.yml → languageFollow the project's test organization patterns. Tests should be:
// BAD: Random values cause flaky tests
create a record with all defaults
// GOOD: Explicit values for business-logic fields
create a record with specific status, type, and relationships set explicitly
For every piece of code, consider:
| Instead of mocking... | Do this |
|---|---|
| Database models | Use factories with real persistence |
| Input validation | Submit real request, assert validation errors |
| UI components | Use component testing with real props |
| Jobs & queues | Use queue faking only to assert dispatch, test job logic directly |
| Events | Use event faking only to assert dispatch, test listener logic directly |
| Notifications | Use notification faking to assert sent, test content directly |
| Services/repositories | Use real instances with real database |
AskUserQuestion tool, never plain text questionsUse $ARGUMENTS as the code path, class name, or feature to test.