ux-ui-expertlisted

UX/UI research and design knowledge base covering study plans, research roadmaps, the researcher's project cycle, usability-testing/card-sort/diary-study sample sizes, small-sample reporting, experimental design, research ethics (Belmont Report), stakeholder leadership/influence, the UX/UI/CX distinction with user-centred design principles, the ROI of UX, the Double Diamond design process, user flow diagrams, common beginner UI mistakes, visual/interaction design fundamentals (hierarchy, grids, typography, color, states), designing around user intent, and the psychology behind UI/UX (cognitive load, conditioning, reinforcement, hedonic adaptation). Use when planning UX research or design work, choosing methods or sample sizes, writing recommendations, leading/influencing stakeholders, scoping UX vs. UI vs. CX work, building a business case for UX investment, mapping a user flow, reviewing a UI for common mistakes, applying visual design fundamentals, or reasoning about why a design choice affects user behavio
fralapo/awesome-agent-skills · ★ 0 · Web & Frontend · score 73

Install: claude install-skill fralapo/awesome-agent-skills

# UX/UI Research & Leadership Expert ## How to Use This Skill - **Without arguments** — load core frameworks below for reference - **With a topic** — ask about `study plan`, `sample size`, `ethics`, or another indexed topic; I find and read the relevant chapter - **With a chapter** — ask for `ch05`; I load that specific chapter file - **Browse** — ask "what chapters do you have?" to see the full index When you ask about a topic not covered in Core Frameworks below, I will read the relevant chapter file before answering. --- ## Core Frameworks & Mental Models **Strategic vs. Tactical Research Map**: Strategic research (= foundational = generative = exploratory = discovery, all the same thing) is big-picture, long-term, and builds the knowledge base of who users are. Tactical research (= evaluative) tests existing ideas/prototypes, splitting into formative (pre-launch, improve) and summative (post-launch, measure at scale). Use "strategic/tactical" language with leadership, "generative/evaluative" with product teams — pick one set per audience and stick with it. **Study Plan Structure**: Background/Problem (why now) → Objectives + Non-Objectives (explicitly scope out what you won't study) → Research Questions + success metrics → Timeline + DACI (who's doing what, when) → Methodology (methods, participants, sample size, materials) → Procedure/Discussion Guide (a "recipe" someone else could replicate). First drafts should take minutes after a good kickoff meeting — treat d