Skill Builder

01 · DEFINE THE JOB

Name & trigger

Skill name

Lowercase letters, numbers, and hyphens. For example: linux-log-review.

What does it do, and when should it be used?When should it not be used? (optional)Inputs, context, and resources (optional)

02 · CHOOSE YOUR INGREDIENTS

138 detailed options

Mix categories. Select only what serves this skill’s job; compatible instructions work better than selecting everything.

Search options

0 selected · 38 matching options

Languages & platforms

PythonFollow the project’s Python version, typing conventions, and environment management.TypeScriptUse TypeScript types to model constraints; avoid unneeded any casts.JavaScriptFollow existing JavaScript module, async, and browser compatibility conventions.RustUse idiomatic Rust ownership and error handling; justify unsafe code if needed.GoUse idiomatic Go, explicit error handling, and context cancellation where appropriate.Java / KotlinMatch the project’s JVM version, build system, and Java or Kotlin conventions.C# / .NETFollow the project’s .NET version, nullable types, and dependency-injection conventions.C / C++Check memory ownership, bounds, lifetime, and compiler compatibility.SQLUse parameterized queries and inspect query plans for performance-sensitive database work.ReactKeep React components focused and handle loading, empty, error, and success states.Next.jsRespect the project’s server/client boundaries, routing, and caching behavior.VueFollow the existing Vue composition and state-management patterns.Node.js APIsValidate API inputs and use consistent status codes and error responses.Django / FastAPIFollow the existing Python web framework’s routing, validation, and authentication patterns.Mobile appsAccount for platform navigation, accessibility, permissions, and offline behavior.CLI toolsProvide clear help, predictable exit codes, and useful errors without leaking secrets.

Engineering workflow

Read before editingInspect relevant code and project instructions before proposing edits.Focused changesKeep changes scoped to the requested behavior and preserve unrelated work.Reproduce bugsEstablish a reproducible failure and identify its cause before fixing it.Unit testsTest meaningful behavior and edge cases with focused unit tests.Integration testsVerify component boundaries, database behavior, and API contracts with integration tests.End-to-end testsExercise the main user journey and important failure paths in end-to-end checks.Regression coverageAdd a regression check that would fail for the original bug.Behavior-preserving refactoringRefactor in small steps and verify that public behavior stays compatible.Code reviewPrioritize actionable correctness, security, and maintainability findings with file references.Performance profilingMeasure bottlenecks before optimizing and compare before/after results.AccessibilityCheck labels, keyboard access, focus behavior, contrast, and responsive layouts.Secure implementationReview trust boundaries, authorization, input validation, and secret handling.Dependency disciplinePrefer existing dependencies; explain the need before adding a new one.Database migrationsUse additive migrations where possible and describe compatibility and rollback considerations.Git hygieneInspect the diff, stage only intended files, and preserve other contributors’ changes.Commit messagesWrite concise commit messages describing the problem and resulting behavior.Pull-request summarySummarize the problem, solution, verification, and remaining limitations for reviewers.DocumentationUpdate examples and documentation when public behavior or setup changes.CI failuresRead the failing CI logs, isolate the failure, and rerun relevant checks after fixing it.API compatibilityPreserve documented contracts and explicitly identify breaking changes.Logging & observabilityAdd useful diagnostics while redacting credentials and personal data.Final diff reviewReview the final diff for accidental changes and report exactly what was verified.

03 · SET THE SEQUENCE

Workflow steps

Edit, reorder, or remove steps. The exported skill follows this order.

Step 1

Step 2

Step 3

Your own rules, output requirements, or examples

Name & trigger

138 detailed options

Workflow steps

My saved skills