goblin-mode

{{ 𝚫𝚫𝚫 }} Rebuild roadmap-system.zip, the distributable snapshot of the roadmap tooling (scripts, HTML template, conventions reference, and every roadmap-touching skill, including this one).

{{ 𝛀𝛀𝛀 }} Create a project roadmap in the rich phase-array format — roadmaps.json as source of truth plus a PHASE task list and prose overview

{{ 𝛀𝛀𝛀 }} Recompute and synchronise roadmap task statuses across roadmaps.json and its projections, with optional codebase reconciliation

{{ 𝛀𝛀𝛀 }} Add a task to a rich-format project roadmap with correct ID, dependency wiring, and graph integrity — ID assignment, status computation, dependency edges in both directions, and no unconnected islands.

Git workflow: branch management, commit conventions, PR patterns, conflict resolution.

{{ 𝛀𝛀𝛀 }} Review a pull request and post it as a GitHub review

{{ 𝛀𝛀𝛀 }} Run a structured interview to discover new features and produce a batch roadmap proposal. Produces a structured proposal for review — nothing is written to the roadmap until the user approves.

"{{ 𝚫𝚫𝚫 }} Suggest the next logical task — grounded in the roadmap's pre-vetted ready-set when one exists, codebase analysis otherwise"

{{ 𝚫𝚫𝚫 }} Generate the HTML roadmap dashboard deterministically via roadmap.py render.

Writing style guide for Jason Warren. Applies whenever writing or editing substantive prose for Jason — drafting sections, reports, documentation, or rewriting passages.

Type-safe API design: Zod validation, Result types, SvelteKit endpoints, middleware patterns.

Polyglot persistence: when to use relational, graph, or document databases; integration patterns.

Systematic debugging methodology — runtime errors, test failures, logic bugs, performance issues, production incidents. Five-step framework, root-cause analysis, browser/Node/Svelte tooling, and common bug patterns.

Pragmatic testing with Vitest: risk-based strategy, Svelte component testing, test-after development.

Neo4j and Cypher: graph schema design, query patterns, performance optimisation, PostgreSQL integration.

OpenTUI terminal UI library reference. Use when working with @opentui/core, terminal UIs, renderables, Yoga layouts, or Zig-native rendering.

Svelte 5 and SvelteKit: runes reactivity, component composition, routing, data loading, form handling.

Use when about to build a non-trivial feature and you want the shape reviewable before the logic. Studs every function in its real file as a runnable walking-skeleton (fake data, real wiring) so names, placement, and contracts are visible before any real logic is written. Lay the skeleton, then checkpoint for review.

{{ ƔƔƔ }} Plan a non-trivial feature by interviewing to resolve unknowns, then studding every function as a runnable walking-skeleton (fake data, real wiring) so names, placement, and contracts can be reviewed before any real logic is written. Stops for review; fill is a separate pass.

{{ 𝛀𝛀𝛀 }} Audit a topic and render an actionable, status-grouped HTML findings artefact.

{{ 𝛀𝛀𝛀 }} Render a visual HTML introduction to this codebase for a newly-joined developer

{{ 𝚫𝚫𝚫 }} Grant a permission rule globally or for the current project

{{ ƔƔƔ }} Create an Architecture Decision Record (ADR) for a significant technical decision

{{ ƔƔƔ }} Update an existing documentation file to reflect recent code changes

{{ ƔƔƔ }} Create or update a README — project root or any directory

{{ 𝚫𝚫𝚫 }} Create a status report that knows what you've done since the last one

{{ ƔƔƔ }} Check the current branch name against convention (type/short-description) and rename it if it drifted — e.g. work started on a misnamed or default branch.

{{ 𝛀𝛀𝛀 }} Assess branch readiness for PR submission

{{ 𝚫𝚫𝚫 }} Split uncommitted changes into granular commits.

{{ 𝚫𝚫𝚫 }} Generate a commit message. If nothing staged, stage all changes.

{{ 𝚫𝚫𝚫 }} Integrate a target branch into the current one by merge, rebase or squash

{{ ƔƔƔ }} Summarise what the user can now see or do that they couldn't before this unit of work

{{ ƔƔƔ }} Create a pull request to main — wordy or shiny (with screenshots), ready-for-review or draft

{{ 𝛀𝛀𝛀 }} Review a pull request

{{ ƔƔƔ }} Update a PR description to account for commits made since it was last written

{{ 𝛀𝛀𝛀 }} Probe the project for architectural weaknesses, technical debt, and risk — a deliberately critical read, not a balanced overview

{{ 𝛀𝛀𝛀 }} Investigate a codebase in detail and write findings to a document, for a named concept, subsystem, or question

{{ 𝛀𝛀𝛀 }} Investigate this repo's dependencies in detail

{{ 𝛀𝛀𝛀 }} Convert an exported Claude artefact (HTML or JSX) into a working Svelte 5 / SvelteKit 2 project

{{ 𝛀𝛀𝛀 }} Convert an old simple-style roadmap (single Markdown, four statuses, <a name> anchors, roadmaps.json pointer registry) into the rich phase-array format (roadmaps.json source of truth + PHASE task list + prose overview).