qwik-docs-development

# Qwik Docs Development Use this skill for `packages/docs/**` work. Keep the repo-wide rules from `.ruler/AGENTS.md` in force. ## Fast Path 1. Identify whether the change is docs content, route/layout code, API docs surfacing, generated LLM output, search/indexing, or deployment behavior. 2. For docs content, follow the writing style below before changing site mechanics. 3. For existing docs pages already in the LLM manifest, edit source content and regenerate only when verification requires generated output. 4. For new pages that should appear in LLM outputs, update the curated manifest in `packages/docs/scripts/generate-llms.ts`. 5. When editing docs scripts, keep generation deterministic and add focused unit coverage for parser, path, URL, or output-shape behavior. 6. Prefer docs-specific commands from `packages/docs/package.json`. ## Writing Style Write Qwik docs for readers who are learning the concept while solving a concrete task. - Start with the user need and the Qwik concept in one or two plain paragraphs. - Split the page into short sections named after the concept or API, such as `useSignal()`, `Passing signals to child components`, or `Nested objects and arrays`. - Explain the default case first, then reveal deeper, less common, or higher-cost cases later, this is done in a note block. There is short and long form notes in MDX. - Use complete, minimal examples with current v2 imports from `@qwik.dev/core`. - After each example, state what the ...