@hanzlaa/rcode 2.8.0 → 3.2.0

package/rihal/skills/core/rihal-rebrand/SKILL.md

@@ -0,0 +1,133 @@
+---
+name: rihal-rebrand
+description: Stack-wide rebranding migration — refs, assets, copy, env vars, docs, redirects, package names. Use when a project's brand changes mid-flight and the rename has to ripple through dozens of files without breaking anything. Specifically encodes the Rihal "had to do complete rebranding" pain — the rename touched 100+ files and broke 3 deploys before we got it right.
+triggers:
+  - "rebrand"
+  - "stack-wide rename"
+  - "product rename"
+  - "rename project"
+  - "brand migration"
+  - "logo refresh"
+  - "domain change"
+  - "company name change"
+user-invocable: true
+---
+
+## Overview
+
+A rebrand is N renames at once: package name, npm scope, repo URL, environment variables, asset paths, copy strings, redirects, social handles, contracts. Each one looks small. Together they break things. This skill enforces a checklist + a decomposition (one category per commit) so the rename ships incrementally without a "Friday at 5pm" big-bang deploy.
+
+## The 9 surfaces of a rebrand
+
+For each: scope it before touching code, identify cross-references, decompose into commits.
+
+### 1. Package + repo identity
+
+- [ ] `package.json` `name`, `description`, `repository.url`, `homepage`, `bugs.url`
+- [ ] `README.md` heading, badges, CDN URLs, npm install commands
+- [ ] Repository name on GitHub (and any forks / deploy keys / webhooks)
+- [ ] npm scope rename (this is one-way; coordinate carefully)
+
+### 2. Environment variables + secrets
+
+- [ ] Old prefix `OLDBRAND_*` → `NEWBRAND_*`
+- [ ] Update `.env.example`, all CI environment definitions, K8s ConfigMaps and Secrets
+- [ ] Compatibility window: read both names for 1 release, then drop the old
+
+### 3. Assets
+
+- [ ] Logos, favicons, OG images, brand-coloured graphics
+- [ ] Email templates (transactional + marketing)
+- [ ] PDF templates, certificate templates, invoice templates
+
+### 4. Copy strings
+
+- [ ] User-facing UI copy
+- [ ] Email subject lines + bodies
+- [ ] Push notification text
+- [ ] Error messages
+- [ ] Marketing site / landing page
+
+### 5. URLs + redirects
+
+- [ ] Old domain → new domain HTTP 301s
+- [ ] Email-link tracking domains
+- [ ] Deep-link schemes (`oldbrand://` → `newbrand://`) with backwards-compat for installed apps
+- [ ] CDN paths + old-image redirects
+
+### 6. Social + external
+
+- [ ] Twitter / LinkedIn / Instagram handles (one-way; rename last after rest is verified)
+- [ ] App Store / Play Store listings + reviews moved
+- [ ] Crashlytics / Sentry project name
+- [ ] Stripe / payment processor business name
+
+### 7. Documentation + onboarding
+
+- [ ] README, CONTRIBUTING, all `docs/`
+- [ ] Internal wiki / Notion
+- [ ] Customer-facing help docs
+
+### 8. Code-internal references
+
+- [ ] CSS variable names (`--oldbrand-blue` → `--newbrand-blue`)
+- [ ] TS / JS namespace exports
+- [ ] Test fixture data containing the old name
+
+### 9. Legal + contracts
+
+- [ ] Customer contracts referencing the old name
+- [ ] Privacy policy, terms of service, DPA
+- [ ] Trademark registrations + domain whois
+
+## Workflow
+
+1. **Inventory.** Grep for the old brand name across the entire monorepo (case-insensitive, all variants — `OldBrand`, `oldbrand`, `old-brand`, `OLD_BRAND`).
+2. **Categorise** each hit into one of the 9 surfaces.
+3. **Decompose into commits** — one surface per commit minimum. Surfaces 1, 2, 4, 5, 7, 8 can be one commit each; surface 6 (social) is the LAST commit because it's hardest to revert.
+4. **Compatibility window.** For env vars, deep links, public APIs: read both names for 1 release, drop the old in the next.
+5. **Verify after each commit:** the build passes, the tests pass, no broken links to the old name.
+6. **Communicate.** Customer-facing rename is an event — schedule it, announce it, follow with a status post 24h later confirming nothing's broken.
+
+## Output Format
+
+```
+Rebrand inventory — <old> → <new>
+Total occurrences: <count> across <files>
+
+By surface:
+  1. Package + repo:    <count>
+  2. Env vars:          <count>
+  3. Assets:            <count>
+  ...
+
+Commit plan:
+  1. refactor(meta): rename package + repo references
+  2. refactor(env): migrate OLDBRAND_* env vars with compat fallback
+  3. refactor(assets): swap logos, favicons, OG images
+  ...
+
+Compatibility windows:
+  - env vars: 1 release
+  - public API: 1 minor version with deprecation warning
+  - deep links: 6 months for installed apps
+
+Communication plan:
+  - Internal heads-up: <date>
+  - Customer email: <date>
+  - Social handle change: <last commit ships>
+  - 24h post-launch status: <date>
+```
+
+## Examples
+
+**Happy path** — `OldBrand → NewBrand` rename. Inventory: 312 occurrences across 87 files in 9 surfaces. 9 commits over 4 days, compat window of 1 release for env vars + public API. Social handles renamed last. Zero customer reports of broken links.
+
+**Edge case — domain change with email** — Old domain hosts customer email aliases. Old domain MUST keep MX records during compatibility window OR customers lose email. Add domain-MX to the checklist before touching DNS.
+
+**Negative — rename in one commit** — Refuse. A 312-line diff across 87 files cannot be reviewed meaningfully and cannot be reverted partially. Decompose into 9 commits minimum.
+
+## Memory Bank Hooks
+
+- **Reads:** `.rihal/memory/people/stakeholders.md` (who needs to approve external changes)
+- **Writes:** `.rihal/memory/change-records/YYYYMMDD-NNN.md` per commit; `.rihal/memory/project/decisions.md` for the rebrand kickoff

package/rihal/skills/core/rihal-review-adversarial-general/SKILL.md

@@ -65,3 +65,8 @@ Markdown bullet list of findings, each describing a specific problem, gap, or ri
 
 - HALT if zero findings — this is suspicious, re-analyze or ask for guidance
 - HALT if content is empty or unreadable
+
+## Memory Bank Hooks
+
+- **Reads:** the content under review (diff, spec, story, doc)
+- **Writes:** nothing — produces findings only. Findings can be persisted by the caller via `rcode-memory-update` if they shape downstream work.

package/rihal/skills/core/rihal-review-edge-case-hunter/SKILL.md

@@ -97,3 +97,8 @@ No extra text, no explanations, no markdown wrapping. An empty array `[]` is val
 ### Negative boundary
 **User:** "critically review this spec"
 **Result:** Not edge-case hunting → route to `rihal-review-adversarial-general`
+
+## Memory Bank Hooks
+
+- **Reads:** the content under review (diff, full file, or function)
+- **Writes:** nothing — produces an unhandled-edges report only

package/rihal/skills/core/rihal-shard-doc/SKILL.md

@@ -135,3 +135,8 @@ Present user with options for the original document:
 ## HALT CONDITIONS
 
 - HALT if npx command fails or produces no output files
+
+## Memory Bank Hooks
+
+- **Reads:** the source document being sharded
+- **Writes:** the sharded output files only; does NOT modify `.rihal/memory/`. If the sharded doc is a Memory Bank file, use `rcode-memory-distill` instead.

package/rihal/skills/core/rihal-theme-system/SKILL.md

@@ -0,0 +1,113 @@
+---
+name: rihal-theme-system
+description: Audit a frontend's design tokens BEFORE launch. Catches inconsistent colours, scattered hex values, hardcoded spacing, font drift, and missing dark/RTL mode support. Specifically encodes Rihal's "had to do complete rebranding mid-project" pain — themes accumulated drift until a full pass was the only fix. Pairs with rihal-rebrand if a rebrand becomes unavoidable.
+triggers:
+  - "theme audit"
+  - "design tokens"
+  - "scattered colours"
+  - "hardcoded hex"
+  - "design system audit"
+  - "before launch design check"
+  - "consistent theme"
+  - "css variable audit"
+user-invocable: true
+---
+
+## Overview
+
+Theme drift is silent until launch — then someone notices that "the brand blue" is 4 different blues across pages, and now you're rebranding under deadline. This skill catches drift early: every colour, font, spacing value, and animation duration must come from a token, not a literal. A 30-minute audit before launch is cheaper than a 3-week rebrand after.
+
+## The 7 token categories
+
+For each, the audit checks: where do values live, are they used consistently, is dark mode + RTL supported.
+
+### 1. Colour
+
+- [ ] All colours defined as CSS custom properties in one location (`globals.css` or `tokens.css`).
+- [ ] No raw hex / rgb in component files (grep for `#[0-9a-f]{3,8}`).
+- [ ] Each colour has a semantic name (`--color-primary`) AND a literal name (`--rihal-blue`).
+- [ ] Dark mode tokens defined alongside light, not retrofitted.
+
+### 2. Typography
+
+- [ ] Font families loaded once (via `next/font` or `<link>` in head).
+- [ ] Font sizes use a scale (`--text-xs`, `--text-sm`, etc.), not arbitrary px values.
+- [ ] Arabic font has explicit line-height bump (Arabic glyphs are denser).
+- [ ] Fallback stack defined for every font family.
+
+### 3. Spacing
+
+- [ ] Spacing scale defined (`--space-1` through `--space-12`).
+- [ ] No raw px values for margin/padding in components.
+- [ ] Logical properties used (`padding-inline-start`, not `padding-left`) for RTL.
+
+### 4. Radii & shadows
+
+- [ ] Radii scale (`--radius-sm`, `--radius-lg`).
+- [ ] Shadow tokens, not inline `box-shadow: 0 4px 6px ...` strings.
+
+### 5. Motion
+
+- [ ] Duration scale (`--duration-fast: 150ms`, `--duration-slow: 400ms`).
+- [ ] Easing tokens (`--ease-out`, `--ease-spring`).
+- [ ] Reduced-motion media query honoured.
+
+### 6. Breakpoints
+
+- [ ] Breakpoint tokens defined and used everywhere.
+- [ ] Mobile (390px), tablet (768px), desktop (1440px) all tested.
+
+### 7. RTL
+
+- [ ] `dir="rtl"` toggle exists and works at the root.
+- [ ] Logical properties used throughout (CSS Logical Properties Level 1).
+- [ ] Icons that imply direction (arrows, slashes) flipped via `transform: scaleX(-1)` or RTL-specific assets.
+- [ ] Mixed-content (Arabic + English in same line) tested.
+
+## Workflow
+
+1. **Inventory token locations.** Should be one file per category, plus a root index.
+2. **Grep for literals.** Every match in a component file is a finding.
+3. **Diff against design.** If Layla / Zahra / the brand guide has tokens that aren't in code, add them. If code has tokens not in the brand guide, flag them.
+4. **Test dark + RTL** per page if they're shipping.
+5. **Generate the fix list** ordered by frequency (a hardcoded `#1e3a8a` in 12 files is more urgent than one in 1).
+
+## Output Format
+
+```
+Theme audit — <date>
+Pages reviewed: <count>
+
+Token coverage:
+  Colour:        <X%>  ✗ <count> raw hex literals
+  Typography:    <X%>  ⚠ <findings>
+  Spacing:       <X%>
+  Radii/shadows: <X%>
+  Motion:        <X%>
+  Breakpoints:   <X%>
+  RTL:           ✓/✗
+
+Top offenders (by file):
+  src/components/Hero.tsx — 8 raw hex values
+  src/app/page.tsx — 4 hardcoded font sizes
+
+Fix order (by impact):
+  1. Replace #1e3a8a → var(--rihal-blue) — 12 occurrences across 8 files
+  2. ...
+
+Memory Bank update:
+  → .rihal/memory/project/decisions.md (token system canonicalised)
+```
+
+## Examples
+
+**Happy path — pre-launch audit** — Page count: 12. Coverage: colour 60%, typography 80%, spacing 50%, RTL 0%. Plan: extract tokens (1 day), migrate components (2 days), add RTL toggle (1 day). Catch the rebrand BEFORE launch.
+
+**Edge case — design partial alignment** — Brand guide has 3 blues, code has 7. Some are intentional shades; some are drift. Walk each with Zahra (`rihal-agent-zahra`) to canonicalise.
+
+**Negative — "we'll add dark mode later"** — Refuse silent commitment. Either ship dark mode now or document the decision in `decisions.md` so it doesn't become a "why don't we have dark mode?" argument in 3 months.
+
+## Memory Bank Hooks
+
+- **Reads:** `.rihal/memory/project/stack.md` (frontend layer), brand tokens from Zahra if available
+- **Writes:** `.rihal/memory/project/decisions.md` (canonical token system); `.rihal/memory/change-records/YYYYMMDD-NNN.md` (the audit itself)

package/rihal/team.yaml

@@ -85,20 +85,6 @@ agents:
       - backlog
     description: Scope, requirements, PRD writing, user stories, and backlog curation.
 
-  - id: rihal-tech-writer
-    name: Tech Writer
-    file_path: rihal/agents/rihal-tech-writer.md
-    role: Technical Documentation Specialist
-    authority_level: operational
-    domain_keywords:
-      - documentation
-      - readme
-      - api-docs
-      - changelog
-      - migration-guide
-      - inline-comments
-    description: Generates and updates README, API docs, changelogs, migration guides, and inline code comments.
-
   - id: rihal-yousef
     name: Yousef (يوسف)
     file_path: rihal/agents/rihal-yousef.md
@@ -238,7 +224,9 @@ agents:
       - pitch-deck
       - changelog
       - blog-post
-    description: Documentation, README files, API docs, architecture diagrams, changelogs, pitch decks, and blog posts.
+      - migration-guide
+      - inline-comments
+    description: Documentation, README files, API docs, architecture diagrams, changelogs, migration guides, inline code comments, pitch decks, and blog posts.
 
   - id: rihal-ahmed
     name: Ahmed Al Hassani (أحمد الحسني)
@@ -365,13 +353,6 @@ tactical_agents:
     authority_level: research
     description: Advisor-level deep research for gray-area decisions
 
-  - id: rihal-architect
-    name: Architect
-    file_path: rihal/agents/rihal-architect.md
-    role: Architect
-    authority_level: technical
-    description: Enterprise architecture and system design reviews
-
   - id: rihal-assumptions-analyzer
     name: Assumptions Analyzer
     file_path: rihal/agents/rihal-assumptions-analyzer.md

package/rihal/templates/memory/INDEX.md

@@ -0,0 +1,46 @@
+# Memory Bank — `{{PROJECT_NAME}}`
+
+> The Memory Bank is your project's persistent brain. AI agents read from here on every session. You write to it as work happens. Survives session resets, team changes, and AI memory limits.
+
+**Last updated:** {{INIT_DATE}}
+
+---
+
+## Directory map
+
+| Path | Purpose |
+|---|---|
+| [`project/stack.md`](project/stack.md) | Languages, frameworks, services in use |
+| [`project/decisions.md`](project/decisions.md) | Append-only architectural decision log |
+| [`project/glossary.md`](project/glossary.md) | Domain terms, internal names, acronyms |
+| [`people/stakeholders.md`](people/stakeholders.md) | External contacts, decision authority, comms |
+| [`people/team.md`](people/team.md) | Internal team, ownership, availability |
+| [`milestones/current.md`](milestones/current.md) | Active milestone — goal, phase, blockers |
+| [`milestones/archive/`](milestones/archive/) | Completed milestones, one file per |
+| [`incidents/known-issues.md`](incidents/known-issues.md) | Active bugs and workarounds |
+| [`incidents/post-mortems/`](incidents/post-mortems/) | Resolved incidents — root cause, fix, lessons |
+| [`change-records/`](change-records/) | Change records — `YYYYMMDD-NNN.md` format |
+| [`distillates/`](distillates/) | Generated, lossless compression for fast LLM loading |
+
+---
+
+## Token budget guide
+
+- **`INDEX.md` only** (~500 tokens) — quick orientation
+- **`INDEX.md` + `distillates/project.distillate.md`** (~5K tokens) — standard session start
+- **Full `project/` directory** (~10–15K tokens) — deep planning
+- **Full Memory Bank** (~30–50K tokens) — major refactor or onboarding
+
+## Update cadence
+
+- **`project/decisions.md`** — append every architectural choice as it's made
+- **`milestones/current.md`** — update on milestone phase transitions
+- **`incidents/known-issues.md`** — add when a workaround ships, remove when a real fix lands
+- **`distillates/`** — regenerate via `/rcode:memory-distill` when source files change
+- **Whole bank** — audit via `/rcode:memory-audit` at every milestone close
+
+## Constraints
+
+- No secrets, tokens, or PII
+- This directory is checked into git
+- Distillates are generated, not hand-edited

package/rihal/templates/memory/change-records/.gitkeep

@@ -0,0 +1,4 @@
+# Change records — production / staging changes that need an audit trail.
+# Filename: `YYYYMMDD-NNN.md` (e.g. `20260426-001.md`).
+# Each change record contains: ID, date, requester, owner, category, type,
+# description, risk, deployment method, approval, rollback plan, verification.

package/rihal/templates/memory/distillates/project.distillate.md

@@ -0,0 +1,11 @@
+---
+generated: true
+do-not-edit: true
+regenerate-with: /rcode:memory-distill
+---
+
+# Project Distillate — `{{PROJECT_NAME}}`
+
+> Generated, lossless compression of `project/`, `people/`, `milestones/current.md`, and `incidents/known-issues.md`. Optimised for LLM context loading. Hand-edits are overwritten on regenerate.
+
+_(Run `/rcode:memory-distill` to populate.)_

package/rihal/templates/memory/distillates/stack.distillate.md

@@ -0,0 +1,11 @@
+---
+generated: true
+do-not-edit: true
+regenerate-with: /rcode:memory-distill
+---
+
+# Stack Distillate — `{{PROJECT_NAME}}`
+
+> Generated, lossless compression of `project/stack.md` only. Useful when you need stack context but not full project history.
+
+_(Run `/rcode:memory-distill --target stack` to populate.)_

package/rihal/templates/memory/incidents/known-issues.md

@@ -0,0 +1,27 @@
+# Known Issues — `{{PROJECT_NAME}}`
+
+Active bugs and workarounds. Searchable so an agent doesn't waste cycles re-debugging an already-known issue.
+
+> **Add an entry when:** a workaround ships before the real fix, OR a bug is acknowledged but won't be fixed this sprint.
+> **Remove an entry when:** the real fix lands and is verified in production.
+
+---
+
+## Format
+
+```
+### Issue title
+
+- **Symptom:** what users see
+- **Surface:** which area / file / route
+- **Workaround:** what we do today
+- **Real fix planned for:** milestone / phase / "out of scope"
+- **First seen:** YYYY-MM-DD
+- **Tracking:** GitHub issue # / Linear ID
+```
+
+---
+
+## Issues
+
+<!-- Add entries here -->

package/rihal/templates/memory/incidents/post-mortems/.gitkeep

@@ -0,0 +1,3 @@
+# Post-mortems land here, one file per resolved incident.
+# Filename: `YYYYMMDD-<short-slug>.md` (e.g. `20260315-keycloak-ad-sync.md`).
+# Use the rcode-incident-record skill (Phase 6) to generate.

package/rihal/templates/memory/milestones/archive/.gitkeep

@@ -0,0 +1,2 @@
+# Archived milestones land here, one file per completed milestone.
+# Filename: `M<N>-<slug>.md` (e.g. `M1-mvp-launch.md`).

package/rihal/templates/memory/milestones/current.md

@@ -0,0 +1,39 @@
+# Current Milestone — `{{PROJECT_NAME}}`
+
+Active milestone. Goal, phases, current sprint, blockers. The agent reads this before starting any task.
+
+---
+
+## Milestone
+
+**Name:** _(e.g. M1 — MVP launch)_
+**Started:** YYYY-MM-DD
+**Target close:** YYYY-MM-DD
+**Goal:** _(one sentence)_
+
+## Active phase
+
+**Phase:** _(e.g. 04 — Implementation)_
+**Started:** YYYY-MM-DD
+**Acceptance criteria:**
+- [ ] criterion 1
+- [ ] criterion 2
+
+## Active sprint / cycle
+
+**Window:** YYYY-MM-DD → YYYY-MM-DD
+**Focus:** _(one sentence)_
+**Stories:**
+- [ ] story id — title
+- [ ] story id — title
+
+## Blockers
+
+| Blocker | Owner | Status |
+|---|---|---|
+| | | |
+
+## Recent decisions
+
+_(Last 3, link to `project/decisions.md` for full log.)_
+

package/rihal/templates/memory/people/stakeholders.md

@@ -0,0 +1,25 @@
+# Stakeholders — `{{PROJECT_NAME}}`
+
+External contacts with decision authority. Client name, role, comm channel, response cadence, areas they own.
+
+> **This file directly addresses the "client late requirements → delays" pain.** When stakeholders' response cadence and ownership areas are documented, work can be sequenced around real human availability instead of optimistic assumptions.
+
+---
+
+## Format
+
+```
+### Name — Role @ Organisation
+
+- **Owns:** what they decide on
+- **Comm:** preferred channel (Slack / email / WhatsApp)
+- **Response cadence:** typical turnaround (e.g. 24h / weekly sync only)
+- **Time zone:** GMT+X
+- **Notes:** quirks, escalation path, who covers when away
+```
+
+---
+
+## Stakeholders
+
+<!-- Add entries here -->

package/rihal/templates/memory/people/team.md

@@ -0,0 +1,35 @@
+# Team — `{{PROJECT_NAME}}`
+
+Internal team. Who owns which area, who reviews what, who is on holiday this week.
+
+---
+
+## Format
+
+```
+### Name — Role
+
+- **Owns:** modules / areas
+- **Reviews:** code review responsibilities
+- **Pairs with:** typical collaborators
+- **Time zone:** GMT+X
+- **Notes:**
+```
+
+---
+
+## Members
+
+<!-- Add entries here -->
+
+---
+
+## Coverage
+
+| Area | Primary | Backup |
+|---|---|---|
+| Frontend | | |
+| Backend | | |
+| Infra / DevOps | | |
+| QA | | |
+| Design | | |

package/rihal/templates/memory/project/decisions.md

@@ -0,0 +1,32 @@
+# Decision Log — `{{PROJECT_NAME}}`
+
+Append-only. Newest at top. Each entry: date, decision, rationale, alternatives considered, who decided. One paragraph per entry. Heavier decisions get their own ADR file referenced from here.
+
+---
+
+## Format
+
+```
+### YYYY-MM-DD — Short decision title
+
+**Decision:** What we chose.
+**Rationale:** Why this over alternatives.
+**Alternatives considered:** A (rejected because...), B (rejected because...).
+**Who decided:** Person or council.
+**Reversibility:** Easy / hard / one-way door.
+**ADR:** [Optional link to a fuller ADR file]
+```
+
+---
+
+## Entries
+
+<!-- Append new decisions above this line -->
+
+### {{INIT_DATE}} — Memory Bank initialised
+
+**Decision:** Adopt rcode Memory Bank for persistent project context.
+**Rationale:** AI agents lose context between sessions; new teammates need a single place to learn the project's history without archaeology through Slack and PRs.
+**Alternatives considered:** CLAUDE.md only (rejected: no structure, goes stale), wiki (rejected: not in-repo, not version-controlled with code), README sections (rejected: doesn't scale).
+**Who decided:** Project lead.
+**Reversibility:** Easy. Just delete `.rihal/memory/` to remove.

package/rihal/templates/memory/project/glossary.md

@@ -0,0 +1,16 @@
+# Glossary — `{{PROJECT_NAME}}`
+
+Domain terms specific to this project: internal names, acronyms, business concepts. Prevents "what does X mean again?" thrash. Add a term any time someone asks about it twice.
+
+---
+
+## Format
+
+`**Term**` — definition. _(optional: where it lives in code)_
+
+---
+
+## Terms
+
+<!-- Add alphabetically -->
+

package/rihal/templates/memory/project/stack.md

@@ -0,0 +1,46 @@
+# Stack — `{{PROJECT_NAME}}`
+
+Inventory of languages, frameworks, libraries, and services. Refreshed via `/rcode:memory-update` when stack changes.
+
+---
+
+## Runtime
+
+| Layer | Choice | Version | Notes |
+|---|---|---|---|
+| Language | _(e.g. TypeScript / Python / Go)_ | | |
+| Framework | _(e.g. Next.js / FastAPI / NestJS)_ | | |
+| Database | _(e.g. Postgres / Mongo / Supabase)_ | | |
+| Cache | _(e.g. Redis / KV)_ | | |
+| Queue / orchestrator | _(e.g. Temporal / SQS / Cron)_ | | |
+| Auth | _(e.g. Keycloak / Firebase / Clerk)_ | | |
+| Observability | _(e.g. Sentry / Datadog / OpenTelemetry)_ | | |
+
+## Frontend (if applicable)
+
+| Layer | Choice | Version |
+|---|---|---|
+| UI library | _(e.g. React / Vue / Svelte)_ | |
+| Styling | _(e.g. Tailwind / shadcn / CSS Modules)_ | |
+| State | _(e.g. Zustand / Redux / TanStack Query)_ | |
+
+## Infrastructure
+
+| Layer | Choice |
+|---|---|
+| Dev environment | _(e.g. Docker Compose)_ |
+| Production | _(e.g. Vercel / AWS ECS / Helm + K8s)_ |
+| CI/CD | _(e.g. GitHub Actions / GitLab CI / Jenkins)_ |
+| CDN / edge | _(e.g. Vercel / Cloudflare)_ |
+
+## Third-party services
+
+| Service | Purpose | Account / region |
+|---|---|---|
+| | | |
+
+---
+
+## Why these choices
+
+_Brief rationale for non-obvious picks. Link to `decisions.md` entries for the full story._

package/rihal/workflows/audit.md

@@ -4,7 +4,7 @@
 Single entry point for every kind of audit. Asks the user *what* to audit
 and dispatches to the right sub-workflow. Closes #234 — replaces the prior
 state where users had to know about six separate audit/verify commands by
-name (`audit-milestone`, `audit-uat`, `audit-fix`, `karpathy-audit`,
+name (`audit-milestone`, `audit-uat`, `audit-fix`, `code-review --karpathy`,
 `verify-phase`, `verify-work`).
 
 Honours `.rihal/config.yaml`: in `mode: yolo`, the router skips the menu
@@ -21,7 +21,7 @@ If `$ARGUMENTS` contains `--help` or `-h`:
 /rihal:audit phase [<NN>]          # → /rihal:verify-phase
 /rihal:audit milestone [--strict]  # → /rihal:audit-milestone (with synth fallback)
 /rihal:audit uat                   # → /rihal:audit-uat
-/rihal:audit code [--scope=...]    # → /rihal:karpathy-audit
+/rihal:audit code [--scope=...]    # → /rihal:code-review --karpathy
 /rihal:audit fix                   # → /rihal:audit-fix
 /rihal:audit work                  # → /rihal:verify-work
 ```
@@ -138,7 +138,7 @@ Run the target's slash command, forwarding remaining args:
 | phase | `/rihal:verify-phase $REST_ARGS` |
 | milestone | `/rihal:audit-milestone $REST_ARGS` |
 | uat | `/rihal:audit-uat $REST_ARGS` |
-| code | `/rihal:karpathy-audit $REST_ARGS` |
+| code | `/rihal:code-review $REST_ARGS --karpathy` |
 | fix | `/rihal:audit-fix $REST_ARGS` |
 | work | `/rihal:verify-work $REST_ARGS` |