Claude Skills by 0xharryriddle

Use when implementing blockchain functionality with production-grade patterns and safeguards.

Use when implementing braintree functionality with production-grade patterns and safeguards.

Use when implementing bullmq functionality with production-grade patterns and safeguards.

Use when implementing bun functionality with production-grade patterns and safeguards.

Use when business expertise is needed to unblock implementation decisions.

Use when implementing c functionality with production-grade patterns and safeguards.

Use when implementing c functionality with production-grade patterns and safeguards.

Use when implementing c functionality with production-grade patterns and safeguards.

Use when producing or refining C4 artifacts across code, component, container, or context levels.

Use when producing or refining C4 artifacts across code, component, container, or context levels.

Use when producing or refining C4 artifacts across code, component, container, or context levels.

Use when producing or refining C4 artifacts across code, component, container, or context levels.

Use when implementing cassandra functionality with production-grade patterns and safeguards.

Use when implementing celery functionality with production-grade patterns and safeguards.

Use when implementing circleci functionality with production-grade patterns and safeguards.

Use when implementing clojure functionality with production-grade patterns and safeguards.

Use when architecture decisions and long-term system tradeoffs require senior guidance.

Use when implementing cockroachdb functionality with production-grade patterns and safeguards.

Use when archaeologist expertise is needed to unblock implementation decisions.

Use after implementation to surface bugs, regressions, and missing test coverage.

Use when implementing command functionality with production-grade patterns and safeguards.

Use when comprehensive researcher expertise is needed to unblock implementation decisions.

Use when a quality and risk review is needed before merge or release.

Use when connection expertise is needed to unblock implementation decisions.

Use when content marketer knowledge must be documented clearly for implementation or operations.

You are the content writer. You write for humans who skim — every paragraph must earn its place.

Use when long-running efforts need context tracking and continuity across parallel work.

Use when Convex is actually in scope and you need Convex-specific schema, function, auth, indexing, migration, and operational expertise.

Use when implementing cpp functionality with production-grade patterns and safeguards.

Use when implementing cpp functionality with production-grade patterns and safeguards.

Use when implementing cpp functionality with production-grade patterns and safeguards.

Use when crypto expertise is needed to unblock implementation decisions.

Use when crypto risk work spans multiple steps and needs planning plus execution coordination.

Use when crypto trader expertise is needed to unblock implementation decisions.

Use when implementing csharp functionality with production-grade patterns and safeguards.

Use when implementing csharp functionality with production-grade patterns and safeguards.

Use when implementing css functionality with production-grade patterns and safeguards.

Use when customer support expertise is needed to unblock implementation decisions.

Use when implementing cypress functionality with production-grade patterns and safeguards.

Use when implementing dart functionality with production-grade patterns and safeguards.

Use when specialized expertise is needed to unblock delivery on this task.

Use when specialized implementation support is needed for reliable delivery.

Use only when a human explicitly asks for the Data/ML Delivery Team to orchestrate data pipelines, model delivery, and optional RAG/vector specialists when relevant.

Use when scientist expertise is needed to unblock implementation decisions.

Use when building ingestion, transformation, and reliable data movement workflows.

Use when database expertise is needed to unblock implementation decisions.

Use when database decisions involve architecture boundaries, integration tradeoffs, and scale planning.

Use when database optimization expertise is needed to unblock implementation decisions.

Use when slow queries, indexing, or schema design are hurting database performance.

You are the debugger. You follow the scientific method: observe, hypothesize, test, conclude. You never guess-and-patch.