prowler-docs

## When to Use Use this skill when writing Prowler documentation for: - Feature documentation - API/SDK references - Tutorials and guides - Release notes ## Brand Voice ### Unbiased Communication - Avoid gendered pronouns (use "you/your" or "they/them") - Use inclusive alternatives: businessman → businessperson, mankind → humanity - No generalizations about gender, race, nationality, culture - Avoid militaristic language: fight → address, kill chain → cyberattack chain ### Technical Terminology - Define key terms and acronyms on first use: "Identity and Access Management (IAM)" - Prefer verbal over nominal constructions: "The report was created" not "The creation of the report" - Use clear, accessible language; minimize jargon ## Formatting Standards ### Title Case Capitalization Use Title Case for all headers: - Good: "How to Configure Security Scanning" - Bad: "How to configure security scanning" ### Hyphenation - Prenominal position: "world-leading company" - Postnominal position: "features built in" ### Bullet Points Use when information can be logically divided: ```markdown Prowler CLI includes: * **Industry standards:** CIS, NIST 800, NIST CSF * **Regulatory compliance:** RBI, FedRAMP, PCI-DSS * **Privacy frameworks:** GDPR, HIPAA, FFIEC ``` ### Interaction Verbs - Desktop: Click, Double-click, Right-click, Drag, Scroll - Touch: Tap, Double-tap, Press and hold, Swipe, Pinch ## SEO Optimization ### Sentence Structure Place keywords at the beginning: - Good: "T...