agentleFS
moronireismoronireis/agent-system-partners/.claude/skills/pipeline-landing-page/SKILL.md

pipeline-landing-page

Skill0 starsChanged 2 months agoMITView on GitHub

End-to-end landing page pipeline — offer/brief, copy through the editor gate, creative direction, UI specs, implementation, and the double gate (functional + aesthetic) before deploy. Use when a complete landing page must go from intent to live.

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    NOT for: copy-only changes on an existing page (pipeline-copy), visual refresh without new copy (dsg-ui → dev-builder → dsg-critic …

    line 13
  2. Distinctive:

    No step starts without its upstream handoff file existing.

    line 30

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Pipeline — Landing Page

The full chain from offer to live page. Runs under a director plan with one task contract per step (docs/task-contract.md).

When to use

  • A new landing page, sales page, or campaign page needs to be built end-to-end.
  • NOT for: copy-only changes on an existing page (pipeline-copy), visual refresh without new copy (dsg-ui → dev-builder → dsg-critic directly), or a full brand build (pipeline-brand).

Chain

  1. mkt-strategist — loads the project pack, defines offer angle + page goal + structure brief → brain/ops/handoffs/brief-<slug>.md
  2. mkt-copywriter — full page copy from the brief (headline variants included) → to gate
  3. mkt-editor — humanization + PASS/BLOCK/EXIT verdict → brain/ops/reports/copy-<slug>.md (max 2 loops)
  4. dsg-director — unified creative brief consuming approved copy + mood report (if premium: activate pipeline-luxo overlay here) → brain/ops/handoffs/brief-design-<slug>.md
  5. dsg-ui — tokens, breakpoint layouts, component specs → brain/ops/handoffs/spec-ui-<slug>.md
  6. dev-builder (+ dsg-motion for motion moments) — implementation from spec + copy
  7. Double gate, in parallel:
    • dev-qa — functional PASS/BLOCK (forms, links, responsive, performance budget) → brain/ops/reports/qa-<slug>.md
    • dsg-critic — aesthetic APPROVE/REVISE/REJECT vs principles + mood report → brain/ops/reports/design-<slug>.md
  8. dev-ops — deploy preview; production only after both gates pass AND explicit human approval.

Rules

  • No step starts without its upstream handoff file existing.
  • Gate failures roll back to the named owner (copy → mkt-copywriter; visual → dsg-ui/dsg-motion; functional → dev-builder). Max 2 loops per gate, then escalate to the user.
  • Lead capture/integration needs (forms → CRM/email) enter as a dev-integrations contract at step 6.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.