agentleFS
zrosenfieldzrosenfield/sharepoint-ai-skills/Skills/style-guidelines/SKILL.md

style-guidelines

Skill96 starsChanged 3 months agoMITView on GitHub

Provides a fill-in-the-blank template for creating an organization-specific visual brand skill. Use when drafting, adapting, or documenting brand colors, typography, spacing, component styles, and visual-output rules for AI in SharePoint.

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 4 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this skill whenever creating any visual output, document, web content, presentation, table, list, or interface element for [Your …

    line 8
  2. Distinctive:

    Never: use [Accent color] as a large background — it should punctuate, not dominate

    line 34
  3. Distinctive:

    All headings use [Font] title case — never lowercase for H1/H2

    line 54
  4. Distinctive:

    Use [line / filled / outline] icons with [stroke weight] stroke weight

    line 71
  5. Very specific:

    All alerts: 4px left border, 6px border-radius, 16px padding

    line 137

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Brand Style Skill — Template

Use this skill whenever creating any visual output, document, web content, presentation, table, list, or interface element for [Your Organization]. This skill ensures all outputs are visually consistent with the brand.

How to use this template: Replace every [placeholder] and the example values below with your organization's actual brand values. Delete this callout when done.


Brand Identity

[Your Organization] is a [brief description — industry, mission, or community focus]. The brand evokes [core brand feeling or theme — e.g., "innovation and trust" or "warmth and community"]. All outputs should feel [adjective], [adjective], and [adjective].


Color Palette

RoleNameHexUsage
Primary[Name]#000000Headers, primary buttons, key UI elements
Accent[Name]#000000Highlights, CTAs, badges
Secondary[Name]#000000Secondary UI, links, icons
Background[Name]#000000Page and card backgrounds
SurfaceWhite#FFFFFFContent cards, modals, table rows
Text Primary[Name]#000000Body copy, headings
Text Secondary[Name]#000000Captions, metadata, placeholder text
Border[Name]#000000Dividers, table borders, input outlines

Color Usage Rules

  • Never use [Accent color] as a large background — it should punctuate, not dominate
  • [Primary color] is the anchor color and should appear in every layout
  • Reserve [Secondary color] for interactive and informational elements

Typography

Typeface Hierarchy

LevelFontWeightSizeColor
Display / Logo[Font]800 ExtraBold32–48pxPrimary
H1[Font]700 Bold28–36pxPrimary
H2[Font]600 SemiBold22–26pxText Primary
H3[Font]600 SemiBold18–20pxText Primary
Body[Font]400 Regular15–16pxText Primary
Caption / Meta[Font]400 Regular12–13pxText Secondary
Button / Label[Font]700 Bold13–14pxUppercase

Typography Rules

  • All headings use [Font] title case — never lowercase for H1/H2
  • Body copy uses [Font] for readability
  • Line-height for body: 1.6; for headings: 1.2

Logo Usage

  • Minimum size: 120px wide (digital), 1 inch (print)
  • Clear space: [Define clearspace rule relative to a logo element]
  • Approved backgrounds: [List approved background colors]
  • Never stretch, recolor, or add drop shadows to the logo

Iconography

  • Use [line / filled / outline] icons with [stroke weight] stroke weight
  • Icon style: [rounded / sharp] — describe the preferred aesthetic
  • Icons should use [Primary color] or [Text Secondary]; [Accent] only for alerts/errors

Spacing & Layout

TokenValueUsage
space-xs4pxTight inline gaps
space-sm8pxComponent internal padding
space-md16pxBetween related elements
space-lg24pxSection spacing
space-xl40pxMajor section breaks
space-2xl64pxPage-level sections
  • Border radius: [N]px for cards/inputs; [N]px for buttons; 999px for pills/badges
  • Grid: 12-column, 24px gutters, max-width 1200px

Component Styles

Buttons

Primary:   bg [Primary]  | text White        | hover: darken 10%
Secondary: bg White      | text [Primary]    | border 2px [Primary] | hover: light bg
Danger:    bg [Danger]   | text White        | hover: darken 10%
Ghost:     bg transparent| text [Primary]    | hover: light bg
  • Border radius: [N]px
  • Font: [Font] 700, uppercase, 13px
  • Padding: 10px 20px

Cards

  • Background: #FFFFFF
  • Border: 1px solid [Border color]
  • Border radius: [N]px
  • Box shadow: 0 2px 8px rgba(0,0,0,0.08)
  • Padding: 24px

Tables

Header row:  bg [Primary]  | text White  | font [Font] uppercase 12px
Even rows:   bg White
Odd rows:    bg [light tint of Background]
Row hover:   bg [light tint of Primary]
Border:      1px solid [Border color]
Cell padding: 12px 16px

Badges & Tags

  • Border radius: 999px (pill)
  • Font: [Font] 600, 11px, uppercase
  • Padding: 3px 10px
  • Variants: Primary, Accent, Neutral — define bg/text combos per variant

Alerts / Banners

TypeBorder-leftBackgroundText
Info[Secondary][light tint]Text Primary
Success[Success color][light tint]Text Primary
Warning[Warning color][light tint]Text Primary
Error[Danger color][light tint]Text Primary

All alerts: 4px left border, 6px border-radius, 16px padding


Voice & Tone (for AI-generated content)

  • [Tone quality 1]: [Description — e.g., "Write as if speaking to a peer, not a customer"]
  • [Tone quality 2]: [Description — e.g., "Use active verbs and direct language"]
  • [Tone quality 3]: [Description — e.g., "Reference the mission and values when relevant"]
  • Concise: Short sentences. No filler. Say what matters.

Do / Don't Summary

✅ Do❌ Don't
Use [Primary] as the anchor colorUse [Accent] as a dominant background
Maintain generous white spaceCrowd elements together
Use [Heading font] for all headingsUse decorative or script fonts
Keep imagery [describe style]Use [describe what to avoid]

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.