tibursocampos/agent-dev-toolkit / core/skills/developer
developer
UnverifiedSmart router for stack skills, or senior fullstack for ad-hoc scripts/HTML/automation. Use for generic development or when invoking /developer.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 4.2 KB |
| reference.md | markdown | 533 B |
| references/fallback-execution.md | markdown | 2.5 KB |
| references/frontend-design-routing.md | markdown | 931 B |
| references/must-not.md | markdown | 500 B |
| references/stack-routing.md | markdown | 4.2 KB |
references/stack-routing.md
View on GitHub## Stack routing
1. **Inspect the workspace** - identify stack in this order (frameworks before generic Node):
| Signal | Route to |
|--------|----------|
| User asks for **new** Blip plugin scaffold (no existing `blip-ds` project) | `blip-plugin-developer` |
| `package.json` with `blip-ds` and `iframe-message-proxy` (existing Blip plugin) | `react-developer` (loads `blip-guidelines/`) |
| `.csproj` with `Microsoft.AspNetCore.Components`, or `_Imports.razor` / `App.razor` | `blazor-developer` |
| `package.json` with `electron`, `electron-builder`, or `electron-vite` | `electron-developer` |
| `package.json` with `vue` (and not React/Angular) | `vue-developer` |
| `package.json` with `react-native` or `expo` | `react-native-developer` |
| `package.json` with `react` | `react-developer` |
| `package.json` with `@angular/core` or `angular` | `angular-developer` |
| Native ESP-IDF signals such as `idf_component.yml`, a Component Manager lockfile, `idf_component_register`, ESP-IDF CMake structure, `sdkconfig`/`sdkconfig.defaults`, or project `idf.py` scripts | `esp-idf-developer`; preserve the observed CMake/`idf.py`, resolved dependencies, defaults, and local configuration |
| Explicit Arduino Core/framework evidence with Arduino project metadata or dependency/version declaration | `arduino-developer`; do not treat Arduino compatibility or an ESP32 board name as native ESP-IDF evidence |
| `platformio.ini` or equivalent with an environment explicitly declaring `framework = arduino` | `arduino-developer` (PlatformIO is conditional, not the default) |
| Declared MicroPython runtime, firmware image workflow, or project runtime files with runtime/target/port evidence | `micropython-developer`; keep device APIs and deployment scoped to the identified MicroPython configuration |
| `.ino`, `main.py`, or board-family name without framework/runtime and toolchain evidence | Request framework/core/runtime/version/toolchain evidence; do not infer Arduino, ESP-IDF, or MicroPython |
| `package.json` (Node.js, no framework above) | `javascript-developer` |
| `.csproj` / `.sln` without Blazor markers | `dotnet-developer` |
| `pom.xml`, `build.gradle`, `build.gradle.kts`, or `settings.gradle` | `java-developer` |
| CPython host tooling/tests, `.py`, `requirements.txt`, or `pyproject.toml` with host-runtime evidence | `python-developer`; do not add device APIs or flashing guidance |
| C/C++ or Python host tooling/tests that exercise firmware without embedded project evidence | Route by the host language (`python-developer` for CPython); do not infer an embedded firmware framework |
| Python source without runtime/target/port evidence where APIs or deployment could differ | Ask for runtime, target, and port evidence before choosing a device workflow; `.py` alone is not MicroPython evidence |
Target and ESP-IDF version are separate evidence fields. A framework match does not establish either one: derive them from project declarations, configuration, build output, dependency metadata, lockfiles, or observed tool output; otherwise state the uncertainty and ask before version-sensitive guidance. Preserve `idf_component.yml`, lockfiles, `sdkconfig.defaults`, generated/local configuration, and existing resolved versions until a reviewed change is requested.
2. **Invoke the specialized skill (if match found)**:
- Silently read the `SKILL.md` of the matched stack under `{{TOOLKIT_ROOT}}/skills/`:
- `blip-plugin-developer`, `blazor-developer`, `electron-developer`, `vue-developer`, `react-native-developer`, `dotnet-developer`, `java-developer`, `react-developer`, `angular-developer`, `javascript-developer`, `python-developer`, `micropython-developer`, `arduino-developer`, or `esp-idf-developer`
- Assume the identity and instructions of that skill immediately.
- Do **not** ask the user for confirmation to switch skills.
3. **Fallback mode (if no match found)**:
- If no major framework structure is detected (e.g., isolated `.html`, `.sh`, `.bat`, `.ps1` files), **do not delegate**.
- Assume the task directly using standard, secure engineering practices as a Senior Developer.
- Proceed to `references/fallback-execution.md`.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 467k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 319k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 319k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 319k | Updated | Claude CodeCodex | Verified | Install |