Frontend design direction — anti-generic design guidance
Choose a deliberate aesthetic direction (purpose, audience, tone, constraints) and build polished UI that avoids generic AI aesthetics — salvaged community guidance, not the official Anthropic skill
- What
- Choose a deliberate aesthetic direction (purpose, audience, tone, constraints) and build polished UI that avoids generic AI aesthetics — salvaged community guidance, not the official Anthropic skill
- Cost
- Free
- Needs
- a frontend project or UI request to apply it to — the skill is design guidance the agent follows, not software to install
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor — @affaan-m's frontend design-direction skill: before coding, choose a deliberate direction — the interface's purpose, its audience, an explicit tone (utilitarian, editorial, playful, industrial, refined…), one memorable detail, and the real constraints (framework, accessibility, performance, existing design system) — then build the actual usable experience as the first screen. It pushes the agent to reuse existing components, tokens and routing before inventing a visual system, prefer contextual typography over oversized hero text, keep palettes multi-dimensional, use motion sparingly but deliberately, and verify text fit on mobile and desktop. The anti-pattern list is the point: no purple gradients, decorative blobs, oversized cards, vague hero copy, stock-like media, or cards-inside-cards. Ends with a review checklist (first viewport communicates the product, hierarchy supports scanning, contrast holds, responsive dimensions are stable). Honest caveats: salvaged from a stale community PR (#1659) — the file itself says to install the official Anthropic `frontend-design` skill for the canonical upstream version (see the `anthropics-claude-code-frontend-design` listing); the skill lives under the repo's Japanese docs path (docs/ja-JP/…) though the content is in English. MIT licensed. Skill Harbor never reviews the code, review it yourself before use. Discovered via skills.sh.
Version:
Quick answer
Frontend design direction is a free Muse skill for choosing a deliberate aesthetic direction before coding, then building polished interfaces that avoid generic AI aesthetics. Before coding, choose purpose, audience, an explicit tone such as utilitarian or editorial, one memorable detail, and real constraints like framework and accessibility, using salvaged community guidance, not the official Anthropic skill.
Install
Copy the install package below, then paste it into Muse🧪 Install ran in our test sandbox · Nov 11, 2026📌 Pinned version: commit 4eb71d9Step 0 — before installing anything: read this install prompt, summarize in a few lines what this build does and what installing it involves, then ask me to confirm before you proceed. Prerequisites: a frontend project or UI request to apply it to — the skill is design guidance the agent follows, not software to install Install "Frontend design direction — anti-generic design guidance" for me. It gives my agent @affaan-m's design-direction workflow: before coding, pick a deliberate aesthetic direction (purpose, audience, explicit tone, one memorable detail, real constraints), build the actual usable experience first, reuse existing components and tokens, prefer contextual typography and multi-dimensional palettes, use motion deliberately, and check every UI against a review checklist. Includes an anti-pattern list (purple gradients, decorative blobs, oversized cards, vague hero copy, cards-inside-cards). MIT-licensed. Note: the skill itself recommends the official Anthropic frontend-design skill for the canonical upstream version (also listed here). Repository: https://raw.githubusercontent.com/affaan-m/ecc/4eb71d92a39cab44ad40ac9d8a6a5ccb4029d6c2/docs/ja-JP/skills/frontend-design-direction/SKILL.md Pinned version: install the code at commit 4eb71d92a39cab44ad40ac9d8a6a5ccb4029d6c2 exactly (Skill Harbor tested this version). Do not substitute a newer version. If this commit is unreachable, stop and tell me. 1. Fetch the SKILL.md file (and any helper files) from the repository path into a temporary folder 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 "frontend-design-direction". 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. point the agent at the UI to build or polish; nothing else — it's a methodology). 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. If anything looks off, stop and ask me.
Saved to your recent installs. Find it anytime on /connect.
🔒 Security, provenance and what this touches
The install prompt below already includes the vetting steps: your agent follows the community checklist before installing anything with executable code. Want more?
Verification certificate
Dated facts about what was checked for this listing, and how. This is not a safety certification.
- Pinned version
- 4eb71d9 · 2026-10-13
- Sandbox install test
- Install ran in our test sandbox · Nov 11, 2026
- Creator identity
- Not verified
- Fingerprint watch
- Last checked · Nov 19, 2026 : no change detected in the files linked by this install prompt
- Install prompt analysis
- 2026-10-13 : No commands, network calls, packages, file writes or API keys detected.
Skill Harbor never reviews the code of a listed skill. These are dated facts about the install prompt and our install test, not a safety certification. Review a skill yourself before you install it. How we verify
Questions
How do I install a skill?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the skill 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 skill before installing it.