Interface Design: rememberable interface rules for dashboards and admin backends

Who it's for

Use this skill when you want dashboards, internal apps, tools, or admin backends to become a repeatable interface system, not a marketing landing page. It asks you to settle interface intent first, then keep later sessions on the same rules instead of reinventing each time.

Official notes keep the scope narrow: interface design, specifically dashboards, apps, tools, admin panels, and explicitly not marketing sites. If the task is a promo page, brand homepage, campaign page, or sales landing page, do not treat this as the main path.

Another precondition is permissions. The notes say the skill uses the same permission set as the coding agent, so after install and before changing any interface, open the skill file and read what it is allowed to do. Evidence does not name clients other than Claude Code, and does not write “auto-invoke when relevant” as a cross-platform capability. Do not assume unwritten environments already work.

First try in 3 minutes

The official page recognizes only this place:

https://github.com/dammyjay93/interface-design

The recommended install path is also only this one. Check the repository address first, confirm this is the skill you mean to install, then run in a local terminal:

npx skills add https://github.com/dammyjay93/interface-design --skill interface-design

The command’s side effect is installing the core skill into ~/.claude/skills/interface-design. After it runs, open that directory, confirm the skill file landed, then enter a conversation. If the directory is missing or the command fails, stop; do not switch to an installer or directory that official notes never named.

In Claude Code, invoke it explicitly with /interface-design. The first time, only check, do not write to disk: pick an existing backend or dashboard page and ask it to state the structure and component rules this interface should keep, plus which decisions must not be written to a file yet. Do not let it change business code, and do not let it create .interface-design/system.md.

Two observable success signals: the conversation states rules aimed at a dashboard or backend (not a marketing page); and you can open the skill file just installed in ~/.claude/skills/interface-design. If either does not match, stay at install and invoke; do not start writing files.

Use cases

Case 1: Align interface intent on an existing admin backend. Open a real admin panel, internal tool, or dashboard, and use /interface-design to have it check the current structure as “build the interface with intent” — which blocks should stay system-consistent, and which should not be laid out like a marketing-site narrative. This case only covers dashboards, apps, tools, admin panels. The notes do not demonstrate generating a whole site from zero, and do not give marketing-page rewrite steps.

Case 2: Keep interface decisions that are already agreed, so the next session can continue. First list a few rules to remember in the conversation; after you confirm they may be written to disk, let the skill write .interface-design/system.md. Open that file immediately and check that it matches those rules. The next time the skill runs, it should reload those decisions. The notes only write save to .interface-design/system.md and reload when the skill runs. They do not describe multi-repo sharing, conflict merges, or automatic overwrite; stop at the one file you can open and check.

Boundaries

Do not use it for marketing sites. Official wording puts “Not for marketing sites” right after the scope; that is a hard boundary, not a style tip.

The skill shares the coding agent’s permissions; read the installed skill itself before use. Do not let it change the repository or write a memory file without having read the file.

Install and invoke are only written as npx skills add, ~/.claude/skills/interface-design, Claude Code auto-invoke, and /interface-design. Do not add other marketplaces, other directories, unnamed clients, or apply this command to platforms the notes never named.

Memory is only written as save and reload of .interface-design/system.md. Do not assume a second store, team sync, or inheritance across projects.

The notes give no language coverage, prices, or official client roster beyond Claude Code. Keep undocumented items unknown; do not invent operations.