Claude Skills by saleh-alhaddad

The full software-engineering lifecycle as one suite — DISCOVER, DEFINE, PLAN, BUILD, VERIFY, REVIEW, SHIP — with approval gates before code, test-first builds, evidence before "done", and resumable multi-session work. Routes to 12 sub-skills covering any stack, plus feature discovery, security audit, UI/UX craft, and learning roadmaps.

Whole-app health report from a panel of experts — how the features connect, which are strong, which are weak, and what to improve, with market evidence. App-level, not diff-level.

Turns an approved spec into an ordered, dependency-sorted task plan with a shape decision per task. Implementation planning, not product roadmap planning.

Writes the code for an already-defined task, test-first, following your codebase's own patterns. Also scoped fixes and performance optimizations on existing code.

Turns a raw idea into an approved spec, including database schema and API-contract design. Use before planning, while intent is still open. For visual UI design, use design.

Crafts or reviews UI/UX for web and mobile — visual and interaction quality, design systems, screens, and flows. For schema and API design, use define.

Proposes what to build next: ranked, cited feature candidates from market research and real usage. Also evaluates tools, platforms, and libraries you are considering switching to.

The full lifecycle in one call — spec, plan, build, verify, review, ship — with approval gates and resume. The default entry point for building or delivering something, and for picking up interrupted work. Routes to every phase skill itself.

Security audit: threat model, OWASP Top 10 (and LLM Top 10), abuse cases, dependency and secret scan, with ranked findings and concrete fixes. Read-only.

Senior code review across correctness, complexity, architecture, security, performance, and cross-service impact. Read-only — it reports and routes fixes to construct.

Builds and tracks a personalized learning roadmap, or onboards you onto an existing codebase. A user-invoked entry point; the lifecycle never routes here.

Ships a reviewed change safely, with a rollback plan and an explicit GO/NO-GO decision, and closes out the task.

Proves a change actually works and root-causes failures — the suite runs first, output actually read. Answers "does it work", where inspect answers "is it good".