playbooks

home / skills / zpankz / mcp-skillset / development-router

development-router skill

/development-router

This skill routes development tasks to frontend, backend, or fullstack experts, accelerating delivery by matching triggers to the right specialized workflows.

npx playbooks add skill zpankz/mcp-skillset --skill development-router

Review the files below or copy the command above to add this skill to your agents.

Files (2)
SKILL.md
2.1 KB
---
name: development-router
description: Routes development tasks to frontend, backend, or fullstack skills. Triggers on build, implement, code, create, feature, component, UI, API, server, database, docker, deploy.
---

# Development Router

Routes development-related tasks to appropriate specialized skills.

## Subcategories

### Frontend Development
```yaml
triggers: [UI, component, React, Vue, Svelte, CSS, Tailwind, design-system, terminal-ui, responsive]
skills:
  - terminal: TUI/CLI interfaces with high design quality
  - component: Claude Code configuration components
  - sc:implement: Feature implementation with persona activation
```

### Backend Development
```yaml
triggers: [api, server, database, auth, REST, GraphQL, microservice, endpoint]
skills:
  - sc:build: Build and compile projects
  - sc:design: System architecture and API design
  - mcp-builder: MCP server development
```

### Fullstack / Infrastructure
```yaml
triggers: [fullstack, monorepo, deployment, docker, ci/cd, pipeline]
skills:
  - sc:workflow: Implementation workflows from PRDs
  - sc:task: Complex task execution with persistence
```

## Routing Decision Tree

```
development request
    │
    ├── UI/component keywords?
    │   ├── TUI/terminal? → @skills/terminal
    │   ├── Claude component? → @skills/component
    │   └── general UI → sc:implement
    │
    ├── API/server keywords?
    │   ├── MCP server? → @skills/mcp-builder
    │   ├── architecture? → sc:design
    │   └── implementation → sc:build
    │
    └── deployment/infra?
        └── sc:workflow
```

## Managed Skills

| Skill | Purpose | Trigger |
|-------|---------|---------|
| terminal | Production-grade TUI | "terminal UI", "CLI tool" |
| component | CC config components | "command", "subagent", "skill" |
| sc:implement | Feature implementation | "implement", "build feature" |
| sc:build | Build/compile | "build", "compile", "package" |
| sc:design | Architecture | "design", "architecture" |
| mcp-builder | MCP servers | "MCP", "model context protocol" |
| sc:workflow | PRD workflows | "workflow", "PRD" |

Overview

This skill routes development tasks to the most appropriate frontend, backend, or fullstack skill. It listens for common development triggers and maps requests to specialized handlers so work is executed by the right sub-skill. The router speeds context-aware delegation and reduces back-and-forth about scope and responsibility.

How this skill works

The router inspects the request for keywords related to UI, API/server, or infrastructure and follows a simple decision tree to choose a target skill. Frontend triggers route to terminal, component, or implementation skills; backend triggers route to build, design, or MCP server skills; infra and fullstack triggers route to workflow or task orchestration skills. It returns a deterministic routing recommendation and context tags for the chosen skill.

When to use it

  • You need to determine whether a request should go to frontend, backend, or fullstack work.
  • Incoming feature requests that mention UI components, APIs, or deployment pipelines.
  • Automated task dispatching in a multi-skill development assistant environment.
  • Pre-routing user queries before invoking specialized implementation agents.
  • When you want consistent, keyword-driven routing for development workflows.

Best practices

  • Include concise keywords (UI, API, deploy, database, Docker) to improve routing accuracy.
  • Provide a short context sentence (goal, tech stack, and constraints) with the trigger terms.
  • Use explicit mentions for special cases (MCP server, TUI, design system) to hit targeted skills.
  • Fallback to fullstack/workflow routing for ambiguous or cross-cutting requests.
  • Validate routing results and adjust keywords if the assigned skill lacks needed context.

Example use cases

  • User asks: 'Create a responsive React component using Tailwind' → routes to component/implementation skill.
  • Request: 'Design REST endpoints for orders and auth' → routes to system design / sc:design.
  • Task: 'Build and package the backend service with CI' → routes to sc:build and sc:workflow.
  • Prompt: 'Set up Docker and deploy the monorepo pipeline' → routes to sc:workflow for infra.
  • Question: 'Implement a terminal UI for admin operations' → routes to terminal TUI skill.

FAQ

What if a request matches multiple categories?

The router applies priority rules: UI keywords first for explicit component work, API/server for backend-specific terms, and infra/fullstack for deployment or monorepo signals. If ambiguity remains, it recommends a fullstack/workflow skill.

Can I add custom triggers or skills?

Yes. Extend the trigger lists and map new skill identifiers into the routing table so future requests route to your custom handlers.