By hpsgd
UX researcher — customer journeys, touchpoints, information architecture, usability assessment, persona definition. The experience layer of the product.
Plan a usability test — define research questions, tasks, participant criteria, and analysis approach. Produces a structured test plan ready for execution. Use before conducting moderated or unmoderated usability testing with real users.
Bootstrap the UX research documentation structure for a project. Appends research conventions to docs/design/CLAUDE.md and copies persona/journey-map templates. Idempotent — merges missing sections into existing files without overwriting.
Map a customer journey — stages, touchpoints, actions, emotions, pain points, and opportunities. Produces a structured journey map with critical moments and prioritised recommendations. Use for understanding end-to-end user experience or identifying friction across touchpoints.
Define a research-backed user persona grounded in real behaviour, not demographics or stereotypes. Produces a structured persona with goals, frustrations, and behaviour patterns backed by evidence. Use to represent a customer segment for product and design decisions.
Create a service blueprint -- mapping both the customer-facing journey and the backstage organisational processes that support it. Extends journey mapping with employee actions, support systems, and physical evidence. Use when analysing end-to-end service delivery or identifying backstage bottlenecks.
Uses power tools
Uses Bash, Write, or Edit tools
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
A plugin marketplace for Claude Code. Agents, skills, rules, and conventions that work together as a virtual team.
/plugin marketplace add hpsgd/turtlestack
Start with the core plugins (rules, thinking skills, and code review), then add agents for your stack:
/plugin install coding-standards@hpsgd
/plugin install writing-style@hpsgd
/plugin install security-compliance@hpsgd
/plugin install thinking@hpsgd
/plugin install tooling@hpsgd
/plugin install code-reviewer@hpsgd
/plugin install ai-engineer@hpsgd
Add a technology stack if relevant:
/plugin install dotnet-stack@hpsgd
/plugin install nextjs-stack@hpsgd
/plugin install python-stack@hpsgd
Then reload:
/reload-plugins
Browse the full plugin list below to see what else is available.
Per-project overrides. Create your own .claude/rules/ files. Project-level rules take precedence over marketplace rules.
Disabling a plugin. Set it to false in .claude/settings.json:
{
"enabledPlugins": {
"writing-style@hpsgd": false
}
}
Local overrides (not committed). Use .claude/settings.local.json for personal preferences that shouldn't affect the team.
{
"enabledPlugins": {
"coding-standards@hpsgd": true,
"writing-style@hpsgd": true,
"security-compliance@hpsgd": true,
"thinking@hpsgd": true,
"tooling@hpsgd": true,
"code-reviewer@hpsgd": true,
"dotnet-stack@hpsgd": true,
"nextjs-stack@hpsgd": true,
"python-stack@hpsgd": true,
"plugin-curator@hpsgd": true,
"coordinator@hpsgd": true,
"cpo@hpsgd": true,
"product-owner@hpsgd": true,
"ui-designer@hpsgd": true,
"ux-researcher@hpsgd": true,
"user-docs-writer@hpsgd": true,
"developer-docs-writer@hpsgd": true,
"internal-docs-writer@hpsgd": true,
"gtm@hpsgd": true,
"support@hpsgd": true,
"customer-success@hpsgd": true,
"grc-lead@hpsgd": true,
"cto@hpsgd": true,
"architect@hpsgd": true,
"react-developer@hpsgd": true,
"dotnet-developer@hpsgd": true,
"python-developer@hpsgd": true,
"ai-engineer@hpsgd": true,
"qa-lead@hpsgd": true,
"qa-engineer@hpsgd": true,
"release-manager@hpsgd": true,
"performance-engineer@hpsgd": true,
"devops@hpsgd": true,
"security-engineer@hpsgd": true,
"data-engineer@hpsgd": true,
"analyst@hpsgd": true,
"investigator@hpsgd": true,
"workflow-tools@hpsgd": true
}
}
After installing plugins, scaffold your project with domain-specific docs:
/coordinator:bootstrap-project my-project
npx claudepluginhub hpsgd/turtlestack --plugin ux-researcherInternal documentation writer — architecture docs, runbooks, changelogs, onboarding guides, ADR documentation. Writes for engineers who know the domain but may be new to the codebase.
Go-to-market specialist — positioning, launch strategy, content marketing, competitive analysis
Customer support — ticket triage, feedback synthesis, knowledge base, bug escalation
Security baseline rules and audit skills for maintaining secure code
Developer documentation writer — API references, SDK guides, integration tutorials, code examples. Writes for developers who are competent but unfamiliar with your codebase.
Use this agent when conducting user research, analyzing user behavior, creating journey maps, or validating design decisions through testing. This agent specializes in understanding user needs, pain points, and behaviors to inform product decisions within rapid development cycles. Examples:\n\n<example>\nContext: Understanding user needs for a new feature
User-centered design and product excellence. Master user research, UX design, accessibility, product strategy, user journey mapping, and inclusive design practices.
User research skills for designers: personas, empathy maps, journey maps, interview scripts, usability testing, and card sorting.
UX/マーケティング向けのユーザーペルソナを、5つの専門エージェントチームで作成するスキル。 ペルソナ設計、ユーザーリサーチ、ナラティブ執筆、バイアスレビュー、データ検証の 5観点からペルソナをディスカッション型で議論・作成し、Markdownドキュメントとして出力する。 data-critic がライブモデレーターとして矛盾を検出・収束を判定する。
User researcher — interviews, personas, Jobs-to-Be-Done, and customer feedback synthesis
Business analysis toolkit: competitive analysis, UX strategy artifacts, market sizing, canvas, PRD, personas