playbooks

home / skills / oimiragieo / agent-studio / content-creation-rules

content-creation-rules skill

/.claude/skills/_archive/dead/content-creation-rules

This skill helps writers apply content creation rules to produce clear, accurate, and audience-focused documentation across formats.

npx playbooks add skill oimiragieo/agent-studio --skill content-creation-rules

Review the files below or copy the command above to add this skill to your agents.

Files (3)
SKILL.md
1.6 KB
---
name: content-creation-rules
description: Applies guidelines for creating high-quality documentation content, focusing on clarity, accuracy, and relevance.
version: 1.0.0
model: sonnet
invoked_by: both
user_invocable: true
tools: [Read, Write, Edit]
globs: '**/*.md'
best_practices:
  - Follow the guidelines consistently
  - Apply rules during code review
  - Use as reference when writing new code
error_handling: graceful
streaming: supported
---

# Content Creation Rules Skill

<identity>
You are a coding standards expert specializing in content creation rules.
You help developers write better code by applying established guidelines and best practices.
</identity>

<capabilities>
- Review code for guideline compliance
- Suggest improvements based on best practices
- Explain why certain patterns are preferred
- Help refactor code to meet standards
</capabilities>

<instructions>
When reviewing or writing code, apply these guidelines:

- Write clear, concise, and grammatically correct content.
- Ensure all information is accurate and up-to-date.
- Tailor the content to the intended audience.
- Use a variety of content formats, such as text, images, and videos, to engage the reader.
  </instructions>

<examples>
Example usage:
```
User: "Review this code for content creation rules compliance"
Agent: [Analyzes code against guidelines and provides specific feedback]
```
</examples>

## Memory Protocol (MANDATORY)

**Before starting:**

```bash
cat .claude/context/memory/learnings.md
```

**After completing:** Record any new patterns or exceptions discovered.

> ASSUME INTERRUPTION: Your context may reset. If it's not in memory, it didn't happen.

Overview

This skill applies practical guidelines for creating high-quality documentation content with a focus on clarity, accuracy, and relevance. It helps writers and developers produce concise, audience-aware documentation that is easy to consume and maintain. The skill is geared toward improving content quality through review, suggestions, and targeted refactoring.

How this skill works

The skill inspects documentation and inline content for clarity, grammar, factual accuracy, and audience fit. It flags ambiguous phrasing, outdated information, and sections that lack necessary context or examples. It then recommends concrete edits, structure changes, and format variations (text, images, code samples) to improve comprehension and engagement. Finally, it can suggest refactoring steps to align content with established guidelines.

When to use it

  • Before publishing technical docs, READMEs, or developer guides to catch clarity and accuracy issues.
  • When onboarding new contributors so documentation matches the audience’s skill level.
  • During documentation sprints to enforce consistent tone, structure, and formatting.
  • When converting long-form content into concise reference material or quick-start guides.
  • When updating docs after API or code changes to ensure accuracy and completeness.

Best practices

  • Write short, grammatically correct sentences and prioritize active voice.
  • Keep content audience-focused: state assumptions and required background up front.
  • Use a mix of formats: short text, diagrams, screenshots, and runnable code samples.
  • Validate facts and examples against the current codebase and external sources.
  • Prefer concrete examples and step-by-step instructions over abstract descriptions.

Example use cases

  • Review a project README and provide a prioritized list of clarity and accuracy fixes.
  • Refactor a long tutorial into a compact quick-start with links to deeper material.
  • Standardize API documentation sections so every endpoint includes purpose, inputs, and examples.
  • Audit onboarding docs to remove outdated steps and add missing prerequisites.
  • Suggest visuals or code snippets where conceptual text causes repeated questions.

FAQ

Can this skill edit code samples as well as prose?

Yes. It reviews code samples for correctness and clarity and suggests fixes or clearer examples.

Will it preserve project voice and style?

It recommends changes that align with the existing voice, but you can accept or adapt suggestions to match your style guide.