From backend-factory
Visualize how the factory handles load with simulated traffic patterns
npx claudepluginhub randyquaye/backend-come-alive --plugin backend-factoryThis skill is limited to using the following tools:
Simulate traffic load on the factory and visualize where bottlenecks form.
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.
Simulate traffic load on the factory and visualize where bottlenecks form.
$ARGUMENTS should contain a traffic pattern:
| Pattern | Description |
|---|---|
spike N | N simultaneous requests hit all routes at once |
sustained N | N requests per second, steady stream |
burst N Ts | N requests compressed into T seconds |
realistic | 80% reads, 15% writes, 5% deletes |
Default to realistic if empty.
curl -s http://localhost:7777/api/architecture | jq '.' > /tmp/factory-stress-base.json
Examine stations for stress vulnerabilities:
Calculate per-action: worker count, throughput estimate, queue depth, block rate.
curl -s -X POST http://localhost:7777/api/architecture \
-H "Content-Type: application/json" \
-d @/tmp/factory-stress-payload.json
Stations from most to least vulnerable, with file paths and estimated failure thresholds.
Which activate, at what level, per-user vs global.
Which queues accumulate backlog, drain time estimates.
Grade A-F based on caching, rate limiting, queue absorption, and external API resilience.
A dramatic factory stress report referencing actual station names, routes, and numbers.