# Packs

Intents only some kinds of app need, added on top of the starter with prongs add <pack>. Each pack's intents still belong to the usual domains, so they are listed there too, marked with their pack.

## Packs

- [SaaS pack](https://www.prongs.dev/docs/intents/packs/saas.md) (8 intents): Apps people work in: records in tables, settings pages, plans and billing. Add it with `npx prongs add saas`.
- [Editorial pack](https://www.prongs.dev/docs/intents/packs/editorial.md) (9 intents): Things people read: articles, posts, docs, news and their previews. Add it with `npx prongs add editorial`.
- [Marketing pack](https://www.prongs.dev/docs/intents/packs/marketing.md) (3 intents): Landing and product pages: the headline and the links that lead on. Add it with `npx prongs add marketing`.
- [Dashboard pack](https://www.prongs.dev/docs/intents/packs/dashboard.md) (6 intents): Numbers to watch: amounts in a range, charts, devices and their status. Add it with `npx prongs add dashboard`.
- [Media pack](https://www.prongs.dev/docs/intents/packs/media.md) (8 intents): Photos, video and music: galleries, players and full-size views. Add it with `npx prongs add media`.

## Adding packs

Name one or more after `prongs add`. Their intents are copied into your registry, where they are yours like the starter, and `PRONGS.md` is regenerated. Running it again skips what is already there.

```bash
npx prongs add saas editorial
```

When to add one, and how packs fit with the starter: [Starter and packs](https://www.prongs.dev/docs/packs.md).