tibursocampos/agent-dev-toolkit / core/skills/developer
developer
VerifiedSmart 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/frontend-design-routing.md
View on GitHub## Frontend design routing
Before UI implementation, check project context:
1. If the task is **net-new UI** or a **visual redesign** and `PRODUCT.md` is missing, clarify the product context before choosing visual direction.
2. If `docs/DESIGN-BRIEF.md` (or `docs/design/DESIGN-BRIEF.md`) exists -> treat it as acceptance source; delegate to the matching `*-developer` skill **without reinterpreting visual decisions**.
3. For net-new UI or a substantial visual redesign without a brief, record visual direction in `docs/DESIGN-BRIEF.md` before implementation. For smaller changes, follow the existing product design system. Keep design decisions and implementation in separate sessions when both need substantial work.
For a substantial visual redesign without a brief, create a concise brief covering audience, hierarchy, visual direction, responsive behavior, component states, and accessibility before stack implementation.
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: 469k | 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: 321k | 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: 321k | 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: 321k | Updated | Claude CodeCodex | Verified | Install |