← Products

Design
⚙ Needs: a frontend project or UI request — the skill is desi…

Frontend design for Codex — anti-generic UI guidance

Short listing — license not verifiable; guidance to commit to a bold aesthetic direction and build distinctive production-grade frontends that avoid generic AI aesthetics

At a glance
What
Short listing — license not verifiable; guidance to commit to a bold aesthetic direction and build distinctive production-grade frontends that avoid generic AI aesthetics
Cost
Free
Needs
a frontend project or UI request — the skill is design guidance the agent follows, not software
Install
Copy the installer prompt below into your Muse — your agent does the rest.

Version:

@
Created by: @am-will
⌁

Install

Prerequisites: a frontend project or UI request — the skill is design guidance the agent follows, not software Install "Frontend design for Codex — anti-generic UI guidance" for me. It gives my agent @am-will's frontend design-direction guidance: commit to a bold aesthetic direction before coding, then implement distinctive production-grade interfaces avoiding generic AI aesthetics. IMPORTANT: the license terms were not verifiable (stated only as "Complete terms in LICENSE.txt") — fetch from the link only, reproduce nothing beyond the link, and read the LICENSE.txt yourself before reuse. Repository: https://github.com/am-will/codex-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. read the repo's LICENSE.txt before reuse; 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.

?

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.