Rechercher

PythonReactSEOPDF

Skills IA Blockchain

Découvrez les skills Blockchain, comparez leurs dépôts et consultez leurs instructions.

Catégories: Blockchain

34,057–34,080 sur 87,085

Explorer

GitHub

sentry-setup-metrics

troykelly

Setup Sentry Metrics in any project. Use this when asked to add Sentry metrics, track custom metrics, setup counters/gauges/distributions, or instrument application performance metrics. Supports JavaScript, Typ...

GitHub

agent-identifier

troykelly

This skill should be used when the user asks to "create an agent", "add an agent", "write a subagent", "agent frontmatter", "when to use description", "agent examples", "agent tools", "agent colors", "autonomou...

GitHub

autonomous-orchestration

troykelly

Use when user requests autonomous operation across multiple issues. Orchestrates parallel workers using Task tool, monitors with TaskOutput, handles SLEEP/WAKE cycles, and works until scope is complete without...

GitHub

hook-development

troykelly

This skill should be used when the user asks to "create a hook", "add a PreToolUse/PostToolUse/Stop hook", "validate tool use", "implement prompt-based hooks", "use ${CLAUDE_PLUGIN_ROOT}", "set up event-driven...

GitHub

timescaledb

troykelly

MANDATORY when working with time-series data, hypertables, continuous aggregates, or compression - enforces TimescaleDB 2.24.0 best practices including lightning-fast recompression, UUIDv7 continuous aggregates...

GitHub

database-architecture

troykelly

MANDATORY when designing schemas, writing migrations, creating indexes, or making architectural database decisions - enforces PostgreSQL 18 best practices including AIO, UUIDv7, temporal constraints, and modern...

GitHub

feedback-triage

troykelly

Use when receiving UAT feedback, bug reports, user testing results, stakeholder feedback, QA findings, or any batch of issues to investigate. Investigates each item BEFORE creating issues, classifies by type an...

GitHub

clean-commits

troykelly

Use when committing code - ensures atomic, descriptive commits that leave the codebase in a merge-ready state at every point

GitHub

project-board-enforcement

troykelly

MANDATORY for all work - the project board is THE source of truth. This skill provides verification functions and gates that other skills MUST call. No work proceeds without project board compliance.

GitHub

sentry-setup-logging

troykelly

Setup Sentry Logging in any project. Use this when asked to add Sentry logs, enable structured logging, setup console log capture, or integrate logging with Sentry. Supports JavaScript, TypeScript, Python, Ruby...

GitHub

postgres-rls

troykelly

MANDATORY when touching auth tables, tenant isolation, RLS policies, or multi-tenant database code - enforces Row Level Security best practices and catches common bypass vulnerabilities

GitHub

frontend-design

troykelly

Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, or applications. Generates creative, polished code that avoid...

GitHub

inline-documentation

troykelly

Use when writing code - ensure complete JSDoc, docstrings, and inline comments assuming documentation will be generated from code

GitHub

ipv6-first

troykelly

IPv6 is THE first-class citizen. All code, tests, documentation, and configurations MUST be IPv6-first. IPv4 MAY be added only for legacy support as a second-class citizen.

GitHub

strict-typing

troykelly

Use when writing code in typed languages - enforces full typing with no any/unknown/untyped escapes, even if it requires extra time

GitHub

features-documentation

troykelly

Use when user-facing features change. Ensures features documentation is updated. Pauses work if documentation has drifted, triggering documentation-audit skill.

GitHub

project-status-sync

troykelly

Use to keep GitHub Project fields synchronized with actual work state - updates status, verification, criteria counts, and other project-specific fields

GitHub

initiative-architecture

troykelly

Use for MASSIVE work requests requiring multi-epic planning. Creates research spikes, documents all unknowns and decisions, builds resumable architecture documents, and structures work into epics and milestones...

GitHub

apply-all-findings

troykelly

Use after code review - implement ALL findings; any finding not fixed MUST have tracking issue created; no finding disappears without trace

GitHub

local-service-testing

troykelly

Use when code changes touch database, cache, queue, or other service-dependent components - enforces testing against real local services instead of mocks

GitHub

research-after-failure

troykelly

Use after 2 consecutive failed attempts at solving a problem - STOP guessing and research documentation, codebase, and online resources before resuming

GitHub

issue-prerequisite

troykelly

Use before starting ANY work - hard gate ensuring a GitHub issue exists, creating one if needed through user questioning

GitHub

postgis

troykelly

MANDATORY when working with geographic data, spatial queries, geometry operations, or location-based features - enforces PostGIS 3.6.1 best practices including ST_CoverageClean, SFCGAL 3D functions, and bigint...

Le classement utilise les étoiles du dépôt GitHub indexé. Plusieurs skills peuvent partager ce nombre : ce n’est ni un nombre d’installations ni une note de qualité.

Plus de filtres

Popularité

Tags populaires