ReddRadar
Topic: skills
17,247 skills in this topic.
-
check-plan
Audit implementation progress against a plan, verify completed work, identify remaining tasks, and validate quality. Use when user asks to check plan status, verify implementation, see what's left to do, or validate plan completion.
aiskillstore/marketplace 232
-
chrome-devtools
Control Chrome browser programmatically using chrome-devtools-mcp. Use when user asks to automate Chrome, debug web pages, take screenshots, evaluate JavaScript, inspect network requests, or interact with browser DevTools. Also use when asked about browser automation, web scraping, or testing websites.
aiskillstore/marketplace 232
-
comprehensive-code-review
This skill should be used when reviewing pull requests, performing comprehensive code review, analyzing code changes before merge, or when the user asks for thorough/ultra-critical code review. Performs EXTREMELY CRITICAL 6-pass analysis identifying runtime failures, code consistency issues, architectural problems, environment compatibility risks, and verification strategies. Posts structured review as GitHub PR comment. Use when user asks to "review PR", "review this code", "review changes", "check this PR", "analyze PR", "post review", or for Phase 3 of devflow. Supports parallel review mode with multiplier (code-review-3, code-review 6X) for consensus-based reviews. This is an ultra-critical reviewer that does not let things slip and desires only perfection.
aiskillstore/marketplace 232
-
create-mcp-skill
Create a new skill that uses an MCP server, following best practices from the MCP CLI guide. Use when user wants to create a skill for a new MCP server or integrate MCP functionality into a skill.
aiskillstore/marketplace 232
-
create-plan
Create comprehensive implementation plan in .plans directory based on analysis or report. Use when user asks to create a plan, plan implementation, design a solution, or structure work for a feature/refactor/fix.
aiskillstore/marketplace 232
-
create-pr
Create a PR for this branch. ALWAYS links related issues and uses closing keywords to auto-close them on merge.
aiskillstore/marketplace 232
-
create-skill
This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.
aiskillstore/marketplace 232
-
create-subagent
This skill should be used when creating custom subagents for Claude Code, configuring specialized AI assistants, or when the user asks about agent creation, agent configuration, or delegating tasks to subagents. Covers both file-based agents and Task tool invocation.
aiskillstore/marketplace 232
-
delphi
This skill should be used when the user asks to "use delphi", "ask delphi", or wants multiple parallel oracle investigations of the same question to discover divergent insights. Delphi launches multiple oracle agents simultaneously with identical prompts, allowing them to independently explore and potentially discover different paths, clues, and solutions. Results are saved to .oracle/[topic]/ and synthesized into a final document.
aiskillstore/marketplace 232
-
design-spec-extraction
Extract comprehensive JSON design specifications from visual sources including Figma exports, UI mockups, screenshots, or live website captures. Produces W3C DTCG-compliant output with component trees, suitable for code generation, design documentation, and developer handoff.
aiskillstore/marketplace 232
-
devflow
End-to-end agent development process. Use when coordinating work, dispatching agents, or reviewing PRs.
aiskillstore/marketplace 232
-
dispatching-parallel-agents
Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies
aiskillstore/marketplace 232
-
executing-plans
Use when you have a written implementation plan to execute in a separate session with review checkpoints
aiskillstore/marketplace 232
-
file-name-wizard
Audit all filename and naming conventions in the codebase against CLAUDE.md standards and common patterns. Use when user asks to check naming conventions, audit filenames, find naming inconsistencies, or validate file naming patterns.
aiskillstore/marketplace 232
-
finishing-a-development-branch
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup
aiskillstore/marketplace 232
-
gh-ticket
Create or update comprehensive GitHub issues that capture ALL context, requirements, and implementation details. Use when creating or updating tickets, issues, feature requests, or bug reports. Ensures no context is lost between ticket creation and implementation - the moment you ask for a ticket, there's maximum context available that will be lost if not captured now.
aiskillstore/marketplace 232
-
obsidian-plan-wiki
This skill should be used when creating or working with modular project plans stored as Obsidian-compatible markdown wikis. Use when the user asks to create a plan, roadmap, or documentation system that needs to be navigable in Obsidian, or when working with existing plan wikis that use the %% [ ] %% task tracking format.
aiskillstore/marketplace 232
-
receiving-code-review
Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation
aiskillstore/marketplace 232
-
requesting-code-review
Use when completing tasks, implementing major features, or before merging to verify work meets requirements
aiskillstore/marketplace 232
-
review-changes
Code review of current git changes, compare to related plan if exists, identify bad engineering, over-engineering, or suboptimal solutions. Use when user asks to review changes, check git diff, validate implementation quality, or assess code changes.
aiskillstore/marketplace 232
-
subagent-driven-development
Use when executing implementation plans with independent tasks in the current session
aiskillstore/marketplace 232
-
superpower-zustand
MANDATORY for creating Zustand stores. This skill is required when users request state management, creating stores, or mention Zustand. Do NOT create Zustand stores without this skill - all stores must use the required StoreBuilder pattern with immer middleware and factory pattern separation
aiskillstore/marketplace 232
-
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
aiskillstore/marketplace 232
-
test-driven-development
Use when implementing any feature or bugfix, before writing implementation code
aiskillstore/marketplace 232