npx claudepluginhub randyquaye/backend-come-alive --plugin backend-factoryThis skill is limited to using the following tools:
Trace a single data entity through every layer of the backend to map its complete lifecycle — from birth to death.
Triggers research for existing libraries, tools, and patterns before coding new features. Searches npm, PyPI, MCP/skills, GitHub; evaluates matches and decides adopt/extend/build.
Audits cross-stack repos (C++/Android/iOS/Web), classifies files as project/third-party/artifacts, detects embedded libraries, assigns module verdicts, generates interactive HTML reports.
Reorganizes X and LinkedIn networks: review-first pruning of low-value follows, priority-based add/follow recommendations, and drafts warm outreach in user's voice.
Share bugs, ideas, or general feedback.
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."