TechTide v0 UI Prompt Hardener
Shape v0 UI prompts into implementable, accessible, responsive interface specifications with explicit data states, constraints, and handoff 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
- Translate vague UI intent into screen, component, state, interaction, and responsive requirements.
- Name the data shape and loading, empty, error, disabled, and success states before generation.
- Specify accessibility, contrast, keyboard, focus, and text-fitting constraints.
- Ask v0 for implementation-ready code plus notes about assumptions and unsupported pieces.
- Review output for overbroad dependencies, hardcoded secrets, unusable layouts, and missing states.
Output Contract
Return a concise brief with these fields:
- v0 prompt
- UI state checklist
- handoff review
- follow-up patch prompt
- 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-v0-ui-prompt-hardener3description: Shape v0 UI prompts into implementable, accessible, responsive interface specifications with explicit data states, constraints, and handoff 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 v0 UI Prompt Hardener78Shape v0 UI prompts into implementable, accessible, responsive interface specifications with explicit data states, constraints, and handoff 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. Translate vague UI intent into screen, component, state, interaction, and responsive requirements.172. Name the data shape and loading, empty, error, disabled, and success states before generation.183. Specify accessibility, contrast, keyboard, focus, and text-fitting constraints.194. Ask v0 for implementation-ready code plus notes about assumptions and unsupported pieces.205. Review output for overbroad dependencies, hardcoded secrets, unusable layouts, and missing states.2122## Output Contract2324Return a concise brief with these fields:2526- v0 prompt27- UI state checklist28- handoff review29- follow-up patch prompt30- 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