supanova-full-output

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Supanova Full-Output Enforcement

Supanova 完整输出强制规范

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:

```

```
```

```
```

```
```

```
```

```
```
// ...
```
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

以下模式属于严重错误，绝对禁止出现：

代码块中：

```

```
```

```
```

```
```

```
```

```
```
// ...
```
单独使用
```
...
```
替代省略的HTML内容

文本描述中：

“若需要我继续生成，请告知”
“我可以按需添加更多板块”
“为简洁起见，我仅展示 hero 板块”
“其余部分遵循相同模式”
“剩余板块同理”
“我将留待您自行定制”

结构上的捷径：

用户要求完整页面却仅输出 Hero 板块
仅展示首尾板块，跳过中间部分
用一个示例加描述替代重复的板块
描述HTML应包含的内容而非直接编写代码
用户要求完整页面却生成骨架/线框图

Execution Process

执行流程

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.
Build — Generate every section completely with full responsive classes, animations, real Korean content, and proper Iconify icons.
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?

范围确认 —— 通读完整请求。统计预期的板块/组件数量。“落地页”至少包含：导航栏 + Hero + 社交证明 + 功能特性 + 用户评价 + CTA + 页脚（共7个板块）。锁定板块数量。
生成构建 —— 完整生成每个板块，包含完整的响应式类、动画、真实的韩语内容，以及正确的Iconify图标。
交叉检查 —— 输出前，验证：HTML文件是否包含开头的
```
<!DOCTYPE html>
```
和结尾的
```
</html>
```
？是否包含全部7个及以上板块？每个板块是否都填充了真实内容？

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.

当落地页内容接近令牌限制时：

不得为了压缩空间而简化剩余板块。
不得直接跳转到页脚。
以完整的质量生成内容，直到一个清晰的断点（完整的
```
</section>
```
标签结束处）。
以以下内容结尾：

[已暂停 —— 已完成Y个板块中的X个。发送“continue”以从下一个板块名称处继续生成]

收到“continue”指令后，从下一个

<section>

标签处精确继续生成。无需回顾，无需重新输出

<head>

，不得重复内容。

Landing Page Completeness Standards

落地页完整性标准

A complete Supanova landing page MUST include:

一个完整的Supanova落地页必须包含：

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

带有
```
<html lang="ko">
```
的
```
<!DOCTYPE html>
```
包含元标签、Tailwind CDN、Pretendard字体、Iconify、tailwind.config的完整
```
<head>
```
导航栏（悬浮玻璃效果或极简栏）
Hero板块（首屏可见，最具影响力的板块）
至少一个信任/社交证明元素
功能特性展示（至少3-5个功能）
用户评价或案例研究
主CTA板块
包含必要链接的页脚
滚动动画JavaScript（
```
IntersectionObserver
```
配置）
完整的
```
</html>
```
闭合标签

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>

每个板块都包含真实的韩语内容（无占位文本）
每个板块都包含完整的响应式类（
```
sm:
```
,
```
md:
```
,
```
lg:
```
）
每个交互元素都有 hover/active 状态
每个图片都带有
```
loading="lazy"
```
、
```
alt
```
文本和有效的
```
src
```

每个图标都使用

<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

在最终确定任何响应前，验证以下内容：

上述禁用模式未在任何地方出现
HTML文件从
```
<!DOCTYPE html>
```
到
```
</html>
```
是完整的
所有要求的板块均已存在且填充完整内容
每个代码块都包含可直接运行的实际HTML，而非描述
未为节省空间而缩短、总结或省略任何内容
所有可见文本内容均为自然韩语