[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7CRZEZGPJB0F385JSZ2813D":3,"skill-same:01M7CRZEZGPJB0F385JSZ2813D":65},{"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":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":30,"install":31,"resources":44},"01M7CRZEZGPJB0F385JSZ2813D","bama-design-from-app",null,"Rebuild the look of an app the user likes as a native SwiftUI design kit, by measuring its screenshots (sizes, spacing, type, colors, icons), building its parts, and comparing pixel by pixel until they match. Use when the user names an app whose look they want, shares screenshots of one, or says \"make it look like X\".","newmindsgroup\u002Fvisual-design-kit","newmindsgroup","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F38358889?v=4","01M7CRXVBNJ0WGRTNWHWY2HVQ9","01M7CRXVC9ZXSZBAPZTP3Y39CA",2,"MIT","https:\u002F\u002Fgithub.com\u002Fnewmindsgroup\u002Fvisual-design-kit\u002Fblob\u002Fmain\u002Fextras\u002Fbama-mac-studio\u002Fskills\u002Fbama-design-from-app\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: bama-design-from-app\ndescription: Rebuild the look of an app the user likes as a native SwiftUI design kit, by measuring its screenshots (sizes, spacing, type, colors, icons), building its parts, and comparing pixel by pixel until they match. Use when the user names an app whose look they want, shares screenshots of one, or says \"make it look like X\".\nargument-hint: \"\u003Capp name or screenshot paths>\"\n---\n\n\u003C!-- Version-Timestamp: 2026-10-27 07:36:32 AST -->\n\n## Adapted execution contract\n\nThis is the pinned, MIT-attributed BAMA capability adapted for the owned design kit. Read `ADAPTATION.md` at the BAMA package root before executing helpers. Project instructions, approved DESIGN.md and canonical tokens take precedence. Use supported Codex or Claude Code tools. Resolve this skill's sibling files relative to its installed SKILL.md; `skill_dir` is a task-local shell variable that you set to that resolved directory before running the examples in either host. Invoke a named `bama-*` skill through the host's supported skill mechanism.\n\nStage local builds by default. Installation, signing identity selection, launch, CLI linking, MCP registration, system setting changes and capture access are separate explicit operations. Existing task authorization applies; ask only for an action not already authorized. Stage or commit only when the current task or repository workflow authorizes it. Stage explicit paths and include required attribution. The helpers do not commit. Preserve the feature, story and testing workflow below using the hardened helpers. Legacy installed-app paths in examples must be replaced by the staged binary returned by `build.sh`.\n\nBefore a new scaffold exists, keep planning evidence under the selected `\u003CAppName>-planning\u002Fdocs\u002F` sibling or an existing approved planning folder. Treat docs paths below as relative to that planning folder until the fresh app is scaffolded, then copy the planning docs explicitly without replacing existing files. For an existing app, keep its current project layout.\n\nThe upstream acceptance statements describe checks to perform, never completed results. Screenshots, runtime behavior, permissions and cross-host acceptance require actual evidence. Use synthetic data and owned temporary test roots. Do not run a hosted session over real app data without project authorization.\n\n\n\n# Design from app\n\nLook at an app, measure it, and rebuild its design system in SwiftUI. The\nresult is a design kit (`bama-design-kit` skill) with the reference app's\nnumbers, and one reference screen that matches the screenshot.\n\nGuessing gets close. Measuring gets it right. Two scripts do the\nmeasuring, next to this skill:\n\n- `scripts\u002Fmeasure.swift`: sizes, positions, text heights, and colors from\n  a screenshot.\n- `scripts\u002Fcompare.swift`: a side-by-side, a diff, and the share of pixels\n  that differ.\n\nRun them with `swift \"${skill_dir}\u002Fscripts\u002Fmeasure.swift\" ...`.\nRecord the capture scale explicitly. Pass `--scale 1` for a 1x screenshot or `--scale 2` for a verified Retina capture when measuring. Full-image comparison uses pixel dimensions directly. Region comparison requires `--scale N`, the measured pixels per logical point. Never infer the scale merely from the browser or host.\n\n## 1. Get the screenshots\n\nAsk for screenshots, or take them with the `bama-clone` skill. You need:\n\n- The window only, at 2x, no desktop. Save them in `design\u002Freference\u002F`.\n- One screen with the most parts on it (a sidebar, a list, a toolbar),\n  plus close-ups of menus, dialogs, and dark mode if they matter.\n- The window size: `measure.swift info shot.png`.\n\nCheck: `info` prints the window size in points, and every screenshot uses\nthe same scale.\n\n## 2. List the parts\n\nLook at each screenshot and name every distinct part: window chrome,\nsidebar row, section header, primary action, list row, checkbox, date\nchip, icon button, divider. Start `design\u002FKIT.md` from the `bama-design-kit`\nskill's kit-spec.md with one section per part.\n\nCheck: every visible element on the main screenshot belongs to a part.\n\n## 3. Measure\n\nFill `design\u002FKIT.md` with numbers, not estimates. The recipes and the\ntraps are in [measuring.md](measuring.md). In short:\n\n| To find | Command |\n| --- | --- |\n| Sidebar width, panes | `hline shot.png \u003Cy in an empty area>` |\n| Row positions and pitch | `rows shot.png \u003Cx0> \u003Cx1> [y0 y1]` |\n| Left edges, gaps | `cols shot.png \u003Cy0> \u003Cy1> [x0 x1]` |\n| Selection pill, dividers | `vline` and `hline` through it, `--tolerance 4` |\n| Text and icon colors | `ink shot.png x y w h` |\n| Surface colors | `palette shot.png x y w h` |\n| A close look | `crop shot.png x y w h out.png 4` |\n\nCheck: every token and every part size in `design\u002FKIT.md` has a number\nfrom a command.\n\n## 4. Find the font and the icons\n\n- Most apps on the Mac use the system font, even web apps. Start there.\n  When the letters differ (a, g, t, digits), name the font and pick it or\n  an open alternative with a license that allows bundling.\n- Text sizes come from step 6: build, measure the same word in both\n  images, scale.\n- Icons: note the size, stroke weight, corners, and whether selected rows\n  switch to a filled form. Match with SF Symbols at a light weight first;\n  draw the ones that do not match as shapes (`bama-design-kit` parts.md, Icons).\n\nCheck: `design\u002FKIT.md` names the font, the icon source, and the icon size\nand weight.\n\n## 5. Build the kit and one screen\n\nInvoke the host-supported skill `bama-design-kit` and build the tokens, the parts, the\nwindow chrome, and the gallery from `design\u002FKIT.md`. Then build the main\nscreenshot's screen from kit parts only, with the same data and the same\nwindow size.\n\nCheck: a snapshot of that screen has the same size in pixels as the\nreference.\n\n## 6. Compare until it matches\n\n```bash\nswift \"${skill_dir}\u002Fscripts\u002Fcompare.swift\" design\u002Freference\u002Fmain.png \u002Ftmp\u002F\u003CApp>-shots\u002F\u003Cpage>-light.png \u002Ftmp\u002F\u003CApp>-compare\nswift \"${skill_dir}\u002Fscripts\u002Fcompare.swift\" ... \u002Ftmp\u002F\u003CApp>-compare-sidebar 0 0 220 300 --scale 2  # only for a verified 2x capture\n```\n\nOpen `side-by-side.png` and `diff.png` with the Read tool. Then measure\nthe same rows, edges, and words in both images, and fix the tokens, not\nthe views. Order: window size, text sizes, columns and left edges, row\nheights, colors, icons.\n\nCheck: under 2% of pixels differ on the whole window, and every row and\nleft edge is within 1.5 pt of the reference.\n\n## 7. Make it yours\n\nBefore the app ships to anyone else, replace what belongs to the other\ncompany: its name, logo, illustrations, and any font or icon it owns.\nKeep the structure, the spacing, and the feel. Write the replacements in\n`design\u002FKIT.md`.\n\nDone when `design\u002FKIT.md` has a measured number for every token and part,\nthe kit's gallery shows every part, the reference screen passes step 6,\nand step 7 lists what was replaced.\n","\u003C!-- Version-Timestamp: 2026-10-27 07:36:32 AST -->\n\n## Adapted execution contract\n\nThis is the pinned, MIT-attributed BAMA capability adapted for the owned design kit. Read `ADAPTATION.md` at the BAMA package root before executing helpers. Project instructions, approved DESIGN.md and canonical tokens take precedence. Use supported Codex or Claude Code tools. Resolve this skill's sibling files relative to its installed SKILL.md; `skill_dir` is a task-local shell variable that you set to that resolved directory before running the examples in either host. Invoke a named `bama-*` skill through the host's supported skill mechanism.\n\nStage local builds by default. Installation, signing identity selection, launch, CLI linking, MCP registration, system setting changes and capture access are separate explicit operations. Existing task authorization applies; ask only for an action not already authorized. Stage or commit only when the current task or repository workflow authorizes it. Stage explicit paths and include required attribution. The helpers do not commit. Preserve the feature, story and testing workflow below using the hardened helpers. Legacy installed-app paths in examples must be replaced by the staged binary returned by `build.sh`.\n\nBefore a new scaffold exists, keep planning evidence under the selected `\u003CAppName>-planning\u002Fdocs\u002F` sibling or an existing approved planning folder. Treat docs paths below as relative to that planning folder until the fresh app is scaffolded, then copy the planning docs explicitly without replacing existing files. For an existing app, keep its current project layout.\n\nThe upstream acceptance statements describe checks to perform, never completed results. Screenshots, runtime behavior, permissions and cross-host acceptance require actual evidence. Use synthetic data and owned temporary test roots. Do not run a hosted session over real app data without project authorization.\n\n\n\n# Design from app\n\nLook at an app, measure it, and rebuild its design system in SwiftUI. The\nresult is a design kit (`bama-design-kit` skill) with the reference app's\nnumbers, and one reference screen that matches the screenshot.\n\nGuessing gets close. Measuring gets it right. Two scripts do the\nmeasuring, next to this skill:\n\n- `scripts\u002Fmeasure.swift`: sizes, positions, text heights, and colors from\n  a screenshot.\n- `scripts\u002Fcompare.swift`: a side-by-side, a diff, and the share of pixels\n  that differ.\n\nRun them with `swift \"${skill_dir}\u002Fscripts\u002Fmeasure.swift\" ...`.\nRecord the capture scale explicitly. Pass `--scale 1` for a 1x screenshot or `--scale 2` for a verified Retina capture when measuring. Full-image comparison uses pixel dimensions directly. Region comparison requires `--scale N`, the measured pixels per logical point. Never infer the scale merely from the browser or host.\n\n## 1. Get the screenshots\n\nAsk for screenshots, or take them with the `bama-clone` skill. You need:\n\n- The window only, at 2x, no desktop. Save them in `design\u002Freference\u002F`.\n- One screen with the most parts on it (a sidebar, a list, a toolbar),\n  plus close-ups of menus, dialogs, and dark mode if they matter.\n- The window size: `measure.swift info shot.png`.\n\nCheck: `info` prints the window size in points, and every screenshot uses\nthe same scale.\n\n## 2. List the parts\n\nLook at each screenshot and name every distinct part: window chrome,\nsidebar row, section header, primary action, list row, checkbox, date\nchip, icon button, divider. Start `design\u002FKIT.md` from the `bama-design-kit`\nskill's kit-spec.md with one section per part.\n\nCheck: every visible element on the main screenshot belongs to a part.\n\n## 3. Measure\n\nFill `design\u002FKIT.md` with numbers, not estimates. The recipes and the\ntraps are in [measuring.md](measuring.md). In short:\n\n| To find | Command |\n| --- | --- |\n| Sidebar width, panes | `hline shot.png \u003Cy in an empty area>` |\n| Row positions and pitch | `rows shot.png \u003Cx0> \u003Cx1> [y0 y1]` |\n| Left edges, gaps | `cols shot.png \u003Cy0> \u003Cy1> [x0 x1]` |\n| Selection pill, dividers | `vline` and `hline` through it, `--tolerance 4` |\n| Text and icon colors | `ink shot.png x y w h` |\n| Surface colors | `palette shot.png x y w h` |\n| A close look | `crop shot.png x y w h out.png 4` |\n\nCheck: every token and every part size in `design\u002FKIT.md` has a number\nfrom a command.\n\n## 4. Find the font and the icons\n\n- Most apps on the Mac use the system font, even web apps. Start there.\n  When the letters differ (a, g, t, digits), name the font and pick it or\n  an open alternative with a license that allows bundling.\n- Text sizes come from step 6: build, measure the same word in both\n  images, scale.\n- Icons: note the size, stroke weight, corners, and whether selected rows\n  switch to a filled form. Match with SF Symbols at a light weight first;\n  draw the ones that do not match as shapes (`bama-design-kit` parts.md, Icons).\n\nCheck: `design\u002FKIT.md` names the font, the icon source, and the icon size\nand weight.\n\n## 5. Build the kit and one screen\n\nInvoke the host-supported skill `bama-design-kit` and build the tokens, the parts, the\nwindow chrome, and the gallery from `design\u002FKIT.md`. Then build the main\nscreenshot's screen from kit parts only, with the same data and the same\nwindow size.\n\nCheck: a snapshot of that screen has the same size in pixels as the\nreference.\n\n## 6. Compare until it matches\n\n```bash\nswift \"${skill_dir}\u002Fscripts\u002Fcompare.swift\" design\u002Freference\u002Fmain.png \u002Ftmp\u002F\u003CApp>-shots\u002F\u003Cpage>-light.png \u002Ftmp\u002F\u003CApp>-compare\nswift \"${skill_dir}\u002Fscripts\u002Fcompare.swift\" ... \u002Ftmp\u002F\u003CApp>-compare-sidebar 0 0 220 300 --scale 2  # only for a verified 2x capture\n```\n\nOpen `side-by-side.png` and `diff.png` with the Read tool. Then measure\nthe same rows, edges, and words in both images, and fix the tokens, not\nthe views. Order: window size, text sizes, columns and left edges, row\nheights, colors, icons.\n\nCheck: under 2% of pixels differ on the whole window, and every row and\nleft edge is within 1.5 pt of the reference.\n\n## 7. Make it yours\n\nBefore the app ships to anyone else, replace what belongs to the other\ncompany: its name, logo, illustrations, and any font or icon it owns.\nKeep the structure, the spacing, and the feel. Write the replacements in\n`design\u002FKIT.md`.\n\nDone when `design\u002FKIT.md` has a measured number for every token and part,\nthe kit's gallery shows every part, the reference screen passes step 6,\nand step 7 lists what was replaced.\n",{"name":5,"description":7,"argument-hint":23},"\u003Capp name or screenshot paths>","main","753c596e097d0288f4f74e22d6b8457014eac8b2","extras\u002Fbama-mac-studio\u002Fskills\u002Fbama-design-from-app",0,"https:\u002F\u002Fgithub.com\u002Fnewmindsgroup\u002Fvisual-design-kit","https:\u002F\u002Fgithub.com\u002Fnewmindsgroup","2026-11-10 11:31:50",{"source":8,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add newmindsgroup\u002Fvisual-design-kit --skill bama-design-from-app",{"tool":37,"command":38},"bunx","bunx skills add newmindsgroup\u002Fvisual-design-kit --skill bama-design-from-app",{"tool":40,"command":41},"pnpm","pnpm dlx skills add newmindsgroup\u002Fvisual-design-kit --skill bama-design-from-app","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fnewmindsgroup\u002Fvisual-design-kit\u002Fblob\u002Fmain\u002Fextras\u002Fbama-mac-studio\u002Fskills\u002Fbama-design-from-app\u002FSKILL.md",true,[45,51,55,61],{"path":46,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":49,"sourceHtmlUrl":50},"agents\u002Fopenai.yaml","REFERENCE","参考文档",129,"https:\u002F\u002Fgithub.com\u002Fnewmindsgroup\u002Fvisual-design-kit\u002Fblob\u002Fmain\u002Fextras\u002Fbama-mac-studio\u002Fskills\u002Fbama-design-from-app\u002Fagents\u002Fopenai.yaml",{"path":52,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":53,"sourceHtmlUrl":54},"measuring.md",4020,"https:\u002F\u002Fgithub.com\u002Fnewmindsgroup\u002Fvisual-design-kit\u002Fblob\u002Fmain\u002Fextras\u002Fbama-mac-studio\u002Fskills\u002Fbama-design-from-app\u002Fmeasuring.md",{"path":56,"resourceType":57,"resourceTypeDesc":58,"sizeBytes":59,"sourceHtmlUrl":60},"scripts\u002Fcompare.swift","SCRIPT","脚本",6218,"https:\u002F\u002Fgithub.com\u002Fnewmindsgroup\u002Fvisual-design-kit\u002Fblob\u002Fmain\u002Fextras\u002Fbama-mac-studio\u002Fskills\u002Fbama-design-from-app\u002Fscripts\u002Fcompare.swift",{"path":62,"resourceType":57,"resourceTypeDesc":58,"sizeBytes":63,"sourceHtmlUrl":64},"scripts\u002Fmeasure.swift",12987,"https:\u002F\u002Fgithub.com\u002Fnewmindsgroup\u002Fvisual-design-kit\u002Fblob\u002Fmain\u002Fextras\u002Fbama-mac-studio\u002Fskills\u002Fbama-design-from-app\u002Fscripts\u002Fmeasure.swift",[66,73,80,87,94,101],{"skillNo":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"publishedAt":18},"01M7CSR2BPCD04SARPWN7EJ5R0","web-design","Load before planning, designing, auditing or launching any website, landing page, cinematic hero, microsite or above-the-fold layout, or a prompt for Lovable, Bolt or v0 to build one, including regulated (prescription drug, health, finance), multilingual or market-specific launches. Covers page types (home, product, pricing, about, blog), conversion and ethical persuasion, responsive and fluid layouts, Core Web Vitals, SEO and structured data, localization and language-law requirements, stack and CMS choice (Astro, Next.js, WordPress, Webflow, Framer) and launch QA.","https:\u002F\u002Fgithub.com\u002Fnewmindsgroup\u002Fvisual-design-kit\u002Fblob\u002Fmain\u002Fplugins\u002Fvisual-design-studio\u002Fskills\u002Fweb-design\u002FSKILL.md",[],[],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":18},"01M7CSQX00CVQAWP2QDHKVXFMS","ux-design","Load before designing or reviewing any flow, form, onboarding, navigation or content for real users, especially low-literacy, older, neurodivergent, child or other specific audiences. Covers research and usability tests, heuristic reviews, personas and jobs to be done, journeys and service blueprints, information architecture, UX laws, SUS, SEQ and HEART metrics, plain language and reading level, and microcopy and error messages.","https:\u002F\u002Fgithub.com\u002Fnewmindsgroup\u002Fvisual-design-kit\u002Fblob\u002Fmain\u002Fplugins\u002Fvisual-design-studio\u002Fskills\u002Fux-design\u002FSKILL.md",[],[],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":18},"01M7CSQQE0HX6Q8YR2EA1TR6P4","ui-design","Load before designing or specifying any interface screen or component, even a quick one: forms, tables, navigation, dashboards, onboarding, auth and passkeys, pricing, checkout, search and filters, settings, empty, loading and error states, notifications, consent and age-appropriate flows, and AI chat and agent interfaces, all to WCAG 2.2 AA. Also picks React UI libraries (toasts, drawers, command menus). Gives component specs, state matrices, sizes, density and keyboard and accessibility behavior.","https:\u002F\u002Fgithub.com\u002Fnewmindsgroup\u002Fvisual-design-kit\u002Fblob\u002Fmain\u002Fplugins\u002Fvisual-design-studio\u002Fskills\u002Fui-design\u002FSKILL.md",[],[],{"skillNo":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":91,"categories":92,"keywords":93,"publishedAt":18},"01M7CSQFM0F9QKZ17S54PYN8M7","typography","Choose, pair, size and set type for brand, web, app, print, slides, signage and motion: modular scales, fluid clamp() type, measure, leading, tracking, OpenType features, font licensing and web font loading, and multiscript setting for CJK, Arabic, Hebrew, Devanagari and Thai. Use when selecting or pairing fonts, building a type scale or type tokens, fixing weak hierarchy or bad line breaks, setting long-form text or numbers, loading web fonts, or localizing type for another market.","https:\u002F\u002Fgithub.com\u002Fnewmindsgroup\u002Fvisual-design-kit\u002Fblob\u002Fmain\u002Fplugins\u002Fvisual-design-studio\u002Fskills\u002Ftypography\u002FSKILL.md",[],[],{"skillNo":95,"name":96,"nameZh":6,"description":97,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":98,"categories":99,"keywords":100,"publishedAt":18},"01M7CSQ95PB7K9JBEFYZVA7226","reference-reconstruction","Reconstructs the observed interface and behavior of a supplied app, site or screenshot set using a screen index, measurements, state and command maps, reusable components and matched-condition comparisons. Use when asked to reverse engineer, clone, reproduce or match a reference product, then adapt it if requested.","https:\u002F\u002Fgithub.com\u002Fnewmindsgroup\u002Fvisual-design-kit\u002Fblob\u002Fmain\u002Fplugins\u002Fvisual-design-studio\u002Fskills\u002Freference-reconstruction\u002FSKILL.md",[],[],{"skillNo":102,"name":103,"nameZh":6,"description":104,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":105,"categories":106,"keywords":107,"publishedAt":18},"01M7CSQ1XRH2MBXH21MSZ7PXWJ","print-packaging-social","Load before any print, packaging, label, barcode, social, out-of-home, slide-deck or email design question, even a quick one, and before making finished collateral files. Specs: bleed, safe zones, 300ppi, CMYK, PDF\u002FX preflight, dielines, barcodes, social formats with 9:16 safe areas, billboard letter heights, 16:9 decks, bulletproof email. Renders token-driven brand books, sell sheets, cards, carousels and decks to PDF and PNG with a Canva editable twin.","https:\u002F\u002Fgithub.com\u002Fnewmindsgroup\u002Fvisual-design-kit\u002Fblob\u002Fmain\u002Fplugins\u002Fvisual-design-studio\u002Fskills\u002Fprint-packaging-social\u002FSKILL.md",[],[]]