nexu-io/open-design

saas-landing

Single-page SaaS landing with hero, features, social proof, pricing, and CTA. Respects the active DESIGN.md color/typography/layout tokens. Trigger keywords: "saas landing", "marketing page", "product landing".

79CollectingWrites files

See how to use it View GitHub source

npx skills add https://github.com/nexu-io/open-design --skill "docs/examples/saas-landing-skill"

Automated source guideDocumentationStandard source

Source checked Jul 28, 2026·Refresh due Oct 26, 2026

Reorganized from the pinned upstream SKILL.md

Source-grounded documentation guide: saas-landing

Produce a single-page SaaS landing. Agent, follow this workflow exactly.

npx skills add https://github.com/nexu-io/open-design --skill "docs/examples/saas-landing-skill"

Check the pinned source

The pinned source supports a structured brief, but not an expanded tutorial. Only detected inputs, outputs, and sections are shown.

496 source words · 7 usable sections

Source materials

Read DESIGN.md in the current working directory. If missing, stop and ask for one.
Identify the color palette, typography tokens, and layout principles.
Note the "Agent Prompt Guide" section — it overrides any instruction here if they conflict.

Documentation workflow

Read saas-landing through these 4 source sections

Sections are extracted automatically from the pinned SKILL.md and link back to the source.

1. Read context

Before writing anything: - Read DESIGN.md in the current working directory. If missing, stop and ask for one. - Identify the color palette, typography tokens, and layout principles. - Note the "Agent Prompt Guide" section — it overrides any instruction here if they conflict.

SKILL.md · 1. Read context

Read DESIGN.md in the current working directory. If missing, stop and ask for one.Identify the color palette, typography tokens, and layout principles.Note the "Agent Prompt Guide" section — it overrides any instruction here if they conflict.

2. Plan sections

Required sections, in order: 1. Hero — logo-or-wordmark, headline (tagline input), subhead (1–2 sentences), primary CTA, secondary CTA. Use the herodensity parameter as vertical padding in px. 2. Features — 3–6 feature tiles. Each: icon, short title, 1–2 sentence body. 3. Social…

SKILL.md · 2. Plan sections

Hero — logo-or-wordmark, headline (tagline input), subhead (1–2 sentences), primary CTA, secondary CTA. Use the herodensity parameter as vertical padding in px.Features — 3–6 feature tiles. Each: icon, short title, 1–2 sentence body.Social proof — proofcount logos or testimonials. If 0, skip this section.

3. Apply design system

All colors must come from DESIGN.md tokens. Do not invent hex values.

SKILL.md · 3. Apply design system

All colors must come from DESIGN.md tokens. Do not invent hex values.Typography: use the declared display font for headlines, body font for everything else.Layout: respect the grid, max-width, and section spacing rules.

4. Write the file

Output a single self-contained index.html with: - All CSS inlined in a block in . - System font fallbacks if DESIGN.md fonts aren't loadable from Google Fonts etc. - No external JS. - Semantic HTML (, , , ). - Each editable element tagged with data-od-id="" so the host app's com…

SKILL.md · 4. Write the file

All CSS inlined in a block in .System font fallbacks if DESIGN.md fonts aren't loadable from Google Fonts etc.No external JS.

Documentation checklist

Verify each item before delivery

The source section “1. Read context” has been checked.

The source section “2. Plan sections” has been checked.

The source section “3. Apply design system” has been checked.

The source section “4. Write the file” has been checked.

Static permission evidence

Inspect the exact source lines that triggered a signal

These are source excerpts matched by deterministic rules, not findings of malicious behavior, safety, or actual execution.

medium · write-files

SKILL.md · L30

## 4. Write the file

The documentation asks the agent to create, modify, or delete local files.

Choose a different workflow

When another Skill is the better fit

saas-landing

A separate implementation from nexu-io/open-design; compare its source, maintenance signals, and permission requirements.

Open source detail

design-intelligence

Grounded design brief from the adopted corpus — style, WCAG-checked color tokens, typography, layout pattern, anti-patterns. Use on ui-design-brief or any which-style/palette/font/chart decision.

A separate implementation from event4u-app/agent-config; compare its source, maintenance signals, and permission requirements.

Open source detail

higgsfield-generate

Use when the user wants to generate an image or video via Higgsfield AI. Covers 30+ models: Soul V2, Seedance 2.0, Kling 3.0, Veo 3.1, GPT Image 2, Nano Banana 2. Also covers Marketing Studio — branded ad video/image with avatars and products. Use whenever: "generate an image", "make a video", "animate this photo", "image-to-video", "img2vid", "edit this image with AI", "produce a clip", "create an ad", "make a UGC video", "marketing video", "brand video", "TV spot", "import product from URL", "

A separate implementation from MoizIbnYousaf/marketing-cli; compare its source, maintenance signals, and permission requirements.

Open source detail

FAQ

What does the saas-landing source document cover?

Produce a single-page SaaS landing. Agent, follow this workflow exactly.

How do I install saas-landing?

The source record exposes this install command: npx skills add https://github.com/nexu-io/open-design --skill "docs/examples/saas-landing-skill". Inspect the command and pinned source before running it.

Which permission-related actions were detected?

Static rules flagged write-files in the source; the page lists the matching lines and excerpts.

Repository stars

82,073

Repository forks

9,485

Quality

79/100

Source repository last pushed

2026-07-28

Quality breakdown

Based on traceable docs and repository signals; stars are not treated as quality.

79/100

Documentation24/30

Specificity16/25

Maintenance20/20

Trust signals19/25

Compare before choosing

Related Agent Skills and source variants

These links are selected from shared tasks, functions, stacks, platforms, and same-name variants. Compare the source owner, documentation, permissions, and maintenance signals.

saas-landing by nexu-io

design-intelligence by event4u-app

Grounded design brief from the adopted corpus — style, WCAG-checked color tokens, typography, layout pattern, anti-patterns. Use on ui-design-brief or any which-style/palette/font/chart decision.

higgsfield-generate by MoizIbnYousaf

creative by MoizIbnYousaf

Generate visual asset briefs, ad copy variants, AI image prompts, video scripts, and storyboards. Full creative production system with 5 specialized modes: product photos, product video, social graphics, talking heads, and ad creative. Make sure to use this skill whenever the user mentions any visual or creative marketing need — ad creative, image prompts, video scripts, thumbnails, banners, social graphics, product photography, storyboards, or marketing visuals of any kind. Even if they just sa

site-architecture by coreyhaines31

When the user wants to plan, map, or restructure their website's page hierarchy, navigation, URL structure, or internal linking. Also use when the user mentions "sitemap," "site map," "visual sitemap," "site structure," "page hierarchy," "information architecture," "IA," "navigation design," "URL structure," "breadcrumbs," "internal linking strategy," "website planning," "what pages do I need," "how should I organize my site," or "site navigation." Use this whenever someone is planning what page

View original Skill.mdThis page is parsed directly from the repository SKILL.md without editorial rewriting. Collected: Jul 28, 2026 · about 3 min

SaaS Landing Skill

Produce a single-page SaaS landing. Agent, follow this workflow exactly.

1. Read context

Before writing anything:

Read DESIGN.md in the current working directory. If missing, stop and ask for one.
Identify the color palette, typography tokens, and layout principles.
Note the "Agent Prompt Guide" section — it overrides any instruction here if they conflict.

2. Plan sections

Required sections, in order:

Hero — logo-or-wordmark, headline (tagline input), subhead (1–2 sentences), primary CTA, secondary CTA. Use the hero_density parameter as vertical padding in px.
Features — 3–6 feature tiles. Each: icon, short title, 1–2 sentence body.
Social proof — proof_count logos or testimonials. If 0, skip this section.
Pricing — 2–3 tiers. Include only if has_pricing is true.
Footer CTA — large accent-colored band with one-button call to action.
Footer — minimal: links + copyright.

3. Apply design system

All colors must come from DESIGN.md tokens. Do not invent hex values.
Typography: use the declared display font for headlines, body font for everything else.
Layout: respect the grid, max-width, and section spacing rules.
Components: use declared button/card/input patterns. Do not add shadows if DESIGN.md's Depth & Elevation says minimal.
Accent: use the accent color only once in the hero, once in the footer CTA, and for all links. Do not flood the page.

4. Write the file

Output a single self-contained index.html with:

All CSS inlined in a <style> block in <head>.
System font fallbacks if DESIGN.md fonts aren't loadable from Google Fonts etc.
No external JS.
Semantic HTML (<header>, <main>, <section>, <footer>).
Each editable element tagged with data-od-id="<unique-slug>" so the host app's comment mode can target it.

5. Self-check

Before finishing, verify:

All text is content-meaningful, not lorem ipsum (use product_name and tagline inputs; generate plausible specific copy for the rest).
No broken color references (every CSS color value is in DESIGN.md's palette or a valid alpha/fallback variant).
Responsive breakpoints match DESIGN.md's Responsive Behavior section.
The page looks good at 1440w, 768w, and 375w (mentally simulate).
Accent used no more than twice total.

6. Done

Write only index.html. Do not generate a separate CSS file, JS file, or README.

For skill authors reading this as a reference

This is a minimal but complete skill. Structure:

saas-landing-skill/
├── SKILL.md    ← you are here
└── assets/
    └── base.html    (optional starter template; this skill doesn't use one)

Things to notice:

The od: front-matter block is optional for Claude-Code-only compatibility, but adding it lights up OD's typed inputs, sliders, preview metadata, and capability gating.
The workflow below the front-matter is plain Markdown that the agent reads as its system prompt.
DESIGN.md is treated as a collaborator, not an override. The skill gives the agent authority to override when the brief conflicts, but never to invent new tokens.
data-od-id tagging is how we wire elements to comment mode. Skills that want comment-mode compatibility must annotate their output.

See ../../skills-protocol.md for the full protocol.

Source repo: nexu-io/open-design
Skill path: docs/examples/saas-landing-skill/SKILL.md
Commit SHA: 89d6d4ef21ba
Repository license: Apache-2.0
Data collected: Jul 28, 2026