Product Content Strategy — AI skill

When to use it

Use before designing content-heavy screens to identify missing content, model fields and ownership, and distinguish primary content from supporting metadata. Product-content planning rather than component-level copywriting or a full information architecture; quarterly review advice is a heuristic. Requires actual product inventory and user vocabulary. Not installed, executed or runtime-tested during discovery. GitHub stars are repository-wide.

Compatible agents

Claude CodeGemini CLI

Installation

In Claude Code, add /plugin marketplace add Owl-Listener/designer-skills, then open /plugin Discover and install ux-strategy; this includes content-strategy. Other supported-agent setup is documented in the upstream README. Retain the skill folder and its companion files.

Review the source and instructions before installing in your agent.

License

MIT

Last checked Oct 25, 2026.

Pair this skill with a visual reference

A skill guides how your agent works; a design reference shows the direction you want. Choose an example for a specific job, such as the headline hierarchy or form layout, and keep your project's existing design rules explicit.

Start with design references you can inspect, then use our guide to briefing an AI coding agent to turn observations into requirements. If you need implementation components, compare UI libraries for your stack.

These pages are public. Browsing a skill does not install it, and TastefulKit's design-reference MCP tools do not search the AI-skill directory.