[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7DM26NQQ5343G12M2SWC957":3,"skill-same:01M7DM26NQQ5343G12M2SWC957":54},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":13,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":29,"install":30,"resources":43},"01M7DM26NQQ5343G12M2SWC957","reverse-engineering-ui",null,"Tear down a live site or web UI into an evidence-backed spec (layout, tokens, components, states, network) for an original rebuild. Use to clone or match one.","Anemos-labs\u002FSleipnir","Anemos-labs","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F292271065?v=4","01M7DM0NMRCBK5YXDB4DPZDJJG","01M7DM0NNVMEW7T30EG9YW2G88",0,"MIT","https:\u002F\u002Fgithub.com\u002FAnemos-labs\u002FSleipnir\u002Fblob\u002Fmain\u002Finternal\u002Fskills\u002Fbuiltin\u002Fdata\u002Freverse-engineering-ui\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: reverse-engineering-ui\ndescription: Tear down a live site or web UI into an evidence-backed spec (layout, tokens, components, states, network) for an original rebuild. Use to clone or match one.\nlicense: MIT\nauthor: Sleipnir; the measured capture and comparison follow the website checks of Craft Anything (github.com\u002Fstorytold\u002Fcraft-anything, MIT OR Apache-2.0); no code is copied\n---\n# Reverse engineering a web UI\n\nRead the `reverse-engineering` skill's boundaries first: rebuild behaviour and structure with your own code, assets,\nname and copy. Never ship the site's images, icons, fonts, logos or text; never bypass logins or bot protection.\nVisit the pages a normal visitor can, at a normal pace.\n\nThe output is a teardown folder in the project (for example `docs\u002Fresearch\u002F\u003Csite>\u002F`) with the capture, a tokens\nfile and a spec, and then an implementation measured against it.\n\n## 1. Capture, with a real browser\n\n`capture.mjs` (beside this file, Playwright only) records what a visitor sees, as measurements: run it from a project\nthat has Playwright installed (`npm i -D playwright && npx playwright install chromium` if it has not).\n\n```sh\nnode ${SLEIPNIR_SKILL_DIR}\u002Fcapture.mjs https:\u002F\u002Fexample.com docs\u002Fresearch\u002Fexample\u002Fcapture --states --har \"$(mktemp -d)\"\n```\n\nIt visits the start page and up to six same-origin pages it links to (navigation links first; `--routes N` changes\nthe number) at 390, 768 and 1440 px (`--widths`), and writes for each page a full-page screenshot per width,\n`aria.yml`, and `capture.json`: the layout measured at each width (page width, heading and body text sizes, and for\neach section its padding, gap, items per row and content column), the design values the page uses most (colours in\nhex, fonts, text sizes, spacing, radii, shadows, `:root` custom properties), the outline, headings, links, forms,\npicture sizes, accessibility basics, the errors and failed requests it logs, and the parts that move by themselves.\n`--states` opens each menu, pop-up, disclosure and tab one at a time at the widest and narrowest width and\nphotographs it into `states\u002F`. `--dark` captures the dark scheme. Other pages go to `routes\u002F\u003Cpage>\u002F`, listed in\n`routes.json`. Raw HARs can hold cookies, tokens and personal data, so `--har` takes a folder outside the repository.\n\nRead every screenshot it writes: images are returned as images, and measurements alone miss what a page looks like.\nThen capture what the script cannot reach by itself: hover and focus on interactive elements, toasts, empty, loading\nand error states, a filled and an invalid form, and reduced motion. Name each screenshot after the state.\n\n## 2. Turn the measurements into design tokens\n\nMeasure, do not eyeball: take values from `capture.json`, not from a look at a screenshot. Its `design` lists are\nordered by use, and `vars` holds the custom properties declared on `:root`, which often are the design system.\n\nFrom those lists, write `tokens.json` (or the project's token format): a colour palette with roles (background,\nsurface, text, muted, accent, border, danger), a type scale, a spacing scale (usually multiples of 4 or 8), radii,\nshadows, breakpoints and motion durations and easings. Rare one-off values are usually accidents; leave them out.\nPick your own fonts with similar metrics instead of shipping theirs.\n\n## 3. Inventory the components and layout\n\n- Page regions and the grid: max content width, columns, gutters at each breakpoint, what reflows or hides.\n- Components: buttons (sizes, variants, states), inputs, cards, navigation, tables, modals, tabs, toasts. For each:\n  anatomy, variants, states, keyboard behaviour, and the accessibility role and name from the ARIA snapshot.\n- Interactions: what each control does, transitions (duration, easing, what moves), scroll effects, focus\n  management in dialogs, shortcuts.\n- Content model: what data each view shows, its sort order, pagination, empty and limit cases.\n\n## 4. Network and data\n\nOpen the raw HARs in the temporary directory (they are JSON) and never commit them; only the sanitized shapes go\ninto the teardown folder. For each user action list the requests it makes: method, path pattern, query\nparameters, request and response shapes, status codes, caching headers, polling or WebSocket use. Write the shapes,\nnot the values, and strip anything personal. These become the API your rebuild serves; design it cleanly rather\nthan copying quirks you did not observe a reason for.\n\n## 5. Spec, then build\n\nWrite `spec.md` from the evidence: pages and flows, components with states, tokens, responsive rules, data and API,\naccessibility requirements, and acceptance checks (for example \"the command palette opens on Ctrl+K and Cmd+K,\ntraps focus, filters as you type, Escape closes and restores focus\"). Each item cites a screenshot or HAR entry.\n\nBuild it with the project's stack and the extracted tokens, using original copy, icons (an open icon set) and\nimagery.\n\n## 6. Compare\n\nServe the rebuild (a preview of its production build, or its built files), capture it with the same command and\noptions into another folder, and compare the two:\n\n```sh\nnode ${SLEIPNIR_SKILL_DIR}\u002Fcapture.mjs http:\u002F\u002Flocalhost:4173\u002F docs\u002Fresearch\u002Fexample\u002Fbuild --states\nnode ${SLEIPNIR_SKILL_DIR}\u002Fcompare.mjs docs\u002Fresearch\u002Fexample\u002Fcapture docs\u002Fresearch\u002Fexample\u002Fbuild\n```\n\n`compare.mjs` pairs the pages by path and prints, per page, **claims** that must hold (the page exists; it does not\nscroll sideways at a width where the original does not; it logs no errors and fails no requests the original does\nnot; it has the original's landmarks), **differences** with the exact values on both sides (text sizes, each\nsection's padding, items per row and content column, the colours, fonts, sizes and spacing the original uses most,\nthe order of the page's parts, accessibility basics) and what was **not compared** (a page or width missing from a\ncapture). It exits 1 while a claim fails or anything was not compared: a part that was never measured never passes.\nDifferences do not fail by themselves. Fix each one the spec says should match, with the value it gives; keep the\nones that make the rebuild your own, and say which in the spec.\n\nThen put each pair of screenshots side by side (read both images) for what numbers do not show: imagery, icons,\nalignment and the states. Parts listed as moving by themselves (videos, canvases, animations) hold one frame in a\nscreenshot: match how they look and move, not the frame. A pixel diff (`pixelmatch`, Playwright's\n`toHaveScreenshot`) is useful for regressions in the rebuild, not as a target of identity with the original.\n\nRun the comparison again after each round of fixes and keep its last report with the teardown. The work is done when\nit exits 0 and every remaining difference is one you chose.\n","# Reverse engineering a web UI\n\nRead the `reverse-engineering` skill's boundaries first: rebuild behaviour and structure with your own code, assets,\nname and copy. Never ship the site's images, icons, fonts, logos or text; never bypass logins or bot protection.\nVisit the pages a normal visitor can, at a normal pace.\n\nThe output is a teardown folder in the project (for example `docs\u002Fresearch\u002F\u003Csite>\u002F`) with the capture, a tokens\nfile and a spec, and then an implementation measured against it.\n\n## 1. Capture, with a real browser\n\n`capture.mjs` (beside this file, Playwright only) records what a visitor sees, as measurements: run it from a project\nthat has Playwright installed (`npm i -D playwright && npx playwright install chromium` if it has not).\n\n```sh\nnode ${SLEIPNIR_SKILL_DIR}\u002Fcapture.mjs https:\u002F\u002Fexample.com docs\u002Fresearch\u002Fexample\u002Fcapture --states --har \"$(mktemp -d)\"\n```\n\nIt visits the start page and up to six same-origin pages it links to (navigation links first; `--routes N` changes\nthe number) at 390, 768 and 1440 px (`--widths`), and writes for each page a full-page screenshot per width,\n`aria.yml`, and `capture.json`: the layout measured at each width (page width, heading and body text sizes, and for\neach section its padding, gap, items per row and content column), the design values the page uses most (colours in\nhex, fonts, text sizes, spacing, radii, shadows, `:root` custom properties), the outline, headings, links, forms,\npicture sizes, accessibility basics, the errors and failed requests it logs, and the parts that move by themselves.\n`--states` opens each menu, pop-up, disclosure and tab one at a time at the widest and narrowest width and\nphotographs it into `states\u002F`. `--dark` captures the dark scheme. Other pages go to `routes\u002F\u003Cpage>\u002F`, listed in\n`routes.json`. Raw HARs can hold cookies, tokens and personal data, so `--har` takes a folder outside the repository.\n\nRead every screenshot it writes: images are returned as images, and measurements alone miss what a page looks like.\nThen capture what the script cannot reach by itself: hover and focus on interactive elements, toasts, empty, loading\nand error states, a filled and an invalid form, and reduced motion. Name each screenshot after the state.\n\n## 2. Turn the measurements into design tokens\n\nMeasure, do not eyeball: take values from `capture.json`, not from a look at a screenshot. Its `design` lists are\nordered by use, and `vars` holds the custom properties declared on `:root`, which often are the design system.\n\nFrom those lists, write `tokens.json` (or the project's token format): a colour palette with roles (background,\nsurface, text, muted, accent, border, danger), a type scale, a spacing scale (usually multiples of 4 or 8), radii,\nshadows, breakpoints and motion durations and easings. Rare one-off values are usually accidents; leave them out.\nPick your own fonts with similar metrics instead of shipping theirs.\n\n## 3. Inventory the components and layout\n\n- Page regions and the grid: max content width, columns, gutters at each breakpoint, what reflows or hides.\n- Components: buttons (sizes, variants, states), inputs, cards, navigation, tables, modals, tabs, toasts. For each:\n  anatomy, variants, states, keyboard behaviour, and the accessibility role and name from the ARIA snapshot.\n- Interactions: what each control does, transitions (duration, easing, what moves), scroll effects, focus\n  management in dialogs, shortcuts.\n- Content model: what data each view shows, its sort order, pagination, empty and limit cases.\n\n## 4. Network and data\n\nOpen the raw HARs in the temporary directory (they are JSON) and never commit them; only the sanitized shapes go\ninto the teardown folder. For each user action list the requests it makes: method, path pattern, query\nparameters, request and response shapes, status codes, caching headers, polling or WebSocket use. Write the shapes,\nnot the values, and strip anything personal. These become the API your rebuild serves; design it cleanly rather\nthan copying quirks you did not observe a reason for.\n\n## 5. Spec, then build\n\nWrite `spec.md` from the evidence: pages and flows, components with states, tokens, responsive rules, data and API,\naccessibility requirements, and acceptance checks (for example \"the command palette opens on Ctrl+K and Cmd+K,\ntraps focus, filters as you type, Escape closes and restores focus\"). Each item cites a screenshot or HAR entry.\n\nBuild it with the project's stack and the extracted tokens, using original copy, icons (an open icon set) and\nimagery.\n\n## 6. Compare\n\nServe the rebuild (a preview of its production build, or its built files), capture it with the same command and\noptions into another folder, and compare the two:\n\n```sh\nnode ${SLEIPNIR_SKILL_DIR}\u002Fcapture.mjs http:\u002F\u002Flocalhost:4173\u002F docs\u002Fresearch\u002Fexample\u002Fbuild --states\nnode ${SLEIPNIR_SKILL_DIR}\u002Fcompare.mjs docs\u002Fresearch\u002Fexample\u002Fcapture docs\u002Fresearch\u002Fexample\u002Fbuild\n```\n\n`compare.mjs` pairs the pages by path and prints, per page, **claims** that must hold (the page exists; it does not\nscroll sideways at a width where the original does not; it logs no errors and fails no requests the original does\nnot; it has the original's landmarks), **differences** with the exact values on both sides (text sizes, each\nsection's padding, items per row and content column, the colours, fonts, sizes and spacing the original uses most,\nthe order of the page's parts, accessibility basics) and what was **not compared** (a page or width missing from a\ncapture). It exits 1 while a claim fails or anything was not compared: a part that was never measured never passes.\nDifferences do not fail by themselves. Fix each one the spec says should match, with the value it gives; keep the\nones that make the rebuild your own, and say which in the spec.\n\nThen put each pair of screenshots side by side (read both images) for what numbers do not show: imagery, icons,\nalignment and the states. Parts listed as moving by themselves (videos, canvases, animations) hold one frame in a\nscreenshot: match how they look and move, not the frame. A pixel diff (`pixelmatch`, Playwright's\n`toHaveScreenshot`) is useful for regressions in the rebuild, not as a target of identity with the original.\n\nRun the comparison again after each round of fixes and keep its last report with the teardown. The work is done when\nit exits 0 and every remaining difference is one you chose.\n",{"name":5,"author":23,"license":14,"description":7},"Sleipnir; the measured capture and comparison follow the website checks of Craft Anything (github.com\u002Fstorytold\u002Fcraft-anything, MIT OR Apache-2.0); no code is copied","main","23fde6dd293bd85fcb7b6a5d37af1ba7ea752a24","internal\u002Fskills\u002Fbuiltin\u002Fdata\u002Freverse-engineering-ui","https:\u002F\u002Fgithub.com\u002FAnemos-labs\u002FSleipnir","https:\u002F\u002Fgithub.com\u002FAnemos-labs","2026-11-13 05:46:48",{"source":8,"skillName":5,"commands":31,"prompt":41,"zipAvailable":42},[32,35,38],{"tool":33,"command":34},"npx","npx skills add Anemos-labs\u002FSleipnir --skill reverse-engineering-ui",{"tool":36,"command":37},"bunx","bunx skills add Anemos-labs\u002FSleipnir --skill reverse-engineering-ui",{"tool":39,"command":40},"pnpm","pnpm dlx skills add Anemos-labs\u002FSleipnir --skill reverse-engineering-ui","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FAnemos-labs\u002FSleipnir\u002Fblob\u002Fmain\u002Finternal\u002Fskills\u002Fbuiltin\u002Fdata\u002Freverse-engineering-ui\u002FSKILL.md",true,[44,50],{"path":45,"resourceType":46,"resourceTypeDesc":47,"sizeBytes":48,"sourceHtmlUrl":49},"capture.mjs","SCRIPT","脚本",20361,"https:\u002F\u002Fgithub.com\u002FAnemos-labs\u002FSleipnir\u002Fblob\u002Fmain\u002Finternal\u002Fskills\u002Fbuiltin\u002Fdata\u002Freverse-engineering-ui\u002Fcapture.mjs",{"path":51,"resourceType":46,"resourceTypeDesc":47,"sizeBytes":52,"sourceHtmlUrl":53},"compare.mjs",12927,"https:\u002F\u002Fgithub.com\u002FAnemos-labs\u002FSleipnir\u002Fblob\u002Fmain\u002Finternal\u002Fskills\u002Fbuiltin\u002Fdata\u002Freverse-engineering-ui\u002Fcompare.mjs",[55,62,69,76,83,90],{"skillNo":56,"name":57,"nameZh":6,"description":58,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":59,"categories":60,"keywords":61,"publishedAt":18},"01M7DM2MTFM5P9A96RBMK0CEWW","spec","Goal to specification, vertical slices and milestones a judge can check. Load when planning a product or large feature or splitting work into tasks.","https:\u002F\u002Fgithub.com\u002FAnemos-labs\u002FSleipnir\u002Fblob\u002Fmain\u002Finternal\u002Fskills\u002Fbuiltin\u002Fdata\u002Fspec\u002FSKILL.md",[],[],{"skillNo":63,"name":64,"nameZh":6,"description":65,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":66,"categories":67,"keywords":68,"publishedAt":18},"01M7DM2HSF795J7BGMN9BSZZYJ","sleipnir-plugin","Make or change a Sleipnir plugin and load it live (sleipnir tool).","https:\u002F\u002Fgithub.com\u002FAnemos-labs\u002FSleipnir\u002Fblob\u002Fmain\u002Finternal\u002Fskills\u002Fbuiltin\u002Fdata\u002Fsleipnir-plugin\u002FSKILL.md",[],[],{"skillNo":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"publishedAt":18},"01M7DM2391M8KK319ZXMWVK6PJ","prototype","Throwaway prototype that settles a design question by observation. Load when choosing between layouts, interactions or state models.","https:\u002F\u002Fgithub.com\u002FAnemos-labs\u002FSleipnir\u002Fblob\u002Fmain\u002Finternal\u002Fskills\u002Fbuiltin\u002Fdata\u002Fprototype\u002FSKILL.md",[],[],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":18},"01M7DM1YHX1MNZJ262D8B7X782","plain-writing","Clear technical writing without machine-generated tells. Load before writing a README, docs, site copy, release notes, a commit or PR message.","https:\u002F\u002Fgithub.com\u002FAnemos-labs\u002FSleipnir\u002Fblob\u002Fmain\u002Finternal\u002Fskills\u002Fbuiltin\u002Fdata\u002Fplain-writing\u002FSKILL.md",[],[],{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":18},"01M7DM1P5W6Y88NHYFQG9JWMDR","diagnose","Feedback-loop-first diagnosis of hard bugs, flaky tests and performance regressions. Load before changing code when the cause is not obvious.","https:\u002F\u002Fgithub.com\u002FAnemos-labs\u002FSleipnir\u002Fblob\u002Fmain\u002Finternal\u002Fskills\u002Fbuiltin\u002Fdata\u002Fdiagnose\u002FSKILL.md",[],[],{"skillNo":91,"name":92,"nameZh":6,"description":93,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":94,"categories":95,"keywords":96,"publishedAt":18},"01M7DM1GNE3JFR8WV1SWJ5EXJ9","codebase-design","Deep modules, interfaces and seams. Load when designing or restructuring modules or deciding where an interface goes.","https:\u002F\u002Fgithub.com\u002FAnemos-labs\u002FSleipnir\u002Fblob\u002Fmain\u002Finternal\u002Fskills\u002Fbuiltin\u002Fdata\u002Fcodebase-design\u002FSKILL.md",[],[]]