사용 방법
- 설치 명령을 복사하고 자신의 에이전트 환경에 설치하기 전에 소스 패키지를 확인하세요.
- 필요한 도구, 인증 정보, 지원 환경은 원본 문서에서 확인하세요.
- 입력과 원하는 산출물을 설명하고 출처와 결과를 대조하세요.
npx skills add https://github.com/owl-listener/designer-skills --skill content-strategy시작 전 확인
- 설치에는 모델 구독, API 한도, 파일 접근 권한이 포함되지 않습니다.
- 별점 수와 설치 수는 활동 지표이며 독립적인 품질·보안 검증이 아닙니다.
원본 Skill 문서
원본 저장소의 제목, 예시, 코드, 표, 링크, 이미지를 유지해 표시합니다.
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
- Audit existing content and identify gaps, redundancy, and orphaned material
- Interview users and stakeholders to understand content needs and vocabulary
- Define content types and models
- Establish voice, tone, and writing principles
- Define governance: owners, workflows, review cycles
- 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
