Shaktra Tdd

Shaktra TDD — Testing & Coding Knowledge

This skill provides the knowledge base for writing tests and production code. It is loaded by agents during the TDD pipeline — it does not orchestrate any workflow.

Boundary

This skill defines: HOW to write tests (practices, patterns, anti-patterns) and HOW to write production code (implementation patterns, security, observability, resilience).

shaktra-quality defines: HOW to evaluate code and tests (checks, review dimensions, gate logic).

shaktra-reference defines: WHAT severity levels mean (severity-taxonomy.md), WHAT quality principles apply (quality-principles.md), and WHAT the handoff state machine looks like (schemas/handoff-schema.md).

This skill never restates severity definitions, quality dimensions, or schema structures — it references them.

Sub-Files

How Agents Use This Skill

sw-engineer loads this skill to inform implementation and test planning:

• Reads testing-practices.md for test strategy guidance
• Reads coding-practices.md for pattern selection during plan creation
• Reads performance-practices.md and data-layer-practices.md for data/performance-aware planning
• In refactoring-plan mode: reads refactoring-smells.md for smell detection

test-agent loads this skill to write behavioral tests:

• Follows testing-practices.md for test structure, naming, assertions
• References edge case strategy and mocking boundaries
• In characterization mode: writes behavior-preserving tests for refactoring safety

developer loads this skill to write production code:

• Follows coding-practices.md for implementation patterns
• Applies security-practices.md for OWASP-aligned secure coding
• Applies performance-practices.md and data-layer-practices.md for efficient data access
• References resilience-practices.md for retry, timeout, circuit breaker, and fallback patterns
• References concurrency-practices.md for idempotency, locking, and atomic operations
• In refactor mode: follows refactoring-transforms.md atomic protocol

architect loads this skill for design-first engineering:

• Reads api-design-practices.md for API contract design
• Reads schema-design-practices.md for data model design
• Reads service-boundary-practices.md for service decomposition
• Reads threat-modeling-practices.md for STRIDE-based threat modeling

References

• shaktra-reference/quality-principles.md — 10 core principles guiding all code
• shaktra-reference/severity-taxonomy.md — severity definitions (never duplicated here)
• shaktra-reference/schemas/handoff-schema.md — TDD state machine phases