stacks-imagegen-web

Generate horizontal frontend design reference images for Stacks application website sections.

2|Updated Jul 2, 2026
One-click install
npx skills add https://github.com/stacksjs/status --skill stacks-imagegen-web
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: stacks-imagegen-web
Source: https://github.com/stacksjs/status/tree/main/.claude/skills/stacks-imagegen-web
Command: npx skills add https://github.com/stacksjs/status --skill stacks-imagegen-web

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill eliminates the need to manually art direct every section of a Stacks app website, providing consistent, premium, Awwwards-level frontend design reference images that avoid generic AI design slop and ensure all sections align with a unified brand vision.

Core Features & Use Cases

  • Section-by-Section Reference Images: Generates one horizontal design reference image per website section (hero, trust bar, features, pricing, CTA, etc.) with strict rules for composition, typography, and spacing.
  • Creative Art Direction Guardrails: Enforces varied composition anchors, background modes, and CTA styles across sections to avoid overused AI patterns like default left-text/right-image heroes, while maintaining brand consistency.
  • Use Case: If you are building a marketing site for a Stacks app, use this skill to generate a full set of implementation-ready design frames that a developer can accurately translate to stx + Crosswind code.

Quick Start

Use the stacks-imagegen-web skill to generate 8 horizontal reference images for a full marketing site for your Stacks app, including a hero, trust bar, features section, product showcase, benefits, testimonials, pricing, and final CTA.

Frequently Asked Questions about stacks-imagegen-web

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

FAQPage Schema
How do I generate consistent frontend design references for a marketing site?

Generating consistent frontend design references requires applying enforced composition, typography, and brand consistency rules to produce one horizontal section reference image per requested page section for accurate implementation.

What is the best way to avoid generic AI design slop when creating web design references?

Avoiding generic AI design slop involves applying creative art direction guardrails that enforce varied composition anchors, background modes, and CTA styles across sections to prevent overused patterns like default left-text and right-image layouts.

Can I generate design references for specific landing page sections like a hero or pricing table?

Generating design references for specific landing page sections supports hero, trust bar, features, product showcase, benefits, testimonials, pricing, and final CTA areas to communicate clear layout hierarchy and spacing for your Stacks app.

Do I need design references before translating my marketing site to stx and Crosswind code?

Implementation-ready visual references are needed before translating to stx and Crosswind code to accurately communicate layout hierarchy, spacing, typography scale, CTA priority, and component styling to the developer.

Why does my AI generated landing page lack unified art direction across different sections?

Landing pages lack unified art direction when sections are generated independently without strict rules for composition, typography, and brand consistency to align all visual frames with a unified brand vision.

Does the stacks-imagegen-web skill work with the Stacks framework for premium web design?

The stacks-imagegen-web skill works with the Stacks framework to generate Awwwards-caliber premium web design references, eliminating manual art direction and ensuring all sections align with a unified brand vision for frontend websites.