interface-design-dammyjay — Claude Code skill: install and usage
interface-design-dammyjay designs data-dense dashboards, admin panels, and SaaS tools without generic AI interface patterns.
MIT 211 installs ★ 35 updated 2026-10-21
npx skills add podo/design-agent-skills --skill interface-design-dammyjay -a claude-codeWhat interface-design-dammyjay does
This skill targets complex screens like settings views, dashboards, and internal tools. It organizes layout hierarchy, design tokens, and element states so crowded layouts remain readable. Generic AI design patterns are pruned away.
During code generation, it can store design rules in .interface-design/system.md. It requests confirmation before writing that file. Marketing sites and campaign pages are explicitly unsupported because the workflow focuses entirely on software products.
This entry acts as a catalogue pointer to Dammyjay93/interface-design. Installing via the Claude Code plugin route also provides the extra design-review and design-deslop commands.
What it helps with
- structure information-dense admin panels and dashboards
- record persistent design decisions in
.interface-design/system.md - replace generic AI component layouts with clean hierarchy
- set up consistent UI states and tokens across SaaS views
Example prompts for the agent
- Design an analytics dashboard with dense data tables
- Use interface-design to build the SaaS settings view
- /interface-design
How to install interface-design-dammyjay
1Skills CLI (Vercel)
npx skills add podo/design-agent-skills --skill interface-design-dammyjay -a claude-code2Manually: put the files in place
~/.claude/skills/interface-design-dammyjay/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/interface-design-dammyjay/
1Skills CLI (Vercel)
npx skills add podo/design-agent-skills --skill interface-design-dammyjay -a codex2Manually: put the files in place
.agents/skills/interface-design-dammyjay/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add podo/design-agent-skills --skill interface-design-dammyjay -a cursor2Manually: put the files in place
.cursor/skills/interface-design-dammyjay/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install podo/design-agent-skills skills/interface-design-dammyjay2Manually: put the files in place
.github/skills/interface-design-dammyjay/SKILL.md1Skills CLI (Vercel)
npx skills add podo/design-agent-skills --skill interface-design-dammyjay -a gemini-cli2Platform CLI
gemini skills install https://github.com/podo/design-agent-skills --path skills/interface-design-dammyjayManually: put the files in place
.devin/skills/interface-design-dammyjay/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add podo/design-agent-skills --skill interface-design-dammyjay -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about interface-design-dammyjay
How to install interface-design-dammyjay in Claude Code?
Run npx skills add podo/design-agent-skills --skill interface-design-dammyjay -a claude-code in your terminal.
What does interface-design-dammyjay do?
It guides coding agents to produce usable admin dashboards and SaaS views with explicit tokens, states, and clear visual hierarchy.
Can I use it for landing pages?
No, the skill excludes promotional work and marketing landing pages to stay focused strictly on product UI.
Source text
SKILL.md · MIT
--- name: interface-design-dammyjay description: | Craft-first interface design for dashboards, admin panels, SaaS apps, tools, and other information-dense product UI. Applies hierarchy, token, state, and consistency principles to produce interfaces that are both functional and visually coherent. Not for marketing or landing pages. triggers: - "interface design" - "dashboard design" - "admin panel" - "SaaS interface" - "dense UI" das: category: interaction-polish upstream: "https://github.com/Dammyjay93/interface-design" upstream_path: ".claude/skills/interface-design/SKILL.md" version: latest install: true --- # interface-design-dammyjay > Catalogue stub — full skill: [Dammyjay93/interface-design](https://github.com/Dammyjay93/interface-design) <!-- das:install:start — generated from stub.yaml by `npm run generate`; edit stub.yaml, not this block --> ## Decision tree 1. **Is the full skill already installed?** Upstream names this skill `interface-design`, so it installs next to this pointer (the pointer is not replaced). - Global: `f=~/.agents/skills/interface-design/SKILL.md; [ -f "$f" ] && ! grep -q "^das:" "$f" && echo "installed" || echo "pointer"` - Project: `f=.agents/skills/interface-design/SKILL.md; [ -f "$f" ] && ! grep -q "^das:" "$f" && echo "installed" || echo "pointer"` - `installed` → the skill is installed as `interface-design`, invoke it and proceed - `pointer` → go to step 2 2. **Detect scope, then install:** ```bash [ -e ~/.agents/skills/interface-design-dammyjay ] && echo "global" || echo "project" ``` **Global:** ```bash npx skills add Dammyjay93/interface-design --skill interface-design -g -y ``` **Project:** ```bash npx skills add Dammyjay93/interface-design --skill interface-design -y ``` > **Claude Code:** send a command as a chat message starting with `!` to run it without leaving the conversation. **Claude Code plugin route:** ``` /plugin marketplace add Dammyjay93/interface-design /plugin install interface-design@interface-design ``` **Heads-up** - **License:** MIT <!-- das:install:end --> ## Invoke after install - Skill name: `interface-design` - Trigger phrases: "interface design", "dashboard design", "admin panel", "SaaS interface", "dense UI" - Claude Code: `/interface-design`, or "use interface-design to build this dashboard" ## What it does Specialises in crafting dashboards, admin panels, SaaS apps, tools, settings pages, and data interfaces where large amounts of information must be presented clearly. Pushes every UI decision to be explicit (direction, hierarchy, tokens, states, motion) so information-dense layouts remain usable, scannable, and visually polished, and strips generic AI-looking UI. It offers to save the design decisions it makes to `.interface-design/system.md` in your project so later sessions stay consistent; the file is only written if you say yes. The Claude Code plugin route additionally provides the `design-review` and `design-deslop` commands, which the skills CLI install does not. ## When NOT to use - Marketing pages, landing pages, campaigns, or brand-only work: the skill itself excludes them - Broader design-engineering and anti-slop workflows beyond product UI → see `ui-craft`
© podo · MIT · podo/design-agent-skills