rules:
  - name: "Astro Frontmatter Rules"
    description: "Guidelines for writing valid Astro frontmatter in .astro files."
    content: |
      1. Always place frontmatter at the very top of the file.
      2. Use triple dashes (---) to open and close the block.
      3. Only one frontmatter block per .astro file.
      4. Use frontmatter for:
         - Imports
         - Declaring constants and variables
         - Exporting metadata with `export const`
         - Accessing Astro.props in components
         - Async data fetching (using await)
      5. Do NOT:
         - Use DOM APIs (document, window)
         - Add client-side scripts here
      6. Everything exported becomes available in the template:
         Example:
           ---
           export const title = "OSS Communities";
           ---
           <h1>{title}</h1>
      7. For components, destructure props from Astro.props:
         ---
         const { heading } = Astro.props;
         ---
      8. Keep heavy logic outside frontmatter (move to utility files).

# Accessibility Guidelines

- **Follow W3C’s Web Content Accessibility Guidelines (WCAG) 2.2** for all frontend code and UI implementations. 
- **Use semantic HTML** to structure content. Use proper elements for headings, lists, landmarks, tables, forms, etc., rather than divs or spans. 
- **Ensure sufficient color contrast** for text and important UI elements. Use color schemes that meet WCAG 2.2 contrast ratios (at least 4.5:1 for normal text). **Do not rely on color alone** to convey information — use icons, patterns, or text labels as needed in addition to color cues. 
- **Make all functionality keyboard-accessible.** Users must be able to navigate and operate all interactive components using a keyboard alone. Ensure a **visible focus indicator** is present on focused elements. Do not remove the browser’s default focus outline without providing an equivalent visible style.
- **Use ARIA attributes sparingly and appropriately.** Only use WAI-ARIA roles/properties when native HTML elements can’t achieve the desired accessible behavior. (Prefer semantic HTML elements with built-in accessibility over adding ARIA roles to non-semantic elements.)
- **Adhere to these accessibility practices in all code**

Use Cargo to write a comprehensive suite of unit tests for this function