troykelly
@troykelly
Public Skills
session-start
by troykelly
Use at the beginning of every work session - establishes context by checking GitHub project state, reading memory, verifying environment, and orienting before starting work
research-after-failure
by troykelly
Use after 2 consecutive failed attempts at solving a problem - STOP guessing and research documentation, codebase, and online resources before resuming
review-scope
by troykelly
Use before code review - determine if change is minor (review new code only) or major (review impacted code too)
pr-test-analyzer
by troykelly
Use when asked to evaluate PR test coverage or explicitly asked to run the pr-test-analyzer subagent.
postgis
by 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 topology
api-documentation
by troykelly
Use when API code changes (routes, endpoints, schemas). Enforces Swagger/OpenAPI sync. Pauses work if documentation has drifted, triggering documentation-audit skill.
no-deferred-work
by troykelly
Use during all development - no TODOs, no FIXMEs, no "we'll add this later"; do it now or get explicit deferral permission
branch-discipline
by troykelly
Use before any code changes - hard gate ensuring work never happens on main branch, with proper feature branch creation from correct base
conflict-resolution
by troykelly
Use when encountering merge conflicts - handle conflicts cleanly, verify resolution, and maintain code integrity
security-review
by troykelly
MANDATORY for security-sensitive code changes - OWASP-based security review with dedicated checklist, required before PR for auth, input handling, API, database, or credential code
inclusive-language
by troykelly
Use when writing code, documentation, or comments - always use accessible and respectful terminology
database-architecture
by 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 indexing strategies
postgres-rls
by 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
database-architecture
by 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 indexing strategies
postgis
by 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 topology
timescaledb
by 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, and Direct Compress
environment-bootstrap
by troykelly
Use for development environment setup - create and maintain init scripts, run smoke tests, ensure consistent environment across sessions
features-documentation
by troykelly
Use when user-facing features change. Ensures features documentation is updated. Pauses work if documentation has drifted, triggering documentation-audit skill.
no-deferred-work
by troykelly
Use during all development - no TODOs, no FIXMEs, no "we'll add this later"; do it now or get explicit deferral permission
memory-integration
by troykelly
Use to maintain context across sessions - integrates episodic-memory for conversation recall and mcp__memory knowledge graph for persistent facts
error-recovery
by troykelly
Use when encountering failures - assess severity, preserve evidence, execute rollback decision tree, and verify post-recovery state
review-scope
by troykelly
Use before code review - determine if change is minor (review new code only) or major (review impacted code too)
pr-creation
by troykelly
Use after completing implementation - create pull request with complete documentation, proper labels, linked issues, and verification summary
initiative-architecture
by 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.