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

forest-style

Skill96 starsChanged 3 months agoMITView on GitHub

Applies the forest-style brand system to any visual output, document, web content, presentation, table, list, or interface element. Enforces the color palette, typography, spacing, component styles, and voice guidelines to ensure consistent brand expression. Use this skill whenever creating or reviewing content that must conform to forest-style brand standards.

The file

We split this skill into the rules it gives an agent

11 rules. About 0 are common, 9 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈9

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    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 the …

    line 8
  2. Distinctive:

    Never: use Canyon Red as a large background — it should punctuate, not dominate

    line 33
  3. Distinctive:

    All headings use Montserrat uppercase or title case — never lowercase for H1/H2

    line 55
  4. Distinctive:

    Never: place the logo on busy photography without an overlay

    line 68
  5. Distinctive:

    Use line icons (2px stroke weight) for UI elements

    line 74
  6. Distinctive:

    Always use ample white space — avoid dense, cluttered layouts

    line 94
  7. Very specific:

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

    line 175
  8. Very specific:

    Image overlays: Use rgba(26, 46, 26, 0.45) Forest Green overlay when placing text over photos

    line 190
  9. Distinctive:

    Warm and community-first: Write as if speaking to a neighbor, not a customer

    line 196
  10. Distinctive:

    Action-oriented: Use active verbs — "Connect," "Build," "Grow," "Catalyze"

    line 197
  11. Distinctive:

    Inclusive: Avoid jargon; write at an accessible reading level

    line 199

≈ “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

Forest-Style Brand Skill

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


Brand Identity

The forest-style brand is rooted in the Pacific Northwest. It evokes the natural beauty of Central Oregon — mountains, forests, rivers — and a sense of warmth, purpose, and community care. All outputs should feel grounded, approachable, and inspired by the outdoors.


Color Palette

RoleNameHexUsage
PrimaryForest Green#1A5C38Headers, primary buttons, key UI elements, nav bars
AccentCanyon Red#C0392BHighlights, CTAs, badges, borders
SkyOregon Blue#4A9CC7Secondary UI, links, icons, info states
EarthMeadow Green#5A8A3CSecondary backgrounds, tags, progress bars
BackgroundWarm Cream#F5F0E8Page backgrounds, card backgrounds
SurfaceWhite#FFFFFFContent cards, modals, table rows
Text PrimaryDeep Forest#1A2E1ABody copy, headings
Text SecondarySlate#5C6B5CCaptions, metadata, placeholder text
BorderSoft Sage#C8D8C0Dividers, table borders, input outlines

Color Usage Rules

  • Never use Canyon Red as a large background — it should punctuate, not dominate
  • Forest Green is the primary brand color and should anchor every layout
  • Warm Cream replaces pure white for backgrounds to maintain warmth
  • Reserve Oregon Blue for interactive and informational elements (links, tooltips, info banners)

Typography

Typeface Hierarchy

LevelFontWeightSizeColor
Display / LogoMontserrat800 ExtraBold32–48pxForest Green
H1Montserrat700 Bold28–36pxForest Green
H2Montserrat600 SemiBold22–26pxDeep Forest
H3Montserrat600 SemiBold18–20pxDeep Forest
BodyOpen Sans400 Regular15–16pxDeep Forest
Body StrongOpen Sans600 SemiBold15–16pxDeep Forest
Caption / MetaOpen Sans400 Regular12–13pxSlate
Button / LabelMontserrat700 Bold13–14pxUppercase

Typography Rules

  • All headings use Montserrat uppercase or title case — never lowercase for H1/H2
  • Body copy uses Open Sans for maximum readability
  • Letter-spacing on display text: 0.05em
  • Line-height for body: 1.6; for headings: 1.2

Logo Usage

  • Minimum size: 120px wide (digital), 1 inch (print)
  • Clear space: Equal to the height of the letter "C" in the wordmark on all sides
  • Approved backgrounds: Warm Cream, White, Forest Green (use reversed white version)
  • Never stretch, recolor, or add drop shadows to the logo
  • Never place the logo on busy photography without an overlay

Iconography

  • Use line icons (2px stroke weight) for UI elements
  • Icon style: rounded caps and joins — avoid sharp or angular styles
  • Icons should use Forest Green or Slate; Canyon Red only for alerts and errors
  • Nature-themed icons preferred where contextually appropriate: mountains, trees, rivers, compass

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: 6px for cards/inputs; 4px for buttons; 999px for pills/badges; 0px for tables
  • Grid: 12-column, 24px gutters, max-width 1200px
  • Always use ample white space — avoid dense, cluttered layouts

Component Styles

Buttons

VariantBackgroundTextBorderHover
PrimaryForest Green #1A5C38White—Darken 10%
SecondaryWhiteForest Green2px Forest GreenWarm Cream bg
DangerCanyon Red #C0392BWhite—Darken 10%
GhostTransparentForest Green—Warm Cream bg
  • Border radius: 4px
  • Font: Montserrat 700, uppercase, 13px, letter-spacing 0.08em
  • Padding: 10px 20px

Cards

  • Background: #FFFFFF
  • Border: 1px solid #C8D8C0 (Soft Sage)
  • Border radius: 6px
  • Box shadow: 0 2px 8px rgba(26, 46, 26, 0.08)
  • Padding: 24px
  • Hover state: shadow deepens to 0 4px 16px rgba(26, 46, 26, 0.14)

Tables

ElementStyle
Header rowbg Forest Green, text White, Montserrat 600 uppercase 12px
Even rowsbg White
Odd rowsbg #F9F6F1 (very light warm cream)
Row hoverbg #EEF4E8 (light sage tint)
Border1px solid Soft Sage #C8D8C0
Cell padding12px 16px

Lists

  • Unordered: Custom bullet — small filled circle in Canyon Red, 6px, vertically centered
  • Ordered: Numbers in Forest Green, bold
  • Checklist: Forest Green fill with white checkmark on checked state
  • List item line-height: 1.7
  • Nested list indent: 20px

Forms & Inputs

  • Border: 1.5px solid Soft Sage
  • Border radius: 6px
  • Focus border: 2px solid Forest Green with box-shadow: 0 0 0 3px rgba(26,92,56,0.15)
  • Label: Montserrat 600, 13px, Deep Forest, uppercase
  • Placeholder: Slate #5C6B5C
  • Error state: Canyon Red border with small red error message below

Badges & Tags

  • Border radius: 999px (pill)
  • Font: Montserrat 600, 11px, uppercase
  • Padding: 3px 10px
VariantBackgroundText
Green#DFF0E4Forest Green
Red#FADEDCCanyon Red
Blue#D6EAF5Oregon Blue
Neutral#E8EDE8Slate

Navigation / Headers

  • Background: Forest Green #1A5C38
  • Text: White, Montserrat 600
  • Active item: bottom border 3px solid Canyon Red
  • Hover: opacity 0.85
  • Logo: always top-left; minimum 40px height in nav

Alerts / Banners

TypeLeft BorderBackgroundText
InfoOregon Blue #4A9CC7#EBF5FBDeep Forest
SuccessMeadow Green #5A8A3C#EAF5ECDeep Forest
Warning#E8A020#FEF6E4Deep Forest
ErrorCanyon Red #C0392B#FADEDCDeep Forest

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

Dividers / Separators

  • Default: 1px solid #C8D8C0
  • Heavy section break: 2px solid #C8D8C0
  • Decorative accent: 3px solid Canyon Red, 40px wide, centered (for section titles)

Imagery & Illustration Guidelines

  • Photography: Prioritize Pacific Northwest landscapes — Cascades, high desert, rivers, forests
  • Tone: Natural light, warm/golden tones; avoid cold blue filters
  • People: Diverse, community-focused, authentic — avoid overly polished stock imagery
  • Illustration style: Flat geometric with slight warmth; nature icons using bold shapes and the brand color palette
  • Image overlays: Use rgba(26, 46, 26, 0.45) Forest Green overlay when placing text over photos

Voice & Tone

  • Warm and community-first: Write as if speaking to a neighbor, not a customer
  • Action-oriented: Use active verbs — "Connect," "Build," "Grow," "Catalyze"
  • Grounded: Reference the place, the region, and the people when relevant
  • Inclusive: Avoid jargon; write at an accessible reading level
  • Concise: Short sentences. No filler. Say what matters.

Do / Don't Summary

✅ Do❌ Don't
Use Forest Green as the anchor colorUse Canyon Red as a dominant background
Maintain generous white spaceCrowd elements together
Use Montserrat for all headingsUse decorative or script fonts
Apply Warm Cream for page backgroundsUse pure white everywhere
Use rounded, friendly icon stylesUse sharp or aggressive icon styles
Keep imagery warm and naturalUse cold, corporate stock photography
Uppercase labels and button textUse all-lowercase for headings

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.