Initializes guided UI design for dashboards, apps, and tools. Assesses intent, proposes styles with rationale, builds components, and offers to save patterns.
From interface-designnpx claudepluginhub lwhite702/klutr_primary --plugin interface-designcommands//initInitializes beads issue tracking database in current directory with optional prefix (defaults to dir name). Shows DB location, prefix, workflow overview, next steps; displays stats if already set up.
/initInitializes guided UI design for dashboards, apps, and tools. Assesses intent, proposes styles with rationale, builds components, and offers to save patterns.
/initDownloads and installs/updates the platform-specific notification binary for claude-notifications plugin from GitHub into the plugin's bin directory.
/initInitializes or re-boots llmdoc/ directory structure, runs multi-themed project investigations with investigator, and generates initial stable docs via recorder.
/initInitializes AI task harness with ai/tasks/ directory for modular backlog, progress log, bootstrap script, and CLAUDE.md instructions. Supports --mode new|scan and --task-type ops|data|infra|manual.
/initScans Claude Code agents directory for custom agents, lets user select and register them for orchestration workflows, updates registry JSON and documentation.
Before writing any code, read this file completely:
../skills/interface-design/SKILL.md — the foundation, principles, craft knowledge, and checksDo not skip this. The craft knowledge is in this file.
Scope: Dashboards, apps, tools, admin panels. Not landing pages or marketing sites.
Before touching code, answer these out loud:
Who is this human? Not "users." Where are they? What's on their mind? A teacher at 7am with coffee is not a developer debugging at midnight.
What must they accomplish? Not "use the dashboard." The verb. Grade submissions. Find the broken deployment. Approve the payment.
What should this feel like? In words that mean something. "Clean" means nothing. Warm like a notebook? Cold like a terminal? Dense like a trading floor?
If you cannot answer these with specifics, stop and ask the user. Do not guess. Do not default.
State the intent AND the technical approach:
Intent: [who, what they need to do, how it should feel]
Palette: [foundation + accent — and WHY these colors fit the product's world]
Depth: [borders / subtle shadows / layered — and WHY]
Surfaces: [your elevation scale — and WHY this temperature]
Typography: [your typeface choice — and WHY it fits the intent]
Spacing: [your base unit]
Every choice must be explainable. If your answer is "it's common" or "it works" — you haven't chosen. You've defaulted.
The test: If another AI given a similar prompt would produce the same output, you have failed. The interface must emerge from THIS user, THIS problem, THIS intent.
Be invisible. Don't announce modes or narrate process.
Never say: "I'm in ESTABLISH MODE", "Let me check system.md..."
Instead: Jump into work. State suggestions with reasoning.
Lead with your exploration and recommendation, then confirm:
"Domain: [concepts from this product's world]
Color world: [colors that exist in this domain]
Signature: [one element unique to this product]
Direction: [approach that connects to the above]"
[AskUserQuestion: "Does that direction feel right?"]
.interface-design/system.md existsThe skill files contain the craft principles. system.md contains project-specific decisions. You need both.
Offer to save when you finish building UI:
"Want me to save these patterns to .interface-design/system.md?"
Always offer — new patterns should be captured whether system.md exists or not.