design-taste-frontend SKILL.md skillA
design-taste-frontend from coolxeo/grok-bot-skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add coolxeo/grok-bot-skills/design-taste-frontend@git:20261113.8af5195Pins git:20261113.8af5195 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- coolxeo/grok-bot-skills
- Path
skills/design/design-taste-frontend/SKILL.md- Versions recorded
- 2
- Latest version
- git:20261113.8af5195, committed Nov 13, 2026
- First version recorded
- Sep 13, 2026
- Size
- 4,349 bytes
- Repository stars
- 8
- License
- MIT
Use when building a landing page, portfolio, or marketing site from a brief, so the result looks chosen for this subject instead of like a template. Reads the brief, plans tokens, builds, then checks the rendered page.
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
# Design taste: frontend Build a page that looks like someone made choices for this subject and this audience. Most generated pages fail by reaching for the same defaults every time; this skill exists to stop that. ## 1. Read the brief Before any code, write a one-line **design read**: what the page is for, who it's for, the one action it should drive, and the mood in three words. Pull it from the brief, linked references, screenshots, existing brand assets, and the audience. If a key piece is missing, ask one question; otherwise state your assumptions and go. Constraints win over taste: accessibility needs, regulated industries, kids, public sector, or an existing brand system. If the brand has a design system or official component package, use it. ## 2. Plan before building Write a compact plan and check it against the brief: - **Color:** 4-6 named hex values with roles (background, text, accent, muted, border). - **Type:** one or two families, chosen for this subject, with a clear size scale. Body lines under about 75 characters. - **Layout:** a one-line idea per section plus a rough ASCII wireframe of the hero. …
Read the whole file at its exact version.
How to install
claude plugin marketplace add https://markdownregistry.com/mp/a/art_giwraq75zdxtwm5h/85f2f21a27f1fa8995d2a47a931b93a759d68d44a62fed223cb499e5714f7091.json
Then /plugin install design-taste-frontend@markdownregistry-giwraq75zdxtwm5h in Claude Code. It installs git:20261113.8af5195, the one graded A here, pinned to the commit it was graded at, and leaves it there.
mdr add coolxeo/grok-bot-skills/design-taste-frontend@sha256:85f2f21a27f1fa89The line at the top of this page pins the label git:20261113.8af5195, 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_giwraq75zdxtwm5h)
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: what changed in coolxeo/grok-bot-skills/design-taste-frontend since the version I have? 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 2 versions of this file, between Sep 13, 2026 and Nov 13, 2026, about one every 61 days. Its first recorded version is graded B and its latest A.
Watch this file (sign in, one email per new version)
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261113.8af5195 latest | 2026-11-13 | 8af5195 | 4,349 B | A | view · diff |
| git:20260913.35a8878 | 2026-09-13 | 35a8878 | 87,253 B | B | view |
Copies
4 files in 4 other repositories hold the exact bytes of one of this file's versions, each committed after this file had them: every one holds an older version.
- fractera/web4-node-starter-kit · lib/agent-kit/skills/base/leonxlnx/design-taste-frontend/SKILL.md · 1 version behind · 68 stars
- cgallic/kai-cmo-harness · harness/skills/design-taste-frontend/SKILL.md · 1 version behind · 65 stars
- datit309/supergraph · plugins/supergraph/skills/design-taste-frontend/SKILL.md · 1 version behind · 23 stars
- joahanmorales/upiixia-agentic-kit · kit/.uak/skills/design-taste-frontend/SKILL.md · 1 version behind · 21 stars
A copy does not update when this file does. Whoever holds one can learn which version it is with the Check your copy box below, or by asking their agent. Matched on exact bytes and commit dates only.
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
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (4349 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
- pass: No script tag
Source
coolxeo/grok-bot-skills · 8 stars · license MIT · pushed 2026-11-14 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_giwraq75zdxtwm5h GET https://markdownregistry.com/api/v1/resolve?ref=coolxeo/grok-bot-skills/design-taste-frontend GET https://markdownregistry.com/api/v1/blob/85f2f21a27f1fa8995d2a47a931b93a759d68d44a62fed223cb499e5714f7091
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.
More from coolxeo/grok-bot-skills
Every file in coolxeo/grok-bot-skills