agentleFS
dhananjaym182dhananjaym182/ai-ui-design-skills/skills/image-logo-icons/SKILL.md

image-logo-icons

Skill17 starsChanged 8 months agoMITView on GitHub

Generate structured image prompts for brand visuals: logos, UI icons, favicons/PWA icons, featured blog images, and Open Graph social cards. Use when users ask to design or iterate brand identity assets, social preview graphics, or reusable prompt templates for image models.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈7

    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:

    Create production-ready prompts for brand and marketing images.

    line 8
  2. Distinctive:

    Keep one coherent visual language.

    line 21
  3. Distinctive:

    Keep output clean and uncluttered.

    line 22
  4. Distinctive:

    Avoid trademarked logo imitation or direct brand copying.

    line 23
  5. Distinctive:

    Prefer legibility at small sizes for logo/icon outputs.

    line 24
  6. Distinctive:

    Use defaults when optional fields are not provided:

    line 42
  7. Distinctive:

    If a user requests multiple assets in one turn:

    line 56
  8. Very specific:

    Keep shared brand fields consistent (brand_name, palette, mood).

    line 58

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

Image Logo Icons

Create production-ready prompts for brand and marketing images.

Workflow

  1. Classify request as one of:
    • site_logo
    • ui_icon
    • featured_blog_image
    • social_og_image
    • favicon_app_icon
  2. Collect required fields from the input matrix below. Ask only for missing required fields.
  3. Load the matching template from references/templates.md.
  4. Apply global quality rules:
    • Keep one coherent visual language.
    • Keep output clean and uncluttered.
    • Avoid trademarked logo imitation or direct brand copying.
    • Prefer legibility at small sizes for logo/icon outputs.
  5. Return results in this exact order:
    • Final prompt:
    • Render settings:
    • Variation ideas:

Input Matrix

TypeRequiredOptional
site_logobrand_name, niche, style, primary_color, moodicon_concept, neutral_color, font_tone
ui_iconicon_name, icon_purpose, icon_style, primary_color, size_contextstroke_weight, corner_style
featured_blog_imagearticle_title, keywords, primary_color, image_style, tonevisual_metaphor, focal_subject
social_og_imagebrand_name, page_title, tagline, primary_color, bg_styledomain_text, logo_position
favicon_app_iconbrand_symbol, shape, primary_color, secondary_colorborder_style, padding_ratio

Defaults

Use defaults when optional fields are not provided:

  • neutral_color: slate gray
  • font_tone: clean modern sans-serif
  • stroke_weight: 1.5px
  • corner_style: slightly rounded
  • visual_metaphor: derive from title + keywords
  • focal_subject: abstract symbol tied to keyword intent
  • domain_text: include only if provided
  • logo_position: bottom-left
  • border_style: none
  • padding_ratio: 12%

Multi-Asset Requests

If a user requests multiple assets in one turn:

  1. Generate one prompt block per asset type.
  2. Keep shared brand fields consistent (brand_name, palette, mood).
  3. Vary only what each artifact needs (size, composition, style constraints).

References

  • Prompt templates: references/templates.md
  • Registry examples: references/registry-snippets.ts

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.