OpenParable
Skip to content
← Back to skills

UI UX Feedback

Design
ui-ux-feedback

UI UX Feedback is an Agent Skill for design published in the majiayu000/claude-skill-registry repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

Capture UI and UX feedback plus feature requests. Use when a customer shares design feedback or asks for product changes.

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/majiayu000/claude-skill-registry/blob/HEAD/skills/data/ui-ux-feedback/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/ui-ux-feedback, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

UI/UX Feedback or Feature Request

Response Patterns (from samples)

Common openings:

  • "Hi,"
  • "Hello,"
  • "Hey,"

Common core lines:

  • "Best,"
  • "Hi,"
  • "Hello,"

Common closings:

  • "Best,"
  • "Thanks for the feedback, we will definitely consider that."
  • "Thanks for reaching out, but we politely decline."

Phrases That Work (4-gram frequency)

  • "thanks for the feedback" — 29 (13.4%)
  • "thanks for reaching out" — 16 (7.4%)
  • "we will definitely consider" — 15 (6.9%)
  • "for the feedback we" — 12 (5.6%)
  • "the feedback we will" — 12 (5.6%)
  • "feedback we will definitely" — 11 (5.1%)
  • "will definitely consider that" — 11 (5.1%)
  • "let me know if" — 9 (4.2%)
  • "www totaltypescript com profile" — 8 (3.7%)
  • "thanks for the heads" — 7 (3.2%)

Tone Guidance (observed)

  • Openings trend toward: "Hi,"
  • Closings often include: "Best,"

What NOT To Do

  • Don't introduce policy details that are not present in the verified response lines above.
  • Don't paraphrase or reframe the customer's question in a way that changes meaning.
  • Don't add refund/discount promises unless they appear in the extracted responses for this topic.

Validation

Draft must:

  • Include at least one of the required phrases from the validation block
  • Stay consistent with the observed response patterns above
  • NOT introduce policy details that are not present in the verified response lines above.