Cline rules for Astro

# Cline and Roo rules

Project rules for Cline and Roo Code in this Astro repository.
Use the project's commands. Do not invent a package manager, and do not run destructive shell commands.

## Tool use

- Read the files you will change before editing them.
- Prefer a focused patch over rewriting a whole file.
- Run the test command from this file after a behavior change, or say why you could not.
- Do not delete generated folders, lockfiles, or migrations unless the task says so.

## Stack

This repository is an Astro site. Pages ship zero client JavaScript unless an island needs it. Content lives in content collections when the repo already uses them.

## Layout

- Routes live in `src/pages` or the content-driven routing the project uses.
- Shared UI lives in `src/components`. Interactive islands are the exception.
- Content collections and their schemas live in `src/content` when the project has them.

## Commands

- Dev server: `npm run dev`
- Build: `npm run build`
- Check: `npm run check`

Use the script the repo already defines when it differs from the command above.

## Conventions

- Do the data load in the frontmatter of the Astro component.
- Add `client:*` only when the component needs state or browser APIs.
- Validate content with the collection schema. Do not cast frontmatter.
- Use Astro's image and font helpers if the project already does.
- Keep endpoints in `src/pages` as `.ts` routes or the project's action style.
- Match the CSS approach already configured. Do not add a second one.

## Testing

Add or update tests when behavior changes.

Test a pure helper or a content schema. Do not require a browser for a markdown change.

## Style

- Optimize for the next reader over the shortest diff.
- Comment only when the why is non-obvious.
- Name things the way neighboring files already do.
- Do not reformat code you did not change.

## Errors

- Fail at the boundary. Do not swallow errors.
- Return a 404 via `Astro.redirect` or the response status the project uses when content is missing. Do not render an empty shell.

## Scope

- Do the requested task. Do not refactor unrelated code.
- Match the rigor already in the repo. Fix what you touch.
- Ask one clarifying question only when the task cannot be finished without it. Otherwise state the assumption and continue.

## Avoid

- Do not mark a whole layout as a client island to use one hook.
- Do not import server-only secrets into an island.
- Do not fetch in `useEffect` inside an island when the Astro page can load the data.
- Do not bypass the content schema with a raw glob.

## Done when

- The requested behavior works.
- `npm run build` succeeds for the routes you touched.
- The diff stays inside the task.
- You list anything you could not run.