agentleFS
Sign inStart free
wedabrowedabro/bro-skills/.agents/skills/imagegen-frontend-web/SKILL.md

imagegen-frontend-web

Skill3 starsChanged 45 days agoMITView on GitHub

Generate premium horizontal website design-reference images for landing pages, marketing sites, and product pages. Use when the requested deliverable is web design imagery or when an image-first implementation workflow needs upstream section concepts. Produce images only, one standalone image per page section; do not write frontend code or mobile-app screens.

We split this skill into the rules it gives an agent

12 rules. 0 are common, 11 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 67 edited versions we read keep these.

  • 11

    Distinctive

    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 a coherent set of implementation-ready website section images, not a compressed mood board.

    line 8
  2. Distinctive:

    Never combine multiple sections into one tall board or tiny overview.

    line 13
  3. Distinctive:

    Keep one palette, typography system, material language, and narrative spine across the set.

    line 14
  4. Distinctive:

    Check legibility, realistic content density, CTA clarity, cross-section consistency, and composition variety.

    line 25
  5. Distinctive:

    Keep the hero clean and readable.

    line 29
  6. Distinctive:

    Do not repeat left-text/right-image layouts throughout the page.

    line 31
  7. Distinctive:

    Use real visual hierarchy instead of filling every section with cards, badges, pills, or KPI tiles.

    line 32
  8. Distinctive:

    Avoid generic AI-purple gradients, empty glass panels, fake dashboards, placeholder copy, and decorative noise.

    line 33
  9. Distinctive:

    Use background imagery, texture, typography, and negative space intentionally.

    line 34
  10. Distinctive:

    Keep all visible text short, plausible, and comfortably readable at the output resolution.

    line 35
  11. Distinctive:

    Read only the relevant section of references/full-guide.md:

    line 39
  12. Very specific:

    Use rg -n "<heading>" references/full-guide.md.

    line 47

“Common” is measured: kept by at least 6 in 10 of the 67 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

Frontend Web Image Direction

Create a coherent set of implementation-ready website section images, not a compressed mood board.

Output contract

  • Generate one separate horizontal image for every requested section.
  • Never combine multiple sections into one tall board or tiny overview.
  • Keep one palette, typography system, material language, and narrative spine across the set.
  • Make each image large enough to inspect and recreate accurately.
  • Generate fresh section images; do not crop earlier outputs to simulate missing views.
  • Return images only. Do not write code.

Workflow

  1. Infer audience, conversion goal, section list, brand constraints, and required visual tone.
  2. Define a compact design bible: palette, type character, imagery, surfaces, grid, CTA language, and recurring motif.
  3. Assign each section a distinct composition and purpose before generating.
  4. Generate sections individually in narrative order while carrying the same design bible forward.
  5. Check legibility, realistic content density, CTA clarity, cross-section consistency, and composition variety.

Composition rules

  • Keep the hero clean and readable; match headline scale to copy length and leave the main CTA visible.
  • Vary composition anchors: centered, split, off-grid, full-bleed, product-led, editorial, or data-led as the story requires.
  • Do not repeat left-text/right-image layouts throughout the page.
  • Use real visual hierarchy instead of filling every section with cards, badges, pills, or KPI tiles.
  • Avoid generic AI-purple gradients, empty glass panels, fake dashboards, placeholder copy, and decorative noise.
  • Use background imagery, texture, typography, and negative space intentionally; not every section needs a container.
  • Keep all visible text short, plausible, and comfortably readable at the output resolution.

Detailed reference

Read only the relevant section of references/full-guide.md:

  • Variation system and composition choices: search COMBINATORIAL VARIATION ENGINE.
  • Hero constraints: search HERO MINIMALISM RULES.
  • Section counting and sizing: search IMAGE COUNT & PAGE SLICING.
  • Anti-slop, type, density, and material rules: search the corresponding heading.
  • Standard page packs or examples: search DEFAULT SITE PACKS or EXAMPLE INTERPRETATIONS.

Use rg -n "<heading>" references/full-guide.md; do not load the full guide unless the brief genuinely needs the complete art-direction system.

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.

Check your setup, free