All authors
Claude Skills by troykelly
github.com/troykelly130 skills0 installs175 views
- Agent DevelopmentThis 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", "autonomous agent", or needs guidance on agent structure, system prompts, triggering conditions, or agent development best practices for Claude Code plugins.Votes: 0GitHub stars: 11
- Frontend DesignCreate 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 avoids generic AI aesthetics.Votes: 0GitHub stars: 11
- Hook DevelopmentThis 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 automation", "block dangerous commands", or mentions hook events (PreToolUse, PostToolUse, Stop, SubagentStop, SessionStart, SessionEnd, UserPromptSubmit, PreCompact, Notification). Provides comprehensive guidance for creating and implementing Claude Code plugin hooks with focus on adva...Votes: 0GitHub stars: 11
- Sentry Code ReviewAnalyze and resolve Sentry comments on GitHub Pull Requests. Use this when asked to review or fix issues identified by Sentry in PR comments. Can review specific PRs by number or automatically find recent PRs with Sentry feedback.Votes: 0GitHub stars: 11
- Sentry Setup Ai MonitoringSetup Sentry AI Agent Monitoring in any project. Use this when asked to add AI monitoring, track LLM calls, monitor AI agents, or instrument OpenAI/Anthropic/Vercel AI/LangChain/Google GenAI. Automatically detects installed AI SDKs and configures the appropriate Sentry integration.Votes: 0GitHub stars: 11
- Sentry Setup LoggingSetup 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, React, Next.js, and other frameworks.Votes: 0GitHub stars: 11
- Sentry Setup MetricsSetup 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, TypeScript, Python, React, Next.js, and Node.js.Votes: 0GitHub stars: 11
- Sentry Setup TracingSetup Sentry Tracing (Performance Monitoring) in any project. Use this when asked to add performance monitoring, enable tracing, track transactions/spans, or instrument application performance. Supports JavaScript, TypeScript, Python, Ruby, React, Next.js, and Node.js.Votes: 0GitHub stars: 11
- Skill DevelopmentThis skill should be used when the user wants to "create a skill", "add a skill to plugin", "write a new skill", "improve skill description", "organize skill content", or needs guidance on skill structure, progressive disclosure, or skill development best practices for Claude Code plugins.Votes: 0GitHub stars: 11
- Acceptance Criteria VerificationUse after implementing features - verifies each acceptance criterion with structured testing and posts verification reports to the GitHub issueVotes: 0GitHub stars: 11
- Api DocumentationUse when API code changes (routes, endpoints, schemas). Enforces Swagger/OpenAPI sync. Pauses work if documentation has drifted, triggering documentation-audit skill.Votes: 0GitHub stars: 11
- Apply All FindingsUse after code review - implement ALL findings; any finding not fixed MUST have tracking issue created; no finding disappears without traceVotes: 0GitHub stars: 11
- Autonomous OperationUse when starting any work session - establishes autonomous operation mode, overriding token limits and time pressure to work until goal is achievedVotes: 0GitHub stars: 11
- Autonomous OrchestrationUse 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 user intervention.Votes: 0GitHub stars: 11
- Branch DisciplineUse before any code changes - hard gate ensuring work never happens on main branch, with proper feature branch creation from correct baseVotes: 0GitHub stars: 11
- Ci MonitoringUse after creating PR - monitor CI pipeline, resolve failures, address review feedback, and merge when all gates passVotes: 0GitHub stars: 11
- Clean CommitsUse when committing code - ensures atomic, descriptive commits that leave the codebase in a merge-ready state at every pointVotes: 0GitHub stars: 11
- Comprehensive ReviewUse after implementing features - 7-criteria code review with MANDATORY artifact posting to GitHub issue; blocks PR creation until completeVotes: 0GitHub stars: 11
- Conflict ResolutionUse when encountering merge conflicts - handle conflicts cleanly, verify resolution, and maintain code integrityVotes: 0GitHub stars: 11
- Database ArchitectureMANDATORY 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 strategiesVotes: 0GitHub stars: 11
- Deferred FindingUse when a review finding cannot be fixed in current PR - creates properly documented tracking issue with full context, linked to parent, following full issue-driven-development processVotes: 0GitHub stars: 11
- Documentation AuditUse when documentation drift is detected. Comprehensively audits codebase and creates/updates Swagger, features docs, and general documentation to achieve full sync.Votes: 0GitHub stars: 11
- Environment BootstrapUse for development environment setup - create and maintain init scripts, run smoke tests, ensure consistent environment across sessionsVotes: 0GitHub stars: 11
- Epic ManagementUse for LARGE work requiring feature-level grouping. Creates epic tracking issues, manages related issues under a common label, tracks epic progress, and coordinates with milestones.Votes: 0GitHub stars: 11
- Error RecoveryUse when encountering failures - assess severity, preserve evidence, execute rollback decision tree, and verify post-recovery stateVotes: 0GitHub stars: 11
- Features DocumentationUse when user-facing features change. Ensures features documentation is updated. Pauses work if documentation has drifted, triggering documentation-audit skill.Votes: 0GitHub stars: 11
- Feedback TriageUse 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 and priority, creates well-formed GitHub issues with proper project board integration.Votes: 0GitHub stars: 11
- Github Api CacheMANDATORY before any GitHub project operations - caches project metadata to prevent rate limit exhaustion. Called by session-start. Other skills MUST use cached data.Votes: 0GitHub stars: 11
- Inclusive LanguageUse when writing code, documentation, or comments - always use accessible and respectful terminologyVotes: 0GitHub stars: 11
- Initiative ArchitectureUse 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.Votes: 0GitHub stars: 11
- Inline DocumentationUse when writing code - ensure complete JSDoc, docstrings, and inline comments assuming documentation will be generated from codeVotes: 0GitHub stars: 11
- 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