Skill

focus

Deep-zoom into a specific component for a detailed 'day in the life' view

npx claudepluginhub randyquaye/backend-come-alive --plugin backend-factory

Tool Access

This skill is limited to using the following tools:

BashReadGlobGrepAgent

Preview

Deep-zoom into a single component (node) in the factory for a detailed station profile, upstream/downstream map, activity log, and first-person narration.

SKILL.md

Similar Skills

search-first

171.7k

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.

everything-claude-code

repo-scan

171.7k

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.

everything-claude-code

connections-optimizer

171.7k

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.

everything-claude-code

Stats

Stars0

Forks0

Last CommitMar 13, 2026

Actions

View Source View Plugin View on GitHub View README

Help us improve

Share bugs, ideas, or general feedback.

Backend Factory - Focus Component

Deep-zoom into a single component (node) in the factory for a detailed station profile, upstream/downstream map, activity log, and first-person narration.

Step 1: Parse Arguments

$ARGUMENTS should contain a component identifier. Match strategy priority:

Exact ID match on id field
Type keyword match on type (auth, database, queue, cache, cron, worker)
Name match (case-insensitive) on name
Route path match
Station label match on metadata.stationLabel

If $ARGUMENTS is empty, list all available nodes and ask the user to pick one.

Step 2: Fetch Architecture & Match Node

curl -s http://localhost:7777/api/architecture > /tmp/factory-focus-arch.json

If the server is not running, inform the user to run /backend-factory:start first.

Step 3: Find All Flows Through This Node

Search all actions for flows that pass through the target node.

Step 4: Read Source Code

If the target node has metadata.filePath, read the source file and up to 5 related files.

Step 5: Generate Station Profile

Station Bio

Name, type, file path, factory role, description, config, dependencies, dependents

Upstream / Downstream Map

[Upstream Components] → [THIS COMPONENT] → [Downstream Components]

Daily Activity Log

Total flows passing through, breakdown by type, busiest flows

"Day in the Life" Narration

A first-person narrative (3-5 paragraphs) from this station's worker, grounded in real code details.

Health Assessment

Performance: Connection pooling, caching, async patterns, N+1 risks
Security: Input validation, injection risks, secrets management
Resilience: Retry logic, circuit breakers, timeout configs
Rating: Healthy / Needs Attention / At Risk

Step 6: Update Visualization

POST a focus mode overlay to highlight this component.

Step 7: Report

Present the complete focus report and suggest:

/backend-factory:trace <flow_name> to trace any passing flow
/backend-factory:focus <upstream_component> to zoom into a connected station