Code Guide agent – analyze docs before implementation

3. Include project and custom content (optional)

• STARTER_GUIDE.md in this skill's directory (.cursor/skills/build-code-guide/STARTER_GUIDE.md): if present, read it. It describes project structure (modules, folders), React Query usage, and typing for query/mutation hooks. Merge its content into the final code guide (e.g. section “Project structure & conventions” or “Starter guide”).
• code-guide-custom.md in this skill's directory (.cursor/skills/build-code-guide/code-guide-custom.md): if present, read it. This is the user’s own Markdown: project-specific conventions, preferred components, naming, or extra rules. Merge into the final code guide (see step 4).
• Both are optional; include only the files that exist.

4. Write the code guide to .cursor/code-guide.md

Create .cursor/code-guide.md in this format:

# Code Guide (generated)

Sources: [list URLs from code-guide-urls.json]

## Components / API (summary)
- **Name** – when to use, import (package).

## Patterns
- Layout: …
- Forms: …
- Navigation: …

## Imports (examples)
\`\`\`
import { X } from '@mantine/...';
\`\`\`

• Keep the guide concise (tens to a few hundred lines) so it can be used during implementation without blowing up context.
• If the documentation is very long, summarize sections (Core, Hooks, Dates, etc.) and list only the most important components plus links to the full URLs.
• If you read STARTER_GUIDE.md (from this skill folder), add a section to the guide, e.g. “Project structure & conventions” or “Starter guide”, with the file content (or a concise summary if very long).
• If you read code-guide-custom.md (from this skill folder), append a section, e.g. “Custom / project-specific”, with that file’s content.

Final guide = generated summary from URLs + optional STARTER_GUIDE section + optional custom section.

5. Confirm

• Tell the user the code guide was updated and where it is (.cursor/code-guide.md).
• Suggest: "You can now ask for implementation; the agent will use this file as the main reference when writing code."

Notes

• Do not implement any features in this skill — only fetch URLs, analyze, and write the guide.
• If a URL fails to fetch (network error, 404), still write the guide with what succeeded and in the "Sources" section note which link was not updated.
• Inputs live in this skill folder (.cursor/skills/build-code-guide/): code-guide-urls.json, STARTER_GUIDE.md, code-guide-custom.md. Edit these to configure what gets merged into the code guide. Output is always .cursor/code-guide.md.
• Project starter: STARTER_GUIDE.md in this folder is optional. When present, the agent reads it and adds its content to the code guide (project structure, modules, React Query patterns).
• Custom file: code-guide-custom.md in this folder is optional. The user can put project-specific rules, conventions, or component preferences there; the agent includes it in the generated guide when present.
• For Mantine: llms-full.txt has the full docs in one file; llms.txt is the index with links to individual pages.