Slice · AI prompt
Config-driven marketing navbar + footer — the chrome every template hand-rolled, now one slice.
# Install `marketing-chrome` — Marketing Chrome — Header + Footer
> Config-driven marketing navbar + footer — the chrome every template hand-rolled, now one slice.
📚 Knowledge base : https://resource.rahmanef.com/llms.txt
📦 Slice detail : https://resource.rahmanef.com/slices/marketing-chrome
🧠 JSON catalog : https://resource.rahmanef.com/api/knowledge?slice=marketing-chrome
🔗 Source : https://github.com/rahmanef63/resource-site/tree/main/frontend/slices/marketing-chrome
## 1. Install
```bash
npx rahman-resources add marketing-chrome
# alias: npx rr add marketing-chrome
```
The CLI copies `frontend/slices/marketing-chrome/` into your project + augments `.env.example` + installs npm deps automatically. Run it from your project root.
## 2. What it ships
- shadcn primitives: `button`, `sheet`, `separator`
## 3. Wire it up
Run `npx rr add marketing-chrome`. Feed MarketingHeader { brand, nav[], cta, layout } and MarketingFooter { brand, columns[], social[], legal[], layout }. Header layout split is the default marketing pattern; footer columns for full sites, slim for single-pagers.
## Rules of engagement
- shadcn-only UI primitives. No raw `<button>` / `<dialog>` / native date or file inputs.
- 200-line hard cap per source file (extract neighbours when over).
- All Convex queries hit an index (`.withIndex(...)`); never bare `.collect()`.
- Public mutations/queries declare `args:` validators + authz.
- Full ruleset: https://resource.rahmanef.com/best-practice
The agent will fetch /llms.txt for the full ruleset and use /api/knowledge for the JSON catalog.