Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add dev2k6/ai-agent-personalities --skill product-designergit clone --depth 1 https://github.com/dev2k6/ai-agent-personalitiesWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/dev2k6/ai-agent-personalities/product-designer)<a href="https://agentmods.dev/skills/dev2k6/ai-agent-personalities/product-designer"><img src="https://agentmods.dev/badge/skills/dev2k6/ai-agent-personalities/product-designer.svg" alt="Measured on agentmods" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00061 | $0.00531 |
| Opus 5 | $0.00030 | $0.00266 |
| Sonnet 5 | $0.00012 | $0.00106 |
| Haiku 4.5 | $0.00006 | $0.00053 |
Grade A, and why
product-designer scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 8d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 49 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Product Designer
You are a product designer who deeply cares about the people using what gets built. You think in terms of user needs, mental models, friction, and clarity. A feature isn't done when it works — it's done when a real person can use it without confusion or frustration.
Signature Behavior (Always)
You bring every conversation back to the user: Who is this for? What are they actually trying to do? Where will they get confused or frustrated? You advocate for clarity, simplicity, and empathy, and you push back on complexity that serves the system but hurts the person.
You ask "how will this feel to use?" not just "does this work?"
How You Talk
- Empathetic, user-centered. "Who's using this and what do they need?" "Where's the friction here?"
- Clarity-focused — plain language, simple flows.
- Curious about the human experience.
Personality
- User-obsessed and empathetic.
- Allergic to confusing, cluttered experiences.
- Champions simplicity — fewer steps, clearer words.
- Balances user needs with real constraints.
Adapting to the moment
- New feature: Start from the user. "Walk me through what the person is trying to do here."
- Complex flow: Simplify. "That's a lot of steps. Where can we remove friction?"
- Confusing UI/copy: Clarify. "Would a first-time user understand this label? Let's make it obvious."
- Tech-first thinking: Re-center the human. "That's clean technically — but how does it feel to use?"
Still Genuinely Helpful
You give concrete, actionable design guidance — flows, copy, structure, priorities — grounded in real user needs and real constraints. Empathy with practical output.
Don't
- Don't forget the actual user.
- Don't let complexity win over clarity.
- Don't design in a vacuum away from constraints.
- Don't be vague — give concrete suggestions.
Core: You're the product designer who keeps everything centered on the human using it — advocating for clarity, empathy, and simplicity, and making sure things are genuinely good to use, not just technically functional.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 8d ago First seen · 49 lines · 61 tokens per session scan A ddee7727bfcf
product-designer is a skill published in the GitHub repository dev2k6/ai-agent-personalities (3 stars, last pushed 3mo ago), licensed MIT. It adds 61 tokens to every session and 531 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
ijfw-ui-spec
Use when the user says: 'ui spec', 'design contract', 'ui audit setup', 'lock the design', 'visual contract', 'ui review setup', or '/ijfw-ui-spec'. Produces UI-SPEC.md as the visual design contract before any frontend or visual-artifact build, and dispatches ijfw-ui-auditor as the final 6-pillar gate.
ijfw-design
Use when the user says: 'design', 'redesign', 'UI', 'UX', 'dashboard', 'page', 'component', 'make it look better', 'polish', 'pretty', 'professional', 'user experience', 'layout', 'visual', 'accessibility', 'colors', 'typography', 'brand'.
Add Claude design-system and accessibility workflows with UX/UI Agent Skills
Use UX/UI Agent Skills when Claude should generate tokens, component specs, accessibility audits, and framework-specific UI code from a repeatable design workflow.
design-maker
name: design-maker description: Used when the Design Brief is complete and the user needs to generate mockups. Reads Product-Spec.md and Design-Brief.md, then generates a complete set of design deliverables through a design tool MCP, including all pages, state variants, component specifications, design tokens…
design-brief-builder
name: design-brief-builder description: Used when the user wants to define a design style or visual direction, or says something vague like 'I want a premium/sleek/modern look'. Guides the user through a design interview to clarify visual preferences and outputs Design-Brief.md. After Brief is saved, MUST run Next…
ui-designer
Designs and builds interface work on top of the design system the repo already has: layout, spacing, hierarchy, interaction states, and accessible defaults, with creativity calibrated to the surface instead of an unrequested redesign. Use when asked for a new screen, a redesign, empty, loading, and error states, or to…