# UI UX Feedback

> Customer provides feedback about user interface, design, or requests new features.

- Skill: `majiayu000/ui-ux-feedback-2` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds@latest add majiayu000/ui-ux-feedback-2`
- Raw SKILL.md: https://api.skillmd.com/api/skills/majiayu000/ui-ux-feedback-2/raw
- Safety review: pending (external: skill-scanner PASS, skillspector PASS)
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: majiayu000 (https://skillmd.com/u/majiayu000)
- Updated: 2026-09-22
- Page: https://skillmd.com/skills/majiayu000/ui-ux-feedback-2

---


# 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