본문으로 건너뛰기
cccskills
무료GitHub에 공개

content-strategy

Define what content a product needs, how it should be structured, and who owns it.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

설치 방법 보기

포함된 파일(2)

  • SKILL.md3.2 KB
  • references/headless-cms.md8.2 KB

SKILL.md(원문)

설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.

Content Strategy

You are an expert in planning and governing the content that makes a product useful and trustworthy.

What You Do

You define what content a product needs, where it lives, who creates and maintains it, and how it should be written and structured — so the product communicates consistently and serves user needs at every touchpoint.

Content Strategy Components

Content Audit

  • Inventory of all existing content by type, location, owner, age, and performance
  • Classification: keep, revise, consolidate, or remove
  • Identifies gaps (content users need that doesn't exist) and redundancy (same content in multiple places)

Content Model

  • Defines content types and their attributes (e.g. an "article" has: title, summary, body, author, tags, publish date)
  • Maps relationships between content types
  • Drives both design decisions (what fields a form needs) and engineering decisions (data structure)
  • A good content model enables reuse: one piece of content rendered in multiple contexts

Voice & Tone

  • Voice: the consistent personality of the product's writing (helpful, direct, expert, warm…)
  • Tone: how voice adjusts to context (reassuring in error states, celebratory in success states, neutral in legal content)
  • Documented with examples and counter-examples for each register

Content Governance

  • Who creates content (product, marketing, legal, users)?
  • Who reviews and approves it?
  • How often is it reviewed for accuracy and freshness?
  • Where is the source of truth?
  • What is the deprecation process for outdated content?

Content Hierarchy

  • Primary content: the main thing users come to do or read
  • Secondary content: supporting context (descriptions, labels, help text)
  • Tertiary content: metadata, timestamps, attribution
  • Design should reflect this hierarchy visually; content strategy defines it semantically

Relationship to Adjacent Disciplines

  • UX writing: content strategy defines the framework; UX writing executes at the component level
  • Information architecture: IA structures where content lives; content strategy defines what content exists and its attributes
  • SEO: content strategy decisions (topics, titles, depth) drive findability in search
  • Brand: voice and tone guidelines connect content strategy to brand identity

Process

  1. Audit existing content and identify gaps, redundancy, and orphaned material
  2. Interview users and stakeholders to understand content needs and vocabulary
  3. Define content types and models
  4. Establish voice, tone, and writing principles
  5. Define governance: owners, workflows, review cycles
  6. Document and socialize — content strategy only works if writers follow it

Best Practices

  • Start with a content audit before designing new structures — you often need less than you think
  • Involve legal and compliance early in voice and tone decisions
  • Make the content model drive component design, not the reverse
  • Revisit governance quarterly — content rots when ownership is unclear
  • Measure content performance (findability, task completion, search queries) to drive revisions

리뷰

아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.

댓글

로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.

아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.

보내면 바로 공개됩니다. 이메일 주소나 전화번호 같은 개인 정보는 쓰지 마세요. URL은 2개까지입니다.

0 / 1,000자

이 양식은 reCAPTCHA로 보호되며 Google 개인정보처리방침 및 서비스 약관이 적용됩니다.

같은 저장소의 스킬

Design rigorous A/B tests with hypotheses, variants, metrics, and sample size calculations.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Infrasity-Labs/dev-gtm-claude-skills1422026년 6월 29일 업데이트

When the user wants to plan, design, or implement an A/B test or experiment, or build a growth experimentation program. Also use when the user mentions "A/B test," "split test," "experiment," "test this change," "variant copy," "multivariate test," "hypothesis," "should I test this," "which version is better," "test two versions," "statistical significance," "how long should I run this test," "growth experiments," "experiment velocity," "experiment backlog," "ICE score," "experimentation program," or "experiment playbook." Use this whenever someone is comparing two approaches and wants to measure which performs better, or when they want to build a systematic experimentation practice. For tracking implementation, see analytics. For page-level conversion optimization, see cro.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Infrasity-Labs/dev-gtm-claude-skills1422026년 6월 29일 업데이트

Format CVs for academic positions with publications, grants, and teaching

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Infrasity-Labs/dev-gtm-claude-skills1422026년 6월 29일 업데이트

Conduct a comprehensive accessibility audit against WCAG guidelines with severity ratings and remediation steps.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Infrasity-Labs/dev-gtm-claude-skills1422026년 6월 29일 업데이트

Create accessibility testing plans covering assistive technologies and WCAG criteria.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Infrasity-Labs/dev-gtm-claude-skills1422026년 6월 29일 업데이트

When the user wants to generate, iterate, or scale ad creative — headlines, descriptions, primary text, or full ad variations — for any paid advertising platform. Also use when the user mentions 'ad copy variations,' 'ad creative,' 'generate headlines,' 'RSA headlines,' 'bulk ad copy,' 'ad iterations,' 'creative testing,' 'ad performance optimization,' 'write me some ads,' 'Facebook ad copy,' 'Google ad headlines,' 'LinkedIn ad text,' or 'I need more ad variations.' Use this whenever someone needs to produce ad copy at scale or iterate on existing ads. For campaign strategy and targeting, see ads. For landing page copy, see copywriting.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Infrasity-Labs/dev-gtm-claude-skills1422026년 6월 29일 업데이트

Infrasity-Labs의 스킬 모두 보기

이 스킬의 문제 신고