# Add category

> Add a category to a ZeroDirs directory site. Edits site.config.ts, picks a lucide icon, seeds at least one listing so the new category page is not empty, and…

You are reading one page of the ZeroDirs documentation. ZeroDirs is a paid Astro + Cloudflare Workers starter for directory sites: every page is rendered to static HTML at build time, the site ships no client JavaScript outside `/search/`, and one file — `site.config.ts` — carries roughly 80% of the customisation.

Two things to hold on to before you act on anything below:

- `site.config.ts` is validated by a zod schema with ten cross-field rules. After any edit to it, run `pnpm check:config`; every problem is reported as `site.config.ts › <path>: <message>` and the whole file is checked at once.
- The repository ships its own `AGENTS.md` with twenty hard rules, and a machine-checked test suite behind them. If you are working inside a ZeroDirs project, read that file first — it overrides anything general you infer from this page.

Source: https://zerodirs.com/docs/agents/recipes/add-category/

---

<!-- DO NOT EDIT — generated from zerodirs/zerodirs .agents/skills/ by .github/docs/generate.ts (docs-sync.yml). Edit the source, not this page. -->

`.agents/skills/add-category/SKILL.md` — 80 lines of instruction that ship inside the starter. This page is generated from it, so it says what the skill does without republishing it.

## When an agent picks this up

The skill description, verbatim — this is the text an agent matches your request against:

> Add a category to a ZeroDirs directory site. Edits site.config.ts, picks a lucide icon, seeds at least one listing so the new category page is not empty, and verifies with pnpm check and a full build. Use when asked to add, rename or reorder a category, or when a category page turns up empty.

## What it walks through

1. Steps
   - Add the entry
   - Seed at least one listing
   - Watch out for orphans
   - Verify
1. Removing or renaming a category

## Commands it runs

```sh
pnpm listings:import
pnpm check:config     # slug shape, duplicates, reserved segments, icon name
pnpm check            # types + config
pnpm build            # the real signal
```

## Files it touches

`site.config.ts` · `src/config/schema.ts` · `src/content/listings/` · `src/loaders/normalize.ts` · `src/content/schema.ts`

## Using it

Skills load themselves — you describe the outcome, not the skill. "Add a Compliance category with an icon and seed it" is enough for an agent that can see `.agents/skills/`; Claude Code reads `.claude/skills/`, which `pnpm skills:sync` mirrors from `.agents/` on every install. See [Working with an agent](https://zerodirs.com/docs/agents/overview/).