design-output

Generate a complete landing page HTML document with all sections and responsive classes.

Updated Apr 11, 2026
One-click install
npx skills add https://github.com/leessju/claude-skills --skill design-output
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: design-output
Source: https://github.com/leessju/claude-skills/tree/main/design-output
Command: npx skills add https://github.com/leessju/claude-skills --skill design-output

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents partial outputs by enforcing production-ready HTML generation with zero placeholder patterns, ensuring every landing page is fully formed.

Core Features & Use Cases

  • Enforces complete landing page generation: nav, hero, features, testimonials, CTA, and footer.
  • Bans placeholder and skeleton patterns; ensures all sections are real content.
  • Provides deterministic output with responsive classes and production-grade structure for web deployments.

Quick Start

Generate a full landing page with all sections, content, and interactions as a single, ready-to-publish HTML document.

Frequently Asked Questions about design-output

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

FAQPage Schema
How do I generate a complete landing page HTML document without placeholder content?

To generate a complete landing page, you need a production-ready HTML document with all sections fully formed. This includes nav, hero, social proof, features, testimonials, CTA, and footer, eliminating any skeleton or placeholder patterns.

What's the best way to build a responsive landing page with scroll animations?

The best way to build a responsive landing page with scroll animations is using an IntersectionObserver-based script. This approach applies scroll animations across responsive breakpoints while maintaining production-grade HTML standards and accessible icons.

Why does my landing page output have missing sections or skeleton patterns?

Landing page outputs have missing sections or skeleton patterns when generation lacks deterministic enforcement. A full-page layout must ban placeholder patterns and enforce real content across all sections like nav, hero, features, testimonials, CTA, and footer.

Can I get a production-ready landing page with lazy-loaded images and responsive utility classes?

Yes, a production-ready landing page can include lazy-loaded images with alt text and responsive utility classes. This ensures the full HTML skeleton conforms to production-grade HTML standards and is ready for web deployments.

Does a full landing page output include accessibility features like alt text and accessible icons?

Yes, a full landing page output includes accessibility features such as alt text for lazy-loaded images and accessible icons. It conforms to production-grade HTML standards across all responsive breakpoints for a complete, ready-to-publish document.

When do I need a full landing page HTML output instead of a partial layout?

You need a full landing page HTML output instead of a partial layout for marketing and design workflows requiring full-page layouts. This ensures a single, ready-to-publish HTML document with all sections and interactions fully formed with zero placeholders.