Interface Design
Design product interfaces with a craft-first methodology: intent, hierarchy, tokens, motion
- What
- Design product interfaces with a craft-first methodology: intent, hierarchy, tokens, motion
- Cost
- Free
- Needs
- none beyond a working agent
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor — a craft-first methodology for product interface design (dashboards, admin panels, SaaS apps, tools, settings pages, data interfaces): start from intent — who the human is, what they must accomplish, what it should feel like — then explore the product domain, name a signature element, call out the defaults to avoid, and make every decision deliberate: visual hierarchy, design-system architecture, tokens that evoke the product's world, states, and motion essentials for production-grade UI. The bar it sets: if another AI given a similar prompt would produce substantially the same output, it failed. Distinct from the already-listed addyosmani-api-and-interface-design — that one covers API design plus general interface principles; this one is a product-UI craft system (not for marketing pages, landing pages, or brand-only work). By @dammyjay93, listed here with credit to its creator. Honest caveats: it's a design process, not a component library — it won't hand you code; it fights generic output, which means slower, more deliberate work; taste is required from the operator too. Skill Harbor never reviews the code, review it yourself before use.
Version:
Install
Prerequisites: none beyond a working agent Install "Interface Design" for me. Design product interfaces with a craft-first methodology: intent, hierarchy, tokens, motion Repository: https://github.com/dammyjay93/interface-design/blob/main/.claude/skills/interface-design/SKILL.md 1. Fetch the SKILL.md file for the dammyjay93-interface-design skill from the repository into a temporary folder and summarize what it does in one or two sentences. 2. Safety check: review the SKILL.md and scripts for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code, credentials only via the secure vault, allowed hosts declared in the SKILL.md. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md and its helper files into the agent's skills directory, in a folder named "dammyjay93-interface-design". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. any accounts, API keys, or CLI tools mentioned in the prerequisites above). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. Never ask me to paste secrets in chat — credentials go through the secure vault or environment variables. If anything looks off, stop and ask me.
Questions
How do I install a build?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a build before installing it.