GPT Taste — Awwwards-Level Frontend Design Skill for Muse
Audit any design against the taste of GPT's interface.
- What
- Audit any design against the taste of GPT's interface.
- Cost
- Free
- Needs
- none beyond standard skill tooling — no external services, APIs, or accounts. Output quality depends on your project's stack; advanced GSAP patterns need GSAP installed in the project.
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Turns Muse into an elite frontend design engineer that aggressively breaks LLM defaults: simulated-Python randomization of hero architecture, typography stacks, and GSAP motion paradigms so no two pages look alike; a mandatory pre-flight `<design_plan>`; AIDA page structure; a hard 2-to-3-line limit on hero headlines with ultra-wide containers; gapless bento grids (`grid-flow-dense`, mathematically verified); and advanced GSAP patterns (scroll pinning, scrubbing text reveals, card stacking, hover physics). It also bans cheap meta-labels ("SECTION 01") and invisible button text. Discovered via skills.sh. Honest note: this is a philosophy-plus-engineering prompt, not a component library — output quality still depends on your stack, and strict GSAP work needs a real GSAP setup in the project. Skill Harbor never reviews the code, review it yourself before use. Not verified.
Curated by Skill Harbor — free, open-source skill (MIT) by @leonxlnx.
Version:
Install
Prerequisites: none beyond standard skill tooling — no external services, APIs, or accounts. Output quality depends on your project's stack; advanced GSAP patterns need GSAP installed in the project. Install "GPT Taste — Awwwards-Level Frontend Design Skill for Muse" for me. Elite UX/UI and GSAP motion engineering: randomized hero architectures, gapless bento grids, AIDA structure, pre-flight design plan, strict typography rules. Repository: https://github.com/leonxlnx/taste-skill 1. Fetch the SKILL.md file for the "gpt-taste" skill (and any helper files) 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 "gpt-taste". 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. confirm my frontend stack so the skill can target GSAP or plain CSS motion). 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.