What problem does it solve? Writing website content for a technical product often misses the mark because developers want implementation details while CTOs want business impact. This Skill provides structured content strategy guidelines so every page, section, and comparison table speaks appropriately to both audiences without inventing features or making unverifiable claims. ## Core Features & Use Cases - Dual-audience guidelines: Separate content rules and selling points for developers (CLI commands, workflows, terminal mockups) and CTOs (compliance, risk reduction, comparison tables). - Content patterns: Ready-to-use formats including before/after comparison tables, TerminalMockup.astro demos, and pixel-card feature grids. - Accuracy constraints: Enforces rules against inventing features, unverifiable performance claims, or mistranslated CLI flags. - Use Case: When drafting a new landing page section for Envilder, apply this Skill to produce copy that shows developers the npx envilder --map=envilder.json --envfile=.env workflow while highlighting zero-secrets-in-source-control for technical leaders. ## Quick Start Use the website-content-strategy skill to write a features section for the Envilder homepage that appeals to both developers and CTOs.
