Claude Skills by marcellocurto

Find needless code complexity and suggest simpler designs that preserve behavior.

Find downstream breakage a code change could cause beyond the files it directly touches.

Review a specific diff, pull request, or commit range for correctness, maintainability, and repository standards. Not for whole-codebase or current-state subsystem audits.

Design small, type-safe interfaces that hide complexity and give domain logic a clear home.

Open a ready-for-review GitHub pull request for completed local changes, including any needed commit and push.

Reproduce, isolate, and fix difficult bugs or performance regressions.

Define and maintain the codebase's shared domain terms and architectural decisions.

Trace and explain how an existing code path or subsystem works.

Guidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults.

Decide whether one GitHub issue is valid, unique, scoped, and ready to proceed.

Stress-test a plan through questions while recording the resulting domain terms and decisions.

Stress-test an idea or decision through focused questions about consequential assumptions and tradeoffs.

Implement a GitHub issue or the work agreed in the conversation, check it, and open a pull request that is ready for review.

Find high-value ways to deepen a codebase's modules, present them visually, and explore the chosen change.

Audit the full PR for merge readiness across correctness, maintainability and complexity, and test quality, then publish one actionable comment. Covers the contribution, not just existing feedback.

Audit open pull-request comments, fix and push the justified ones, and reply to and resolve each thread.

Challenge an existing proposal or result to find material risks and a better path.

Build, update, debug, and style shadcn/ui components using the project's registry and conventions.

Simplify a proposed or existing code solution through recommendations or implementation while preserving requirements and clear ownership.

Use before implementing features or bug fixes with testable behavior, including requests that do not mention tests or TDD. Not for behavior-preserving refactors or prose, styling, and static-content edits.

Judge whether tests catch realistic regressions and recommend what to keep, change, or remove.

Turn approved work into well-scoped GitHub issues after checking for duplicates and dependencies.

Assess one specified GitHub issue for implementation readiness, ask blocking questions, and update it after approval.

Apply scalable React composition patterns when designing or refactoring component interfaces.

Apply Vercel's React and Next.js performance guidance when writing or reviewing code.

Create an interactive Bash wizard for setup steps that only a human can complete.