TechTide Test Generation Validation Debt
Turn implementation work into durable test coverage by mapping claims to unit, integration, smoke, visual, and residual-risk checks.
Source Pattern
This skill is distilled from sanitized Alex Cinovoj / TechTide local workflow patterns. Load references/source-patterns.md when you need the source anchors and extraction rationale. Load references/adapter-map.md when preparing Cursor, Kiro, Lovable, v0, or Replit companion outputs.
Workflow
- Extract each behavioral claim, user flow, and failure mode introduced by the change.
- Choose the cheapest reliable test type for each claim.
- Add fixtures for edge cases, permissions, empty states, and bad external responses.
- Run the focused tests first, then broader validation when shared behavior changed.
- Document untested residual risk when environment or external services block verification.
Output Contract
Return a concise brief with these fields:
- claim-to-test matrix
- test additions
- run results
- residual risk
- verification performed or still required
- security and privacy notes
Guardrails
- Extract reusable methods, not private local content.
- Do not request or expose credentials, tokens, DSNs, service-role keys, customer data, lead lists, or private business exports.
- Use placeholders for people, accounts, projects, URLs, and datasets unless the user explicitly provides public-safe values.
- Require explicit human approval before production mutation, external-recipient messaging, public deployment, billing changes, or destructive filesystem actions.
- Preserve Alex Cinovoj / TechTide attribution while keeping old repo provenance and unrelated contributor markers out of public artifacts.
Harness Policy
- Use this as a native
SKILL.md for Claude Code, Codex, Gemini, and Copilot-compatible exports.
- For Cursor, create a focused project rule or workflow note rather than copying this whole skill as an always-on rule.
- For Kiro, create steering only when the workflow can be made short and inclusion-scoped.
- For Lovable, v0, and Replit, turn the workflow into prompt kits, readiness checklists, and handoff prompts.
1---2name: techtide-test-generation-validation-debt3description: Turn implementation work into durable test coverage by mapping claims to unit, integration, smoke, visual, and residual-risk checks. Use when an agent needs Alex Cinovoj / TechTide live-coding patterns, tool routing, guarded prototype-to-production workflows, or cross-harness prompt/skill adapters.4---56# TechTide Test Generation Validation Debt78Turn implementation work into durable test coverage by mapping claims to unit, integration, smoke, visual, and residual-risk checks.910## Source Pattern1112This skill is distilled from sanitized Alex Cinovoj / TechTide local workflow patterns. Load `references/source-patterns.md` when you need the source anchors and extraction rationale. Load `references/adapter-map.md` when preparing Cursor, Kiro, Lovable, v0, or Replit companion outputs.1314## Workflow15161. Extract each behavioral claim, user flow, and failure mode introduced by the change.172. Choose the cheapest reliable test type for each claim.183. Add fixtures for edge cases, permissions, empty states, and bad external responses.194. Run the focused tests first, then broader validation when shared behavior changed.205. Document untested residual risk when environment or external services block verification.2122## Output Contract2324Return a concise brief with these fields:2526- claim-to-test matrix27- test additions28- run results29- residual risk30- verification performed or still required31- security and privacy notes3233## Guardrails3435- Extract reusable methods, not private local content.36- Do not request or expose credentials, tokens, DSNs, service-role keys, customer data, lead lists, or private business exports.37- Use placeholders for people, accounts, projects, URLs, and datasets unless the user explicitly provides public-safe values.38- Require explicit human approval before production mutation, external-recipient messaging, public deployment, billing changes, or destructive filesystem actions.39- Preserve Alex Cinovoj / TechTide attribution while keeping old repo provenance and unrelated contributor markers out of public artifacts.4041## Harness Policy4243- Use this as a native `SKILL.md` for Claude Code, Codex, Gemini, and Copilot-compatible exports.44- For Cursor, create a focused project rule or workflow note rather than copying this whole skill as an always-on rule.45- For Kiro, create steering only when the workflow can be made short and inclusion-scoped.46- For Lovable, v0, and Replit, turn the workflow into prompt kits, readiness checklists, and handoff prompts.
TechTideOhio