agent-skills

Decompose a piece of an existing codebase — a function, method, class, or module — into a runnable notebook that explains it top-down: a call-graph map, then each piece defined and executed on concrete mock inputs with its real output shown inline. Turns code you didn't write (or have forgotten) into an interactive, line-by-line walkthrough. Use this skill only when the user explicitly invokes it by name (`explain-as-notebook`) or near-match mentioning.

Analyze the agent experience ("AX") of an interface an AI agent drives — a CLI, MCP server, HTTP/REST API, or library/SDK — against the principles of what makes a system easy for a reasoning-loop agent to use, and prescribe prioritized fixes. Use this skill only when the user explicitly invokes it by name (`ax-interface-analysis`) or near-match mentioning.

Reverse-engineer and document the user-facing API and UX/DX of an existing or cloned codebase — the system as seen from outside the boundary, whether the "user" is an end user or a developer. Use this skill only when the user explicitly invokes it by name (`explain-ux-dx-design`) or near-match mentioning.

Reverse-engineer and document the data architecture of an existing or cloned codebase — where data rests (stores, schema) and how it moves (dataflow, lineage). Use this skill only when the user explicitly invokes it by name (`explain-data-architecture`) or near-match mentioning.

Reverse-engineer and document the architecture of an existing or cloned codebase. Use this skill only when the user explicitly invokes it by name (`explain-system-architecture`) or near-match mentioning.

Reference for the DCMTK (OFFIS DICOM Toolkit) command-line tools — the canonical CLI for working with DICOM files and DIMSE network services. Use when converting, dumping, anonymizing, or validating DICOM files, or running DIMSE services (C-ECHO/STORE/FIND/MOVE/GET), worklists, or structured reports from the terminal.

Reference for driving an Orthanc DICOM server through its REST API. Use this skill whenever a task involves Orthanc — uploading, browsing, searching, downloading, anonymizing, or modifying DICOM resources (patients/studies/series/instances) on a local or remote Orthanc; performing DICOM network operations through Orthanc such as C-ECHO, C-STORE, C-MOVE, C-GET, or Query/Retrieve (C-FIND) against remote modalities/PACS; configuring Orthanc peers or modalities; tracking changes; decoding instances to PNG/NumPy for AI pipelines; or running asynchronous Orthanc jobs. Trigger this even when the user only mentions an Orthanc URL (e.g. localhost:8042), 'the Orthanc REST API', or building a script/tool/pipeline that talks to Orthanc, even if no specific endpoint is named.

Drive 3D Slicer (medical imaging app) over HTTP via the slicer-cli tool. Use when the user mentions Slicer, MRML, DICOM viewing/loading from a Slicer scene, or asks to render a slice/3D view from a volume they have loaded in Slicer.

Transform project requirements, problems, user stories, or rough ideas into Simon Brown's C4 architecture diagrams — System Context (C1), Containers (C2), and Components (C3). Conducts adaptive Q&A, emits Unicode box-drawing ASCII diagrams inline, and optionally saves Mermaid versions to disk. Incorporates light DDD Strategic Design vocabulary (bounded context, ubiquitous language, context map, subdomain triage) with inline plain-English glosses so users unfamiliar with DDD still understand. Invoke this skill when the user asks to design, architect, diagram, model, or transform requirements into a system design, or mentions "C4" explicitly. Stops deliberately at each phase boundary for user confirmation. Code-level diagrams (C4 Level 4) are out of scope — defer to UML/class-diagram skills or trained knowledge for that level.

Git workflow: commit, push, and create/update a draft PR. If a PR exists for the current branch, update its body. Trigger: 'commit push pr', 'ship it', 'send a PR', or /commit-push-pr.