Entry point: /faion-net — invoke this skill for automatic routing to the appropriate domain.
Software Developer Orchestrator
Coordinates 7 specialized sub-skills for comprehensive software development.
Purpose
Routes development tasks to appropriate specialized sub-skills based on technology, domain, and task type.
Context Discovery
Auto-Investigation
Detect tech stack from project files BEFORE asking questions:
| Signal |
How to Check |
Detected Stack |
manage.py |
Glob("**/manage.py") |
Django → faion-python-developer |
pyproject.toml with fastapi |
Grep("fastapi", "**/pyproject.toml") |
FastAPI → faion-python-developer |
pyproject.toml with django |
Grep("django", "**/pyproject.toml") |
Django → faion-python-developer |
package.json with react |
Grep("react", "**/package.json") |
React → faion-javascript-developer |
package.json with next |
Grep("next", "**/package.json") |
Next.js → faion-javascript-developer |
package.json with express |
Grep("express", "**/package.json") |
Node.js → faion-javascript-developer |
go.mod |
Glob("**/go.mod") |
Go → faion-backend-systems |
Cargo.toml |
Glob("**/Cargo.toml") |
Rust → faion-backend-systems |
pom.xml or build.gradle |
Glob("**/pom.xml") |
Java → faion-backend-enterprise |
*.csproj |
Glob("**/*.csproj") |
C# → faion-backend-enterprise |
composer.json |
Glob("**/composer.json") |
PHP → faion-backend-enterprise |
Gemfile |
Glob("**/Gemfile") |
Ruby → faion-backend-enterprise |
tailwind.config.* |
Glob("**/tailwind.config.*") |
Tailwind → faion-frontend-developer |
Also check for patterns:
Glob("**/services/*.py") → Service layer exists, follow pattern
Glob("**/tests/**") → Tests exist, check style
Grep("class.*ViewSet", "**/*.py") → DRF ViewSets used
Discovery Questions
Use AskUserQuestion if stack not detected or task type unclear.
Q1: Task Type (if unclear from request)
question: "What type of development task is this?"
header: "Task"
multiSelect: false
options:
- label: "Build new feature"
description: "Create new functionality from scratch"
- label: "Fix a bug"
description: "Something isn't working correctly"
- label: "Refactor / improve"
description: "Restructure without changing behavior"
- label: "Add tests"
description: "Improve test coverage"
- label: "Review / audit code"
description: "Check quality, find issues"
Routing:
- "Build new feature" → Full workflow, may need architecture
- "Fix a bug" → Investigate first, minimal targeted changes
- "Refactor / improve" →
Skill(faion-code-quality)
- "Add tests" →
Skill(faion-testing-developer)
- "Review / audit code" →
Skill(faion-code-quality)
Q2: Tech Stack (only if not auto-detected)
question: "What's the primary technology?"
header: "Stack"
multiSelect: false
options:
- label: "Python (Django/FastAPI)"
description: "Python backend development"
- label: "JavaScript/TypeScript"
description: "React, Node.js, Next.js"
- label: "Go"
description: "Go backend services"
- label: "Other (Rust/Java/C#/PHP/Ruby)"
description: "Enterprise or systems languages"
Routing:
- "Python" →
Skill(faion-python-developer)
- "JavaScript/TypeScript" →
Skill(faion-javascript-developer)
- "Go" →
Skill(faion-backend-systems)
- "Other" →
Skill(faion-backend-enterprise)
Q3: Code Area (for large codebases)
question: "Which area of the codebase?"
header: "Area"
multiSelect: false
options:
- label: "Backend / API"
description: "Server-side logic, database"
- label: "Frontend / UI"
description: "User interface, components"
- label: "Both (full-stack)"
description: "Changes span frontend and backend"
- label: "Infrastructure"
description: "Build, deploy, CI/CD"
Q4: Existing Patterns (for existing codebases)
question: "Should I follow existing patterns in the codebase?"
header: "Patterns"
multiSelect: false
options:
- label: "Yes, match existing style"
description: "I'll investigate and follow conventions"
- label: "No, use best practices"
description: "Apply modern patterns regardless"
- label: "Improve while matching"
description: "Follow style but suggest improvements"
Action:
- "Yes, match existing" → Read existing code first, extract patterns
- "No, use best practices" → Apply methodology defaults
- "Improve while matching" → Note improvements in comments/TODOs
Sub-Skills
| Sub-skill |
Methodologies |
Focus |
| faion-python-developer |
24 |
Django, FastAPI, async, pytest, type hints |
| faion-javascript-developer |
18 |
React, Node.js, Next.js, TypeScript, Bun |
| faion-backend-developer |
47 |
Go, Rust, Java, C#, PHP, Ruby, databases |
| faion-frontend-developer |
18 |
Tailwind, CSS-in-JS, design tokens, PWA, a11y |
| faion-api-developer |
19 |
REST, GraphQL, OpenAPI, auth, versioning |
| faion-testing-developer |
12 |
Unit, integration, E2E, TDD, mocking |
| faion-devtools-developer |
46 |
Automation, architecture, code quality, CI/CD |
Total: 184 methodologies across 7 sub-skills
Routing Logic
| Task Type |
Route To |
| Python/Django/FastAPI code |
faion-python-developer |
| JavaScript/TypeScript/React/Node.js code |
faion-javascript-developer |
| Go/Rust/Java/C#/PHP/Ruby code |
faion-backend-developer |
| Database design, caching |
faion-backend-developer |
| Tailwind/CSS/UI libraries |
faion-frontend-developer |
| Design tokens, PWA, accessibility |
faion-frontend-developer |
| REST/GraphQL API design |
faion-api-developer |
| API auth, versioning, rate limiting |
faion-api-developer |
| Testing (any type) |
faion-testing-developer |
| Browser automation, web scraping |
faion-devtools-developer |
| Code review, refactoring |
faion-devtools-developer |
| Architecture patterns (DDD, CQRS) |
faion-devtools-developer |
| CI/CD, monorepo, tooling |
faion-devtools-developer |
Multi-Skill Tasks
For tasks spanning multiple domains, coordinate relevant sub-skills:
Full-stack Python app:
- faion-python-developer (backend)
- faion-api-developer (API design)
- faion-frontend-developer (UI)
- faion-testing-developer (tests)
React + Node.js app:
- faion-javascript-developer (React + Node.js)
- faion-frontend-developer (styling)
- faion-api-developer (API)
- faion-testing-developer (tests)
Microservices architecture:
- faion-backend-developer (services in Go/Rust/Java)
- faion-api-developer (API gateway)
- faion-devtools-developer (architecture patterns)
- faion-testing-developer (integration tests)
Agents
| Agent |
Purpose |
| faion-code-agent |
Code generation and review |
| faion-test-agent |
Test generation and execution |
| faion-frontend-brainstormer-agent |
Generate 3-5 design variants |
| faion-storybook-agent |
Setup/maintain Storybook |
| faion-frontend-component-agent |
Develop components with stories |
Related Skills
| Skill |
Relationship |
| faion-net |
Parent orchestrator for all projects |
| faion-software-architect |
Architecture design decisions |
| faion-devops-engineer |
Deployment, infrastructure |
| faion-ml-engineer |
AI/ML integrations |
| faion-sdd |
Specification-driven development |
Usage
Invoked via /faion-net or directly as /faion-software-developer. Automatically routes to appropriate sub-skill.
faion-software-developer v2.0 | Orchestrator | 7 sub-skills | 184 methodologies
1---2name: faion-software-developer3description: Full-stack development: Python, JavaScript, Go, APIs, testing, frontend.4---5> **Entry point:** `/faion-net` — invoke this skill for automatic routing to the appropriate domain.
6
7# Software Developer Orchestrator
8
9Coordinates 7 specialized sub-skills for comprehensive software development.
10
11## Purpose
12
13Routes development tasks to appropriate specialized sub-skills based on technology, domain, and task type.
14
15---
16
17## Context Discovery
18
19### Auto-Investigation
20
21Detect tech stack from project files BEFORE asking questions:
22
23| Signal | How to Check | Detected Stack |
24|--------|--------------|----------------|
25| `manage.py` | `Glob("**/manage.py")` | Django → faion-python-developer |
26| `pyproject.toml` with fastapi | `Grep("fastapi", "**/pyproject.toml")` | FastAPI → faion-python-developer |
27| `pyproject.toml` with django | `Grep("django", "**/pyproject.toml")` | Django → faion-python-developer |
28| `package.json` with react | `Grep("react", "**/package.json")` | React → faion-javascript-developer |
29| `package.json` with next | `Grep("next", "**/package.json")` | Next.js → faion-javascript-developer |
30| `package.json` with express | `Grep("express", "**/package.json")` | Node.js → faion-javascript-developer |
31| `go.mod` | `Glob("**/go.mod")` | Go → faion-backend-systems |
32| `Cargo.toml` | `Glob("**/Cargo.toml")` | Rust → faion-backend-systems |
33| `pom.xml` or `build.gradle` | `Glob("**/pom.xml")` | Java → faion-backend-enterprise |
34| `*.csproj` | `Glob("**/*.csproj")` | C# → faion-backend-enterprise |
35| `composer.json` | `Glob("**/composer.json")` | PHP → faion-backend-enterprise |
36| `Gemfile` | `Glob("**/Gemfile")` | Ruby → faion-backend-enterprise |
37| `tailwind.config.*` | `Glob("**/tailwind.config.*")` | Tailwind → faion-frontend-developer |
38
39**Also check for patterns:**
40- `Glob("**/services/*.py")` → Service layer exists, follow pattern
41- `Glob("**/tests/**")` → Tests exist, check style
42- `Grep("class.*ViewSet", "**/*.py")` → DRF ViewSets used
43
44### Discovery Questions
45
46Use `AskUserQuestion` if stack not detected or task type unclear.
47
48#### Q1: Task Type (if unclear from request)
49
50```yaml
51question: "What type of development task is this?"
52header: "Task"
53multiSelect: false
54options:
55 - label: "Build new feature"
56 description: "Create new functionality from scratch"
57 - label: "Fix a bug"
58 description: "Something isn't working correctly"
59 - label: "Refactor / improve"
60 description: "Restructure without changing behavior"
61 - label: "Add tests"
62 description: "Improve test coverage"
63 - label: "Review / audit code"
64 description: "Check quality, find issues"
65```
66
67**Routing:**
68- "Build new feature" → Full workflow, may need architecture
69- "Fix a bug" → Investigate first, minimal targeted changes
70- "Refactor / improve" → `Skill(faion-code-quality)`
71- "Add tests" → `Skill(faion-testing-developer)`
72- "Review / audit code" → `Skill(faion-code-quality)`
73
74#### Q2: Tech Stack (only if not auto-detected)
75
76```yaml
77question: "What's the primary technology?"
78header: "Stack"
79multiSelect: false
80options:
81 - label: "Python (Django/FastAPI)"
82 description: "Python backend development"
83 - label: "JavaScript/TypeScript"
84 description: "React, Node.js, Next.js"
85 - label: "Go"
86 description: "Go backend services"
87 - label: "Other (Rust/Java/C#/PHP/Ruby)"
88 description: "Enterprise or systems languages"
89```
90
91**Routing:**
92- "Python" → `Skill(faion-python-developer)`
93- "JavaScript/TypeScript" → `Skill(faion-javascript-developer)`
94- "Go" → `Skill(faion-backend-systems)`
95- "Other" → `Skill(faion-backend-enterprise)`
96
97#### Q3: Code Area (for large codebases)
98
99```yaml
100question: "Which area of the codebase?"
101header: "Area"
102multiSelect: false
103options:
104 - label: "Backend / API"
105 description: "Server-side logic, database"
106 - label: "Frontend / UI"
107 description: "User interface, components"
108 - label: "Both (full-stack)"
109 description: "Changes span frontend and backend"
110 - label: "Infrastructure"
111 description: "Build, deploy, CI/CD"
112```
113
114#### Q4: Existing Patterns (for existing codebases)
115
116```yaml
117question: "Should I follow existing patterns in the codebase?"
118header: "Patterns"
119multiSelect: false
120options:
121 - label: "Yes, match existing style"
122 description: "I'll investigate and follow conventions"
123 - label: "No, use best practices"
124 description: "Apply modern patterns regardless"
125 - label: "Improve while matching"
126 description: "Follow style but suggest improvements"
127```
128
129**Action:**
130- "Yes, match existing" → Read existing code first, extract patterns
131- "No, use best practices" → Apply methodology defaults
132- "Improve while matching" → Note improvements in comments/TODOs
133
134---
135
136## Sub-Skills
137
138| Sub-skill | Methodologies | Focus |
139|-----------|---------------|-------|
140| faion-python-developer | 24 | Django, FastAPI, async, pytest, type hints |
141| faion-javascript-developer | 18 | React, Node.js, Next.js, TypeScript, Bun |
142| faion-backend-developer | 47 | Go, Rust, Java, C#, PHP, Ruby, databases |
143| faion-frontend-developer | 18 | Tailwind, CSS-in-JS, design tokens, PWA, a11y |
144| faion-api-developer | 19 | REST, GraphQL, OpenAPI, auth, versioning |
145| faion-testing-developer | 12 | Unit, integration, E2E, TDD, mocking |
146| faion-devtools-developer | 46 | Automation, architecture, code quality, CI/CD |
147
148**Total:** 184 methodologies across 7 sub-skills
149
150## Routing Logic
151
152| Task Type | Route To |
153|-----------|----------|
154| Python/Django/FastAPI code | faion-python-developer |
155| JavaScript/TypeScript/React/Node.js code | faion-javascript-developer |
156| Go/Rust/Java/C#/PHP/Ruby code | faion-backend-developer |
157| Database design, caching | faion-backend-developer |
158| Tailwind/CSS/UI libraries | faion-frontend-developer |
159| Design tokens, PWA, accessibility | faion-frontend-developer |
160| REST/GraphQL API design | faion-api-developer |
161| API auth, versioning, rate limiting | faion-api-developer |
162| Testing (any type) | faion-testing-developer |
163| Browser automation, web scraping | faion-devtools-developer |
164| Code review, refactoring | faion-devtools-developer |
165| Architecture patterns (DDD, CQRS) | faion-devtools-developer |
166| CI/CD, monorepo, tooling | faion-devtools-developer |
167
168## Multi-Skill Tasks
169
170For tasks spanning multiple domains, coordinate relevant sub-skills:
171
172**Full-stack Python app:**
1731. faion-python-developer (backend)
1742. faion-api-developer (API design)
1753. faion-frontend-developer (UI)
1764. faion-testing-developer (tests)
177
178**React + Node.js app:**
1791. faion-javascript-developer (React + Node.js)
1802. faion-frontend-developer (styling)
1813. faion-api-developer (API)
1824. faion-testing-developer (tests)
183
184**Microservices architecture:**
1851. faion-backend-developer (services in Go/Rust/Java)
1862. faion-api-developer (API gateway)
1873. faion-devtools-developer (architecture patterns)
1884. faion-testing-developer (integration tests)
189
190## Agents
191
192| Agent | Purpose |
193|-------|---------|
194| faion-code-agent | Code generation and review |
195| faion-test-agent | Test generation and execution |
196| faion-frontend-brainstormer-agent | Generate 3-5 design variants |
197| faion-storybook-agent | Setup/maintain Storybook |
198| faion-frontend-component-agent | Develop components with stories |
199
200## Related Skills
201
202| Skill | Relationship |
203|-------|--------------|
204| faion-net | Parent orchestrator for all projects |
205| faion-software-architect | Architecture design decisions |
206| faion-devops-engineer | Deployment, infrastructure |
207| faion-ml-engineer | AI/ML integrations |
208| faion-sdd | Specification-driven development |
209
210## Usage
211
212Invoked via `/faion-net` or directly as `/faion-software-developer`. Automatically routes to appropriate sub-skill.
213
214---
215
216*faion-software-developer v2.0 | Orchestrator | 7 sub-skills | 184 methodologies*