jerseycheese
- 21 skills
- 0 followers
- 1 week ago last updated
- ▌ Narraitor Storybook App Parity · jerseycheese bundleIsolation-vs-integration parity reasoning and the component promotion ladder for Narraitor. Use when something "works in Storybook" but not the app (or vice versa), before calling any component done/integrated, when writing stories with withStores or MSW, or when deciding whether Storybook-green is enough evidence. Storybook is the canon DESIGN surface, never proof of app behavior.
- ▌ Narraitor AI Quality Discipline · jerseycheese bundleThe 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 generation is a signal not evidence, and how to turn a hunch into a checked improvement.
- ▌ Narraitor Architecture Contract · jerseycheese bundleThe 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 logic between server and client, or whenever deps:validate / skott / boundary questions come up.
- ▌ Narraitor Diagnostics And Tooling · jerseycheese bundleHow 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", "what computed style applies", "where is the playwright report" - or when a claim needs an artifact.
- ▌ Narraitor Pattern Alignment Skill · jerseycheese bundleAutomatically 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 boundaries, accessibility. Do NOT wait for user to ask; run as a post-edit check before committing.
- ▌ Narraitor Hardest Problem Campaign · jerseycheese bundleExecutable 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", "validate the play loop end to end", "is this shippable", or to run/resume the release campaign.
- ▌ Narraitor Prompt Template Governance · jerseycheese bundleThe 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 asked "where do prompts live" / "can I just tweak the prompt".
- ▌ Narraitor Parallel Lane Orchestration · jerseycheeseRun 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 lanes", or when planning a multi-issue push that should run concurrently rather than serially. Covers batch selection, collision avoidance against work already in motion, model tiering, and the lane failure modes that have actually bitten this repo.
- ▌ Narraitor Feature Experiment Lifecycle · jerseycheese bundleHow 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 narrative", or when deciding whether in-flight work ships, holds, or gets retired.
- ▌ Style Port · jerseycheesePort inline styles from a reference/demo component to production CSS in the Narraitor design system. Rigid 6-phase process that diffs inline styles against production stylesheets, ports gaps using design tokens, and removes inline styles from production components. Use when porting design system styles from any reference source to the app.
- ▌ Narraitor Architecture · jerseycheese bundleAutomatically 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 integration conventions. Do NOT wait for user to ask — invoke before writing new structural code.
- ▌ Narraitor Playtest Loop · jerseycheese bundleDrive 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 needs a before-and-after read on story quality. This is the taste instrument; narraitor-qa-walkthrough is the release defect gate and narraitor-ai-quality-discipline is the evidence bar both of them answer to.
- ▌ Narraitor Build Test Env · jerseycheese bundleRecreate, 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 Playwright can't run locally, when jest runs out of memory, or before claiming any gate is green.
- ▌ Narraitor Change Control · jerseycheese bundleHow 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 when deciding what evidence a PR needs. This is the anti-overclaiming gate for every other skill.
- ▌ Narraitor Docs And Writing · jerseycheese bundleMaintaining 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 contradicts the code, when recording a correction to an earlier wrong claim, or when drafting PR/issue text. (Deciding whether the claim is true -> narraitor-change-control; which docs to trust -> narraitor-repo-orientation.)
- ▌ Narraitor Domain Reference · jerseycheese bundleApplied 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 relate, what a store field means, why hydration/persistence behaves oddly, or how AI-provider quirks shape the code.
- ▌ Narraitor Product Frontier · jerseycheese bundleNarraitor'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 to check whether a big idea already has an epic, an asset, or a failed attempt.
- ▌ Narraitor Repo Orientation · jerseycheese bundleFast orientation map for a zero-context session in the Narraitor repo. Use FIRST when starting work here, when asked "where does X live", "how is this repo organized", "what's the stack", "where do I look for the stores / AI code / themes / tests", or to check WHICH docs are trustworthy before acting on one. (Asking WHY something is built this way -> narraitor-failure-archaeology; fixing or correcting a stale doc -> narraitor-docs-and-writing; "where do prompts live" -> narraitor-prompt-template-governance.)
- ▌ Narraitor Validation And QA · jerseycheese bundleWhat counts as evidence in Narraitor - the test tiers (unit, Storybook, visual regression, e2e, manual QA walkthrough), what each can and cannot prove, acceptance thresholds, how to add tests, and how to read failures. Use when deciding which tests a change needs, interpreting a red or suspiciously green run, planning QA before a release, or when someone cites "tests pass" as proof.
- ▌ Narraitor Debugging Playbook · jerseycheese bundleSymptom-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 you're about to try a second fix for the same symptom.
- ▌ Narraitor Failure Archaeology · jerseycheese bundleNarraitor'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 claims HISTORY the tree contradicts ("was X removed?", "did we already try Y?"), or when asked "why is it built this way". Do not re-fight settled battles. (Which docs to trust at all -> narraitor-repo-orientation; writing the correction -> narraitor-docs-and-writing.)