---
description: Mandatory pre-flight check before planning or coding in sandbox projects. Verifies material-hu documentation is accessible.
alwaysApply: true
---

# Pre-flight: Verify material-hu documentation is accessible (BLOCKING)

Before `/refine-feature` or any component mapping, verify that the key material-hu files exist and are readable. The actual reading happens in `/refine-feature` — only for the specific components that feature needs.

## Required: project must be installed first

If `node_modules/material-hu` does not exist, run `bun install` before proceeding. The project scaffold + `bun install` is done by `/bootstrap-react-project`.

## Verify file access

Check that these files exist in the installed package:

```bash
ls node_modules/material-hu/src/components/design-system/COMPONENTS.md
ls node_modules/material-hu/src/components/composed-components/COMPONENTS.md
ls node_modules/material-hu/src/theme/hugo/newTokens.ts
```

If any file is missing, it likely means `bun install` didn't complete correctly. Re-run it with the GitHub token:

```bash
GITHUB_TOKEN=$(cat ~/.humand/github-token) bun install
```

All `@humanddev/*` packages install via GitHub Packages using that token — no repo cloning needed.

## What gets read and when

These files are read lazily during `/refine-feature`, only for the components that a specific feature will use:

- `COMPONENTS.md` (design-system) — component index and import paths
- `COMPONENTS.md` (composed-components) — higher-level components and preferred patterns
- `newTokens.ts` — exact color token paths
- `<Component>/types.ts` — props, defaults, onChange signatures

⛔ Do NOT read all files upfront. Read only what you need, when you need it, during `/refine-feature`.
