hoover-content-system

Creates structured context documents that AI systems can consume to generate consistent, accurate content for a feature. Use when preparing a feature for AI-assisted content generation, building AI writing workflows, or enabling LLMs to write within product constraints.

Creates the canonical vocabulary for a feature, including term definitions, usage rules, and prohibited alternatives. Use when starting content work on a new feature, resolving terminology inconsistencies, or establishing naming conventions for concepts within a feature.

Compares context pack versions to identify changes, generates semantic diffs, and applies version control discipline. Use when updating context packs, reviewing changes before publish, auditing context drift, or maintaining context history.

Creates structured context packs that provide AI systems and content creators with complete information about a feature. Use when preparing for content generation, onboarding writers to features, or building AI-ready documentation.

Creates visual and structured representations of all possible states a feature can exist in, including transitions, triggers, and content requirements per state. Use when documenting a new feature, auditing existing state handling, or preparing context for UI copy.

Maps content touchpoints to user journey stages, identifying what content appears at each phase from awareness through advocacy. Use when planning content strategy for a feature, auditing content coverage, or identifying content gaps in the user experience.

Updates existing feature content context based on user feedback, research findings, or product changes. Use when feedback reveals gaps, inaccuracies, or shifts in user mental models within an existing context pack.

Validates that a context pack contains all required fields, consistent state coverage, and no conflicting definitions. Use when reviewing context packs before handoff, after major updates, or before AI integration.

Systematically evaluate existing UI copy for consistency, clarity, and compliance. Use when reviewing shipped interfaces, preparing for redesigns, or establishing baseline content quality.

Create workflows and rules for how content moves from creation through approval to publication. Use when establishing content operations, scaling content teams, or reducing bottlenecks in content delivery.

Create reusable content patterns with rules, examples, and constraints for consistent UI writing at scale. Use when establishing content systems, onboarding writers, or automating content generation.

Create scalable, consistent microcopy patterns for UI components. Use when building design systems, establishing copy standards for component libraries, or systematizing recurring UI text.

Layer information and options to match user attention and need. Use when designing onboarding flows, complex forms, settings interfaces, or any screen with more information than users need at once.

Translate user goals and mental models into appropriate UI copy. Use when designing new features, diagnosing user confusion, or aligning content with user research findings.

Generate and evaluate names for product features, settings, and UI elements. Use when launching new features, renaming existing functionality, or establishing naming conventions.

Identify and eliminate unnecessary mental effort in UI content. Use when simplifying complex interfaces, improving task completion rates, or diagnosing user confusion.

Organize and sequence content within UI screens for optimal comprehension and task completion. Use when designing new screens, restructuring existing interfaces, or optimizing content hierarchy.

Ensures content execution matches brand strategy and positioning. Use when auditing brand alignment, creating brand-content bridges, or onboarding content teams to brand standards.

Creates information architecture and taxonomy structures for content organization. Use when designing navigation, categorization systems, or content hierarchies.

Creates structured briefs that guide content creation with clear objectives, requirements, and context. Use when assigning content work, briefing writers, or aligning stakeholders on content needs.

Defines foundational content principles that guide all content decisions. Use when establishing content standards, aligning teams on content values, or creating governance frameworks.

Structures marketing and product messaging from high-level positioning to feature-specific claims. Use when launching products, aligning teams on messaging, or creating content briefs.

Creates voice and tone guidelines for a product or brand. Use when establishing new content standards, onboarding writers, or aligning cross-functional teams on communication style.

Designs and documents A/B tests and experiments for content optimization. Use when testing messaging, content formats, or user experience hypotheses.

Defines metrics, measurement frameworks, and reporting structures for content effectiveness. Use when establishing content KPIs, building dashboards, or proving content value.

Creates strategic content roadmaps that align content production with business goals and user needs. Use when planning quarterly/annual content, prioritizing backlogs, or aligning teams on content strategy.

Designs developer onboarding experiences and documentation sequences. Use when creating getting-started guides, quickstart flows, developer portals, sandbox environments, or progressive learning paths for APIs and platforms.

Document complex developer tooling workflows that span multiple tools or systems. Use when writing guides for build pipelines, deployment processes, CI/CD workflows, or multi-tool integration patterns.

Generates CLI error messages and defines exit code conventions. Use when writing stderr output, defining exit codes, creating error message templates, or designing error recovery guidance for command-line tools.

Generates CLI help text, usage strings, and command documentation. Use when writing --help output, man pages, command syntax documentation, or argument descriptions for command-line tools.

Generates inline code comments and documentation strings. Use when writing function/class documentation, explaining complex logic, adding TODO/FIXME annotations, or documenting APIs in code.

Generates step-by-step CLI tutorials and command sequences. Use when creating getting-started guides, multi-step workflows, command chaining examples, or progressive CLI learning paths.

Write clear, comprehensive configuration documentation for developer tools and applications. Use when documenting config files, environment variables, feature flags, or initialization parameters.

Generates SDK documentation and code samples. Use when documenting client libraries, writing quickstarts, creating code examples, or explaining SDK architecture and usage patterns.

Creates multiple headline options optimized for different purposes and platforms. Use when writing headlines for A/B testing, multi-channel distribution, or when stakeholder input requires options.

Edits content for consistency, clarity, and adherence to style guides. Use when reviewing drafts, enforcing editorial standards, or preparing content for publication.

Enhances content clarity, pacing, and reader comprehension through structural and linguistic improvements. Use when editing drafts for readability, optimizing content for specific audiences, or improving engagement metrics.

Organizes complex content into readable, navigable structures. Use when writing articles over 2000 words, comprehensive guides, multi-section reports, or content requiring hierarchical organization.

Creates blog posts for company and product blogs. Use when writing thought leadership, tutorials, announcements, or educational content for publication on a blog.

Creates customer case studies for marketing and sales. Use when documenting customer success stories, transformations, or results for use in marketing collateral, sales enablement, or website content.