Claude Skills by adtn0810

Use when new cross-module work, unclear system boundaries, or a costly architecture decision needs an implementation plan. Skip small changes with an obvious approach.

Use when implementing or refactoring server logic, endpoints, jobs, persistence, integrations, or backend concurrency. Contract and schema changes also use database-api-evolution.

Use for an explicit review of a defined diff, pull request, file, or code scope for actionable defects and regressions. Does not authorize an unsolicited rewrite or replace native delegated review routing.

Use when designing or changing database schemas, migrations, persisted-data transformations, indexes, API contracts, or compatibility across consumers and deployed versions.

Prepare and execute deployments with user-confirmed server identity and destination, a usable rollback, health checks, and bounded release-backup retention. Applies to deployment and redeployment, not ordinary local edits or read-only server diagnosis.

Complete the full scope of assigned implementation tasks, including all/every target requests and agent handoffs, through instructions, edits, evaluation, and focused corrections. Excludes read-only questions, research, and reviews unless changes are requested.

Use when building, styling, fixing, or reshaping an interface, component, page, or frontend interaction. Use ui-ux-review for a read-only assessment of existing UI.

Use when diagnosing broken, incorrect, flaky, slow, or resource-heavy behavior, or checking a claimed root cause. Require causal evidence before confirmation; skip routine implementation without a defect.

Use when selecting or performing verification, adding meaningful regression tests, evaluating test evidence, or establishing whether a change meets its acceptance criteria.

Use when reviewing an existing interface for usability, visual hierarchy, responsive layout, accessibility, or interaction problems. Assessment is read-only unless the user requests fixes or redesign.

Research UI references and component options for a requested interface, verify fit and reuse conditions, and turn the findings into a concrete design brief before implementation.

Create or edit Excalidraw workflow, architecture, sequence and state diagrams with editable scene files and visually checked exports. Use when Excalidraw, a reusable diagram artifact or a reference-matched technical diagram is requested.

Explain processes, systems and technical designs with a diagram first, numbered steps, named actors and short plain-English supporting text. Use for how-it-works, workflow or architecture explanations; simple facts and one-step edits usually need only prose.

Plan and create deterministic HTML video compositions with HyperFrames for product promos, explainers, motion graphics or edits to an existing HyperFrames project. Use when HyperFrames or rendered video is requested; excludes ordinary websites, static carousels and standalone presentation decks.