Reskin — rebuild a site's pages with byte-faithful content on a donor design system
Rebuild an existing site's pages with byte-faithful content (text, ordered images, SEO metadata) on a separately-defined donor design system — gated on byte equality, pages generated programmatically, never retyped
- What
- Rebuild an existing site's pages with byte-faithful content (text, ordered images, SEO metadata) on a separately-defined donor design system — gated on byte equality, pages generated programmatically, never retyped
- Cost
- Free
- Needs
- a website project + Node.js 22+ with Playwright/Chromium installed, playwright-cli on PATH, and the impeccable skill installed alongside the stardust skills (per the compatibility note)
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor — @adobe's reskin skill (part of the Stardust chain): rebuild an existing site's pages so every visible byte of content survives — whitespace-normalized visible text, the ordered visible-image set, full SEO metadata carry-over — while the surface comes entirely from a donor's tokens and module vocabulary (another live site, or local static HTML prototypes; Figma donors are contract-defined but not yet implemented). The decisive rule: the page is generated programmatically from the captured content model — content strings are never retyped; byte fidelity then holds by construction and the gate becomes a regression check. Six phases: ingest the donor (curated probe-able token sheet + enumerated module vocabulary, pinning one reference page per module family), byte-oriented content-model capture (mandatory scope declaration, executable normalization ledger), a mapping brief (≥80% of content slots mapped onto named donor modules), programmatic render from the model's ordered stream, three gate families (content byte-equality, design-adoption probe, sanity), then handoff to the existing migrate/deploy skills. Honest caveats: heavy setup — requires Node 22+, Playwright with Chromium, playwright-cli on PATH, and the impeccable skill installed alongside; not for redesigning from intent or for migrating while keeping the current design (those are the sibling extract/replica flows). Apache-2.0 licensed. Skill Harbor never reviews the code, review it yourself before use. Discovered via skills.sh.
Version:
Install
Prerequisites: a website project + Node.js 22+ with Playwright/Chromium installed, playwright-cli on PATH, and the impeccable skill installed alongside the stardust skills (per the compatibility note) Install "Reskin — rebuild a site's pages with byte-faithful content on a donor design system" for me. It gives my agent @adobe's Stardust reskin workflow: capture a donor design system into a curated token sheet and module vocabulary (pinning one reference page per module family), capture a byte-oriented content model of each content page (mandatory scope declaration + executable normalization ledger), author a mapping brief with ≥80% of slots mapped onto donor modules, render pages programmatically from the model's ordered stream (never retyping content), and pass three gate families — content byte-equality, design-adoption probe, and sanity — before handing off to migrate/deploy. Apache-2.0 licensed. Repository: https://github.com/adobe/skills/blob/main/plugins/stardust/skills/reskin/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 "reskin". 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. verify the Node 22+/Playwright/impeccable prerequisites; note Figma donors are not yet implemented — use a live URL donor or static HTML prototypes). 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.