agentsclimarketplace

Web marketing landing

Skill robzilla1738/roberts-skills/plugins/web-marketing-landing/skills/web-marketing-landing

Provider-agnostic agent skills and plugins for AI coding assistants. By Robert Courson.

Install
npx -y skills add robzilla1738/roberts-skills --skill web-marketing-landing

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 5 stars5 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Design and scaffold a premium SaaS marketing home page: aurora hero, glass nav, connector hub, bento product grid, comparison bands, FAQ, CSS-driven motion (no Framer required). Use for /web-marketing-landing or when recreating a long-form product landing in Next.js + Tailwind v4.

SKILL.md

5.7 KB, as published. Nobody here has run it

Web Marketing Landing

Hub skill for a long-form product landing page: editorial typography, monochrome surfaces with a single cyan–navy accent gradient, glass on hero/chrome only, CSS-first motion, and eleven ordered sections inside a marketing shell.

Read this file first, then open only the spoke files needed for the task.

Mission

Build a landing that feels premium and product-specific, not a generic SaaS template. The page should read as one continuous story: hero promise → plain explanation → integrations → product depth → outputs → flow → differentiation → trust → personas → FAQ → final CTA.

Use placeholders in specs and copy decks: {{Brand}}, {{Accent}}, {{AppUrl}}, {{Connectors[]}}. Do not hard-code a customer name in skill prose.

Non-negotiables

  1. CSS-first motion — entrance stagger, gradient shift, connector orbit, and nav glass use keyframes/utilities. Do not require Framer Motion for the landing.
  2. Token-driven color — monochrome UI (--color-bg, --surface-panel*, hairlines) plus one accent gradient (--accent-grad-* or project-prefixed vars). Accent is punctuation, not wallpaper.
  3. Glass disciplinebackdrop-blur on hero eyebrow, CTAs, hero feature cards, and scroll-phase nav only. Body sections use solid panels and hairline borders.
  4. Viewport-aware heromin-h-[calc(100svh-<nav-offset>)] on the hero panel; respect mobile safe areas.
  5. Reduced motion — disable rise, gradient shift, and orbit animations under prefers-reduced-motion: reduce; set scroll-behavior: auto on html.
  6. Scroll nav — fixed nav interpolates width/padding/background; data-glass over dark hero, solid pill after scroll threshold. Support solidNav for pages without a dark hero.
  7. Accessible structure — semantic sections, aria-hidden on decorative layers, focus-visible outlines on interactive elements.

Section blueprint (implement in order)

#Section IDComponent patternSpoke
1(hero)Full-viewport aurora hero + 3 feature cardshero-aurora.md
2#what-is-{{slug}}55/45 intro grid + 3 fact pillslayout-sections.md
3#connectorsCentered copy + connector hubconnector-hub.md
4#productHeadline + bento features gridsection-components.md
5(deliverables)4-column icon cardssection-components.md
6#flowSplit header + flow preview + marketing-washsection-components.md
7(comparison)“Typical vs {{Brand}}” gradient panel rowssection-components.md
8#secureSplit header + security matrixsection-components.md
9(use-cases)4-column persona cardslayout-sections.md
10(faq)2-column FAQ cardssection-components.md
11(footer CTA)Large wordmark CTA bandshell-and-nav.md

Wrap all sections in MarketingShellmain → sections. See shell-and-nav.md.

Spoke routing

TaskRead
Tokens, type, buttons, cardsfoundations.md
Section grids, spacing, max-widthslayout-sections.md
Hero backdrop, cards, orbithero-aurora.md
Shell, nav scroll, footershell-and-nav.md
Connector gridconnector-hub.md
CSS animations, washes, glassmotion-and-effects.md
Bento, comparison, FAQ, previewssection-components.md
New repo, deps, file treestack-and-scaffold.md
JSON-LD, metadataseo-metadata.md

Greenfield checklist

  1. Next.js 16+ App Router, React 19, Tailwind CSS v4 — see stack-and-scaffold.md.
  2. Add globals.css tokens + marketing utilities + .public-nav rules (unlayered, after @layer utilities).
  3. Implement shell + nav + footer, then hero, then remaining sections top to bottom.
  4. Wire CTAs to {{AppUrl}} (external app) — marketing site does not embed auth.
  5. Add JSON-LD on home per seo-metadata.md.
  6. Verify: hero stagger, nav glass→solid, hub ring, bento breakpoints, reduced-motion, production build.

Do / don't

DoDon't
One gradient accent word per major headlineGradient-fill every heading
Hairline borders + soft shadows on cardsHeavy neumorphism everywhere
text-balance / text-pretty on headlines and bodyFixed pixel widths that break mobile
Stagger animationDelay 0–320ms on hero childrenIdentical delay on all elements
Keep connector hub to 14 tiles + center markCrowd the hub with 20+ icons

Reference implementation

If the user has an existing marketing home built with this stack, use it for parity checks only; the skill itself stays brand-agnostic.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.