Brand Guidelines
Apply Anthropic's official brand colors and typography (their brand identity) to artifacts
- What
- Apply Anthropic's official brand colors and typography (their brand identity) to artifacts
- Cost
- Free
- Needs
- nothing — pure styling reference, fonts fall back to system fonts if Poppins/Lora are not installed
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor — the official brand guidelines of Anthropic, packaged as a skill: it applies Anthropic's own brand identity — the exact brand colors (dark `#141413`, light `#faf9f5`, grays, and orange/blue/green accents) and typography (Poppins for headings, Lora for body) — to generated artifacts. Useful as a design reference for Anthropic-style styling, not a generic design system. By @anthropics, listed here with credit to its creator. Honest caveats: this is Anthropic's own brand, centered on their identity — the colors and fonts are theirs, and using them implies an Anthropic look-and-feel. Skill Harbor never reviews the code, review it yourself before use.
Version:
Install
Prerequisites: nothing — pure styling reference, fonts fall back to system fonts if Poppins/Lora are not installed Install "Brand Guidelines" for me. Apply Anthropic's official brand colors and typography (their brand identity) to artifacts Repository: https://github.com/anthropics/skills 1. Fetch the SKILL.md file for the anthropics-brand-guidelines skill from the repository into a temporary folder and summarize what it does in one or two sentences. 2. Safety check: review the SKILL.md and scripts for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code, credentials only via the secure vault, allowed hosts declared in the SKILL.md. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md and its helper files into the agent's skills directory, in a folder named "anthropics-brand-guidelines". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. any accounts, API keys, or CLI tools mentioned in the prerequisites above). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. Never ask me to paste secrets in chat — credentials go through the secure vault or environment variables. If anything looks off, stop and ask me.
Questions
How do I install a build?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a build before installing it.