Use this agent when implementing or reviewing UI components, styles, or accessibility features to ensure they align with the project's design token system, WCAG 2 standards, and established code patterns. Examples:\n\n \nContext: User has just created a new React component with custom colors\nuser: "I've created a new…
Use this agent when you need to analyze and prioritize GitHub issues for a React project, particularly when deciding what to work on next. The agent will examine all open issues, analyze their priority based on multiple factors, and provide actionable recommendations with clear justifications. Examples:\n\n \nContext…
Use this agent automatically after a PR is merged to update the related GitHub issue(s). Examples:\n\n \nContext: User just merged PR #45 which implements feature described in issue #23.\nuser: "I just merged PR #45"\nassistant: "I'm going to use the Task tool to launch the pr-merge-issue-updater agent to update issue…
The evidence bar for AI narrative quality in Narraitor. Use when judging whether a prompt or generation change "works", when someone says "the output reads better", "the AI handles it", "works on my world", or when evaluating narrative coherence, choices, endings, or any Gemini-generated behavior. Encodes why one good…
The load-bearing architecture invariants of Narraitor - domain boundaries, Zustand store contracts, the event bus, persistence rules, Next.js 15 server/client boundaries, and what may never be bypassed. Use before changing a store's shape, adding cross-domain imports, touching src/lib/api or src/lib/ai seams, moving…
Automatically invoke when creating new components, stores, API routes, or planning a feature in Narraitor. Triggers on: new file creation under src/, architecture questions, feature design discussions, or any structural decision. Applies domain boundaries, naming conventions, state management patterns, and AI…
Recreate, run, and verify the Narraitor environment - install, dev server, Storybook, the full quality gate, and how to classify failures as environment vs data vs AI-provider vs code. Use when setting up from scratch, when "npm test / build / lint fails", when the dev server won't start or the port is taken, when…
How changes are classified, gated, evidenced, and shipped in Narraitor - and what may never be claimed without proof. Use before declaring anything "done", "fixed", "validated", or "verified", before re-baselining any gate (visual snapshots, dep-cruiser, skott, ds-canon), when correcting an earlier wrong claim, or…
Symptom-to-triage runbook for Narraitor failures - blank narrative, AI route 500/timeouts, hydration mismatch, state not persisting after reload, works-in-Storybook-but-broken-in-app, theming drift, flaky visual specs, mystery tsc errors. Use whenever something is broken and the cause isn't already proven, or when…
How to MEASURE instead of eyeball in Narraitor - curl smokes for the AI/API routes, inspecting persisted Zustand state in IndexedDB, DOM/computed-style checks for layout and theming, visual tooling, and where reports land. Use when you need proof of runtime behavior - "is the route up", "what's actually in the store"…
Maintaining Narraitor's docs of record - status language, marking stale claims, append-only corrections, doc templates, and the project voice for all generated prose (PRs, issues, comments, code comments, user-facing copy, docs). Use when WRITING or FIXING any documentation or prose, when marking/correcting a doc that…
Applied domain knowledge a mid-level engineer lacks for Narraitor - the world/character/narrative/session data model, Zustand store and persistence conventions, Next.js 15 App Router pitfalls, streaming/latency realities of Gemini, and the single-design-system (ds3) theming model. Use when reasoning about how domains…
Narraitor's memory of painful failures, reverts, dead ends, and deliberately settled decisions. Use BEFORE proposing to remove/replace something that looks wrong or overengineered (the event bus, the react-joyride pin, split store files), before re-attempting an idea that may have been tried, when a doc or memory…
How a hunch becomes a shipped, held, or retired change in Narraitor - issue capture, acceptance criteria, experiment flagging for AI-behavior changes, the gate sequence, and ship/hold memos. Use when starting any feature or improvement idea, when someone says "let's try", "quick experiment", "I have an idea for the…
Executable campaign for Narraitor's hardest live problem - closing the v1.0 release gate, whose un-automatable core is validating the live AI play loop (real Gemini, multi-turn, consequences, endings) that every automated suite deliberately gates off. Use when asked to "get v1.0 out", "close the release gate"…
Run a batch of Narraitor issues as parallel worktree lanes, with a Fable orchestrator picking the batch and delegating each issue to a subagent whose model matches the issue's model-power label. Use when asked to "work the top N issues in parallel", "fan out the backlog", "kick off a parallel batch", "orchestrate…
Automatically run after any code change in this repo (components, stores, API routes, CSS, tests, types). Triggers on: new files, refactors, feature additions, or any edit touching src/. Reviews changes for alignment with established project patterns — design tokens, state conventions, error handling, domain…
Drive real multi-turn game sessions in a browser against live Gemini and score whether the story is actually engaging. Use when asking "is this fun to play", "does the narrative hold up over 30 turns", "why does the story get boring", when planning a release playtest, or when a change to prompts or narrative logic…
Narraitor's open frontier problems and how to attack them in THIS repo - long-arc story memory and coherence, consequence tracking, progressive streaming, replayability, and automated prompt evaluation. Use when asked "what's next", "what would make this state of the art", when scoping ambitious AI-narrative work, or…
The governed lifecycle for AI prompt templates in Narraitor - registry, input contract, context-leakage gate, evaluation, regression, cost, and integration gates. Use when adding or editing any prompt template, when tempted to inline a prompt string into a generator or route, when reviewing a prompt change, or when…