tdd
Test-Driven Development (TDD)
Apply this skill to execute strict test-first development: write a failing test, implement the minimum code to pass, then refactor while keeping tests green.
Decide when to use TDD
Use this decision table:
| Situation | Use this skill? | Default action |
|---|---|---|
| New utility function | Yes | Run TDD cycle immediately |
| New Effect service | Yes | Define behavior through tests first |
| Complex business logic | Yes | Lock behavior with tests before implementation |
| Bug fix | Yes | Reproduce bug with failing test first |
| UI styling/layout-only change | No | Use standard implementation flow |
| Exploratory prototyping | No | Prototype first, then switch to TDD once behavior stabilizes |
| TRPC endpoint (simple CRUD) | Usually no | Use testing-patterns by default; use this skill only when user explicitly requests test-first/RGR |
More from blogic-cz/blogic-marketplace
marketing-expert
This skill should be used when writing or rewriting marketing copy for software products, including positioning, messaging, homepage rewrite work, landing pages, product descriptions, conversion-focused updates, and sales-enablement content. Produces clear, truthful, high-performing SaaS copy.
97requirements
This skill should be used when clarifying a feature, writing a requirements spec, running a structured discovery session, or when users mention requirements-start, requirements-status, requirements-current, requirements-list, requirements-remind, or requirements-end.
78frontend-design
This skill should be used when a task requires designing or implementing frontend UI (components, pages, layouts, styling) and no more specialized frontend skill is a better fit. It guides production-grade, brand-consistent visual implementation with distinctive but controlled aesthetics.
78testing-patterns
This skill should be used when implementing or reviewing testing workflows in template-ts projects, especially for testing, Vitest, Playwright, integration test, and mocking scenarios.
76git-workflow
Automates the full PR lifecycle — create or update a pull request, then aggressively monitor CI checks and review feedback in a continuous loop, fixing failures and addressing comments until the PR is fully green. Also covers push, branch creation, and branch sync workflows.
76debugging-with-opensrc
Load this skill when debugging behavior in external libraries by reading local OpenSrc mirrors (Effect, TanStack, TRPC, Drizzle, Better Auth, Sentry, Pino), or when docs conflict with runtime behavior and source-level verification is required.
75