backend-patterns

Before a change is made, present the findings, the options, and a recommendation with evidence, and agree with the user on one approach.

Own a new feature, from a vague idea to an agreed spec and design, and split the work into tickets for the other roles.

Split an agreed spec into a set of tickets, put them in order, and give each ticket to the correct role.

Use an app as a real user does, and keep a guide at the root of the repository that tells agents how to use it.

Create a narrated video walkthrough of a pull request with code slides and audio narration.

Map a codebase into a structured vocabulary — surfaces, features, entities, flows, compartments, invariants, tech stack — plus code-health metrics.

Fetch and triage code review findings from PR comments and/or review markdown files.

Shape a rough plan, idea, or feature request into something concrete by working through it like a smart cross-functional advisor with strong instincts across…

Generates a rich, visual HTML one-pager that lets a busy reviewer understand a body of changes and either approve a proposed PR stack or merge a finished one…

Generally-applicable conventions for how code is written and arranged — tooling/package manager, import style, file & component naming, comments, and where…

Interview the user to understand their learning goal and existing knowledge, then generate an interactive Obsidian-based learning map — a DAG of bite-sized…

Expand an existing Obsidian-based learning map in any direction.