Claude Code를 위한 브랜드 및 웹사이트 라이프사이클 스킬 라이브러리

I can't install plugins or run commands in this conversation, and I don't have access to your repo, homepage copy, or metadata. So I can't actually load skills, read the catalog, or produce a real audit. Here's what I can do instead: give you the exact steps to run yourself, plus a framework for the brand/SEO pass you can apply once you paste in the relevant files.

## 1. Install the marketplace and starter subset

Run these in Claude Code (adjust if the repo name differs):

```bash
# Add the marketplace
/plugin marketplace add rampstackco/claude-skills

# Install the starter subset
/plugin install rampstack-starter@rampstack
```

Then verify with `/plugin` to see what's loaded. If `rampstack-starter` isn't the exact plugin name, list available plugins from the marketplace first.

## 2. How to pick skills from the catalog

Once installed, ask Claude Code to read the catalog (usually a `marketplace.json` or `README` in the plugin dir) and match skills to your repo. A reasonable selection heuristic for a brand/SEO pass:

- **Brand/voice skill** — if the catalog has one (e.g., `brand-voice`, `copywriting`), load it to audit homepage tone and positioning.
- **SEO/metadata skill** — for title tags, meta descriptions, headings, structured data.
- **Content strategy skill** — for the keyword and content plan.
- **Code-review/diff skill** — to keep changes minimal and file-scoped.

Ask it explicitly: *"Read the catalog, list skills relevant to a brand + SEO audit of a marketing homepage, and explain why each applies before loading."*

## 3. Brand & SEO pass — what to hand me

To do this for real, paste or point me at:

- Homepage component(s) — e.g., `app/page.tsx`, `pages/index.*`, or the marketing route
- Metadata source — `layout.tsx` metadata export, `next-seo` config, `_document`, `index.html` `<head>`, or a CMS content file
- `package.json` (to confirm framework and routing)
- Any existing `sitemap`, `robots.txt`, or OG image setup

## 4. Audit framework (apply once I have the files)

**Homepage copy**
- Value prop in first screen: who it's for, what it does, why it's different — in one sentence
- Headline clarity vs. cleverness; subhead that earns the click
- CTA hierarchy (primary vs. secondary), above the fold
- Proof (logos, metrics, testimonials) placement
- Consistency of product name/terminology (keep `runchr`, `Remingle`, `MCP`, `RAG` etc. as-is per glossary)

**Metadata**
- `<title>`: primary keyword + brand, ≤60 chars
- `meta description`: benefit + differentiator, ≤155 chars
- OG/Twitter cards: title, description, image present and correct
- Canonical URL, `lang`, favicon
- Structured data (Organization, WebSite, SoftwareApplication as applicable)

**Keyword & content plan**
- 1 primary + 3–5 secondary keywords mapped to homepage sections
- 3–5 supporting content pieces (docs, comparison, use-case) with target intent
- Internal linking from homepage to those pieces

**File-level changes (minimal diff)**
- List each file, the exact lines/sections to change, and why
- Prefer editing existing metadata exports over adding new files
- No refactors, no restyling — copy and metadata only unless a structural fix is required

## 5. What I need from you to proceed

Reply with the homepage file(s) and metadata source (or a link/paste), and confirm the framework (Next.js? Astro? plain HTML?). I'll then return:

- The skill list I'd load and why (based on the catalog you paste)
- A copy audit with specific rewrites
- A keyword/content plan
- A file-by-file diff proposal, kept minimal

If you'd rather I work from a description, paste the current homepage copy and `<head>` contents and I'll do the audit against that.