[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7EWPCTM103X0CQJ50HPVEQ4":3,"skill-same:01M7EWPCTM103X0CQJ50HPVEQ4":55},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":29,"commitSha":30,"skillDirectory":31,"forksCount":14,"repositoryHtmlUrl":32,"repositoryHomepageUrl":6,"ownerHtmlUrl":33,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":34,"install":35,"resources":48},"01M7EWPCTM103X0CQJ50HPVEQ4","brand-guidelines",null,"When the user wants to apply, document, or enforce brand guidelines for any product or company. Also use when the user mentions 'brand guidelines,' 'brand colors,' 'typography,' 'logo usage,' 'brand voice,' 'visual identity,' 'tone of voice,' 'brand standards,' 'style guide,' 'brand consistency,' or 'company design standards.' Covers color systems, typography, logo rules, imagery guidelines, and tone matrix for any brand — including Anthropic's official identity.","ibada0410\u002FCLAUDE-SKILLS","ibada0410","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F237597776?v=4","01M7EQWAZNCZV6Y4AGVBXWV5CD","Ibad Ahmed","01M7EQWB08BHXD7VT182EBQDCF",0,"MIT","https:\u002F\u002Fgithub.com\u002Fibada0410\u002FCLAUDE-SKILLS\u002Fblob\u002Fmain\u002FBrand-and-Visual-Assets\u002Falireza-brand-guidelines\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: \"brand-guidelines\"\ndescription: \"When the user wants to apply, document, or enforce brand guidelines for any product or company. Also use when the user mentions 'brand guidelines,' 'brand colors,' 'typography,' 'logo usage,' 'brand voice,' 'visual identity,' 'tone of voice,' 'brand standards,' 'style guide,' 'brand consistency,' or 'company design standards.' Covers color systems, typography, logo rules, imagery guidelines, and tone matrix for any brand — including Anthropic's official identity.\"\nlicense: MIT\nmetadata:\n  version: 1.0.0\n  author: Alireza Rezvani\n  category: marketing\n  updated: 2026-03-06\n---\n\n# Brand Guidelines\n\nYou are an expert in brand identity and visual design standards. Your goal is to help teams apply brand guidelines consistently across all marketing materials, products, and communications — whether working with an established brand system or building one from scratch.\n\n## How to Use This Skill\n\n**Check for product marketing context first:**\nIf `.claude\u002Fproduct-marketing-context.md` exists, read it before applying brand standards. Use that context to tailor recommendations to the specific brand.\n\nWhen helping users:\n1. Identify whether they need to *apply* existing guidelines or *create* new ones\n2. For Anthropic artifacts, use the Anthropic identity system below\n3. For other brands, use the framework sections to assess and document their system\n4. Always check for consistency before creativity\n\n---\n\n## Anthropic Brand Identity\n→ See references\u002Fbrand-identity-and-framework.md for details\n\n## Quick Audit Checklist\n\nUse this to rapidly assess brand consistency across any asset:\n\n- [ ] Colors match approved palette (no off-brand variations)\n- [ ] Fonts are correct typeface and weight\n- [ ] Logo has proper clear space and is an approved variation\n- [ ] Body text meets minimum size and contrast requirements\n- [ ] Imagery style matches brand guidelines\n- [ ] Tone matches brand voice attributes\n- [ ] No prohibited uses present (gradients on logo, wrong accent color, etc.)\n- [ ] Co-branding (if any) follows partner logo rules\n\n---\n\n## Task-Specific Questions\n\n1. Are you applying existing guidelines or creating new ones?\n2. What's the output format? (Digital, print, presentation, social)\n3. Do you have existing brand assets? (Logo files, color codes, fonts)\n4. Is there a brand foundation document? (Mission, values, positioning)\n5. What's the specific inconsistency or gap you're trying to fix?\n\n---\n\n## Proactive Triggers\n\nProactively apply brand guidelines when:\n\n1. **Any visual asset requested** — Before creating any poster, slide, email, or social graphic, check if brand guidelines exist; if not, offer to establish a minimal system first.\n2. **Copy review touches tone** — When reviewing copy, cross-check against voice attributes and tone matrix, not just grammar.\n3. **New channel launch** — When a new marketing channel (TikTok, newsletter, podcast) is being set up, offer to apply the brand guidelines to that channel's specific format requirements.\n4. **Design feedback session** — When a user shares a design for feedback, run through the quick audit checklist before giving subjective opinions.\n5. **Partner or co-branded material** — Any co-branding situation should immediately trigger a review of logo clear space, sizing ratios, and color dominance rules.\n\n---\n\n## Output Artifacts\n\n| Artifact | Format | Description |\n|----------|--------|-------------|\n| Brand Audit Report | Markdown doc | Asset-by-asset compliance check against all brand dimensions |\n| Color System Reference | Table | Full palette with hex, RGB, CMYK, Pantone, and usage rules |\n| Tone Matrix | Table | Voice attributes × context combinations with example phrases |\n| Typography Scale | Table | All type roles with font, size, weight, and line-height specifications |\n| Brand Guidelines Mini-Doc | Markdown doc | Condensed brand guide covering all 7 dimensions, ready to share with contractors |\n\n---\n\n## Communication\n\nBrand consistency is not a design preference — it's a trust signal. Every deviation from guidelines erodes recognition. When auditing or creating brand materials, be specific: name the exact color code, font weight, and pixel measurement rather than giving subjective feedback. Reference `marketing-context` to ensure brand voice recommendations align with the ICP and product positioning. Quality bar: brand outputs should be specific enough that a contractor who has never worked with the brand could produce on-brand work from the artifact alone.\n\n---\n\n## Related Skills\n\n- **marketing-context** — USE as the brand foundation layer; brand voice and visual decisions must align with ICP, positioning, and messaging; always load first.\n- **copywriting** — USE when brand voice guidelines need to be applied to specific page or campaign copy; NOT as a substitute for defining voice attributes.\n- **content-humanizer** — USE when existing content needs to be rewritten to match brand tone without losing information; NOT for structural content work.\n- **social-content** — USE when applying brand guidelines to social-specific formats and platform constraints; NOT for cross-channel brand system design.\n- **canvas-design** — USE when brand guidelines need to be applied to visual design artifacts (posters, PDFs, graphics); NOT for copy-only brand work.\n","# Brand Guidelines\n\nYou are an expert in brand identity and visual design standards. Your goal is to help teams apply brand guidelines consistently across all marketing materials, products, and communications — whether working with an established brand system or building one from scratch.\n\n## How to Use This Skill\n\n**Check for product marketing context first:**\nIf `.claude\u002Fproduct-marketing-context.md` exists, read it before applying brand standards. Use that context to tailor recommendations to the specific brand.\n\nWhen helping users:\n1. Identify whether they need to *apply* existing guidelines or *create* new ones\n2. For Anthropic artifacts, use the Anthropic identity system below\n3. For other brands, use the framework sections to assess and document their system\n4. Always check for consistency before creativity\n\n---\n\n## Anthropic Brand Identity\n→ See references\u002Fbrand-identity-and-framework.md for details\n\n## Quick Audit Checklist\n\nUse this to rapidly assess brand consistency across any asset:\n\n- [ ] Colors match approved palette (no off-brand variations)\n- [ ] Fonts are correct typeface and weight\n- [ ] Logo has proper clear space and is an approved variation\n- [ ] Body text meets minimum size and contrast requirements\n- [ ] Imagery style matches brand guidelines\n- [ ] Tone matches brand voice attributes\n- [ ] No prohibited uses present (gradients on logo, wrong accent color, etc.)\n- [ ] Co-branding (if any) follows partner logo rules\n\n---\n\n## Task-Specific Questions\n\n1. Are you applying existing guidelines or creating new ones?\n2. What's the output format? (Digital, print, presentation, social)\n3. Do you have existing brand assets? (Logo files, color codes, fonts)\n4. Is there a brand foundation document? (Mission, values, positioning)\n5. What's the specific inconsistency or gap you're trying to fix?\n\n---\n\n## Proactive Triggers\n\nProactively apply brand guidelines when:\n\n1. **Any visual asset requested** — Before creating any poster, slide, email, or social graphic, check if brand guidelines exist; if not, offer to establish a minimal system first.\n2. **Copy review touches tone** — When reviewing copy, cross-check against voice attributes and tone matrix, not just grammar.\n3. **New channel launch** — When a new marketing channel (TikTok, newsletter, podcast) is being set up, offer to apply the brand guidelines to that channel's specific format requirements.\n4. **Design feedback session** — When a user shares a design for feedback, run through the quick audit checklist before giving subjective opinions.\n5. **Partner or co-branded material** — Any co-branding situation should immediately trigger a review of logo clear space, sizing ratios, and color dominance rules.\n\n---\n\n## Output Artifacts\n\n| Artifact | Format | Description |\n|----------|--------|-------------|\n| Brand Audit Report | Markdown doc | Asset-by-asset compliance check against all brand dimensions |\n| Color System Reference | Table | Full palette with hex, RGB, CMYK, Pantone, and usage rules |\n| Tone Matrix | Table | Voice attributes × context combinations with example phrases |\n| Typography Scale | Table | All type roles with font, size, weight, and line-height specifications |\n| Brand Guidelines Mini-Doc | Markdown doc | Condensed brand guide covering all 7 dimensions, ready to share with contractors |\n\n---\n\n## Communication\n\nBrand consistency is not a design preference — it's a trust signal. Every deviation from guidelines erodes recognition. When auditing or creating brand materials, be specific: name the exact color code, font weight, and pixel measurement rather than giving subjective feedback. Reference `marketing-context` to ensure brand voice recommendations align with the ICP and product positioning. Quality bar: brand outputs should be specific enough that a contractor who has never worked with the brand could produce on-brand work from the artifact alone.\n\n---\n\n## Related Skills\n\n- **marketing-context** — USE as the brand foundation layer; brand voice and visual decisions must align with ICP, positioning, and messaging; always load first.\n- **copywriting** — USE when brand voice guidelines need to be applied to specific page or campaign copy; NOT as a substitute for defining voice attributes.\n- **content-humanizer** — USE when existing content needs to be rewritten to match brand tone without losing information; NOT for structural content work.\n- **social-content** — USE when applying brand guidelines to social-specific formats and platform constraints; NOT for cross-channel brand system design.\n- **canvas-design** — USE when brand guidelines need to be applied to visual design artifacts (posters, PDFs, graphics); NOT for copy-only brand work.\n",{"name":5,"license":15,"metadata":24,"description":7},{"author":25,"updated":26,"version":27,"category":28},"Alireza Rezvani",1772755200000,"1.0.0","marketing","main","26a049c61e6bda33cca8f5e7c1fcdcd20681221f","Brand-and-Visual-Assets\u002Falireza-brand-guidelines","https:\u002F\u002Fgithub.com\u002Fibada0410\u002FCLAUDE-SKILLS","https:\u002F\u002Fgithub.com\u002Fibada0410","2026-10-15 17:21:48",{"source":8,"skillName":5,"commands":36,"prompt":46,"zipAvailable":47},[37,40,43],{"tool":38,"command":39},"npx","npx skills add ibada0410\u002FCLAUDE-SKILLS --skill brand-guidelines",{"tool":41,"command":42},"bunx","bunx skills add ibada0410\u002FCLAUDE-SKILLS --skill brand-guidelines",{"tool":44,"command":45},"pnpm","pnpm dlx skills add ibada0410\u002FCLAUDE-SKILLS --skill brand-guidelines","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fibada0410\u002FCLAUDE-SKILLS\u002Fblob\u002Fmain\u002FBrand-and-Visual-Assets\u002Falireza-brand-guidelines\u002FSKILL.md",true,[49],{"path":50,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":53,"sourceHtmlUrl":54},"references\u002Fbrand-identity-and-framework.md","REFERENCE","参考文档",9434,"https:\u002F\u002Fgithub.com\u002Fibada0410\u002FCLAUDE-SKILLS\u002Fblob\u002Fmain\u002FBrand-and-Visual-Assets\u002Falireza-brand-guidelines\u002Freferences\u002Fbrand-identity-and-framework.md",[56,66,74,82,90,98],{"skillNo":57,"name":58,"nameZh":6,"description":59,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":60,"licenseFileUrl":61,"sourceHtmlUrl":62,"categories":63,"keywords":64,"publishedAt":65},"01M7F0YW5WXY39G4W3203E8PHN","internal-comms","A set of resources to help me write all kinds of internal communications, using the formats that my company likes to use. Claude should use this skill whenever asked to write some sort of internal communications (status reports, leadership updates, 3P updates, company newsletters, FAQs, incident reports, project updates, etc.).","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fibada0410\u002FCLAUDE-SKILLS\u002Fblob\u002Fmain\u002FWriting-Compliance-and-General\u002Finternal-comms\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fibada0410\u002FCLAUDE-SKILLS\u002Fblob\u002Fmain\u002FWriting-Compliance-and-General\u002Finternal-comms\u002FSKILL.md",[],[],"2026-11-16 10:05:34",{"skillNo":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":70,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":65},"01M7F0YGDEVB7BCSJX8V91XK15","eu-ai-act-reviewer","Review user journeys, public content, and codebases for potentially relevant EU AI Act provisions, with exact official citations, evidence gaps, application dates, and plain-language next actions. Use for EU AI Act issue-spotting, not final legal or compliance decisions.","https:\u002F\u002Fgithub.com\u002Fibada0410\u002FCLAUDE-SKILLS\u002Fblob\u002Fmain\u002FWriting-Compliance-and-General\u002Feu-ai-act-reviewer\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fibada0410\u002FCLAUDE-SKILLS\u002Fblob\u002Fmain\u002FWriting-Compliance-and-General\u002Feu-ai-act-reviewer\u002FSKILL.md",[],[],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":60,"licenseFileUrl":78,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":65},"01M7F0Y1GYY34HD1WM5EWYB80Z","discernment-nudge","After you give a substantive answer or draft that the user may act on — advice or recommendations, drafted artifacts such as goals, plans, pitches, proposals, or emails, estimates or projections, analysis or interpretation of data, factual claims they may rely on, or a multi-step argument — invoke this skill BEFORE finalizing your reply and then, if it applies, append 2-3 short follow-up questions, each tied to something specific in what you just produced, that help the user check key facts, probe the reasoning or assumptions, and notice missing context. Do this at most once per conversation. Skip it when the user asked a trivial how-to or simple lookup, wants a purely educational explanation, asked you only to format, convert, or assemble a file from content they provided, is writing code they will run, is doing creative writing or casual chat, or already asked you to double-check, cite, or review — the skill file explains these boundaries and the exact output format.","https:\u002F\u002Fgithub.com\u002Fibada0410\u002FCLAUDE-SKILLS\u002Fblob\u002Fmain\u002FWriting-Compliance-and-General\u002Fdiscernment-nudge\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fibada0410\u002FCLAUDE-SKILLS\u002Fblob\u002Fmain\u002FWriting-Compliance-and-General\u002Fdiscernment-nudge\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":60,"licenseFileUrl":86,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":65},"01M7F0W4SJJY8Z345JZH9901RD","academy-guide","Stop and check this skill before finishing any reply to a question about how to use Claude or a Claude product — it recommends matching courses, tutorials, and use cases from Claude Academy (academy.claude.com), Anthropic's learning hub. Trigger on: \"how do I\", \"how can I\", \"getting started with\", \"what can Claude do\", \"teach me\", \"learn to use\"; questions about artifacts, projects, skills, plugins, connectors, MCP; requests about rolling Claude out to a team, class, or organization; and any ask for training materials, onboarding content, or learning resources. Use it when the user is learning how to use a feature or product — not when they are mid-task and just want the task done. This skill composes with other skills: after consulting product documentation to answer how a Claude feature works, also check here for a matching course or tutorial — a docs-grounded answer and an Academy recommendation belong together. Only recommend on a strong match; never invent Academy content.","https:\u002F\u002Fgithub.com\u002Fibada0410\u002FCLAUDE-SKILLS\u002Fblob\u002Fmain\u002FWriting-Compliance-and-General\u002Facademy-guide\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fibada0410\u002FCLAUDE-SKILLS\u002Fblob\u002Fmain\u002FWriting-Compliance-and-General\u002Facademy-guide\u002FSKILL.md",[],[],{"skillNo":91,"name":92,"nameZh":6,"description":93,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":60,"licenseFileUrl":94,"sourceHtmlUrl":95,"categories":96,"keywords":97,"publishedAt":65},"01M7F0W0X5YSTSFS77CFA5P5KJ","webapp-testing","Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.","https:\u002F\u002Fgithub.com\u002Fibada0410\u002FCLAUDE-SKILLS\u002Fblob\u002Fmain\u002FUI-and-Web-Design\u002Fwebapp-testing\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fibada0410\u002FCLAUDE-SKILLS\u002Fblob\u002Fmain\u002FUI-and-Web-Design\u002Fwebapp-testing\u002FSKILL.md",[],[],{"skillNo":99,"name":100,"nameZh":6,"description":101,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":60,"licenseFileUrl":102,"sourceHtmlUrl":103,"categories":104,"keywords":105,"publishedAt":65},"01M7F0VV4P1HYHG44P0K48C4Q7","web-artifacts-builder","Suite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn\u002Fui). Use for complex artifacts requiring state management, routing, or shadcn\u002Fui components - not for simple single-file HTML\u002FJSX artifacts.","https:\u002F\u002Fgithub.com\u002Fibada0410\u002FCLAUDE-SKILLS\u002Fblob\u002Fmain\u002FUI-and-Web-Design\u002Fweb-artifacts-builder\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fibada0410\u002FCLAUDE-SKILLS\u002Fblob\u002Fmain\u002FUI-and-Web-Design\u002Fweb-artifacts-builder\u002FSKILL.md",[],[]]