AGENTS GUIDE — clrviz

This project uses a generator-driven color-space catalog and Azure-centric deployment. Follow the notes below when making changes as an AI coding assistant.

Workflow guardrails

Always run

npm run generate:color-spaces

after modifying

scripts/generate-color-spaces.mjs

colour_rgb_colourspaces.json

. The generated file (

src/data/generatedColorSpaces.ts

) is committed.

Keep the repository middle-grey aesthetic; UI changes should respect the existing palette unless explicitly requested.
When touching the request workflow, ensure the API route
```
app/api/request-color-space
```
still works without Azure credentials (it must fail gracefully and log locally).
Do not remove or bypass the Vitest suite; add tests for new helpers or data transforms.
Prefer
```
npm ci
```
in CI contexts to preserve lockfile integrity.

Data curation tips

```
colour_rgb_colourspaces.json
```
originates from the Python
```
colour-science
```
package. If you need new entries not covered there, add them in the generator’s
```
missingProfiles
```
section with reason tags.
Tone-curve overrides and popularity heuristics live in
```
scripts/generate-color-spaces.mjs
```
. Keep tone curve labels user-friendly (e.g.
```
ARRI LogC4
```
) and regenerate the dataset after edits.

Deployment expectations

GitHub Actions (
```
.github/workflows/deploy.yml
```
) runs lint + test before deploying via Azure Static Web Apps. Keep build output at
```
.next
```
and retain
```
skip_app_build: true
```
unless you refactor the workflow.
The Dockerfile expects Next.js standalone output. If you change the build process, update both the Dockerfile and README accordingly.

Quality checklist before handing work back

```
npm run lint
```
```
npm run test
```
```
npm run build
```

If any step fails, fix the root cause before responding.

Communication hints

Document user-facing or operational changes in
```
README.md
```
.
Note any new environment variables or secrets.
Flag follow-up TODOs inside the README “TODO & future enhancements” list rather than scattering standalone TODO comments in code.

AGENTS GUIDE — clrviz

This project uses a generator-driven color-space catalog and Azure-centric deployment. Follow the notes below when making changes as an AI coding assistant.

Workflow guardrails

Always run

npm run generate:color-spaces

after modifying

scripts/generate-color-spaces.mjs

colour_rgb_colourspaces.json

. The generated file (

src/data/generatedColorSpaces.ts

) is committed.

Keep the repository middle-grey aesthetic; UI changes should respect the existing palette unless explicitly requested.
When touching the request workflow, ensure the API route
```
app/api/request-color-space
```
still works without Azure credentials (it must fail gracefully and log locally).
Do not remove or bypass the Vitest suite; add tests for new helpers or data transforms.
Prefer
```
npm ci
```
in CI contexts to preserve lockfile integrity.

Data curation tips

```
colour_rgb_colourspaces.json
```
originates from the Python
```
colour-science
```
package. If you need new entries not covered there, add them in the generator’s
```
missingProfiles
```
section with reason tags.
Tone-curve overrides and popularity heuristics live in
```
scripts/generate-color-spaces.mjs
```
. Keep tone curve labels user-friendly (e.g.
```
ARRI LogC4
```
) and regenerate the dataset after edits.

Deployment expectations

GitHub Actions (
```
.github/workflows/deploy.yml
```
) runs lint + test before deploying via Azure Static Web Apps. Keep build output at
```
.next
```
and retain
```
skip_app_build: true
```
unless you refactor the workflow.
The Dockerfile expects Next.js standalone output. If you change the build process, update both the Dockerfile and README accordingly.

Quality checklist before handing work back

```
npm run lint
```
```
npm run test
```
```
npm run build
```

If any step fails, fix the root cause before responding.

Communication hints

Document user-facing or operational changes in
```
README.md
```
.
Note any new environment variables or secrets.
Flag follow-up TODOs inside the README “TODO & future enhancements” list rather than scattering standalone TODO comments in code.

AGENTS GUIDE — clrviz

AGENTS GUIDE — clrviz

Workflow guardrails

Data curation tips

Deployment expectations

Quality checklist before handing work back

Communication hints

Related Skills

Markdown Converter

Nano Banana Pro

1password

AGENTS GUIDE — clrviz

Workflow guardrails

Data curation tips

Deployment expectations

Quality checklist before handing work back

Communication hints