bd init: initialize beads issue tracking

Author: angusbezzina

.agents/skills/beads/SKILL.md

@@ -0,0 +1,80 @@
+---
+name: beads
+description: Use when working in a repository that uses bd or Beads for durable project task tracking, issue dependencies, blocker management, multi-session handoff, or shared work memory. Trigger when the user asks to find ready work, claim or close tasks, create follow-up work, inspect blockers, recover project context, or choose between local planning and persistent project tracking.
+---
+
+# Beads
+
+Use Beads as the shared project task system. Local plans, scratch files, and personal memories are useful, but they are not the durable source of truth for project work.
+
+## First Step
+
+Run:
+
+```bash
+bd prime
+```
+
+If that prints nothing, check whether the repository has an active Beads workspace:
+
+```bash
+bd where
+```
+
+## Preferred Route
+
+Use the `bd` CLI when shell access is available. It is the most compact and direct Beads interface.
+
+## Core CLI Workflow
+
+1. Find work:
+
+```bash
+bd ready
+bd list --status=open
+bd list --status=in_progress
+```
+
+2. Inspect before editing:
+
+```bash
+bd show <id>
+```
+
+3. Claim work atomically:
+
+```bash
+bd update <id> --claim
+```
+
+4. Create durable follow-up work when implementation reveals new tasks:
+
+```bash
+bd create "Short title" --description="Why this exists and what needs to be done" --type=task --priority=2
+```
+
+5. Close completed work:
+
+```bash
+bd close <id> --reason="Completed"
+```
+
+## What Belongs In Beads
+
+Use Beads for:
+
+- shared project tasks
+- blockers and dependencies
+- discovered follow-up work
+- work that must survive thread reset, compaction, or handoff
+- status that another person or agent should be able to resume
+
+Use agent-local planning tools only for the current turn's execution checklist. Do not treat them as shared project state.
+
+## Rules
+
+- Do not create markdown TODO files as the source of truth when Beads is available.
+- Do not use `bd edit`; it opens an interactive editor. Use `bd update` flags instead.
+- Prefer `--json` when parsing `bd` output programmatically.
+- If hooks are installed, `bd prime` may already be injected. Run it manually when context is missing.
+- Do not auto-close or mutate tasks unless the work is actually complete.

.agents/skills/beads/agents/openai.yaml

@@ -0,0 +1,4 @@
+interface:
+  display_name: "Beads"
+  short_description: "Project task tracking with bd"
+  default_prompt: "Use $beads to inspect ready work and manage durable project tasks."

.agents/skills/hallmark/SKILL.md

@@ -0,0 +1,95 @@
+# Colour
+
+Most AI-generated UI fails on colour. It picks blue. It uses pure black. It draws a gradient from purple to cyan. It leaves accents on 30% of the page. Fix all of this.
+
+## Principles
+
+- **OKLCH only.** Perceptually uniform; predictable lightness; consistent hue across tints. `hsl()` and `rgb()` lie about brightness.
+- **One accent.** Maximum two. Everything else is neutral. The accent should occupy **3% or less** of any given viewport.
+- **No pure extremes.** No `#000`, no `#fff`. Always tint with a trace of chroma toward the palette's anchor hue.
+- **Tint the greys.** If your anchor hue is orange, your neutrals lean warm. If it's blue, they lean cool. A page with a warm accent and cool grey body copy looks wrong and most people can't name why.
+
+## Palette construction
+
+A complete Hallmark palette has four layers.
+
+1. **Paper** — the base surface. `oklch(96–98% 0.005–0.015 <anchor hue>)` for light mode, `oklch(12–16% 0.008–0.015 <anchor hue>)` for dark.
+2. **Ink** — the primary text. `oklch(16–22% 0.005–0.015 <anchor hue>)` for light mode, `oklch(92–96% 0.005–0.01 <anchor hue>)` for dark.
+3. **Neutrals** — 5 to 9 steps between Paper and Ink, each with the anchor's chroma tint at low values (0.005–0.015).
+4. **Accent** — one saturated colour with meaningful chroma (0.12–0.22). Used for links, active states, highlights, focus rings. Never as a background fill that covers more than a few percent of the surface.
+
+Example (warm-oat anchor, hue 80):
+
+```css
+:root {
+  --color-paper:    oklch(96%  0.012 80);
+  --color-paper-2:  oklch(93%  0.014 80);
+  --color-rule:     oklch(82%  0.010 80);
+  --color-neutral:  oklch(56%  0.008 80);
+  --color-muted:    oklch(40%  0.008 70);
+  --color-ink:      oklch(18%  0.010 60);
+  --color-accent:   #FC4C02;                   /* signal orange */
+  --color-focus:    oklch(55%  0.19  55);
+}
+```
+
+Example (midnight anchor, hue 40):
+
+```css
+:root {
+  --color-paper:    oklch(14%  0.008 40);
+  --color-paper-2:  oklch(18%  0.010 40);
+  --color-rule:     oklch(30%  0.008 40);
+  --color-neutral:  oklch(58%  0.008 40);
+  --color-muted:    oklch(72%  0.006 40);
+  --color-ink:      oklch(94%  0.006 80);
+  --color-accent:   #FC4C02;
+  --color-focus:    oklch(70%  0.19  55);
+}
+```
+
+## Contrast
+
+Use the APCA contrast check when you can; otherwise WCAG 2.1 ratios.
+
+| Content | Minimum | Target |
+| --- | --- | --- |
+| Body text | 4.5:1 | 7:1 |
+| Large text (≥ 18.66px bold or 24px) | 3:1 | 4.5:1 |
+| UI component boundaries | 3:1 | 4.5:1 |
+| Placeholder / helper text | 4.5:1 | 4.5:1 |
+
+Verify with the browser devtools vision-deficiency emulator before shipping.
+
+## Dark mode recipe
+
+- Paper: lightness 12–18% (not `#000`).
+- Ink: lightness 92–96% (not `#fff`).
+- Body font-weight: reduce by 50 units (400 → 350) to compensate for the optical weight of light text on dark.
+- Accent: reduce chroma by 0.02–0.04; increase lightness by 5–10%.
+- Elevation: higher surfaces are *lighter*, not darker. Add ~3% lightness per level.
+- Never switch the hue between modes. Keep the anchor. Only lightness and chroma move.
+
+## Bans
+
+- **Pure `#000000`** anywhere. Use `oklch(16% 0.01 <hue>)` or similar.
+- **Pure `#ffffff`** as a base surface. Use a tinted paper.
+- **Flat grey** (`oklch(L 0 H)` with zero chroma). Add at least 0.005.
+- **Purple-to-cyan gradients, purple-to-blue gradients, orange-to-pink gradients.** Every LLM picks these. Don't.
+- **Accent as background fill** covering more than ~5% of any view.
+- **Grey text on coloured background.** Always reads washed out.
+- **Red–green pairing as the only signal.** Add an icon or pattern.
+- **Alpha transparency as the definition of a colour.** If it's a named token, it's opaque. Transparency is a *modifier* for overlays and shadows, not a palette.
+- **Three-colour gradients.** Two-stop gradients only. The third stop is vanity.
+
+## Use of the accent
+
+The accent is a highlighter, not a colour block. Reach for it to:
+
+- Mark an active nav item.
+- Draw a focus ring.
+- Underline a link on hover.
+- Indicate a primary CTA's border or text.
+- Place a small square beside a heading as a visual anchor.
+
+Do not fill giant buttons with it. Do not set whole sections on it. Do not use it for decorative gradients. If you feel the urge to use more, that's the slop defaulting. Use less.