design-taste-frontend SKILL.md skillB
design-taste-frontend in leonxlnx/taste-skill is at git:20261107.b900a80 (Nov 7, 2026), graded B.
mdr add leonxlnx/taste-skill/design-taste-frontend@git:20261107.b900a80This copy is 16 versions behind it. See what changed · install this older copy instead
This line moves to the next version by itself within about an hour of that file saving one. A copy already installed stays as it is until you update it.
design-taste-frontend from yikart/aitoearn is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
- Audit grade
- B, 16 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- yikart/aitoearn
- Path
project/aitoearn-web/.agents/skills/taste-skill/SKILL.md- Versions recorded
- 1
- Latest version
- git:20260623.e3abc45, committed Jun 23, 2026
- Size
- 87,253 bytes
- Repository stars
- 27,948
- License
- MIT
Anti-slop frontend skill for landing pages, portfolios, and redesigns. The agent reads the brief, infers the right design direction, and ships interfaces that do not look templated. Real design systems when applicable, audit-first on redesigns, strict pre-flight check.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# tasteskill: Anti-Slop Frontend Skill > Landing pages, portfolios, and redesigns. Not dashboards, not data tables, not multi-step product UI. > Every rule below is **contextual**. None of it fires automatically. First read the brief, then pull only what fits. --- ## 0. BRIEF INFERENCE (Read the Room Before Anything Else) Before touching code or tweaking dials, **infer what the user actually wants**. Most LLM design output is bad because the model jumps to a default aesthetic instead of reading the room. ### 0.A Read these signals first 1. **Page kind** - landing (SaaS / consumer / agency / event), portfolio (dev / designer / creative studio), redesign (preserve vs overhaul), editorial / blog. 2. **Vibe words** the user used - "minimalist", "calm", "Linear-style", "Awwwards", "brutalist", "premium consumer", "Apple-y", "playful", "serious B2B", "editorial", "agency-y", "glassy", "dark tech". 3. **Reference signals** - URLs they linked, screenshots they pasted, products they named, brands they're competing with. 4. **Audience** - B2B procurement panel vs. design-conscious consumer vs. recruiter scanning a portfolio. The audience picks the aesthetic, not your taste. …
Read the whole file at its exact version.
How to install
mdr add yikart/aitoearn/design-taste-frontend@git:20260623.e3abc45Pins git:20260623.e3abc45 in mdr.lock, 16 versions behind the newest at the top of this page.
claude plugin marketplace add https://markdownregistry.com/mp/a/art_kmeb7p765trazhrf/aa194351b246b8b4799099d4ed7b033d29eab6e6e3d58d8d2172978be7b3ec89.json
Then /plugin install design-taste-frontend@markdownregistry-kmeb7p765trazhrf in Claude Code. It installs git:20260623.e3abc45, the one graded B here, pinned to the commit it was graded at, and leaves it there.
mdr add yikart/aitoearn/design-taste-frontend@sha256:aa194351b246b8b4The older copy line above pins the label git:20260623.e3abc45, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_kmeb7p765trazhrf)
3 badge image fetches in 30 days. What the badge shows.
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it: get me the newest leonxlnx/taste-skill/design-taste-frontend, and what changed since aa19435? It reads every saved version here, no key and no account. Any agent that speaks MCP can add it.
Got a copy of design-taste-frontend from somewhere else? Ask it: where did my design-taste-frontend come from, and what was changed? It names the public original, the version yours is closest to and every changed line. The text is not kept.
Versions
The registry has recorded 1 version of this file, committed on Jun 23, 2026.
Watch this file (sign in, one email per new version)
Copies
Newest: git:20261107.b900a80 of design-taste-frontend in leonxlnx/taste-skill (skills/taste-skill/SKILL.md), graded B.
This copy: byte for byte that file's version git:20260526.3c7017d, which it committed on May 26, 2026, before this repository did; graded B, 16 versions behind.
See what changed since these bytes · ask your agent
Matched on the exact bytes and the commit dates, nothing else. It does not say who wrote the file or where this repository got it.
Committed this skill to a repository? Install the markdownregistry skill updates app on it, or on all of them. When the registry saves a newer version, a pull request brings your copy to it within minutes, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.
It asks to read and write contents and pull requests, and to read metadata. No workflow file, no Actions setting, nothing runs on your runners. Uninstall it and everything the registry kept about your repository is deleted.
Committed this skill to a repository? Add one workflow file, and when a newer version is saved, a pull request brings your copy to it, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.
mkdir -p .github/workflows && curl -fsSL https://markdownregistry.com/ci/skill-updates.yml -o .github/workflows/skill-updates.yml
It runs daily on GitHub Actions, no key and no account. Read the workflow before you add it.
Installed this file, say at .claude/skills/design-taste-frontend/SKILL.md? Drop it here to learn which saved version you have and what changed since. Your browser works out its SHA-256 fingerprint and sends only that; the file itself never leaves your computer.
Or paste its contents
Your agent can run this same check on the agent markdown files you have installed, up to 50 in one ask. Add the registry once:
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it to check the files you have installed. No key and no account.
From the root of your project, one line hashes each installed skill's SKILL.md, your AGENTS.md and your CLAUDE.md, and asks the registry once. Only the fingerprints and paths are sent.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --data-binary @- https://markdownregistry.com/api/v1/check-copies
In CI, add --fail-with-body: the answer is 409 when any file is behind, so the step fails and still prints which files.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --fail-with-body --data-binary @- https://markdownregistry.com/api/v1/check-copies
No sha256sum on your machine? shasum -a 256 prints the same lines.
Audit of the latest version
- fail: No script tag (matched: <script)
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (87253 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
Starting a new one? Use a template for SKILL.md on mdpantry, which passes every one of these checks and says what to change in it.
Source
yikart/aitoearn · 27,948 stars · license MIT · pushed 2026-11-12 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_kmeb7p765trazhrf GET https://markdownregistry.com/api/v1/resolve?ref=yikart/aitoearn/design-taste-frontend GET https://markdownregistry.com/api/v1/blob/aa194351b246b8b4799099d4ed7b033d29eab6e6e3d58d8d2172978be7b3ec89
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.