How this skill is triggered — by the user, by Claude, or both
Slash command
/backend-factory:dataflowThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Trace a single data entity through every layer of the backend to map its complete lifecycle — from birth to death.
Trace a single data entity through every layer of the backend to map its complete lifecycle — from birth to death.
$ARGUMENTS should contain a data entity name (e.g., User, Order, Payment, Session).
If $ARGUMENTS is empty, scan the codebase for model/schema definitions and list discovered entities.
Quick check for web framework, ORM/DB layer, cache layer, and queue system.
Cast a wide net across all layers:
Organize references into lifecycle stages:
If the factory server is running, POST lifecycle overlay data.
Present findings in two formats:
Entity details, lifecycle stages with file paths, relationship map, potential issues.
A creative narration told BY the data entity as a factory worker. Use real file names, routes, and field names.
Suggest: "Run /backend-factory:trace on specific routes to see the detailed station-by-station path."
npx claudepluginhub randyquaye/backend-come-alive --plugin backend-factoryTraces HTTP request lifecycle from router through middleware, controller, use case, repository to response in PHP apps. Documents routes, methods, stacks, codes, errors.
Traces feature, request, or data flows through codebase from entry points (API routes, UI handlers, jobs) to storage, documenting layers, transformations, side effects, and dependencies via graphs or grep.
Traces execution paths, maps dependencies, follows data flows, and explores unfamiliar code systematically from entry points to build incremental understanding.