supanova-full-output
Overrides default LLM truncation behavior. Enforces complete HTML generation with zero placeholder patterns. Every landing page must be delivered as a complete, production-ready file. No shortcuts, no skeletons, no "add more as needed" patterns.
What this skill does
# Supanova Full-Output Enforcement ## Baseline Treat every landing page generation as production-critical. A partial output is a broken output. If the user asks for a landing page, deliver the COMPLETE landing page — every section, every animation, every responsive breakpoint. No exceptions. ## Banned Output Patterns The following patterns are hard failures. Never produce them: **In code blocks:** - `<!-- ... -->` - `<!-- rest of sections -->` - `<!-- similar to above -->` - `<!-- add more sections as needed -->` - `<!-- TODO -->` - `// ...` - Bare `...` standing in for omitted HTML **In prose:** - "Let me know if you want me to continue" - "I can add more sections if needed" - "For brevity, I'll show just the hero section" - "The rest follows the same pattern" - "Similarly for the remaining sections" - "I'll leave that for you to customize" **Structural shortcuts:** - Outputting only the Hero when a full page was requested - Showing the first and last section while skipping the middle - Replacing repeated sections with one example and a description - Describing what HTML should contain instead of writing it - Generating a skeleton/wireframe when a complete page was requested ## Execution Process 1. **Scope** — Read the full request. Count how many sections/components are expected. A "landing page" means: nav + hero + social proof + features + testimonials + CTA + footer at minimum (7 sections). Lock the count. 2. **Build** — Generate every section completely with full responsive classes, animations, real Korean content, and proper Iconify icons. 3. **Cross-check** — Before output, verify: Does the HTML file have an opening `<!DOCTYPE html>` and closing `</html>`? Are all 7+ sections present? Is every section fully populated with real content? ## Handling Long Outputs When a landing page approaches the token limit: - Do NOT compress remaining sections to fit. - Do NOT skip to the footer. - Write at full quality up to a clean breakpoint (end of a complete `</section>` tag). - End with: ``` [PAUSED — X of Y sections complete. Send "continue" to resume from: next section name] ``` On "continue", pick up with the next `<section>` exactly where you stopped. No recap, no re-outputting the `<head>`, no repetition. ## Landing Page Completeness Standards A complete Supanova landing page MUST include: ### Required Elements - `<!DOCTYPE html>` with `<html lang="ko">` - Complete `<head>` with meta tags, Tailwind CDN, Pretendard font, Iconify, tailwind.config - Navigation (floating glass or minimal bar) - Hero section (above the fold, single most impactful section) - At least one trust/social proof element - Feature presentation (3-5 features minimum) - Testimonials or case studies - Primary CTA section - Footer with essential links - Scroll animation JavaScript (`IntersectionObserver` setup) - Complete `</html>` closing ### Required Quality - Every section has real Korean content (no placeholder text) - Every section has full responsive classes (`sm:`, `md:`, `lg:`) - Every interactive element has hover/active states - Every image has `loading="lazy"`, `alt` text, and valid `src` - Every icon uses `<iconify-icon icon="solar:..."></iconify-icon>` ## Quick Check Before finalizing any response, verify: - No banned patterns from the list above appear anywhere - The HTML file is complete from `<!DOCTYPE html>` to `</html>` - All requested sections are present and fully populated - Every code block contains actual runnable HTML, not descriptions - Nothing was shortened, summarized, or omitted to save space - All visible text content is in natural Korean
Related in Ads & Marketing
ads
IncludedMulti-platform paid advertising audit and optimization skill. Analyzes Google, Meta, YouTube, LinkedIn, TikTok, Microsoft, and Apple Ads. 250+ checks with scoring, parallel agents, industry templates, and AI creative generation.
banana
IncludedAI image generation Creative Director powered by Google Gemini Nano Banana models. Use this skill for ANY request involving image creation, editing, visual asset production, or creative direction. Triggers on: generate an image, create a photo, edit this picture, design a logo, make a banner, visual for my anything, and all /banana commands. Handles text-to-image, image editing, multi-turn creative sessions, batch workflows, and brand presets.
rpg-migration-analyzer
IncludedAnalyzes legacy RPG (Report Program Generator) programs from AS/400 and IBM i systems for migration to modern Java applications. Extracts business logic from RPG III/IV/ILE source code, identifies data structures (D-specs), file operations (F-specs), program dependencies (CALLB/CALLP), and converts RPG constructs to Java equivalents. Generates migration reports, complexity estimates, and Java implementation strategies with POJO classes, JPA entities, and service methods. Use when modernizing AS/400 or IBM i legacy systems, analyzing RPG source files (.rpg, .rpgle, .RPGLE), converting RPG to Java, mapping data specifications to Java classes, planning legacy system migration, or when user mentions RPG analysis, Report Program Generator, RPG III/IV/ILE, AS/400 modernization, IBM i migration, packed decimal conversion, or mainframe application rewrite.
brand-library-architect
IncludedBuild a complete brand library for a product — visual asset render pipeline, brand documentation set (BRAND, COPY, MANIFESTO, BIOS, FAQ, GLOSSARY, TONE, PRICING), open-source convention files (README, CONTRIBUTING, SECURITY, CODE_OF_CONDUCT), and a self-contained press kit. This skill should be used when the user asks to "build a brand library / brand kit / press kit / brand assets" for a product, "set up a brand library workflow," "create a positioning manifesto plus visual identity," or any combination of brand documentation + visual asset pipeline. Apply phase-by-phase or run end-to-end. Templates are product-agnostic and use {{TOKEN}} placeholders the skill prompts the user to fill.
writing-tech-post
IncludedAuthors engineering blog posts end-to-end: launch deep-dives, incident postmortems, architecture migrations, performance case studies, tutorials, AI/agent system writeups, security disclosures, and research-to-product translations. Picks the correct archetype, plans the abstraction ladder, enforces an evidence cadence (diagrams, benchmarks, profiles, traces, code, ablations), tunes voice against publisher house styles (Datadog, Vercel, GitHub, AWS, Meta, Cloudflare, Jane Street), and runs a pre-publish gate for narrative momentum and disclosure ethics. Use when drafting a new engineering post, restructuring a draft that feels flat, deciding which evidence form belongs where, validating that depth and product context are balanced, or preparing a postmortem, migration, or performance narrative for external publication. Do not use for API reference documentation, README authoring, marketing copy, release notes, generic SEO content, ghost-written executive thought leadership, or non-engineering long-form essays.
blog-google
IncludedGoogle API integration for blog performance: PageSpeed Insights, CrUX Core Web Vitals with 25-week history, Search Console performance, URL Inspection, Indexing API, GA4 organic traffic, NLP entity analysis for E-E-A-T, YouTube video search for embedding, and Google Ads Keyword Planner. Progressive feature availability based on credential tier (API key, OAuth/service account, GA4, Ads). Shares config with claude-seo at ~/.config/claude-seo/google-api.json. Use when user says "google data", "page speed", "core web vitals", "search console", "indexation", "GA4", "keyword research", "nlp entities", "blog performance", "youtube search", "google api setup".