How do I install the Guidelines skill?

Run npx skillmds@latest add bromso/guidelines in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

What does the Guidelines skill do?

Package all brand elements into a complete brand guidelines document It is listed under Coding & Dev Tools on SkillMD.

Is Guidelines safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Guidelines?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Guidelines free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Guidelines?

bromso (@bromso) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Guidelines by bromso — Agent Skill

Name: Guidelines
Author: bromso

File contents

Brand Guidelines

Compile all brand work for "$ARGUMENTS" into a comprehensive brand guidelines document — the single source of truth for anyone using the brand.

Prerequisites

Read all prior phase artifacts. If 04-visual.md does not exist, tell the user:

Phase 4 (Visual) has not been completed for "$ARGUMENTS". Run /branding:visual $ARGUMENTS first, or use --skip-checks to bypass.

If --skip-checks is present in $ARGUMENTS, skip this check and log to .metapowers/branding/$ARGUMENTS/skip-log.md.

Process

Read all prior artifacts:
- Read .metapowers/branding/$ARGUMENTS/01-discover.md for context
- Read .metapowers/branding/$ARGUMENTS/02-strategy.md for brand platform
- Read .metapowers/branding/$ARGUMENTS/03-verbal.md for voice, tone, messaging
- Read .metapowers/branding/$ARGUMENTS/04-visual.md for visual identity
- Read plugins/branding/shared/brand-guidelines-template.md for output structure
Compile the brand guidelines following the template, combining:
- Brand overview (purpose, vision, mission, values from Strategy)
- Logo usage rules and variations (from Visual)
- Color palette with specifications (from Visual)
- Typography system (from Visual)
- Imagery and photography guidelines (from Visual)
- Voice and tone guidelines (from Verbal)
- Application examples — how the brand appears across key touchpoints
Add compliance rules:
- What must always be done (mandatory elements)
- What must never be done (prohibited uses)
- Common mistakes to avoid
- When to seek brand team approval
Reference assets:
- Link to all files in .metapowers/branding/$ARGUMENTS/assets/
- List available logo variants, fonts, and imagery
Write the artifact to .metapowers/branding/$ARGUMENTS/05-guidelines.md

Output

The brand guidelines written to .metapowers/branding/$ARGUMENTS/05-guidelines.md. Present a summary to the user highlighting:

Sections covered
Number of compliance rules
Asset inventory
How other domains can use these guidelines (e.g., /branding:audit)

---name: guidelinesdescription: Package all brand elements into a complete brand guidelines document---# Brand GuidelinesCompile all brand work for "$ARGUMENTS" into a comprehensive brand guidelines document — the single source of truth for anyone using the brand.## PrerequisitesRead all prior phase artifacts. If `04-visual.md` does not exist, tell the user:> Phase 4 (Visual) has not been completed for "$ARGUMENTS". Run `/branding:visual $ARGUMENTS` first, or use `--skip-checks` to bypass.If `--skip-checks` is present in $ARGUMENTS, skip this check and log to `.metapowers/branding/$ARGUMENTS/skip-log.md`.## Process1. **Read all prior artifacts:** - Read `.metapowers/branding/$ARGUMENTS/01-discover.md` for context - Read `.metapowers/branding/$ARGUMENTS/02-strategy.md` for brand platform - Read `.metapowers/branding/$ARGUMENTS/03-verbal.md` for voice, tone, messaging - Read `.metapowers/branding/$ARGUMENTS/04-visual.md` for visual identity - Read `plugins/branding/shared/brand-guidelines-template.md` for output structure2. **Compile the brand guidelines** following the template, combining: - Brand overview (purpose, vision, mission, values from Strategy) - Logo usage rules and variations (from Visual) - Color palette with specifications (from Visual) - Typography system (from Visual) - Imagery and photography guidelines (from Visual) - Voice and tone guidelines (from Verbal) - Application examples — how the brand appears across key touchpoints3. **Add compliance rules:** - What must always be done (mandatory elements) - What must never be done (prohibited uses) - Common mistakes to avoid - When to seek brand team approval4. **Reference assets:** - Link to all files in `.metapowers/branding/$ARGUMENTS/assets/` - List available logo variants, fonts, and imagery5. **Write the artifact** to `.metapowers/branding/$ARGUMENTS/05-guidelines.md`## OutputThe brand guidelines written to `.metapowers/branding/$ARGUMENTS/05-guidelines.md`. Present a summary to the user highlighting:- Sections covered- Number of compliance rules- Asset inventory- How other domains can use these guidelines (e.g., `/branding:audit`)

Frequently asked questions

Guidelines