All authors

Claude Skills by troykelly
github.com/troykelly130 skills3 installs197 views
- Ipv6 FirstIPv6 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.Votes: 0GitHub stars: 11
- Issue DecompositionUse when an issue is too large for a single task - breaks into linked sub-issues with full documentation, ensuring manageable work unitsVotes: 0GitHub stars: 11
- Issue Driven DevelopmentUse for any development work - the master 13-step coding process that orchestrates all other skills, ensuring GitHub issue tracking, proper branching, TDD, code review, and CI verificationVotes: 0GitHub stars: 11
- Issue LifecycleUse throughout all work - ensures GitHub issues are updated continuously as work happens, not batched at the endVotes: 0GitHub stars: 11
- Issue PrerequisiteUse before starting ANY work - hard gate ensuring a GitHub issue exists, creating one if needed through user questioningVotes: 0GitHub stars: 11
- Local Service TestingUse when code changes touch database, cache, queue, or other service-dependent components - enforces testing against real local services instead of mocksVotes: 0GitHub stars: 11
- Memory IntegrationUse to maintain context across sessions - integrates episodic-memory for conversation recall and mcp__memory knowledge graph for persistent factsVotes: 0GitHub stars: 11
- Milestone ManagementUse for time-based grouping of issues into delivery phases. Creates, updates, and tracks milestones, associates issues and epics, monitors progress toward milestone completion.Votes: 0GitHub stars: 11
- No Deferred WorkUse during all development - no TODOs, no FIXMEs, no "we'll add this later"; do it now or get explicit deferral permissionVotes: 0GitHub stars: 11
- Pexels MediaSource royalty-free images and videos from Pexels API for design, placeholders, or content. Supports search, curated/popular content, collections, multiple resolutions, and ALWAYS creates detailed sidecar metadata files.Votes: 0GitHub stars: 11
- PostgisMANDATORY 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 topologyVotes: 0GitHub stars: 11
- Postgres RlsMANDATORY when touching auth tables, tenant isolation, RLS policies, or multi-tenant database code - enforces Row Level Security best practices and catches common bypass vulnerabilitiesVotes: 0GitHub stars: 11
- Pr CreationUse after completing implementation - create pull request with complete documentation, proper labels, linked issues, and verification summaryVotes: 0GitHub stars: 11
- Pre Work ResearchUse before starting implementation - research repository documentation, codebase patterns, and external resources to inform the approachVotes: 0GitHub stars: 11
- Project Board EnforcementMANDATORY 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.Votes: 0GitHub stars: 11
- Project Status SyncUse to keep GitHub Project fields synchronized with actual work state - updates status, verification, criteria counts, and other project-specific fieldsVotes: 0GitHub stars: 11
- Research After FailureUse after 2 consecutive failed attempts at solving a problem - STOP guessing and research documentation, codebase, and online resources before resumingVotes: 0GitHub stars: 11
- Review GateHARD GATE before PR creation - verifies review artifact exists in issue comments, all findings addressed or tracked, blocks PR creation if requirements not metVotes: 0GitHub stars: 11
- Review ScopeUse before code review - determine if change is minor (review new code only) or major (review impacted code too)Votes: 0GitHub stars: 11
- Security ReviewMANDATORY for security-sensitive code changes - OWASP-based security review with dedicated checklist, required before PR for auth, input handling, API, database, or credential codeVotes: 0GitHub stars: 11
- Session StartUse at the beginning of every work session - establishes context by checking GitHub project state, reading memory, verifying environment, and orienting before starting workVotes: 0GitHub stars: 11
- Strict TypingUse when writing code in typed languages - enforces full typing with no any/unknown/untyped escapes, even if it requires extra timeVotes: 0GitHub stars: 11
- Style Guide AdherenceUse when writing code - follow Google style guides where available, otherwise follow established best practices for the languageVotes: 0GitHub stars: 11
- Tdd Full CoverageUse when implementing features or fixes - test-driven development with RED-GREEN-REFACTOR cycle and full code coverage requirementVotes: 0GitHub stars: 11
- TimescaledbMANDATORY 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 CompressVotes: 0GitHub stars: 11
- Verification Before MergeUse before merging PR - final gate ensuring all tests pass, review complete, CI green, and acceptance criteria verifiedVotes: 0GitHub stars: 11
- Work IntakeEntry point for ALL work requests - triages scope from trivial to massive, asks clarifying questions, and routes to appropriate planning skills. Use this when receiving any new work request.Votes: 0GitHub stars: 11
- Worker DispatchUse to spawn isolated worker processes for autonomous issue work. Creates git worktrees, constructs worker prompts, and handles worker lifecycle.Votes: 0GitHub stars: 11
- Worker HandoverDefines context handover format when workers hit turn limit. Posts structured handover to GitHub issue comments enabling replacement workers to continue seamlessly.Votes: 0GitHub stars: 11
- Worker ProtocolDefines behavior protocol for spawned worker agents. Injected into worker prompts. Covers startup, progress reporting, exit conditions, and handover preparation.Votes: 0GitHub stars: 11