Help us improve
Share bugs, ideas, or general feedback.
Share bugs, ideas, or general feedback.
Share bugs, ideas, or general feedback.
By bpainter
Nine customer-experience specialists: customer research, jobs-to-be-done, persona development, journey mapping, service design, information architecture, product trend research, customer-feedback synthesis, and personalization strategy. Information architecture outputs feed directly into the engineering plugin's content modeling.
npx claudepluginhub bpainter/composable-dxp-claude-marketplace --plugin cxFeedback analyst who transforms raw customer data into clear, actionable insights that drive product, design, and marketing decisions. You synthesize patterns across surveys, reviews, support, and research to identify pain points, opportunities, and emerging needs. Also known as: customer insights analyst, feedback researcher, CX analyst, voice-of-customer specialist, research synthesizer.
Senior research expertise across qualitative and quantitative methods — designing in-depth interviews, focus groups, ethnographic studies, surveys, and mixed-methods studies; writing screeners and discussion guides; building valid and reliable instruments; sampling and analysis; reporting insights for executive and product audiences. Use this skill any time the user is planning, designing, fielding, analyzing, or reporting customer / user / market research, even when they say "talk to users," "test the messaging," "what do customers think," "run a survey," "validate this assumption," or "we need data on X." Trigger whenever a research effort is being shaped so the design produces evidence the team can actually act on rather than confirmatory anecdotes.
You're an information architect and content modeling expert. Design scalable, reusable content structures in headless CMS platforms like Contentful. Create modular content types, relationships, and taxonomies that support omnichannel delivery. Bridge content strategy with engineering. Also known as: IA specialist, content strategist, CMS architect, data modeler.
Frame product, service, and content decisions through Jobs-to-be-Done — what the user is trying to get done, the situation they're in, the progress they want to make, and what is currently blocking them. Produces JTBD statements, job maps, and prioritized job lists usable for product strategy, feature scope, and messaging. Use this skill any time the team is debating "what does the user want" or "what should we build" — "should we add X," "what's the user's goal," "JTBD," "outcome statement," "what job does this do" — even when the words aren't used. Trigger whenever feature priority or value prop arguments are happening so the team has a goal to argue against, not vibes.
Build current-state and future-state journey maps that show what the user does, thinks, and feels across the stages of an experience — with pain points, moments of truth, opportunities, and the channels and touchpoints that matter. Use this skill any time the user is mapping an experience, debugging a stuck flow, identifying where to invest, or aligning a team on how the audience actually moves through a process — "journey map," "experience map," "where are users dropping off," "show me the funnel," even when the words aren't used. Trigger whenever the conversation crosses from "who is the user" to "how do they move through this" so the team has a shared picture of the experience instead of disconnected screens.
Uses power tools
Uses Bash, Write, or Edit tools
Share bugs, ideas, or general feedback.
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge.
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge.
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
Comprehensive skill pack with 66 specialized skills for full-stack developers: 12 language experts (Python, TypeScript, Go, Rust, C++, Swift, Kotlin, C#, PHP, Java, SQL, JavaScript), 10 backend frameworks, 6 frontend/mobile, plus infrastructure, DevOps, security, and testing. Features progressive disclosure architecture for 50% faster loading.
Develop, test, build, and deploy Godot 4.x games with Claude Code. Includes GdUnit4 testing, web/desktop exports, CI/CD pipelines, and deployment to Vercel/GitHub Pages/itch.io.
Comprehensive feature development workflow with specialized agents for codebase exploration, architecture design, and quality review
Access thousands of AI prompts and skills directly in your AI coding assistant. Search prompts, discover skills, save your own, and improve prompts with AI.
Upstash Context7 MCP server for up-to-date documentation lookup. Pull version-specific documentation and code examples directly from source repositories into your LLM context.
Complete developer toolkit for Claude Code
Claude tooling skills for Cowork and Claude Code. Two skills: claude-plugin-creator scaffolds new plugins (folder structure, manifest, .plugin build, Cowork install) with empirically-established validation rules; claude-orchestrator designs the orchestration layer for new Cowork projects (CLAUDE.md routing, multi-phase commands, agent teams). One slash command (/plugin-help).
Seven behavioral-economics specialists grounded in canonical sources — Kahneman's Thinking Fast and Slow, Thaler & Sunstein's Nudge, Ariely's Predictably Irrational, and Wendel's Designing for Behavior Change — plus Slalom's 6-stage Behavioral Design Model. Six ready-to-use templates: Behavioral Profile, Choice Architecture, Nudges/Biases, Intervention Design, Use-Case Scoring, Use-Case Validation.
Eleven innovation specialists grounded in canonical sources — Christensen's Innovator's Dilemma, Dyer/Gregersen/Christensen's Innovator's DNA, Furr & Dyer's Innovator's Method, Doblin's Ten Types, Ramanujam & Tacke's Monetizing Innovation, Innovation Lab Excellence, Kelley's Ten Faces, Catmull's Creativity Inc, Dyer/Furr/Lefrandt's Innovation Capital, Rogers's Driving Digital Strategy, Tushman/Anand's Why Digital Transformations Fail, and Kane et al's Technology Fallacy — plus HBR Must-Reads on Innovation and Design a Better Business. Skills cover strategy, portfolio governance, value engineering across horizons, JTBD discovery, lean validation, ten-types diagnosis, willingness-to-pay monetization, lab design, disruption analysis, creative leadership/political capital, and digital transformation. One agent (innovation-agent) sequences them. Eight slash commands (audit, strategy, portfolio, discover, validate, value-case, charter, disruption-test) provide high-leverage recurring operations. Six templates: Three Horizons canvas, Ambition Matrix, JTBD Interview Guide, Ten Types diagnostic, Value Engineering canvas, Innovation Charter.
Leadership coaching, people-management, hiring, meetings and cadences, goal-setting, transitions, and stoic perspective. Seven specialized skills under one orchestrating agent. The two original skills (executive coach for neurodivergent leaders, people-leader for everyday craft) are joined by skills for hiring, meetings & cadences, onboarding & transitions, goals & OKRs, and stoic perspective. Each skill carries deep reference files distilled from canonical leadership texts — Hire With Your Head, The First 90 Days, Radical Focus, Drive, Good to Great, The Coaching Habit, Never Split the Difference, Meeting Design, The Effective Manager, Managing Humans, The Manager's Path, A Guide to the Good Life, How F*cked Up Is Your Management, Peopleware, Scaling Teams, Performance Appraisal Phrase Book, Exactly What to Say, How We Talk, Radical Candor, and 7 Habits.
Six brand specialists: strategy (positioning, narrative, voice, audience), naming (five-category framework, six-step process), identity-system (logo direction, color, type, photography, iconography), voice-tone (attributes with not-X pairings, tone register matrix, filler-words bans), guidelines-composer (9-chapter deliverable, sized to brand context), and audit (drift detection across identity, voice, surface application, governance). Outputs feed the design plugin and marketing plugin.
The Composable DXP plugin marketplace for Claude. 18 plugins, 182 skills, packaged for Claude Code (CLI), Claude Desktop (Cowork mode), and drag-and-drop install.
Marketplace name: composable-dxp (the value in .claude-plugin/marketplace.json)
Repo: https://github.com/bpainter/composable-dxp-claude-marketplace (public, personal)
# Cowork (Git URL — Cowork requires Git, not local paths)
claude plugin marketplace add https://github.com/bpainter/composable-dxp-claude-marketplace.git
claude plugin install <plugin>@composable-dxp
# Claude Code (also accepts the local path)
claude plugin marketplace add "/Users/bermon.painter/Library/CloudStorage/OneDrive-Slalom/Slalom Second Brain/80_Skills_and_Agents"
claude plugin install <plugin>@composable-dxp
For full install paths (Cowork, Claude Code, drag-and-drop), see INSTALL.md.
80_Skills_and_Agents/
├── README.md # this file (conventions and structure)
├── INSTALL.md # how to install the marketplace and plugins
├── .claude-plugin/
│ └── marketplace.json # marketplace manifest — lists every plugin
├── Memory/ # cross-cutting working memory (CLAUDE.md, people, glossary, etc.)
│ # NOT a plugin — read by Claude every session
├── Plugins/ # built .plugin files (build artifacts)
│ └── <plugin>.plugin
└── <plugin-name>/ # one folder per plugin SOURCE (e.g., obsidian/, claude/)
└── ... (see "Plugin layout" below)
The marketplace itself is a single Claude plugin marketplace. Tools that consume marketplaces (Claude Code CLI, Claude Desktop via Cowork) read .claude-plugin/marketplace.json to discover what's installable.
Memory/ is not a plugin. It's the user's working memory and shared knowledge base, read every session by Claude, and shared across all plugins.
Plugins/ holds built artifacts — the .plugin files (renamed ZIPs) that get dragged into Claude Desktop's Personal Plugins panel for install. The source of each plugin lives in its own folder at the marketplace root (e.g., obsidian/, claude/); the .plugin files in Plugins/ are derived from those sources via the build process described in INSTALL.md.
Every plugin under this marketplace follows this exact shape. Deviations break tooling.
<plugin-name>/ # plugin SOURCE (lives at marketplace root)
├── README.md # plugin overview for humans
├── .claude-plugin/
│ └── plugin.json # plugin manifest for Claude (only `name` is required)
├── references/ # plugin-wide shared references (optional)
│ └── <plugin>-foundations.md
├── skills/ # auto-discovered by Claude
│ ├── <plugin>-<skill-name>/ # one folder per skill
│ │ ├── SKILL.md # required — frontmatter (name, description) + body
│ │ └── references/ # skill-specific deep references (typical, 1–3 files)
│ │ └── <topic>.md
│ └── ... (more skills)
├── agents/ # auto-discovered by Claude (workers)
│ └── <plugin>-<agent-name>.md # single file per agent, Claude Code agent format
└── commands/ # slash commands (optional)
└── <command-name>.md
| Piece | Required? | Purpose |
|---|---|---|
README.md | recommended | Plugin overview, opinion, roadmap, written for humans browsing the repo |
.claude-plugin/plugin.json | required | Manifest Claude reads. Only name is strictly required; version, description, author, keywords, license are optional. Don't include empty optional fields (e.g., "homepage": "") — they fail manifest validation |
references/ | optional | Plugin-wide shared references at the plugin root. From a SKILL.md, cite as ../../references/<file>.md |
skills/ | optional | Skills (one folder per skill, each with a SKILL.md). Auto-discovered by Claude |
skills/<skill>/SKILL.md | required if folder exists | The skill itself — YAML frontmatter (name, description) + body |
skills/<skill>/references/ | optional | Skill-specific deep references (frameworks, checklists, examples). From the SKILL.md, cite as references/<file>.md |
agents/ | optional | Workers that act on user data — Claude Code agent file format (one file per agent) |
commands/ | optional | Slash commands — single Markdown files with description: frontmatter and a body that names the skill or workflow to invoke |
A plugin can have any combination of skills, agents, and commands. Empty folders are fine if you intend to fill them later.