정보
`content-and-copy` 스킬은 블로그 게시물, 기사, 웹사이트 카피와 같은 일반적인 편집 콘텐츠를 작성하고 편집하며, 목소리, 구조 및 목표에 중점을 둡니다. 콘텐츠 초안 작성, 편집 또는 재작성 명령에 반응하며, 개요를 구체화해야 하거나 기존 텍스트의 명확성을 개선해야 할 때 사용됩니다. 이것은 범용 콘텐츠 스킬이며, 랜딩 페이지와 이메일은 전용 스킬이 담당합니다.
빠른 설치
Claude Code
추천npx skills add rampstackco/claude-skills -a claude-code/plugin add https://github.com/rampstackco/claude-skillsgit clone https://github.com/rampstackco/claude-skills.git ~/.claude/skills/content-and-copyClaude Code에서 이 명령을 복사하여 붙여넣어 스킬을 설치하세요
문서
Content and Copy
Write or edit content that serves a specific reader and goal. Stack-agnostic. This skill is for general content production. Specialized skills exist for landing pages (landing-page-copy) and email (email-sequences).
When to use
- Writing a blog post or article
- Drafting website copy (homepage sections, about, services)
- Editing existing content for voice or clarity
- Writing how-to guides, listicles, or explainers
- Producing knowledge base or help center articles
- Adapting brand voice to a specific piece
When NOT to use
- Landing pages with conversion goals (use
landing-page-copy) - Email campaigns or sequences (use
email-sequences) - Brand voice definition (use
brand-voice) - SEO keyword research (use
seo-keyword) - Content strategy and planning (use
content-strategy)
Required inputs
- The piece to be written or edited
- The target reader (specific audience segment)
- The goal of the piece (inform, convert, rank, retain, entertain)
- The brand voice (or willingness to define it)
- Length target and any structural constraints
If brand voice is undefined, run brand-voice first or use a working voice and document it as you go.
The framework: 5 dimensions
Strong content is strong on all five. Weakness on any one drags the rest down.
1. Hook
The opening earns the read. Most readers decide whether to continue within 3 to 5 seconds.
Strong hooks do one of:
- Promise specific value. "By the end, you'll know exactly which X to pick for your situation."
- Surface a tension. "Most advice on X is wrong. Here's why."
- Open a loop. A question or scenario the rest of the piece resolves.
- State a contrarian point. Provided you can defend it.
- Show, don't summarize. A specific moment or scenario the reader recognizes.
Weak hooks:
- Throat-clearing ("In today's fast-paced world...")
- Dictionary-definition openers ("X is a type of Y that...")
- Stating the obvious ("Many people struggle with X.")
- Vague promises ("This article will explore X.")
2. Structure
The reader follows the flow without effort.
Common structures:
- Problem → Solution → Proof. Most non-fiction.
- List + reasoning. Listicles with substance, not filler.
- How-to (numbered steps). Procedural content.
- Compare → Contrast → Recommend. Comparison and review content.
- Story → Lesson. Narrative non-fiction.
- Question → Answer → Implication. Explainers and analysis.
Pick a structure. Stick to it. Most weak content fails because the writer drifted between structures.
3. Voice
The piece sounds like the brand.
- Voice attributes consistent throughout (per
brand-voicedefinition) - Tone shifts appropriately for context (a serious topic gets a serious tone, even from a playful brand)
- Vocabulary preferences honored
- Grammar and style standards followed (contractions, em dashes, sentence length)
- Reads aloud like the brand would actually talk
Test: Read a paragraph aloud. Does it sound like the brand? If it sounds like AI, generic marketing, or someone else's voice, edit until it doesn't.
4. Substance
The piece earns its length. Every paragraph adds something.
Substance comes from:
- Specifics. "Roughly 40 percent" beats "many." Names, numbers, examples, data.
- Original perspective. Your take, not a summary of everyone else's.
- Actionable detail. What the reader does with this information.
- Honest tradeoffs. What's NOT true, what doesn't work, what's overhyped.
- Real examples. Specific scenarios, real customers, real failures.
Lack of substance shows up as:
- Padding ("It's important to note that...")
- Restating the same point in three different paragraphs
- Generalities that anyone in the category could write
- Word counts hit by stretching, not depth
5. Closing
The piece ends with intention.
Strong closings:
- Resolve the loop opened in the hook.
- Issue a specific next action. What does the reader do now?
- Land a memorable line. Something quotable.
- Return to the opening. Echo or invert the first line.
Weak closings:
- Summary that restates the article
- "Hope this helps!" or equivalent
- A wall of CTAs from unrelated programs
- Trailing off with no clear ending
Workflow
For new pieces
- Confirm the brief. Reader, goal, length, voice. If the brief is vague, do not write yet.
- Outline. Structure first. Headlines and section purposes only. Skip prose until the structure is sound.
- Open with the hook. Write the opening before anything else. If the hook isn't working, the rest won't either.
- Draft for substance. First draft is about getting the substance down. Voice comes in editing.
- Edit for voice. Read aloud. Tighten sentences. Cut padding. Apply brand voice.
- Edit for clarity. Each paragraph: does it earn its place? Each sentence: is the meaning unambiguous?
- Pre-publish checks. Headers in order, no skipped levels, internal links present, image alt text written, SEO basics applied (title, meta, slug).
For editing existing content
- Read the whole piece first. Do not edit on first read. Understand it before changing it.
- Identify what's working. Note the strong sections so you don't damage them.
- Identify what's broken. Voice mismatches, weak structure, vague claims, padding.
- Edit by priority. Structure first (move sections, cut sections). Then substance (strengthen claims). Then voice. Then sentence-level polish.
- Read aloud. Catch awkward phrasing the eye misses.
Failure patterns
- Writing without a brief. Without reader, goal, and voice defined, the piece drifts.
- Burying the lead. The most important thing is in paragraph 8 because the writer "got there."
- Padding to hit word count. Length should serve the reader, not the production schedule.
- Generic voice. Sounds like every other article in the category. Brand voice neutralized.
- Weak transitions. Sections feel disconnected. Reader has to do the work the writer should have done.
- No closing. The piece runs out instead of ending.
- Edit by adding. Fixing weak content by piling on more words. Strong editing usually cuts.
- Ignoring the headers. Headers carry navigation weight. Bad headers fail readers who scan.
Output format
Default output is a markdown document at [content-slug].md ready to import into the CMS.
Structure:
# [H1: matches the title or tightly paraphrases]
[Hook paragraph. Earns the read in 3 to 5 seconds.]
[Body content with H2 sections, H3 subsections where useful.]
## [H2 section heading - descriptive, not clever]
[Section content.]
### [H3 if needed]
[Subsection content.]
## [H2 section heading]
[Section content.]
## [Closing section]
[Closing that resolves and points to next action.]
Front-matter for SEO and CMS:
---
title: [SEO title, 50 to 60 chars]
description: [Meta description, 120 to 160 chars]
slug: [url-slug]
author: [author]
date: [YYYY-MM-DD]
last_updated: [YYYY-MM-DD]
tags: [tag1, tag2]
category: [category]
---
Reference files
references/content-brief-template.md- The brief that should exist before any content is written.references/content-edit-checklist.md- Pre-publish editing checklist.
GitHub 저장소
자주 묻는 질문
content-and-copy Skill이란 무엇인가요?
content-and-copy은(는) rampstackco이(가) 만든 Claude Skill입니다. Skill은 Claude가 필요할 때 불러오는 지침과 리소스를 묶어 추가 프롬프트 없이 content-and-copy 관련 작업을 수행할 수 있게 합니다.
content-and-copy은(는) 어떻게 설치하나요?
이 페이지의 설치 명령을 사용하세요. content-and-copy을(를) Claude Code 플러그인으로 추가하거나 저장소를 skills 디렉터리에 복제한 다음 Claude를 다시 시작해 Skill을 불러옵니다.
content-and-copy은(는) 어떤 카테고리에 속하나요?
content-and-copy은(는) 메타 카테고리에 속합니다.
content-and-copy은(는) 무료로 사용할 수 있나요?
네. content-and-copy은(는) AIMCP에 등록되어 있으며 무료로 설치할 수 있습니다.
연관 스킬
이 스킬은 콘텐츠 콜렉션(Content Collections)을 위한 프로덕션 검증된 설정을 제공합니다. 콘텐츠 콜렉션은 Markdown/MDX 파일을 Zod 검증이 포함된 타입 안전한 데이터 콜렉션으로 변환해주는 TypeScript 최우선 도구입니다. 블로그, 문서 사이트 또는 콘텐츠 중심의 Vite + React 애플리케이션을 구축할 때 타입 안전성과 자동 콘텐츠 검증을 보장하기 위해 사용하세요. Vite 플러그인 구성과 MDX 컴파일부터 배포 최적화 및 스키마 검증에 이르기까지 모든 것을 다룹니다.
이 스킬은 개발자들이 Polymarket 예측 시장 플랫폼을 활용한 애플리케이션을 구축할 수 있도록 지원하며, 거래 및 시장 데이터를 위한 API 통합 기능을 포함합니다. 또한 WebSocket을 통한 실시간 데이터 스트리밍을 제공하여 실시간 거래와 시장 활동을 모니터링할 수 있습니다. 이를 통해 거래 전략을 구현하거나 실시간 시장 업데이트를 처리하는 도구를 생성하는 데 활용할 수 있습니다.
이 스킬은 개발자들이 명령어, 파일, LSP 작업 등 25개 이상의 이벤트 유형에 연결되는 OpenCode 플러그인을 만들 수 있도록 돕습니다. JavaScript/TypeScript 모듈을 위한 플러그인 구조, 이벤트 API 명세, 구현 패턴을 제공합니다. OpenCode AI 어시스턴트의 라이프사이클을 사용자 정의 이벤트 기반 로직으로 가로채거나, 모니터링하거나, 확장해야 할 때 사용하세요.
SGLang은 RadixAttention 프리픽스 캐싱을 활용하여 JSON, 정규식, 에이전트 워크플로우를 위한 고속 구조화 생성에 특화된 고성능 LLM 서빙 프레임워크입니다. 특히 반복되는 프리픽스가 있는 작업에서 상당히 빠른 추론 속도를 제공하여 복잡한 구조화 출력 및 다중 턴 대화에 이상적입니다. 제약 디코딩이 필요하거나 광범위한 프리픽스 공유가 있는 애플리케이션을 구축할 때는 vLLM과 같은 대안보다 SGLang을 선택하십시오.
