slice icon Context Slice

Styleguide Format Specification

When saving a style guide, generate a comprehensive YAML document with this structure:

name: [ask user for a name, or use "My Icons"]

# Record the user's philosophical choices verbatim
philosophy:
  character: "[precise and minimal / balanced and clear / warm and expressive]"
  voice: "[whisper / speak / announce]"
  color: "[none / signature touch / expressive]"
  accent: [color name if signature touch, otherwise null]

# A 3-4 sentence prose manifesto describing this style's essence
# See sliceIconography Philosophy for examples by style combination
identity: |
  [Describe what these icons ARE. What feeling do they evoke? What values do they
  embody? How should someone think about them? Write as a creative director
  describing the visual identity to a team.]

# Pre-computed prompt phrases ready to paste into generation prompts
# Translate each setting using sliceIcon Prompt Construction
visual_dna:
  weight: "[full prompt phrase for their weight setting]"
  corners: "[full prompt phrase for their corners setting]"
  palette: "[full prompt phrase for their palette setting]"
  metaphor: "[full prompt phrase for their metaphor setting]"
  size: "[full prompt phrase for their size setting]"
  mood: "[full prompt phrase for their mood setting]"

# Style-specific rules for maintaining consistency
# See sliceIconography Philosophy for examples by style
consistency_rules:
  always:
    - [4-5 specific things every icon in this set MUST do]
    - [Tailor these to their specific style choices]
  never:
    - [4-5 specific things to NEVER do in this set]
    - [Tailor these to their specific style choices]

# 3 fully-written example prompts showing the style applied
# Pick common icons and write complete generation prompts
examples:
  settings: "[Complete prompt for a settings icon in this style]"
  search: "[Complete prompt for a search icon in this style]"
  home: "[Complete prompt for a home icon in this style]"

The styleguide should be 80-100 lines—comprehensive enough to fully capture the style without needing to reference other documents during generation.