engineering-catchall
starsforks
How to install engineering-catchall?
chipagosfinest/enterprise-team/engineering-catchall
$npx -y skills add Chipagosfinest/enterprise-team --skill engineering-catchallRoutes engineering requests to the correct specialist based on technology domain, task type, and stack involved. Covers backend, frontend, mobile, fullstack, embedded, blockchain, ML/AI, QA, architecture, and technical documentation. Triggers: build feature, write code, implement
SKILL.md
| 1 | # Engineering Department |
| 2 | |
| 3 | Routes engineering work to the appropriate specialist role. |
| 4 | |
| 5 | ## Routing Targets |
| 6 | |
| 7 | | Role | Handles | |
| 8 | |---|---| |
| 9 | | backend-engineer | APIs, servers, databases, microservices, authentication | |
| 10 | | frontend-engineer | Web UI, React/Vue/Angular components, CSS, accessibility | |
| 11 | | fullstack-engineer | End-to-end features spanning client and server | |
| 12 | | mobile-developer | iOS (Swift), Android (Kotlin), React Native, Flutter apps | |
| 13 | | embedded-engineer | Firmware, IoT devices, RTOS, hardware interfaces | |
| 14 | | blockchain-engineer | Smart contracts, Solidity, DeFi protocols, on-chain logic | |
| 15 | | ml-developer | Model training, data pipelines, inference, NLP, computer vision | |
| 16 | | solutions-architect | System design, infrastructure planning, scaling strategy | |
| 17 | | qa-engineer | Test plans, automation frameworks, regression, load testing | |
| 18 | | technical-writer | API docs, runbooks, architecture decision records | |
| 19 | |
| 20 | ## Examples |
| 21 | |
| 22 | - "Build a REST API for user management" -> backend-engineer |
| 23 | - "Create a responsive dashboard with React" -> frontend-engineer |
| 24 | - "Add a new feature with a form that saves to the database" -> fullstack-engineer |
| 25 | - "Build an iOS app for scanning barcodes" -> mobile-developer |
| 26 | - "Write firmware for the temperature sensor module" -> embedded-engineer |
| 27 | - "Deploy an ERC-20 token contract" -> blockchain-engineer |
| 28 | - "Train a classification model on our support tickets" -> ml-developer |
| 29 | - "Design the architecture for our event-driven order system" -> solutions-architect |
| 30 | - "Set up end-to-end tests for the checkout flow" -> qa-engineer |
| 31 | - "Write API reference docs for the payments service" -> technical-writer |
| 32 | |
| 33 | ## Workflow |
| 34 | |
| 35 | 1. Identify the primary technology domain from the user request. |
| 36 | 2. If the request spans multiple domains, route to the role closest to the core task. |
| 37 | 3. For ambiguous requests (e.g., "build a feature"), default to fullstack-engineer. |
| 38 | 4. For requests focused on planning or design rather than implementation, route to solutions-architect. |
People who liked this also viewed
6 picksType
- find-skillsHelps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skSkillsJul 2026
- grill-meA relentless interview to sharpen a plan or design.SkillsJul 2026
- vercel-react-best-practicesVercel's official collection of agent skillsSkillsJul 2026
- improve-codebase-architectureScan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.SkillsJul 2026
- setup-matt-pocock-skillsConfigure this repo for the engineering skills — set up its issue tracker, triage label vocabulary, and domain doc layout. Run once before first use of the other engineering skills.SkillsJul 2026
- triageMove issues and external PRs through a state machine of triage roles — categorise, verify, grill if needed, and write agent-ready briefs.SkillsJul 2026
