imagegen-frontend-web

Generates one horizontal website design reference image per page section for frontend implementation.

1|Updated Feb 22, 2026
One-click install
npx skills add https://github.com/TarunTeja44/portfolio --skill imagegen-frontend-web-tarunteja44
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: imagegen-frontend-web
Source: https://github.com/TarunTeja44/portfolio/tree/main/.agents/skills/imagegen-frontend-web
Command: npx skills add https://github.com/TarunTeja44/portfolio --skill imagegen-frontend-web-tarunteja44

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? AI image generation for website design often collapses into repetitive defaults like left-text/right-image heroes, purple-blue gradients, and single tall page slices that developers cannot accurately recreate. This Skill enforces disciplined art direction so every generated image is a usable, section-level frontend design reference. ## Core Features & Use Cases - One Image Per Section: Generates a separate horizontal image for every page section (hero, features, pricing, CTA), never combining sections into one frame. - Combinatorial Variation Engine: Selects theme paradigm, typography character, hero architecture, background mode, and CTA style per section while keeping one consistent brand palette across all images. - Anti-AI-Slop Rules: Bans generic gradients, cloned card rows, fake dashboards, and overused copy patterns to produce premium, codeable design comps. - Use Case: Ask for a landing page for a SaaS product and receive 6-8 labeled horizontal section images (Hero, Trust bar, Features, Showcase, Testimonials, Pricing, CTA) that a developer or coding model can directly implement. ## Quick Start Generate a landing page design for a premium fintech product with one horizontal image per section.

Frequently Asked Questions about imagegen-frontend-web

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate website design images section by section?

Request a landing page or site template and the skill outputs one horizontal image per section, labeled sequentially (Section 1 of 8: Hero, etc.). A landing page defaults to 6 sections and a full website to 8, each rendered as its own 16:9 or 16:10 frame.

How many images does a landing page request produce?

A landing page request with no section count defaults to 6 sections and therefore 6 separate horizontal images. A full website template defaults to 8 sections, and explicit counts are always honored one-to-one.

Can developers implement designs from these generated images?

Yes, each image is generated as a frontend reference that clearly communicates layout, hierarchy, spacing, typography scale, CTA priority, and component styling. The skill targets high implementation clarity so a developer or coding model can build directly from the frames.

How does it avoid generic AI-looking website designs?

It uses a combinatorial variation engine that picks distinct theme paradigms, typography characters, hero architectures, and background modes per section. It also bans AI slop patterns like purple-blue gradients, cloned card rows, floating blobs, and default left-text/right-image heroes.

Does it keep branding consistent across multiple section images?

Yes, all per-section frames share one palette, typography family, CTA identity, image treatment, and tonal voice. Only composition anchors, background modes, and section density vary, so every frame reads as one brand.

When should I not use this image generation approach?

Avoid it when you need actual production code rather than visual references, or when the request is for abstract mood art rather than website comps. The skill defaults to structured frontend design references, not freeform artwork.