Xbklairith

Use when implementing features/bugfixes to enforce strict TDD discipline - enforces RED (write failing test), GREEN (minimal code), REFACTOR cycle with no exceptions. Prevents "test after" trap, catches rationalizations. Activates when user says "implement", "let's code", "write this feature", mentions "TDD", or during spec-driven execution phase.

Create distinctive, production-grade frontend interfaces with high design quality. Use when user asks to build web components, pages, or applications. Activates when user says "build UI", "create component", "design page", "make it look good", mentions "frontend", "CSS", "styling", or asks for visual improvements.

Use when writing tests, debugging failures, or investigating bugs - provides TDD guidance, test generation patterns, systematic debugging framework. Activates when user says "write tests", "this test fails", "debug this", mentions "TDD", "test coverage", or encounters errors/bugs.

Use when converting strategy documentation to code - translates markdown strategy docs into Python functions (for backtesting frameworks like Backtrader) and TradingView Pine Script. Activates when user says "convert to Python", "generate Pine Script", "code this strategy", mentions "backtest", or uses /trading:translate command.

Use when planning new features or need structured requirements - creates feature structure, elicits EARS requirements through systematic questioning, proposes architectural approaches with trade-offs. Activates when user mentions "new feature", "requirements", "specs", "design", "architecture", or uses /dev-workflow:spec commands (create, requirements, design).

Use when ready to implement designed features - breaks design into TDD tasks (Red-Green-Refactor), tracks progress with checkboxes in tasks.md, enforces strict testing discipline. Activates when user says "implement this", "let's code", "start execution", mentions "tasks", "TDD", or uses /dev-workflow:spec commands (tasks, execute).