dammyjay93/interface-design

★ 4,848ShellAudience · vibe coderComplexity · 2/5LicenseSetup · easy

Mindmap

mindmap
  root((interface-design))
    What it does
      Saves design decisions
      Enforces consistency
      Session memory
    Commands
      init new session
      audit existing code
      extract patterns
      show current system
    Design directions
      Precision and Density
      Warmth and Approachability
      Data and Analysis
    Use cases
      Dashboards
      Admin panels
      App interfaces

mindmap root((interface-design)) What it does Saves design decisions Enforces consistency Session memory Commands init new session audit existing code extract patterns show current system Design directions Precision and Density Warmth and Approachability Data and Analysis Use cases Dashboards Admin panels App interfaces

Click or tap to explore — scroll the page freely

Things people build with this

USE CASE 1

Build consistent dashboards by having Claude remember your spacing and color choices across multiple coding sessions.

USE CASE 2

Audit existing AI-generated UI code to find components that don't match your saved design system.

USE CASE 3

Extract design patterns from code you've already written and save them as reusable tokens for future sessions.

USE CASE 4

Have Claude infer a design direction from your project context and apply it automatically before building new screens.

Tech stack

ShellClaude Code

Getting it running

Difficulty · easy Time to first run · 5min

Requires Claude Code installed, run /interface-design:init inside your project to begin.

Use freely for any purpose, including commercial use, as long as you keep the copyright notice.

In plain English

Interface Design is a plugin for Claude Code, the AI coding assistant, that brings structure and memory to UI building. When you ask Claude to build a dashboard, an app, or an admin panel, design choices get made on the fly: spacing values, colors, depth treatment, button sizes. Without a system in place, those choices drift between sessions, leaving inconsistent interfaces where buttons are 36px in one place and 40px in another. This plugin addresses that by giving Claude a set of design principles to follow and a persistent memory file. Your decisions get saved to a file called .interface-design/system.md in your project, things like your spacing base, color tokens, and component patterns. At the start of each session, Claude loads that file and applies the same established patterns automatically, so a settings page built in week two matches the dashboard built in week one. The plugin also adds commands you can run inside Claude Code: /interface-design:init starts a new design session, /interface-design:status shows the current system, /interface-design:audit checks existing code against the system, and /interface-design:extract pulls patterns out of code you have already written. When starting fresh, Claude infers a design direction from your project context, choosing between directions like Precision & Density for developer tools, Warmth & Approachability for consumer apps, or Data & Analysis for analytics dashboards, then asks for confirmation before applying it. It is scoped to functional interface design: dashboards, apps, tools, and admin panels. It explicitly does not target marketing sites. Written primarily in Shell. Licensed under MIT.

Copy-paste prompts

Prompt 1

I am using the interface-design Claude Code plugin. Run /interface-design:init for my developer tool project and apply the Precision and Density design direction.

Prompt 2

Run /interface-design:audit on my codebase and list every component that violates the spacing or color rules saved in .interface-design/system.md.

Prompt 3

Use /interface-design:extract to pull button sizing and color token patterns from my existing components and add them to the design system file.

Prompt 4

Build me a settings page using Claude Code with the interface-design plugin active, making sure it matches the design system already established for my dashboard.

Prompt 5

My project is a consumer app. Run /interface-design:init with the Warmth and Approachability direction and then show me the full system with /interface-design:status.

Open on GitHub → Explain another repo

← dammyjay93 on gitmyhub — every repo by this author, as a profile.

Verify against the repo before relying on details.