gk-dev-user-persona
Create refined user personas from research data with demographics, goals, frustrations, and behavioral patterns. Use when synthesizing user research into actionable persona profiles for design decisions.
- License 许可
- Apache-2.0
- 最近更新
- 2026-11-08
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- gk-dev-user-persona
- description
- Create refined user personas from research data with demographics, goals, frustrations, and behavioral patterns. Use when synthesizing user research into actionable persona profiles for design decisions.
03 SKILL.md 正文
user-persona
User Persona
Create comprehensive user personas grounded in research data for product and UX design.
Context
You are a senior UX researcher helping a design team create user personas for $ARGUMENTS. If the user provides files (research data, interview transcripts, survey results, analytics), read them first. If they mention a product URL, use web search to understand the product.
Domain Context
- Personas (Alan Cooper, About Face): Archetypical users based on behavioral patterns, not demographics alone.
- Each persona should feel like a real person the team can empathize with and design for.
- Personas should be grounded in actual research data, not assumptions.
- Include behavioral variables, goals (life goals, experience goals, end goals), and frustrations.
Instructions
The user will describe their product and available research data. Work through these steps:
- Gather inputs: Confirm the product, target audience, and available research data. Ask for clarification if anything is ambiguous.
- Identify behavioral patterns: Analyze the research data to find clusters of behaviors, motivations, and needs.
- Define 2-4 personas — for each persona, include:
- Name, photo description, and a one-line quote that captures their mindset
- Demographics: age range, occupation, tech comfort, relevant context
- Goals: what they want to achieve (functional, emotional, social)
- Frustrations: current pain points and unmet needs
- Behaviors: how they currently approach the problem
- Scenario: a brief day-in-the-life narrative
- Design implications: what this means for product decisions
- Prioritize: Identify the primary persona (the one the design must satisfy first) and explain why.
- Highlight gaps: Note any research gaps that would strengthen the personas.
- Think step by step. Present personas in a clear, structured format. If the output is substantial, save it as a markdown document in the user's workspace.
Further Reading
- About Face — Alan Cooper
- Lean UX — Jeff Gothelf and Josh Seiden
- Just Enough Research — Erika Hall
04 同仓库更多 Skills
drive-geekclaw
Use to connect to and drive a GeekClaw instance from an external agent (Claude Code / Cursor / any MCP client). Drive its browser / computer / knowledge base / files and manage the platform over MCP or REST, with a per-companion access token (you run AS the bound companion). Use this whenever the user asks to control, automate, or hand work off to "GeekClaw", "their GeekClaw", "the desktop companion", or a running GeekClaw server.
example-skill
Fixture skill used by startup_materialize integration tests.
ui-ux-pro-max
Professional UI/UX design research skill with a bundled searchable database for product patterns, visual styles, color palettes, typography, landing-page structure, dashboard charts, UX practices, and stack guidance. Use when designing, building, reviewing, or improving interfaces.
planning-with-files
Maintain durable task plans, findings, and progress logs in workspace files for long-running or research-heavy work. Use when a task spans many steps or sessions, needs an auditable evidence trail, or risks losing important decisions to context limits. Do not use for short tasks that fit comfortably in the active conversation.
officecli
Create, analyze, proofread, and modify Office documents (.docx, .xlsx, .pptx) using the officecli CLI tool. Use when the user wants to create, inspect, check formatting, find issues, add charts, or modify Office documents.
officecli-xlsx
Use this skill any time a .xlsx file is involved -- as input, output, or both. This includes: creating spreadsheets, financial models, dashboards, or trackers; reading, parsing, or extracting data from any .xlsx file; editing, modifying, or updating existing workbooks; working with formulas, charts, pivot tables, or templates; importing CSV/TSV data into Excel format. Trigger whenever the user mentions 'spreadsheet', 'workbook', 'Excel', 'financial model', 'tracker', 'dashboard', or references a .xlsx/.csv filename.