writing-popkorn-docs

Rewrites Popkorn documentation into clear, human-centered prose.

19|Updated Jul 8, 2026

Search Tags:#documentation #technical writing #readme #content rewriting #css animation #popkorn

Ready to run

npx skills add https://github.com/ayarse/popkorn --skill writing-popkorn-docs

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: writing-popkorn-docs
Source: https://github.com/ayarse/popkorn/tree/main/.claude/skills/writing-popkorn-docs
Command: npx skills add https://github.com/ayarse/popkorn --skill writing-popkorn-docs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill transforms developer-oriented or inconsistent Popkorn prose into clear, compelling documentation for humans discovering and using the project.

Core Features & Use Cases

Human-first rewriting: Reshapes READMEs, guides, package documentation, and marketing copy around the concept before the mechanics.
Consistent positioning: Presents Popkorn as a format and runtime for portable motion graphics, using a close CSS dialect without claiming it is CSS.
Voice and accuracy checks: Applies the project's confident, honest, forward-looking tone, verifies examples against the repository, keeps capability claims precise, and removes em-dashes.
Use Case: Use it to revise a README that reads like internal developer notes into an approachable introduction that explains the CSS thesis, shows a verified scene, and guides newcomers toward the playground.

Quick Start

Use this skill to rewrite the selected Popkorn documentation for a human audience while preserving accurate project positioning and verified examples.

Frequently Asked Questions about writing-popkorn-docs

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I rewrite technical documentation for a human audience?▼

Rewriting technical documentation for a human audience means restructuring developer-oriented prose to explain concepts before mechanics. This approach transforms internal notes into approachable introductions that highlight project value and guide newcomers effectively.

What is the best way to make a README approachable for new users?▼

The best way to make a README approachable is to apply human-first rewriting that presents the concept before the mechanics. This shifts internal developer notes into clear, compelling introductions that show verified examples and guide users toward exploration.

How do I keep technical syntax examples accurate when rewriting docs?▼

Keeping syntax examples accurate when rewriting docs requires verifying examples against the source repository. This ensures that rewritten marketing copy and package documentation maintain precise capability claims while adopting a more approachable tone.

Does rewriting marketing copy require preserving specific project positioning?▼

Rewriting marketing copy does require preserving specific project positioning. It must present accurate format and runtime claims, use precise terminology without overclaiming compatibility, and maintain a confident, forward-looking tone throughout the text.

Why should I remove em-dashes from technical writing?▼

Removing em-dashes from technical writing enforces a specific voice and formatting style guide. This constraint ensures consistent, readable prose across all public-facing documentation, package guides, and landing copy without unexpected punctuation breaks.