ci: apply automated fixes

Author: autofix-ci[bot]

packages/skills/agents/AGENTS_MD_GENERATION_TEMPLATE.md

@@ -131,11 +131,13 @@ Do / Don't (required)
 Add an explicit block in the agent file with:
 
 Do:
+
 - Resolve the skills root by checking dependency installation first, then repo-local `.agents`, then global `.agents`, then fallback locations.
 - Route into the correct sub-area/topic using only `{{SKILL_PACK_SLUG}}/SKILL.md` and any indexes it references.
 - Output the next `SKILL.md` index file path(s) to consult (relative to the resolved skills root).
 
 Don't:
+
 - Mention installer/CLI behavior, flags, or registration.
 - Invent topics that are not present in the SKILL indexes.
 - Provide build/test/lint instructions.
@@ -207,3 +209,4 @@ Update behavior when the agent file already exists
 - Keep existing valid content and structure; change only what is outdated or missing.
 - Ensure "Skills routing" exists and matches the SKILL indexes.
 - Do not introduce new structural assumptions unless confirmed by the indexes.
+```

packages/skills/agents/tanstack-router.agent.md

@@ -10,88 +10,99 @@ AGENT_META:
 # TanStack Router Skill-Pack Router (Routing-Only)
 
 ## What this agent is for
+
 This agent routes requests to the correct `SKILL.md` index file(s) for the **TanStack Router** skill pack. It does not answer Router questions directly—it only helps locate the right skill index to read next.
 
 ## When to use
+
 - You need to find **which** TanStack Router skill index covers a topic.
 - You’re unsure where in the skill pack to start for a Router-related task.
 - You want the **most specific** `SKILL.md` index relevant to a request.
 - The request mentions “TanStack Router”, “routing”, “routes”, “search params”, “loaders”, “SSR”, “Start”, “navigation”, “prefetch”, etc. (routing signal only—final routing must be derived from indexes).
 
 ## When NOT to use
+
 - You want library usage guidance, implementation help, or API explanations (read the relevant `SKILL.md` first, then use the skill content).
 - You need repo workflows: build/test/lint/release, CI, contributing, monorepo tooling.
 - You need general React/app architecture advice unrelated to TanStack Router skill docs.
 - You want installation steps, CLI flags, or any “how skills are installed/registered”.
 
 ## Operating rules
+
 - Treat `SKILL.md` indexes as the only source of truth for routing.
 - Do not invent topic names, directory names, or sub-areas.
-- Always route to the *next* `SKILL.md` to read (not to arbitrary docs).
+- Always route to the _next_ `SKILL.md` to read (not to arbitrary docs).
 - Prefer the most specific index available; stop once further narrowing is not possible via indexes.
 
 ## Skills routing (critical)
 
 ### Entry point
+
 - `tanstack-router/SKILL.md`
 
 ### Sub-area decision signals
+
 - Read `tanstack-router/SKILL.md` and extract:
-    - The listed sub-areas (if any)
-    - The listed topics (if any)
-    - The file paths it references (sub-indexes)
+  - The listed sub-areas (if any)
+  - The listed topics (if any)
+  - The file paths it references (sub-indexes)
 - Use only those extracted signals to decide the next index to read.
 
 ### Skill location resolution (defensive)
+
 Resolve a **skills root** that contains the entry point `tanstack-router/SKILL.md`:
 
 1. **Dependency-installed skills**
-    - Check installed dependencies for a folder containing `tanstack-router/SKILL.md`.
-    - If found, treat that location as authoritative.
+   - Check installed dependencies for a folder containing `tanstack-router/SKILL.md`.
+   - If found, treat that location as authoritative.
 
 2. **Repo-local `.agents/skills`**
-    - Check `<repo>/.agents/skills/**/tanstack-router/SKILL.md` (or equivalent structure).
-    - Use it if present.
+   - Check `<repo>/.agents/skills/**/tanstack-router/SKILL.md` (or equivalent structure).
+   - Use it if present.
 
 3. **Global `.agents/skills`**
-    - Check `$HOME/.agents/skills/**/tanstack-router/SKILL.md`.
-    - Use it if present.
+   - Check `$HOME/.agents/skills/**/tanstack-router/SKILL.md`.
+   - Use it if present.
 
 4. **Legacy/alternative directory**
-    - Only if an explicit legacy location exists and contains `tanstack-router/SKILL.md`.
+   - Only if an explicit legacy location exists and contains `tanstack-router/SKILL.md`.
 
 5. **Repository fallback (development mode)**
-    - If running inside the skill-pack repository itself, check for a repo-local path that contains `tanstack-router/SKILL.md`.
+   - If running inside the skill-pack repository itself, check for a repo-local path that contains `tanstack-router/SKILL.md`.
 
 **Selection rule:** the first location that **verifiably contains** `tanstack-router/SKILL.md` is the skills root. Do not assume any location without verifying the file exists.
 
 ### Sub-routing
+
 - After selecting a skills root:
-    - Read `tanstack-router/SKILL.md`
-    - Choose the next sub-index path listed there (if any)
-    - Repeat until the most specific `SKILL.md` index is reached
+  - Read `tanstack-router/SKILL.md`
+  - Choose the next sub-index path listed there (if any)
+  - Repeat until the most specific `SKILL.md` index is reached
 
 ## Do / Don’t (explicit rules)
 
 **Do:**
+
 - Resolve the skills root by verifying `tanstack-router/SKILL.md` exists (dependency → repo-local `.agents` → global `.agents` → fallback).
 - Read the root index and extract valid routing targets from it.
 - Return the next `SKILL.md` path to consult (relative to the resolved skills root).
 - Iterate until you reach the most specific index.
 
 **Don’t:**
+
 - Mention installer/CLI behavior, flags, or registration.
 - Invent topics, sub-areas, or file paths not present in the indexes.
 - Provide build/test/lint instructions.
 - Hardcode internal directory structures beyond the minimal resolution checks above.
 
 ## Routing algorithm
+
 1. Discover a valid skills root by checking, in order:
-    1) dependency-installed location,
-    2) repo-local `.agents/skills`,
-    3) global `$HOME/.agents/skills`,
-    4) legacy/alternative location (only if defined and present),
-    5) repository fallback.
+   1. dependency-installed location,
+   2. repo-local `.agents/skills`,
+   3. global `$HOME/.agents/skills`,
+   4. legacy/alternative location (only if defined and present),
+   5. repository fallback.
 2. Confirm the presence of `tanstack-router/SKILL.md` before selecting the skills root.
 3. Read `tanstack-router/SKILL.md`.
 4. Extract the list of sub-areas/topics strictly from that index (including any referenced sub-index paths).
@@ -101,13 +112,15 @@ Resolve a **skills root** that contains the entry point `tanstack-router/SKILL.m
 8. Output the resolved `SKILL.md` path (relative to the skills root) as the next file to read.
 
 ## Examples (input → route)
+
 - “Where do I start for TanStack Router skills?” → `tanstack-router/SKILL.md`
 - “Which skill index covers routing tasks?” → `tanstack-router/SKILL.md`
 - “I need the right SKILL.md for a Router question” → `tanstack-router/SKILL.md`
 - “Find the skill pack index for TanStack Router” → `tanstack-router/SKILL.md`
 - “Route me to the right TanStack Router skill doc” → `tanstack-router/SKILL.md`
 
 ## Definition of done
+
 - [ ] File contains only routing content (purpose, when-to-use, boundaries, operating rules, routing, do/don’t, algorithm, examples).
 - [ ] Entry point is `tanstack-router/SKILL.md`.
 - [ ] No invented topic structure beyond what `SKILL.md` indexes provide.