tdd
Test-Driven Development (TDD)
Overview
Write the test first. Watch it fail. Write minimal code to pass.
Core principle: If you didn't watch the test fail, you don't know if it tests the right thing.
Violating the letter of the rules is violating the spirit of the rules.
When to Use
Always:
- New features
- Bug fixes
- Refactoring
- Behavior changes
Exceptions (ask your human partner):
More from jeff-tian/agent-skills
oidc-integration
Plan and implement OIDC and OAuth 2.0 integration for React or TypeScript frontends and Java or Spring Boot backends. Use whenever the user mentions OIDC, OpenID Connect, OAuth login, SSO, PKCE, authorization code flow, refresh tokens, JWT or JWKS validation, login callback pages, protected routes, Keycloak, Auth0, IdentityServer, Authing, multi-provider auth, or "add login" and "integrate IdP" style requests even if they do not explicitly say OIDC.
10markdown-output
>-
9cohosted-frontend-backend
Co-host a frontend SPA and backend API in the same server process or container — separate codebases in development, single entry point in production. Use when integrating React/Next.js/Umi frontends with Node.js (Fastify/Egg.js) or ASP.NET Core backends. Trigger on keywords like "co-hosted frontend backend", "single container deployment", "SPA + API same server", "add frontend to backend project", "integrate Next.js with .NET", "static export", "SSR takeover", etc.
4specflow-to-reqnroll
>-
3repo-memory
>-
2