troykelly/claude-skills

1

pexels-media Source royalty-free images and videos from Pexels API for design, placeholders, or content. Supports search, curated/…

troykelly/claude-skills

295

2

postgres-rls MANDATORY when touching auth tables, tenant isolation, RLS policies, or multi-tenant database code - enforces Row Lev…

troykelly/claude-skills

205

3

conflict-resolution Use when encountering merge conflicts - handle conflicts cleanly, verify resolution, and maintain code integrity

troykelly/claude-skills

164

4

documentation-audit Use when documentation drift is detected. Comprehensively audits codebase and creates/updates Swagger, features docs,…

troykelly/claude-skills

78

5

database-architecture MANDATORY when designing schemas, writing migrations, creating indexes, or making architectural database decisions - …

troykelly/claude-skills

61

6

postgis MANDATORY when working with geographic data, spatial queries, geometry operations, or location-based features - enfor…

troykelly/claude-skills

57

7

memory-integration Use to maintain context across sessions - integrates episodic-memory for conversation recall and mcp__memory knowledg…

troykelly/claude-skills

56

8

security-review MANDATORY for security-sensitive code changes - OWASP-based security review with dedicated checklist, required before…

troykelly/claude-skills

50

9

acceptance-criteria-verification Use after implementing features - verifies each acceptance criterion with structured testing and posts verification r…

troykelly/claude-skills

43

10

comprehensive-review Use after implementing features - 7-criteria code review with MANDATORY artifact posting to GitHub issue; blocks PR c…

troykelly/claude-skills

41

11

strict-typing Use when writing code in typed languages - enforces full typing with no any/unknown/untyped escapes, even if it requi…

troykelly/claude-skills

33

12

worker-handover Defines context handover format when workers hit turn limit. Posts structured handover to GitHub issue comments enabl…

troykelly/claude-skills

33

13

autonomous-operation Use when starting any work session - establishes autonomous operation mode, overriding token limits and time pressure…

troykelly/claude-skills

32

14

error-recovery Use when encountering failures - assess severity, preserve evidence, execute rollback decision tree, and verify post-…

troykelly/claude-skills

32

15

issue-driven-development Use for any development work - the master 13-step coding process that orchestrates all other skills, ensuring GitHub …

troykelly/claude-skills

32

16

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

troykelly/claude-skills

30

17

branch-discipline Use before any code changes - hard gate ensuring work never happens on main branch, with proper feature branch creati…

troykelly/claude-skills

28

18

local-service-testing Use when code changes touch database, cache, queue, or other service-dependent components - enforces testing against …

troykelly/claude-skills

28

19

timescaledb MANDATORY when working with time-series data, hypertables, continuous aggregates, or compression - enforces Timescale…

troykelly/claude-skills

28

20

autonomous-orchestration Use when user requests autonomous operation across multiple issues. Orchestrates parallel workers using Task tool, mo…

troykelly/claude-skills

27

21

issue-decomposition Use when an issue is too large for a single task - breaks into linked sub-issues with full documentation, ensuring ma…

troykelly/claude-skills

26

22

style-guide-adherence Use when writing code - follow Google style guides where available, otherwise follow established best practices for t…

troykelly/claude-skills

26

23

tdd-full-coverage Use when implementing features or fixes - test-driven development with RED-GREEN-REFACTOR cycle and full code coverag…

troykelly/claude-skills

26

24

verification-before-merge Use before merging PR - final gate ensuring all tests pass, review complete, CI green, and acceptance criteria verifi…

troykelly/claude-skills

26

25

inclusive-language Use when writing code, documentation, or comments - always use accessible and respectful terminology

troykelly/claude-skills

25

26

ipv6-first IPv6 is THE first-class citizen. All code, tests, documentation, and configurations MUST be IPv6-first. IPv4 MAY be a…

troykelly/claude-skills

25

27

pre-work-research Use before starting implementation - research repository documentation, codebase patterns, and external resources to …

troykelly/claude-skills

25

28

worker-dispatch Use to spawn isolated worker processes for autonomous issue work. Uses Task tool with run_in_background for parallel …

troykelly/claude-skills

25

29

apply-all-findings Use after code review - implement ALL findings; any finding not fixed MUST have tracking issue created; no finding di…

troykelly/claude-skills

24

30

review-scope Use before code review - determine if change is minor (review new code only) or major (review impacted code too)

troykelly/claude-skills

24

31

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

troykelly/claude-skills

23

32

research-after-failure Use after 2 consecutive failed attempts at solving a problem - STOP guessing and research documentation, codebase, an…

troykelly/claude-skills

23

33

worker-protocol Defines behavior protocol for spawned worker agents. Injected into worker prompts. Covers startup, progress reporting…

troykelly/claude-skills

23

34

epic-management Use for LARGE work requiring feature-level grouping. Creates epic tracking issues, manages related issues under a com…

troykelly/claude-skills

22

35

features-documentation Use when user-facing features change. Ensures features documentation is updated. Pauses work if documentation has dri…

troykelly/claude-skills

22

36

feedback-triage Use when receiving UAT feedback, bug reports, user testing results, stakeholder feedback, QA findings, or any batch o…

troykelly/claude-skills

22

37

milestone-management Use for time-based grouping of issues into delivery phases. Creates, updates, and tracks milestones, associates issue…

troykelly/claude-skills

22

38

review-gate HARD GATE before PR creation - verifies review artifact exists in issue comments, all findings addressed or tracked, …

troykelly/claude-skills

22

39

work-intake Entry point for ALL work requests - triages scope from trivial to massive, asks clarifying questions, and routes to a…

troykelly/claude-skills

22

40

github-api-cache MANDATORY before any GitHub project operations - caches project metadata to prevent rate limit exhaustion. Called by …

troykelly/claude-skills

21

41

pr-creation Use after completing implementation - create pull request with complete documentation, proper labels, linked issues, …

troykelly/claude-skills

21

42

project-board-enforcement MANDATORY for all work - the project board is THE source of truth. This skill provides verification functions and gat…

troykelly/claude-skills

21

43

session-start Use at the beginning of every work session - establishes context by checking GitHub project state, reading memory, ve…

troykelly/claude-skills

21

44

api-documentation Use when API code changes (routes, endpoints, schemas). Enforces Swagger/OpenAPI sync. Pauses work if documentation h…

troykelly/claude-skills

20

45

deferred-finding Use when a review finding cannot be fixed in current PR - creates properly documented tracking issue with full contex…

troykelly/claude-skills

20

46

environment-bootstrap Use for development environment setup - create and maintain init scripts, run smoke tests, ensure consistent environm…

troykelly/claude-skills

20

47

initiative-architecture Use for MASSIVE work requests requiring multi-epic planning. Creates research spikes, documents all unknowns and deci…

troykelly/claude-skills

20

48

issue-lifecycle Use throughout all work - ensures GitHub issues are updated continuously as work happens, not batched at the end

troykelly/claude-skills

20

49

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

troykelly/claude-skills

20

50

no-deferred-work Use during all development - no TODOs, no FIXMEs, no "we'll add this later"; do it now or get explicit deferral permi…

troykelly/claude-skills

20