Frontend design guardrails — distinctive, non-generic UI with hard rules
A rule-driven frontend design methodology: hard constraints against generic AI aesthetics, typography and color discipline, component consistency checks, and a design review checklist
- What
- A rule-driven frontend design methodology: hard constraints against generic AI aesthetics, typography and color discipline, component consistency checks, and a design review checklist
- Cost
- Free
- Needs
- a frontend project or UI request — the skill is a design methodology the agent follows, not software
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor — @customware-ai's frontend-design skill: a rule-driven methodology for distinctive interfaces, with hard guardrails rather than vague inspiration. Enforces typography discipline (a small set of deliberate type choices), color discipline (restrained palettes with intent), hard constraints against the generic AI look (no default gradients, no cookie-cutter hero sections, no stock-icon mush), component consistency checks, spacing and layout rules, and a design-review checklist to run before shipping. Honest caveats: several frontend-design fiches already exist in the catalog — this one is kept for its strict, checkable rule format; compare with the existing ones and install the one whose style of guidance fits you best. MIT licensed. Skill Harbor never reviews the code, review it yourself before use. Discovered via skills.sh.
Version:
Install
Prerequisites: a frontend project or UI request — the skill is a design methodology the agent follows, not software Install "Frontend design guardrails — distinctive, non-generic UI with hard rules" for me. It gives my agent @customware-ai's rule-driven design methodology: typography and color discipline, hard constraints against generic AI aesthetics, component consistency checks, spacing/layout rules, and a pre-ship design-review checklist. NOTE: several frontend-design listings already exist in the catalog — compare and install the one whose guidance style fits you best. MIT-licensed. Repository: https://github.com/customware-ai/skills/blob/main/skills/frontend-design/SKILL.md 1. Fetch the SKILL.md file (and any helper files) from the repository path 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. 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". 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 design or review; nothing else — it's a design 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.
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.