Bencium Controlled UX Designer
Sibling of Innovative UX Designer for consistency-first projectsâsame deep UX references, tighter control over creative variance.
Overview
Bencium Controlled UX Designer is a Claude skill catalogued in LimeDock Directories for teams working across design, product, operations. It is tagged for saas, fintech, healthtech, other contexts. Sibling of Innovative UX Designer for consistency-first projectsâsame deep UX references, tighter control over creative variance. Use this page as the operational brief: install path, how to invoke it, copy-paste prompts, prerequisites, and concrete use cases so your team can adopt it without re-reading every roundup article.
Work with LimeDock
Using this skill? LimeDock can wire it into a durable automation you own.
Skills show what's possible. LimeDock builds and runs the owned marketing, sales, and ops automations around them.
We sell owned automations for SaaS teams — live workflows that plug into Slack, CRM, and your internal platform — not just a skill list.
Link
Installation guide
cp -r bencium-claude-code-design-skill/bencium-controlled-ux-designer ~/.claude/skills/Generic install paths
CLI
npx skills add https://github.com/bencium/bencium-claude-code-design-skill**Claude Code plugins** (when published as a marketplace skill)
/plugin marketplace add <org/repo>
/plugin install <skill>@<marketplace>**Manual** — copy the skill folder into `~/.claude/skills/bencium-controlled-ux-designer/` or your project `.claude/skills/`.
Always review `SKILL.md` and bundled scripts before enabling.
How to use it
Use when design-system consistency matters more than novelty; same activation patterns as the innovative variant.
**Suggested workflow** 1. Install and enable the skill. 2. Open the target project (or Claude.ai chat) with enough product context. 3. Invoke with a clear goal, constraints, and success criteria. 4. Review the first output against your standards; refine with follow-ups. 5. Save winning prompts / outputs into your team playbook.
If Claude does not auto-select it, mention the skill by name: “Use the Bencium Controlled UX Designer skill…”
Example prompts
- “Use the Bencium Controlled UX Designer skill for this task: Enterprise settings UI under a strict DS”
- “Walk me through how Bencium Controlled UX Designer would approach this step by step, then execute.”
- “Review my current draft/plan and improve it using Bencium Controlled UX Designer. Call out assumptions.”
- “Produce a checklist I can reuse whenever we run Bencium Controlled UX Designer on similar work.”
Use cases and examples
- Enterprise settings UI under a strict DS
- Regulated-product form patterns
- Responsive redesign within brand constraints
- Motion specs without visual chaos
- First-week trial of Bencium Controlled UX Designer on a real design workflow
- Document a reusable prompt template for Bencium Controlled UX Designer for your team
Prerequisites
- Claude Code, Claude.ai (Skills enabled), or an Agent Skills–compatible host
- Network access if the skill fetches guidelines or calls external tools
- Project or brand context (CLAUDE.md / product notes) for better outputs
- Permission to install third-party skills — audit SKILL.md and scripts first
Tips
- Keep descriptions/triggers tight so Bencium Controlled UX Designer fires only when relevant (avoids context tax).
- Prefer one sharp job over a mega-skill that tries to do everything.
- Pair with verification (tests, review, screenshots) before shipping outputs.
- Re-audit installed skills monthly — unused skills still cost context every turn.