Vercel tdd red green refactor
Skill TechTideOhio/techtide-harness-kit/skills/vercel/vercel-tdd-red-green-refactor
Trust contracts for AI agent skills: JSON Schema risk tiers, tool permissions, deny-by-default egress, approval gates, prompt-injection fixtures, ~28 CI validation gates. Apache-2.0.
npx -y skills add TechTideOhio/techtide-harness-kit --skill vercel-tdd-red-green-refactorAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Guide Vercel Agent Skills through red, green, and refactor cycles for risky changes where tests need to drive the implementation. Use when expanding, reviewing, or operating Vercel Agent Skills skills, rules, prompt kits, provider lanes, or generated-code handoffs in the TechTide skill library.
SKILL.md
2.2 KB, as published. Nobody here has run it
Vercel Agent Skills TDD Red Green Refactor
Guide Vercel Agent Skills through red, green, and refactor cycles for risky changes where tests need to drive the implementation.
Verified Surface
- Provider lane: vercel
- Native surface: Vercel-published Agent Skills installed with the skills CLI
- Harness export: codex, claude-code, cursor, other
- Import mode: techtide-synthesis
- Source evidence: load
references/source-evidence.mdbefore promoting third-party material.
Workflow
- Write or identify one failing test that expresses the desired behavior.
- Confirm the test fails for the expected reason.
- Implement the smallest change that makes the test pass.
- Refactor only after the behavior is green.
- Repeat with the next behavior until acceptance criteria are covered.
Output Contract
Return:
- provider lane and native surface
- source evidence used
- promotion decision or operating recommendation
- security and privacy notes
- verification still required
Guardrails
- Keep third-party source bodies out of public artifacts unless direct import has clean license, attribution, and manual review.
- Do not use star counts, popularity, screenshots, or social posts as the sole evidence for promotion.
- Do not install or execute unreviewed external scripts as part of source research.
- Quarantine missing licenses, unclear ownership, vague prompt packs, duplicate skill packs, and unsupported native-surface claims.
- Preserve Alex Cinovoj / TechTide ownership for TechTide-authored synthesis while citing third-party sources as references.