{"enrichment":{"faq":[{"a":"Prowler-docs establishes the official authoring standards for all Prowler documentation. The style guide covers brand voice principles emphasizing inclusive communication, markdown formatting conventions, proper header hierarchy for SEO optimization, and consistent structure across feature documentation, tutorials, API references, and compliance guides. Following these standards ensures documentation remains accessible, searchable, and aligned with Prowler's communication identity.","q":"What are the prowler documentation style guide principles?"},{"a":"Prowler-docs specifies how to use MDX components and templates when creating feature documentation. The framework guides you through component selection, proper syntax, and integration patterns for different documentation types. MDX allows you to combine markdown with React components, enabling interactive examples and dynamic content within Prowler tutorials and guides while maintaining consistent formatting across the documentation site.","q":"How do I write prowler docs using MDX components?"},{"a":"Prowler-docs defines specific markdown formatting rules including header hierarchy structure, code block conventions, list formatting, and link syntax. Proper formatting ensures your documentation renders correctly, maintains SEO value through semantic HTML structure, and provides a consistent reading experience. The guide covers best practices for emphasis, tables, and inline code to keep Prowler docs professional and scannable.","q":"What formatting rules should I follow for prowler markdown docs?"},{"a":"Prowler-docs provides templates and structural guidelines for tutorials, API references, and compliance guides. Each documentation type has specific sections, ordering conventions, and content requirements. Tutorials follow a step-by-step format with clear objectives, while API references use consistent parameter documentation and example patterns. Compliance guides emphasize framework alignment and control mapping to ensure readers find information efficiently.","q":"How do I structure prowler tutorials and API references correctly?"},{"a":"Prowler-docs establishes brand voice guidelines emphasizing clarity, accessibility, and inclusive communication. The standards guide writers to use plain language, avoid jargon where possible, employ gender-neutral pronouns, and ensure content serves diverse audiences. These principles apply across all documentation types, from technical API references to user-facing guides, creating welcoming and understandable Prowler documentation.","q":"What is the prowler docs brand voice and inclusive language approach?"},{"a":"Prowler-docs incorporates SEO best practices including proper header hierarchy, descriptive metadata, keyword placement, and semantic structure. The guidelines recommend using H1 for page titles, logical H2/H3 nesting, descriptive alt text for images, and internal linking strategies. These practices improve discoverability while maintaining readability, ensuring Prowler documentation ranks well in search results and serves users effectively.","q":"How does prowler documentation optimize for SEO?"}],"shadow_tags":["style-guide","technical-writing","content-standards","markdown-formatting","documentation-template","inclusive-language","seo-best-practices","brand-voice","mdx-components","documentation-structure"],"summary_rewrite":"Prowler-docs provides the authoring standards and formatting conventions for creating consistent Prowler documentation. It covers brand voice principles, markdown formatting, SEO best practices, and MDX component usage across feature docs, tutorials, API references, and compliance guides."},"files":[{"bytes":3157,"path":"skills/prowler-docs/SKILL.md","sha256":"3ee31ac65f7e72cd932b3d57db6d5bf1136726eeddf476281b9e08e46f6e9592","url":"https://skillfed.io/files/prowler-cloud/prowler/prowler-docs/0dc4f6ad/SKILL.md"}],"id":"prowler-cloud/prowler/prowler-docs","links":{"html":"https://skillfed.io/prowler-cloud/prowler/prowler-docs","md":"https://skillfed.io/prowler-cloud/prowler/prowler-docs.md","repo":"https://github.com/prowler-cloud/prowler"},"meta":{"agents_supported":[],"first_seen":"2026-07-28","forks":2285,"language":"Python","last_updated":"2026-07-27","license":"Apache-2.0","name":"prowler-docs","publisher":"prowler-cloud","stars":14491},"relations":{"similar":[{"id":"foryourhealth111-pixel/Vibe-Skills/prowler-docs"},{"id":"prowler-cloud/prowler/skill-creator"},{"id":"prowler-cloud/prowler/prowler-compliance-review"},{"id":"prowler-cloud/prowler/prowler-ci"},{"id":"prowler-cloud/prowler/prowler-compliance"},{"id":"prowler-cloud/prowler/prowler"},{"id":"prowler-cloud/prowler/prowler-mcp"},{"id":"prowler-cloud/prowler/skill-sync"},{"id":"prowler-cloud/prowler/playwright"},{"id":"prowler-cloud/prowler/prowler-pr"}]},"slug":{"owner":"prowler-cloud","repo":"prowler","skill":"prowler-docs"},"version":"0dc4f6ad"}