Super-Dev Full-Stack Self-Evolving Suite

Problem

Many dev skills focus only on code generation: vague requirements, weak tests, unchecked dependencies, and UI/UX judgment left to whether it renders. Super-Dev puts requirements clarification, architecture, TDD, experience audits, security gates, and memory into one delegatable workflow.

How it works

The orchestrator detects the task mode (BOOTSTRAP, FEATURE, FIX, REFACTOR) and delegates to sub-skills:
- Requirements: states assumptions, drills into 95% confidence, and pushes back on vague asks.
- Shared language: builds a domain glossary to reduce losses between user, account, and member.
- TDD: follows Red → Green → Refactor with a test pyramid and Stop-the-Line debugging.
- UI/UX audit: checks responsive behavior, accessibility, and AI aesthetic anti-patterns from a critical user perspective.
- Security gate: compares dependencies against malicious-package databases before npm install, using ssafe, depspector, owasp-depscan, and OpenSSF Scorecard.
- Memory and evolution: stores project facts, preferences, and failure notes in .memory/ for reuse.

Boundaries

It fits full-stack work that needs a steadier process, but it does not replace product judgment, manual acceptance, or formal security compliance. UX audits are heuristic, security scans depend on known malicious packages and metadata, and local .memory/ quality affects later runs.