项目文件夹

文件
Seth Hobson 608c3840ca feat: native plugin-install for Codex/Cursor/Gemini + CLAUDE.md→AGENTS.md symlink
Add lean, native plugin-install entry points so each harness's own plugin
manager can install this marketplace (mirroring obra/superpowers) — committing
only small JSON registries, not duplicated skill/agent content trees.

- Codex: committed marketplace registry (.agents/plugins/marketplace.json) +
  per-plugin manifests (plugins/*/.codex-plugin/plugin.json). Entries point at
  source ./plugins/<name>; Codex reads SKILL.md directly. Transformed
  .codex/skills|agents stay gitignored.
- Cursor: commit the existing .cursor-plugin/ marketplace + .cursor/rules/
  (these already point at source plugins/).
- Gemini: gemini-extension.json already committed (contextFileName: AGENTS.md);
  transformed trees stay gitignored (install via clone + make generate).
- OpenCode: unchanged — install via `make install-opencode` (transformed tree
  stays gitignored).
- CLAUDE.md is now a symlink to AGENTS.md; Claude-Code addenda moved to
  docs/harnesses.md.
- CI: new step fails if `make generate-all` drifts from the committed registries.

Net new committed: ~720 KB of manifests (no skill/agent duplication). Adds
round-trip tests for the new registries + the symlink. Docs updated across
README, docs/harnesses.md, ARCHITECTURE.md, CONTRIBUTING.md, GEMINI.md,
docs/authoring.md, and the PR template.
2026-05-29 13:02:40 -04:00
..

Brand Landing Page

A Claude Code skill that runs a structured brand discovery interview, generates iterative landing pages via Stitch, and delivers a deployment-ready HTML bundle.

Turn brand decisions you haven't made yet into a landing page you'd actually ship.

When To Use

You have a product, side project, or service that needs a landing page. You can build the product but haven't established a brand direction — color palette, font pairing, visual hierarchy, or page structure. This skill handles the design decisions you'd otherwise skip or guess at.

Just ask Claude to create a landing page for your project. The skill takes it from there.

What It Does

  • Brand discovery interview — 10 questions across 3 phases (Product & Purpose, Brand Feel, Visual Preferences) with follow-up triggers for vague or contradictory answers
  • Design system translation — maps brand adjectives to Stitch parameters: color palette, font pairing, shape direction, color mode
  • Visual feedback loop — generates landing pages, opens them in your browser, translates feedback ("it looks too corporate") into targeted Stitch operations
  • Iteration — edit specific sections, explore variants across layout/color/typography, roll back to earlier versions
  • Image handling — extracts style cues from logos or screenshots you provide, saves originals for developer handoff
  • Delivery bundle — final HTML, design tokens (JSON), brand documentation, and deployment checklist as a zip

Setup

Stitch's free tier (350 standard + 200 experimental generations/month) covers all skill functionality — no paid plan required.

The skill walks you through Stitch setup the first time you use it: it'll point you to the Stitch web app for an API key and handle the SDK installation.

Requires Node.js 18+.

File Structure

brand-landingpage/
  .claude-plugin/
    plugin.json
  skills/
    brand-landingpage/
      SKILL.md                         # Main skill instructions
      references/
        interview-framework.md         # Brand discovery question bank and feedback guide
        stitch-architecture.md         # Font/color/prompt/section reference
        state-and-pitfalls.md          # State schema, pitfalls, DEPLOY.md template
  README.md

Limitations

  • Stitch generates static HTML (no JS interactivity, no forms, no animations)
  • No image upload via Stitch API — logos and images are saved in the bundle for manual integration
  • You'll need to replace placeholder images, wire up the CTA link, and add analytics after deployment