# {{name}} — fallback reference

> This file is a **stub**. The package is in your project but no
> automated `llms.txt` source is known. Replace this content with notes
> as you learn the API — keep it scoped to what the agent needs to know
> when working with this dependency.
>
> _Generated by `/references-sync` on {{date}}. For in-repo agent
> context, not SEO._

## Package

- **Name:** `{{name}}`
- **Version:** `{{version}}` (from `{{manifest_path}}`)
- **Homepage:** {{homepage}}

## Why this exists

Your manifest lists `{{name}}` as a direct dependency. The agent benefits
from having a short reference here when it needs to read or modify code
that uses this package — it saves a roundtrip to upstream docs.

## What to put here

Capture only what the agent would otherwise have to discover on its own:

- The 3–5 most common API entry points used in this project
- Surprising gotchas (config combinations that bit you in production)
- Version-specific behaviour (if you're pinned to a specific minor)
- Links to the upstream docs you actually use

Keep it short. If this stub gets longer than ~80 lines, split it — the
agent reads this in-context and bloat hurts.

## What NOT to put here

- A copy of the upstream README (the upstream is authoritative)
- Tutorials or "getting started" prose (the agent doesn't need motivation)
- Anything that drifts from the actual code (use `/doc-gardening` to find drift)

## See also

- `docs/references/index.md` — full reference index
- `/references-sync` — refresh this file
- `/skill-extractor` — promote a recurring lesson about this package into a skill