[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7CS5SMRNQ5EN4KXHM838X8T":3,"skill-same:01M7CS5SMRNQ5EN4KXHM838X8T":50},{"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":23,"commitSha":24,"skillDirectory":25,"forksCount":26,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":29,"install":30,"resources":43},"01M7CS5SMRNQ5EN4KXHM838X8T","design-google-docs",null,"Design and audit native Google Docs for clear, attractive, easy-to-skim reading. Use for pageless reports, questionnaires, department workbooks, document tabs, typography, spacing, tables, and visual cleanup. Preserves answers and source evidence; complements the Google Docs connector skill rather than replacing its editing safeguards.","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\u002Fplugins\u002Fvisual-design-studio\u002Flibrary\u002Fdraft-skills\u002Fdesign-google-docs\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: design-google-docs\ndescription: Design and audit native Google Docs for clear, attractive, easy-to-skim reading. Use for pageless reports, questionnaires, department workbooks, document tabs, typography, spacing, tables, and visual cleanup. Preserves answers and source evidence; complements the Google Docs connector skill rather than replacing its editing safeguards.\n---\n\n# Google Docs editorial design\n\nVersion-Timestamp: 2026-10-05 13:07:59 AST\n\n## Outcome\n\nProduce a native, editable document that makes its purpose, next action, section boundaries, and evidence status easy to find. Use restrained editorial design and progressive disclosure. These are general readability practices, not a claim of clinical ADHD validation.\n\nUse this method with the installed Google Docs skill for trusted reads, native controls, revision guards, and exact API operations. Do not use website-generation or image-generation tools for ordinary document styling.\n\n## Inputs and boundaries\n\n1. Confirm target document IDs, account, audience, declared viewing context (desktop, split panel or mobile), tab roles, approved brand guidance, and whether wording may change. Reuse answers already in the conversation. For a styling-only request, preserve wording by default. Record the user's authorized scope and any approved content delta in the work packet.\n2. Read project brand\u002Fdesign guidance when present. The neutral starter tokens below are a fallback, never a substitute for approved client tokens. After any token override, repeat contrast, style read-back and rendered checks.\n3. Save a rich before snapshot and a semantic baseline in the private project work packet. Inventory every tab, table shape, merged cell, answer area, native chip, link, and protected control. A plain-text export is not a safe reconstruction source.\n4. Inspect the rendered document before deciding the treatment. Select a pilot containing the main tab roles and the densest relevant table. Record viewport, zoom and selected text-width setting.\n5. Keep client content and screenshots in its approved workspace. The reusable skill and external method reviews contain generic examples only. Do not change sharing, send documents, or publish a plugin as a side effect.\n\n## Design decisions\n\n### Structure and hierarchy\n\n- One tab should have one clear purpose. Use descriptive tab names, one title, native section headings, and short action labels.\n- Give the reader a starting point: purpose, what to do, and what is still unvalidated. Reuse existing text when rewriting is outside scope.\n- Use a compact introduction. Avoid putting a full instruction manual ahead of the first useful question.\n- Use native Title and Heading styles so navigation and future editing work. Update named-style defaults before range-specific exceptions. Verify actual API support and read back the result.\n- Separate primary content, actions, pending decisions, and source evidence. Use text labels as well as color. Preserve uncertainty and source limits visibly.\n- Do not bold entire paragraphs by default. Emphasize the question or decision and short labels. Preserve legally or operationally meaningful emphasis unless a reviewed change is authorized.\n- Long evidence passages need semantic chunking. If wording changes are allowed, use short finding blocks with statement, source, implication, and open decision. If wording is fixed, use spacing and headings; propose content restructuring separately rather than silently abridging evidence.\n\n### Typography and rhythm\n\nUse [tokens and layout rules](references\u002Ftokens.md) as a neutral starting point. Body text should usually be 11.5 to 12pt. Keep metadata readable, usually 10pt or larger. Do not reduce text size to force a table to fit.\n\nUse more space before a section than between its heading and text. Body prose may use 6pt after, while table paragraphs and lists usually need only 3 to 4pt. Remove oversized blank-paragraph styling without deleting content or answer space. Do not compress intentionally blank response areas.\n\nKeep left alignment and avoid long all-caps passages. Use color sparingly. Decorative rules may be light only if heading text and spacing independently communicate the boundary. All text must meet a measured 4.5:1 contrast ratio against its background.\n\n### Pageless width and tables\n\nPageless mode and viewer text width are different. Google's Text width preference affects the viewer's pageless documents, not a guaranteed layout setting for recipients. Page margins and page-size changes are not a pageless width solution. Explain this distinction when widening a document.\n\nMeasure available reading space with the tab sidebar open. Use a comfortable prose measure; a wider data table does not justify unlimited prose width. Verify both normal desktop and the actual constrained workspace.\n\nClassify each table before styling:\n\n| Table role | Treatment |\n| --- | --- |\n| Questionnaire or form | Short question heading, ordinary context text, clearly labeled response area, consistent restrained answer fill. Do not zebra rows mechanically or pin a question as a data header. |\n| Evidence or comparison | Clear header row, deliberate column proportions, light alternating fills only when useful, top alignment, pinned header where supported. |\n| Introduction or callout | Compact padding and concise hierarchy. No oversized decorative box. |\n\nResolve widths from fresh table anchors, not text searches or guessed offsets. A typical starting padding is 9pt vertical and 12pt horizontal. Tune it from actual screenshots. Verify that every response region has a visible text label. Compare empty-cell and blank-paragraph counts before and after; retain usable answer space at body size, not a tiny spacer size.\n\nWhen a table overflows: first reduce excess padding, then rebalance columns. Prefer stacked content for forms or split\u002Ftransposed comparisons when content restructuring is authorized. If fixed structure must remain, document horizontal scrolling honestly and provide a practical viewer-width\u002Fsidebar adjustment. For required mobile delivery that fails the fit check, obtain authorization for the necessary restructuring before declaring it ready. Never claim mobile readiness from a desktop viewport. Do not make every table wider by a universal constant.\n\n## Execution and verification\n\n1. Create a reviewed styling plan and preserve the before snapshot. Make a recoverable pilot first.\n2. Use native connector requests with tab IDs, narrow field masks and required revision IDs. Validate nonempty UTF-16 ranges. Apply defaults before explicit exceptions. Do not rebuild a form from Markdown or plain text.\n3. On an uncertain write result, read the current state and reconcile before another mutation. An explicit rejected atomic batch may be repaired; an unknown result must not be replayed blindly.\n4. Read back every modified tab. Compare ordered text, link targets, chip type and target\u002Fdate\u002Fperson properties, list IDs\u002Fnesting\u002Fglyphs, table row and column counts, merged-cell map, and per-cell content. Ignore only intended visual style fields. When explicit text edits are authorized, compare against the approved delta rather than ignoring all text changes.\n5. Verify tab mode, heading semantics, named styles and intended exceptions, cell widths, padding, header treatment and answer areas.\n6. Visually inspect title\u002Fintro, a dense question with its answer, an evidence section, the widest data table, and a feature\u002Fstatus block. Check desktop and the constrained viewer, plus zoom or mobile when those are delivery requirements. Record actual regions and dimensions. Sampling is not exhaustive inspection.\n7. Only after the pilot passes, apply the same role-based rules to other documents. Inventory exceptions first, verify every document structurally, and sample materially different layouts visually.\n8. Save screenshots privately and provide a useful preview and direct document links. Report defects that remain, including content density and untested devices.\n\n## Model and review choice\n\nUse the active tool-capable Codex model to coordinate native edits, structural checks and visual inspection. Select effort through model-governor for the current stage; do not claim prose changes the running model. A capable independent reviewer such as approved Fable 5.1 can critique the generic method and skill. Use confidential screenshots with another model only when project-specific data approval exists. Model choice does not replace rendering, contrast checks or preservation tests, and there is no verified universal best model for Google Docs aesthetics.\n\n## Deliverables and acceptance\n\nReturn updated native documents, a private before\u002Fafter audit, style tokens, preservation results, screenshot coverage, limitations and next action. Add the actual Version-Timestamp to the work record and newly authored artifact metadata. Preserve source-version metadata rather than falsely re-dating the underlying evidence.\n\nPass only when the authorized documents were edited, content\u002Fcontrol preservation passed, intended styles were read back, sampled rendering is acceptable for the declared viewing context, and required independent review is resolved. If access fails, name the exact completed subset and resume point. Do not call a specification or API success alone a beautiful, verified document.\n\nFor future work, invoke `$design-google-docs` with the document links, audience and permitted content changes. Combine it with the native Google Docs connector skill.\n","# Google Docs editorial design\n\nVersion-Timestamp: 2026-10-05 13:07:59 AST\n\n## Outcome\n\nProduce a native, editable document that makes its purpose, next action, section boundaries, and evidence status easy to find. Use restrained editorial design and progressive disclosure. These are general readability practices, not a claim of clinical ADHD validation.\n\nUse this method with the installed Google Docs skill for trusted reads, native controls, revision guards, and exact API operations. Do not use website-generation or image-generation tools for ordinary document styling.\n\n## Inputs and boundaries\n\n1. Confirm target document IDs, account, audience, declared viewing context (desktop, split panel or mobile), tab roles, approved brand guidance, and whether wording may change. Reuse answers already in the conversation. For a styling-only request, preserve wording by default. Record the user's authorized scope and any approved content delta in the work packet.\n2. Read project brand\u002Fdesign guidance when present. The neutral starter tokens below are a fallback, never a substitute for approved client tokens. After any token override, repeat contrast, style read-back and rendered checks.\n3. Save a rich before snapshot and a semantic baseline in the private project work packet. Inventory every tab, table shape, merged cell, answer area, native chip, link, and protected control. A plain-text export is not a safe reconstruction source.\n4. Inspect the rendered document before deciding the treatment. Select a pilot containing the main tab roles and the densest relevant table. Record viewport, zoom and selected text-width setting.\n5. Keep client content and screenshots in its approved workspace. The reusable skill and external method reviews contain generic examples only. Do not change sharing, send documents, or publish a plugin as a side effect.\n\n## Design decisions\n\n### Structure and hierarchy\n\n- One tab should have one clear purpose. Use descriptive tab names, one title, native section headings, and short action labels.\n- Give the reader a starting point: purpose, what to do, and what is still unvalidated. Reuse existing text when rewriting is outside scope.\n- Use a compact introduction. Avoid putting a full instruction manual ahead of the first useful question.\n- Use native Title and Heading styles so navigation and future editing work. Update named-style defaults before range-specific exceptions. Verify actual API support and read back the result.\n- Separate primary content, actions, pending decisions, and source evidence. Use text labels as well as color. Preserve uncertainty and source limits visibly.\n- Do not bold entire paragraphs by default. Emphasize the question or decision and short labels. Preserve legally or operationally meaningful emphasis unless a reviewed change is authorized.\n- Long evidence passages need semantic chunking. If wording changes are allowed, use short finding blocks with statement, source, implication, and open decision. If wording is fixed, use spacing and headings; propose content restructuring separately rather than silently abridging evidence.\n\n### Typography and rhythm\n\nUse [tokens and layout rules](references\u002Ftokens.md) as a neutral starting point. Body text should usually be 11.5 to 12pt. Keep metadata readable, usually 10pt or larger. Do not reduce text size to force a table to fit.\n\nUse more space before a section than between its heading and text. Body prose may use 6pt after, while table paragraphs and lists usually need only 3 to 4pt. Remove oversized blank-paragraph styling without deleting content or answer space. Do not compress intentionally blank response areas.\n\nKeep left alignment and avoid long all-caps passages. Use color sparingly. Decorative rules may be light only if heading text and spacing independently communicate the boundary. All text must meet a measured 4.5:1 contrast ratio against its background.\n\n### Pageless width and tables\n\nPageless mode and viewer text width are different. Google's Text width preference affects the viewer's pageless documents, not a guaranteed layout setting for recipients. Page margins and page-size changes are not a pageless width solution. Explain this distinction when widening a document.\n\nMeasure available reading space with the tab sidebar open. Use a comfortable prose measure; a wider data table does not justify unlimited prose width. Verify both normal desktop and the actual constrained workspace.\n\nClassify each table before styling:\n\n| Table role | Treatment |\n| --- | --- |\n| Questionnaire or form | Short question heading, ordinary context text, clearly labeled response area, consistent restrained answer fill. Do not zebra rows mechanically or pin a question as a data header. |\n| Evidence or comparison | Clear header row, deliberate column proportions, light alternating fills only when useful, top alignment, pinned header where supported. |\n| Introduction or callout | Compact padding and concise hierarchy. No oversized decorative box. |\n\nResolve widths from fresh table anchors, not text searches or guessed offsets. A typical starting padding is 9pt vertical and 12pt horizontal. Tune it from actual screenshots. Verify that every response region has a visible text label. Compare empty-cell and blank-paragraph counts before and after; retain usable answer space at body size, not a tiny spacer size.\n\nWhen a table overflows: first reduce excess padding, then rebalance columns. Prefer stacked content for forms or split\u002Ftransposed comparisons when content restructuring is authorized. If fixed structure must remain, document horizontal scrolling honestly and provide a practical viewer-width\u002Fsidebar adjustment. For required mobile delivery that fails the fit check, obtain authorization for the necessary restructuring before declaring it ready. Never claim mobile readiness from a desktop viewport. Do not make every table wider by a universal constant.\n\n## Execution and verification\n\n1. Create a reviewed styling plan and preserve the before snapshot. Make a recoverable pilot first.\n2. Use native connector requests with tab IDs, narrow field masks and required revision IDs. Validate nonempty UTF-16 ranges. Apply defaults before explicit exceptions. Do not rebuild a form from Markdown or plain text.\n3. On an uncertain write result, read the current state and reconcile before another mutation. An explicit rejected atomic batch may be repaired; an unknown result must not be replayed blindly.\n4. Read back every modified tab. Compare ordered text, link targets, chip type and target\u002Fdate\u002Fperson properties, list IDs\u002Fnesting\u002Fglyphs, table row and column counts, merged-cell map, and per-cell content. Ignore only intended visual style fields. When explicit text edits are authorized, compare against the approved delta rather than ignoring all text changes.\n5. Verify tab mode, heading semantics, named styles and intended exceptions, cell widths, padding, header treatment and answer areas.\n6. Visually inspect title\u002Fintro, a dense question with its answer, an evidence section, the widest data table, and a feature\u002Fstatus block. Check desktop and the constrained viewer, plus zoom or mobile when those are delivery requirements. Record actual regions and dimensions. Sampling is not exhaustive inspection.\n7. Only after the pilot passes, apply the same role-based rules to other documents. Inventory exceptions first, verify every document structurally, and sample materially different layouts visually.\n8. Save screenshots privately and provide a useful preview and direct document links. Report defects that remain, including content density and untested devices.\n\n## Model and review choice\n\nUse the active tool-capable Codex model to coordinate native edits, structural checks and visual inspection. Select effort through model-governor for the current stage; do not claim prose changes the running model. A capable independent reviewer such as approved Fable 5.1 can critique the generic method and skill. Use confidential screenshots with another model only when project-specific data approval exists. Model choice does not replace rendering, contrast checks or preservation tests, and there is no verified universal best model for Google Docs aesthetics.\n\n## Deliverables and acceptance\n\nReturn updated native documents, a private before\u002Fafter audit, style tokens, preservation results, screenshot coverage, limitations and next action. Add the actual Version-Timestamp to the work record and newly authored artifact metadata. Preserve source-version metadata rather than falsely re-dating the underlying evidence.\n\nPass only when the authorized documents were edited, content\u002Fcontrol preservation passed, intended styles were read back, sampled rendering is acceptable for the declared viewing context, and required independent review is resolved. If access fails, name the exact completed subset and resume point. Do not call a specification or API success alone a beautiful, verified document.\n\nFor future work, invoke `$design-google-docs` with the document links, audience and permitted content changes. Combine it with the native Google Docs connector skill.\n",{"name":5,"description":7},"main","753c596e097d0288f4f74e22d6b8457014eac8b2","plugins\u002Fvisual-design-studio\u002Flibrary\u002Fdraft-skills\u002Fdesign-google-docs",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":31,"prompt":41,"zipAvailable":42},[32,35,38],{"tool":33,"command":34},"npx","npx skills add newmindsgroup\u002Fvisual-design-kit --skill design-google-docs",{"tool":36,"command":37},"bunx","bunx skills add newmindsgroup\u002Fvisual-design-kit --skill design-google-docs",{"tool":39,"command":40},"pnpm","pnpm dlx skills add newmindsgroup\u002Fvisual-design-kit --skill design-google-docs","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fnewmindsgroup\u002Fvisual-design-kit\u002Fblob\u002Fmain\u002Fplugins\u002Fvisual-design-studio\u002Flibrary\u002Fdraft-skills\u002Fdesign-google-docs\u002FSKILL.md",true,[44],{"path":45,"resourceType":46,"resourceTypeDesc":47,"sizeBytes":48,"sourceHtmlUrl":49},"references\u002Ftokens.md","REFERENCE","参考文档",2180,"https:\u002F\u002Fgithub.com\u002Fnewmindsgroup\u002Fvisual-design-kit\u002Fblob\u002Fmain\u002Fplugins\u002Fvisual-design-studio\u002Flibrary\u002Fdraft-skills\u002Fdesign-google-docs\u002Freferences\u002Ftokens.md",[51,58,65,72,79,86],{"skillNo":52,"name":53,"nameZh":6,"description":54,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":55,"categories":56,"keywords":57,"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":59,"name":60,"nameZh":6,"description":61,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":62,"categories":63,"keywords":64,"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":66,"name":67,"nameZh":6,"description":68,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":69,"categories":70,"keywords":71,"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":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"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":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"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":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"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",[],[]]