Code Slice Explainer

Use this skill when the user wants one bounded walkthrough of how part of a system works from start to finish. The canonical term is slice.

Purpose

Explain one slice end to end without dropping meaningful steps.
Start with the incoming data shape, what it represents, who sends it, and why it enters the flow.
Walk the execution path in order, including boundaries, branch points, shared versus specialized steps, and data transformations.
End with the final output shape, who receives it, and what purpose it serves.
Let the user control explanation density with a detail level, not by silently skipping steps.

slice: one bounded end-to-end walkthrough of a request, event, feature action, job, or data item.
data shape: the meaningful structure of the data at a point in the slice, what it represents, and why it has that shape.
boundary: a meaningful crossing such as caller/callee, module, package, process, service, client/server, queue, storage, or external API.
branch point: any step that can route execution down different paths.