Skill

engineering-catchall

Routes engineering requests to specialist roles for backend, frontend, mobile, fullstack, embedded, blockchain, ML/AI, QA, architecture, and docs based on tech domain and task type.

React

Vue

Node

Python

developer-tools

npx claudepluginhub chipagosfinest/enterprise-team --plugin enterprise-team

Tool Access

This skill uses the workspace's default tool permissions.

Preview

Routes engineering work to the appropriate specialist role.

SKILL.md

Similar Skills

using-agent-skills

37.4k

Discovers and invokes agent skills matching the current development task or phase, from idea refinement to shipping-and-launch. Use at session start or for skill selection.

agent-skills

00-andruia-consultant

37.1k

Diagnoses AI project workspaces as new 'Pure Engine' or existing 'Evolution', conducts Spanish requirements interviews, proposes expert skill squads, and generates tareas.md and plan_implementacion.md roadmaps. Use at project start.

antigravity-awesome-skills

strategic-compact

179.0k

Suggests manual /compact at logical task boundaries in long Claude Code sessions and multi-phase tasks to avoid arbitrary auto-compaction losses.

1 file

ecc

Stats

Parent Repo Stars16

Parent Repo Forks6

Last CommitApr 3, 2026

Actions

View Source View Plugin View on GitHub View README

Help us improve

Share bugs, ideas, or general feedback.

Engineering Department

Routes engineering work to the appropriate specialist role.

Routing Targets

Role

Handles

backend-engineer

APIs, servers, databases, microservices, authentication

frontend-engineer

Web UI, React/Vue/Angular components, CSS, accessibility

fullstack-engineer

End-to-end features spanning client and server

mobile-developer

iOS (Swift), Android (Kotlin), React Native, Flutter apps

embedded-engineer

Firmware, IoT devices, RTOS, hardware interfaces

blockchain-engineer

Smart contracts, Solidity, DeFi protocols, on-chain logic

ml-developer

Model training, data pipelines, inference, NLP, computer vision

solutions-architect

System design, infrastructure planning, scaling strategy

qa-engineer

Test plans, automation frameworks, regression, load testing

technical-writer

API docs, runbooks, architecture decision records

Examples

"Build a REST API for user management" -> backend-engineer

"Create a responsive dashboard with React" -> frontend-engineer

"Add a new feature with a form that saves to the database" -> fullstack-engineer

"Build an iOS app for scanning barcodes" -> mobile-developer

"Write firmware for the temperature sensor module" -> embedded-engineer

"Deploy an ERC-20 token contract" -> blockchain-engineer

"Train a classification model on our support tickets" -> ml-developer

"Design the architecture for our event-driven order system" -> solutions-architect

"Set up end-to-end tests for the checkout flow" -> qa-engineer

"Write API reference docs for the payments service" -> technical-writer

Workflow

Identify the primary technology domain from the user request.

If the request spans multiple domains, route to the role closest to the core task.

For ambiguous requests (e.g., "build a feature"), default to fullstack-engineer.

For requests focused on planning or design rather than implementation, route to solutions-architect.

Engineering Department

Routes engineering work to the appropriate specialist role.

Routing Targets

Role	Handles
backend-engineer	APIs, servers, databases, microservices, authentication
frontend-engineer	Web UI, React/Vue/Angular components, CSS, accessibility
fullstack-engineer	End-to-end features spanning client and server
mobile-developer	iOS (Swift), Android (Kotlin), React Native, Flutter apps
embedded-engineer	Firmware, IoT devices, RTOS, hardware interfaces
blockchain-engineer	Smart contracts, Solidity, DeFi protocols, on-chain logic
ml-developer	Model training, data pipelines, inference, NLP, computer vision
solutions-architect	System design, infrastructure planning, scaling strategy
qa-engineer	Test plans, automation frameworks, regression, load testing
technical-writer	API docs, runbooks, architecture decision records

Examples

"Build a REST API for user management" -> backend-engineer
"Create a responsive dashboard with React" -> frontend-engineer
"Add a new feature with a form that saves to the database" -> fullstack-engineer
"Build an iOS app for scanning barcodes" -> mobile-developer
"Write firmware for the temperature sensor module" -> embedded-engineer
"Deploy an ERC-20 token contract" -> blockchain-engineer
"Train a classification model on our support tickets" -> ml-developer
"Design the architecture for our event-driven order system" -> solutions-architect
"Set up end-to-end tests for the checkout flow" -> qa-engineer
"Write API reference docs for the payments service" -> technical-writer

Workflow

Identify the primary technology domain from the user request.
If the request spans multiple domains, route to the role closest to the core task.
For ambiguous requests (e.g., "build a feature"), default to fullstack-engineer.
For requests focused on planning or design rather than implementation, route to solutions-architect.