Claude Skills by caongocquy

Invoke a specific Showdar flagship skill explicitly

Use when resolving an observed defect end-to-end, adaptively sequencing understand, debug, build, test, and review stages based on whether root cause is already proven.

Use when implementing or refactoring an agreed application change within existing architecture and contracts.

Use when observed behavior fails through crashes, regressions, build failures, races, networking, memory, or performance issues.

Use when product UI needs design direction, UX decisions, responsive layout, accessibility, or visual polish.

Use when implementing a complete feature end-to-end, adaptively sequencing understand, requirements, plan, design, build, test, and review stages based on existing definition.

Use when performing local Git inspection, staging, commits, branch integration, conflicts, cleanup, or explicitly requested remote Git actions.

Use when investigating and recovering from an active operational incident, adaptively sequencing understand, debug, recover, verification, and ops stages with strict mutation authority.

Use when inspecting or changing CI/CD, containers, environments, deployment, observability, rollback, or runtime operations.

Use when agreed behavior needs a bounded implementation plan, change surface, task order, risks, or verification steps.

Use when planning QA/QC scenarios, risk coverage, regression scope, compatibility checks, or bug-report evidence.

Use when interrupted or partial engineering work must be reconstructed from repository evidence before continuing.

Use when preparing, validating, or executing a release lifecycle, adaptively sequencing quality, security, ship, and ops stages with strict authority boundaries.

Use when product or business input needs explicit behavior, rules, acceptance criteria, assumptions, or open decisions.

Use when reviewing code or diffs for general correctness, architecture, performance, maintainability, or tests.

Use when assessing threat models, attack surfaces, trust boundaries, auth/authz, secrets, exposure, or exploitability.

Use when checking whether a change, artifact, or release is ready for handoff or external release.

Use when choosing or implementing automated tests for behavior, regressions, integration, E2E, or coverage.

Use when mapping an unfamiliar repository, architecture, dependencies, or impact before deciding what to change.

Use when upgrading dependencies, frameworks, runtimes, or native platforms and compatibility or rollback risk matters.