# Design guidelines library

Nib ships curated **task guides** and **visual styles**. Load them through `get_guidelines` in this order:

1. `get_guidelines({})` — list guides and styles.
2. `get_guidelines({ category, name })` — param schema for one entry.
3. `get_guidelines({ category, name, params })` — full markdown for the session.

The guidelines API has three steps:

```json
{}
```

```json
{ "category": "guide", "name": "graphics" }
```

```json
{
  "category": "guide",
  "name": "graphics",
  "params": { "preset": "story-9-16" }
}
```

Task guides: `graphics`, `mobile-app`, and `landing-page`.

Styles: `quiet-linen`, `obsidian-brief`, `broadsheet-noon`, `block-signal`, `cotton-arcade`, `terminal-ledger`, `chamber-ivory`, and `poster-rally`.

## Task guides

- **graphics** — Single-frame and multi-frame compositions for paid social, stories, thumbnails, and Open Graph cards.
- **mobile-app** — Screen mockups with safe areas, tab bars, and component spacing aligned to iOS logical points.
- **landing-page** — Wide artboards and section frames for hero, proof, pricing, and CTA bands — judged as rendered pixels.

## Styles

- **quiet-linen** — Warm minimal — oat grounds, soft ink, one clay accent; editorial calm for lifestyle and wellness.
- **obsidian-brief** — Dark premium — near-black layers, cool silver type, single electric accent for fintech and pro tools.
- **broadsheet-noon** — Editorial serif — newsroom hierarchy, serif display + humanist body, restrained red accent.
- **block-signal** — Brutalist bold — high contrast, slab headlines, hard edges, poster-like blocks for campaigns.
- **cotton-arcade** — Pastel friendly — candy washes on white, rounded UI, approachable SaaS and consumer apps.
- **terminal-ledger** — Technical mono — graphite surfaces, mono captions, green/teal signal for devtools and data.
- **chamber-ivory** — Luxury restrained — ivory ground, deep espresso ink, gold accent hairlines; hospitality and premium retail.
- **poster-rally** — Vibrant poster — saturated fields, display sans/shout type, event and launch creative.

## Recommended loop

## Recommended design loop

1. Call `get_state` before editing. Read the active file, current selection, variables, tree, and schema summary.
2. Call `get_guidelines()` to list the design guides and styles.
3. Load one task guide and one suitable style with their parameters.
4. Use `get_nodes` when you need full details for specific nodes.
5. Make one coherent atomic change with `batch_edit`.
6. Call `screenshot` and judge the rendered pixels—not only the JSON.
7. Use `snapshot_layout` to catch clipping, overlap, or incorrect sizing.
8. Iterate until the composition is clean, then call `export`.

Do not guess node IDs or edit the `.nibs` file directly while Nib is open.