redesign SKILL.md skillA
redesign from kulykivska/claude-plugins is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add kulykivska/claude-plugins/redesign@git:20261104.4063c88Pins git:20261104.4063c88 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- kulykivska/claude-plugins
- Path
ux-craft/skills/redesign/SKILL.md- Versions recorded
- 2
- Latest version
- git:20261104.4063c88, committed Nov 4, 2026
- First version recorded
- Sep 29, 2026
- Size
- 7,877 bytes
- Repository stars
- 6
- License
- MIT
Orchestrate a full product redesign, design first: audit the current product (hig-review, conversion-review, ux-copy), propose 5 to 6 distinct style directions on one shared Apple-style UX as a live interactive page, build a design system and detailed web and native mobile screens from the direction the owner picks, run delight-spec, habit-loop and conversion-review over them, and only after explicit approval write the implementation plan (tokens, then components, then screens, behind a…
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
# Redesign
**Product name.** `{{app}}` here and in the references stands for the user's product. Take its name from the project (README title, package.json, app.json, Info.plist) or ask once, then write every example with that name and the product's own screens.
A redesign is five gated stages. Each stage ends with something the owner
can look at, and the next stage starts only when they have answered.
**No product code is written before a design is approved.** Not a spike,
not "just the tokens", not a prototype in the app repo.
## Gates
| Stage | Output | Gate to pass |
|-------|--------|--------------|
| A. Audit | Ranked findings, the problems the redesign must solve | Owner confirms the problem list |
| B. Directions | One live page with 5 to 6 directions | Owner names one direction |
| C. System and screens | Design system + detailed screens | Owner reviews the screens |
| D. Behaviour pass | delight, habit and conversion findings applied | Owner says "approved" for the design |
| E. Plan and hand-off | Implementation plan in the repo's usual place | Owner approves the plan; then SDLC |
Approval comes from the owner in the conversation, never from another
…Read the whole file at its exact version.
How to install
claude plugin marketplace add https://markdownregistry.com/mp/a/art_tepsmlicvnpcqbue/886923ca013276dc4e34b2a951cd40b26c5884291981b9a0139e27ab8b7caf88.json
Then /plugin install redesign@markdownregistry-tepsmlicvnpcqbue in Claude Code. It installs git:20261104.4063c88, the one graded A here, pinned to the commit it was graded at, and leaves it there.
mdr add kulykivska/claude-plugins/redesign@sha256:886923ca013276dcThe line at the top of this page pins the label git:20261104.4063c88, 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_tepsmlicvnpcqbue)
1 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 kulykivska/claude-plugins/redesign 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 redesign from somewhere else? Ask it: where did my redesign 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 29, 2026 and Nov 4, 2026, about one every 37 days.
Watch this file (sign in, one email per new version)
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261104.4063c88 latest | 2026-11-04 | 4063c88 | 7,877 B | A | view · diff |
| git:20260929.ac62207 | 2026-09-29 | ac62207 | 7,624 B | A | view |
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/redesign/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 (7877 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
kulykivska/claude-plugins · 6 stars · license MIT · pushed 2026-11-13 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_tepsmlicvnpcqbue GET https://markdownregistry.com/api/v1/resolve?ref=kulykivska/claude-plugins/redesign GET https://markdownregistry.com/api/v1/blob/886923ca013276dc4e34b2a951cd40b26c5884291981b9a0139e27ab8b7caf88
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 kulykivska/claude-plugins
Every file in kulykivska/claude-plugins