Claude Skills by NenadBanjeglav

Use before planning or implementation for one bounded feature, roadmap outcome, behavior, app, site, tool, component, UI, API, workflow, or architecture change

Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module vocabulary.

Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies

Use when executing a policy-accepted written Implementation Plan linearly in the current or fresh phase session

Use when implementation tasks are complete and final verification, review evidence, commit summary, changed-file summary, and local closeout are needed

Use when scanning a codebase for shallow modules, unclear interfaces, weak seams, poor adapters, low locality, or weak leverage and writing a local architecture review

Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation

Use when completing tasks, implementing major features, or before merging to verify work meets requirements

Use when executing a policy-accepted implementation plan with mostly independent sequential writer tasks and isolated advisory review

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes

Use when implementing any feature or bugfix, before writing implementation code

Use when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback

Use when starting a conversation to resolve workflow policy, migrate legacy Superpowers gates at a safe boundary, and route project-wide work to wayfinder or bounded work to brainstorming before planning or implementation

Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always

Use for greenfield project inception or project-wide reorientation to establish or resume the Agentic Foundation, Project Blueprint, traceable roadmap, Approval Policy, and Phase Mode before bounded design

Use when an exact policy-accepted local Design Spec exists and a concrete implementation plan is needed before implementation