agentleFS
passion4it-gmbhpassion4it-gmbh/passionfruit-site/.claude/skills/brand/SKILL.md

brand

Skill0 starsChanged 12 days agoMITView on GitHub

Replace placeholder favicon and OG image with your brand assets. Supports uploading existing logos or generating new ones.

  • Reads credentials

64 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use brand-strategy, content and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • Google CloudSkill

    brand-strategy

    Brand strategy and campaign positioning expertise. Covers audience segmentation, competitive differentiation, value proposition frameworks, and campaign brief creation. Load this skill when setting up campaigns, selecting audience segments, or defining creative direction.

    Also in 3 projects that use this

  • Rayan55050Skill

    content

    Создание контента: посты, статьи, тексты

    Also in 3 projects that use this

  • hardikpandyaSkill

    stop-slop

    Remove AI writing patterns from prose. Use when drafting, editing, or reviewing text to eliminate predictable AI tells.

    Also in 4 projects that use this

  • CesarjoquinSkill

    competitors

    When the user wants to create competitor comparison or alternative pages for SEO and sales enablement. Also use when the user mentions 'alternative page,' 'vs page,' 'competitor comparison,' 'comparison page,' '[Product] vs [Product],' '[Product] alternative,' 'competitive landing pages,' 'how do we compare to X,' 'battle card,' or 'competitor teardown.' Use this for any content that positions your product against competitors. Covers four formats: singular alternative, plural alternatives, you vs competitor, and competitor vs competitor. For sales-specific competitor docs, see sales-enablement.

    Also in 3 projects that use this

  • OpenAISkill

    image-to-code

    Implement a selected image, screenshot, mockup, or Image Gen reference as a faithful, responsive frontend.

    Also in 5 projects that use this

  • AnasX7Skill

    brandkit

    Premium brand-kit image generation skill for creating high-end brand-guidelines boards, logo systems, identity decks, and visual-world presentations. Trained for minimalist, cinematic, editorial, dark-tech, luxury, cultural, security, gaming, developer-tool, and consumer-app brand systems. Optimized for intentional logo concepting, refined composition, sparse typography, strong symbolic meaning, premium mockups, art-directed imagery, and flexible grid layouts.

    Also in 5 projects that use this

The file

Show its rules and text

We split this skill into the rules it gives an agent

13 rules. 0 are common, 8 are distinctive, and 5 are very specific to this project.

  • 0

    Common

    Most of the 19 edited versions we read keep these.

  • 8

    Distinctive

    This author's own choices. Worth a look.

  • 5

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Ask using AskUserQuestion with these options:

    line 17
  2. Distinctive:

    Local session: ask for the file path.

    line 31
  3. Distinctive:

    If PNG/JPG: Create an SVG wrapper that embeds the raster image:

    line 39
  4. Distinctive:

    Ask: "Describe your brand briefly — what does your company do, and what style do you prefer?

    line 50
  5. Very specific:

    If OPENAI_API_KEY isn't set, don't send a non-technical user off to get one.

    line 52
  6. Distinctive:

    If the key is set, generate:

    line 54
  7. Very specific:

    After generation, create public/favicon.svg from the result by embedding the PNG as base64, then delete public/favicon-source.png.

    line 60
  8. Distinctive:

    No code changes needed — bg.png absence falls back to the flat surface look.

    line 99
  9. Distinctive:

    Ask: "Describe what you'd like the image to convey — visual style, mood, key elements."

    line 103
  10. Very specific:

    If OPENAI_API_KEY isn't set, offer the branded template instead.

    line 119
  11. Distinctive:

    After assets are created, verify:

    line 127
  12. Very specific:

    No changes needed unless the user wants a different path.

    line 143
  13. Very specific:

    Run pnpm build to confirm no broken asset references.

    line 145

“Common” is measured: kept by at least 6 in 10 of the 19 edited versions of this file we could read. “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 Assets

This skill helps users replace the template's placeholder favicon and OG image with their own brand assets.

When to trigger

  • User explicitly runs /brand
  • Suggested after /onboard completes

Step 1: Logo / Favicon

Ask using AskUserQuestion with these options:

"Let's set up your brand assets. Do you have a logo?"

Options:

  • "Yes, I have a logo file"
  • "No, generate one for me"
  • "Skip for now"

Option A: User has a logo file

Get the file:

  • Local session: ask for the file path.
  • Cloud session (CLAUDE_CODE_REMOTE=true): there's no file path. Ask the user to upload the logo to their repo on GitHub (Add file → Upload files), then pull it.

Then:

Always keep a public/favicon.svg. pnpm generate-og and its tests need it, so removing it breaks CI. A raster logo gets the SVG wrapper below.

  1. If SVG: Copy it to public/favicon.svg. This is the preferred format — crisp at all sizes.
  2. If PNG/JPG: Create an SVG wrapper that embeds the raster image:
    <svg xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" viewBox="0 0 32 32" width="32" height="32">
      <image href="data:image/png;base64,..." width="32" height="32"/>
    </svg>
    Base64-encode the image and embed it. Also suggest generating an SVG-native version using pnpm generate-image for better scaling.
  3. Generate public/favicon.ico for legacy browsers: use sharp to convert the source to a 32x32 ICO, or inform the user they can use an online converter (realfavicongenerator.net). The SVG favicon covers all modern browsers.

Option B: Generate a logo

Ask: "Describe your brand briefly — what does your company do, and what style do you prefer? (minimal, bold, playful, corporate, etc.)"

If OPENAI_API_KEY isn't set, don't send a non-technical user off to get one. Write a simple SVG mark yourself, such as their initial on a shape in the accent color, save it as public/favicon.svg, and show them the result.

If the key is set, generate:

pnpm generate-image "<prompt for a minimal icon suitable as a favicon, simple shapes, single subject, no text>" -o public/favicon-source.png --size 1024x1024

After generation, create public/favicon.svg from the result by embedding the PNG as base64, then delete public/favicon-source.png.

Option C: Skip

Move on. The template ships with a default passionfruit-themed favicon.

Step 2: OG Image (Social Sharing Preview)

This is the image that appears when someone shares a link to the site on LinkedIn, Twitter/X, Slack, etc. There are two ways to make one — ask the user via AskUserQuestion:

"How should we create your social sharing image?"

Options:

  • "Branded template (recommended)" — composes site.name + site.tagline + accent color + favicon into a clean 1200×630 PNG. Runs in under a second, no API key needed, produces one image per locale.
  • "AI generated" — describe an image and OpenAI's GPT Image model creates it. Slower, costs money, requires OPENAI_API_KEY.
  • "Skip" — keep whatever's already at public/og-default-{de,en}.png.

/onboard already creates a branded image. If the logo changed in Step 1, run pnpm generate-og again so the image shows it, then skip this question unless they want something different.

Option A: Branded template

Run:

pnpm generate-og

This writes public/og-default-de.png and public/og-default-en.png from the project's i18n strings (site.name, site.tagline), the accent color in src/styles/global.css, and the logo in public/favicon.svg. If the user has run /onboard (so the i18n + accent are theirs) and the favicon is their logo (Step 1 above), the result is on-brand without any prompting.

For per-locale regeneration: pnpm generate-og --lang de or --lang en.

Optional background photo. Drop a 1200×630-ish image at src/assets/og/bg.png before running and the generator composites it full-cover behind the text (a left-anchored scrim keeps the title legible regardless of the photo's brightness). Best results when the photo has a darker left third — Satori text sits on the left. Use pnpm generate-image to produce a fitting photo first, e.g.:

pnpm generate-image "<describe a banner-style photo with empty/dark left third, no text>" -o src/assets/og/bg.png --size 1536x1024
pnpm generate-og

No code changes needed — bg.png absence falls back to the flat surface look.

Option B: AI generated

Ask: "Describe what you'd like the image to convey — visual style, mood, key elements."

Generate once, then copy to the second locale — gpt-image-2 is non-deterministic, so two separate calls with the same prompt produce two visually different images. We want DE and EN visitors to see the same artistic image.

pnpm generate-image "<prompt including company name, brand style, professional look>" -o public/og-default-de.png --size 1536x1024
cp public/og-default-de.png public/og-default-en.png

Guidelines for the prompt:

  • Include the company name if the user wants text on the image
  • Match the site's accent color and visual style
  • Ideal OG dimensions: 1200×630. Using 1536x1024 gives good quality; platforms will crop to fit.
  • Example prompt: "Professional banner for [Company Name], [industry], accent color #6265f0, clean modern design, suitable as social media preview"

If OPENAI_API_KEY isn't set, offer the branded template instead.

Option C: Skip

Move on. The current public/og-default-{de,en}.png files stay as they are.

Step 3: Verify Integration

After assets are created, verify:

  1. Favicon: public/favicon.svg exists and is referenced in src/layouts/BaseLayout.astro at:

    <link rel="icon" type="image/svg+xml" href="/favicon.svg" />

    This is already configured in the template. No changes needed unless the user wants a different path.

  2. OG image: public/og-default-de.png AND public/og-default-en.png exist. src/layouts/BaseLayout.astro already picks the locale-specific file:

    const defaultOgImage = `/og-default-${lang}.png`;

    No changes needed unless the user wants a different path. Individual pages can still override via the ogImage prop.

  3. Run pnpm build to confirm no broken asset references.

Final message

"Your brand assets are set up:

  • Favicon: public/favicon.svg — appears in browser tabs
  • OG images: public/og-default-de.png and public/og-default-en.png — appear when your site is shared on social media (locale-aware: DE pages get the DE image, EN pages get the EN image)

Individual pages can override the OG image by passing ogImage to BaseLayout. To regenerate the branded template later, run pnpm generate-og. To run the full brand flow again, use /brand."

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.