content-strategy

Included with Lifetime

$97 forever

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

Writing & Docs

What this skill does

# 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

Files: 1

Size: 3.2 KB

Complexity: 5/100

Category: Writing & Docs

Source: https://github.com/owl-listener/designer-skills/tree/main/ux-strategy/skills/content-strategy

Related in Writing & Docs

jax-development

Included

Use this skill when the user is writing, debugging, profiling, refactoring, reviewing, benchmarking, parallelising, exporting, or explaining JAX code, or when they mention JAX, jax.numpy, jit, grad, value_and_grad, vmap, scan, lax, random keys, pytrees, jax.Array, sharding, Mesh, PartitionSpec, NamedSharding, pmap, shard_map, Pallas, XLA, StableHLO, checkify, profiler, or the JAX repo. It helps turn NumPy or PyTorch-style code into pure functional JAX, fix tracer/control-flow/shape/PRNG bugs, remove recompiles and host-device syncs, choose transforms and sharding strategies, inspect jaxpr/lowering/IR, and benchmark compiled code correctly.

Writing & Docsscripts

nature-article-writer

Included

Drafts, rewrites, diagnostically critiques, and style-calibrates primary research manuscripts for Nature and Nature Portfolio journals. Use when the user wants a Nature-style title, summary paragraph or abstract, introduction, results, discussion, methods, figure legends, presubmission enquiry, cover letter, reviewer response, or when a scientific draft sounds generic, jargon-heavy, structurally weak, or AI-ish and needs precise, broad-reader-friendly prose without inventing data, analyses, or references. Best for primary research articles and letters rather than reviews or press releases unless explicitly adapting one.

Writing & Docsscripts

deckrd

Included

Document-driven framework that derives requirements, specifications, implementation plans, and executable tasks from goals through structured AI dialogue. Use when user says "write requirements", "create spec", "plan implementation", "derive tasks", "structure this feature", "break down into tasks", or "document this module". Also use for reverse engineering existing code into docs (/deckrd rev). Do NOT use for direct code writing — use /deckrd-coder after tasks are generated. Do NOT use when the user only wants to run or fix existing code without planning.

Writing & Docsscripts

clinical-decision-support

Included

Generate professional clinical decision support (CDS) documents for pharmaceutical and clinical research settings, including patient cohort analyses (biomarker-stratified with outcomes) and treatment recommendation reports (evidence-based guidelines with decision algorithms). Supports GRADE evidence grading, statistical analysis (hazard ratios, survival curves, waterfall plots), biomarker integration, and regulatory compliance. Outputs publication-ready LaTeX/PDF format optimized for drug development, clinical research, and evidence synthesis.

Writing & Docsscripts

handling-sf-data

Included

Salesforce data operations with 130-point scoring. Use this skill to create, update, delete, bulk import/export, generate test data, and clean up org records using sf CLI and anonymous Apex. TRIGGER when: user creates test data, performs bulk import/export, uses sf data CLI commands, needs data factory patterns for Apex tests, or needs to seed/clean records in a Salesforce org. DO NOT TRIGGER when: SOQL query writing only (use querying-soql), Apex test execution (use running-apex-tests), or metadata deployment (use deploying-metadata).

Writing & Docsscripts

accelint-ac-to-playwright

Included

Convert and validate acceptance criteria for Playwright test automation. Use when user asks to (1) review/evaluate/check if AC are ready for automation, (2) assess if AC can be converted as-is, (3) validate AC quality for Playwright, (4) turn AC into tests, (5) generate tests from acceptance criteria, (6) convert .md bullets or .feature Gherkin files to Playwright specs, (7) create test automation from requirements. Handles both bullet-style markdown and Gherkin syntax with JSON test plan generation and validation.

Writing & Docsscripts