agentleFS
molayabmolayab/swift-ai-provider-kit/.claude/skills/update-banner/SKILL.md

update-banner

Skill1 starsChanged 8 months agoMITView on GitHub

Regenerates Documentation/Assets/banner.svg following the project's canonical 6-color palette and layout rules. Use when asked to 'update the banner', 'add a provider to the banner', 'refresh the banner', or 'change the banner'.

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    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. Very specific:

    All arrow markers: fill="$GRAY"

    line 68
  2. Very specific:

    Keep the SVG clean: use <defs> for gradients and filters, group related elements with comments, and maintain the existing viewBox and font …

    line 97

≈ “Common” is an estimate: at least 1 in 5 of the 308,232 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

You are the banner author for AIProviderKit. Your job is to update Documentation/Assets/banner.svg following the canonical design rules below.

Invocation: /update-banner <description> The full argument string is available as $ARGUMENTS (e.g. /update-banner add GeminiProvider as upcoming → $ARGUMENTS = "add GeminiProvider as upcoming"). If no argument is given, ask the user what change they want before proceeding.

Canonical 6-color palette

TokenHexUsage
$BG#0F0F13SVG background fill (gradient end: #18181F)
$ORANGE#F05138Swift accent bar, AIClient border/glow, orange rule, Skills badge
$WHITE#E8E8F0Primary text (package name, box labels)
$GRAY#6B6B75Muted text, dividers, arrows, upcoming / disabled providers
$BLUE#3B82F6Apple Intelligence provider, Streaming badge
$GREEN#22C55EOpenAI provider, Tools badge

Derived tints (do NOT introduce additional hues):

  • Slightly lighter $ORANGE tint for Claude box label: #F0D090 (warm yellow — still orange family)
  • $BLUE at 15% opacity for Apple Intelligence box fill
  • $GREEN at 15% opacity for OpenAI box fill
  • $ORANGE at 15% opacity for Claude box fill and AIClient fill
  • $GRAY at 20% opacity for upcoming provider box fills

Rule: never add a 7th hue. If you need a new provider accent, derive it from $ORANGE, $BLUE, or $GREEN.

Upcoming / disabled providers

Upcoming providers use the muted gray treatment:

  • Box stroke: $GRAY (#6B6B75) at 60% opacity
  • Box fill: #1A1A20 (flat, no gradient)
  • Indicator dot: $GRAY
  • Label text: $GRAY
  • Optional "coming soon" label in $GRAY

Active providers use their accent color at full opacity for stroke, dot, and label.

Fixed layout (900 × 240 px)

[4px orange bar] [LEFT SECTION — x:16–330] [1px gray divider x:345] [RIGHT SECTION — x:360–884]

Left section:

  • Package name: font-size="36" font-weight="700" fill="$WHITE" at y≈75
  • Orange rule: 2.5px tall rect below name
  • Tagline: font-size="13" fill slightly lighter than $GRAY
  • Feature badges: pill shape rx="12", fill="#18181F", stroke="$GRAY" at 40% opacity
    • Streaming → $BLUE label
    • Tools → $GREEN label
    • Skills → $ORANGE label
  • Platform line: font-size="11" fill="$GRAY"

Right section — architecture diagram:

  • "Your App" box: neutral dark fill #1C1C24, stroke $GRAY
  • AIClient box: $ORANGE border + soft glow filter, gradient fill from $ORANGE at ~15% opacity
  • Provider boxes: 140×32 px, rx="6", stacked vertically with 42px pitch
    • Active: colored stroke + fill tint + colored dot + colored label
    • Upcoming: gray stroke + flat fill + gray dot + gray label
  • Arrows between boxes: dashed stroke-dasharray="4 3" in $GRAY
  • All arrow markers: fill="$GRAY"

Steps

1 — Read the current banner

Read: Documentation/Assets/banner.svg

Note the current providers, their state (active/upcoming), and the exact coordinates of every provider box so you can add, remove, or reposition consistently.

2 — Plan the change

Apply $ARGUMENTS (the full user-supplied description) to decide what changes are needed:

  • Adding a provider → assign it an accent from $ORANGE, $BLUE, or $GREEN; compute new y positions (42px pitch); shift others if needed
  • Removing a provider → close the gap; recompute y positions
  • Marking active/upcoming → swap color treatment only, keep coordinates unchanged

3 — Apply palette rules

For every color value in the SVG, map it to the canonical palette. Do not introduce any new hues. Use opacity variants of the 6 base colors for fills, borders, and glow effects.

4 — Write the updated SVG

Write: Documentation/Assets/banner.svg

Keep the SVG clean: use <defs> for gradients and filters, group related elements with comments, and maintain the existing viewBox and font stack.

5 — Report

Tell the user:

  • What changed (which providers, states, text)
  • The exact palette tokens used for each new element
  • Any layout shifts (y-coordinate changes for provider rows)

Palette quick-reference card

Background:  #0F0F13 → #18181F  (gradient)
Accent bar:  #F05138 → #D94C2A  (gradient, 4px left edge)
Orange:      #F05138   Claude stroke / AIClient border / Skills
Blue:        #3B82F6   Apple Intelligence stroke / Streaming badge
Green:       #22C55E   OpenAI stroke / Tools badge
White:       #E8E8F0   Primary labels
Gray:        #6B6B75   Muted text / dividers / upcoming providers

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.