ReddRadar
Topic: claude-code-plugin
1,213 skills in this topic.
-
feature-prioritization
RICE, MoSCoW, Kano, and value-effort prioritization frameworks with scoring methodologies and decision documentation. Use when prioritizing features, evaluating competing initiatives, creating roadmaps, or making build vs defer decisions.
rsmdt/the-startup 248
-
analyze
Discover and document business rules, technical patterns, and system interfaces through iterative analysis
rsmdt/the-startup 248
-
writing-skills
Use when creating new skills, editing existing skills, auditing skill quality, converting skills to markdown conventions, or verifying skills before deployment. Triggers include skill authoring requests, skill review needs, or "the skill doesn't work" complaints.
rsmdt/the-startup 248
-
code-quality-review
Unified code review skill for correctness, design, readability, security, performance, testability, accessibility, and error-handling conventions. Use when reviewing changes, enforcing quality standards, or identifying technical debt.
rsmdt/the-startup 248
-
validate
Validate specifications, implementations, constitution compliance, or understanding. Includes spec quality checks, drift detection, and constitution enforcement.
rsmdt/the-startup 248
-
platform-operations
Unified platform operations guidance for CI/CD pipeline design, deployment strategies, observability, SLI/SLOs, and incident-ready rollouts. Use when building release workflows, production monitoring, or reliability controls.
rsmdt/the-startup 248
-
test
Use when completing implementation, fixing bugs, refactoring code, or any time you need to verify the test suite passes. Also use when tests fail and you hear "pre-existing" or "not my changes" — enforces strict code ownership. Ensures MECE coverage (no overlap, no gaps) and that ALL test categories including E2E are executed.
rsmdt/the-startup 248
-
testing
Writing effective tests and running them successfully. Covers layer-specific mocking rules, test design principles, debugging failures, and flaky test management. Use when writing tests, reviewing test quality, or debugging test failures.
rsmdt/the-startup 248
-
specify-solution
Create and validate solution design documents (SDD). Use when designing architecture, defining interfaces, documenting technical decisions, analyzing system components, or working on solution.md files in .start/specs/. Includes validation checklist, consistency verification, and overlap detection.
rsmdt/the-startup 248
-
review
Analyzes a codebase's modularity imbalances using the Balanced Coupling model and produces a review of design issues. Use when reviewing existing code for coupling problems, assessing architecture quality, identifying distributed monolith risks, or finding areas where changes are unexpectedly expensive.
vladikk/modularity 209
-
document
Produces modularity review documents in both Markdown and HTML formats. Use when writing the final review output from a modularity analysis.
vladikk/modularity 209
-
design
Designs modular high-level architectures from functional requirements and produces design documents for each module. Use when designing a new system, creating architecture documentation, or producing module-level design specs with integration contracts and test specifications.
vladikk/modularity 209
-
balanced-coupling
The Balanced Coupling model for software design. Use when: designing modular architectures, evaluating coupling between components, reviewing code modularity, deciding whether to split or merge modules/services, assessing integration patterns, classifying coupling as balanced or unbalanced, applying DDD strategic and tactical patterns, reasoning about cohesion vs coupling trade-offs, identifying distributed monolith risks, or explaining why a system is hard to change. Provides the three-dimensional framework (integration strength, distance, volatility) and the balance rule for making coupling decisions.
vladikk/modularity 209
-
worktree-execution
Git worktree management for isolated parallel prompt execution. Use when creating isolated environments for prompt comparison or managing worktree lifecycle. Provides creation, cleanup, and orphan detection scripts.
shinpr/rashomon 9
-
recipe-eval-skill
Creates or updates Claude Code skills through interactive dialog, then evaluates effectiveness by parallel execution comparison. Use when creating new skills, updating existing skills, or evaluating skill quality.
shinpr/rashomon 9
-
recipe-eval-prompt
Compares original and optimized prompts by parallel execution in git worktrees. Use when evaluating prompt improvement effects or learning prompt engineering through concrete examples.
shinpr/rashomon 9
-
prompt-optimization
Analyzes and optimizes prompts using BP-001~008 patterns and 3-step flow (detect, optimize, balance). Use when "optimize this prompt", "review prompt quality", "analyze prompt issues", or creating/reviewing rashomon skill content.
shinpr/rashomon 9
-
knowledge-base
Project-specific prompt optimization knowledge management. Use when storing or retrieving learned patterns from comparisons. Provides schema, extraction criteria, capacity management, and retention scoring.
shinpr/rashomon 9
-
recall-write
Write a note to memory with write gate evaluation. Only saves behavior-changing facts.
davegoldblatt/total-recall 192
-
recall-status
Show memory system health — word counts, stale entries, hook status, recommendations.
davegoldblatt/total-recall 192
-
recall-search
Search across all memory tiers (registers, daily logs, archive) for relevant information.
davegoldblatt/total-recall 192
-
recall-init-ids
Add durable IDs to memory entries. Required before /recall-maintain can run.
davegoldblatt/total-recall 192
-
recall-init
Scaffold the Total Recall memory directory structure in this project.
davegoldblatt/total-recall 192
-
recall-forget
Mark memory entries as superseded. Preserves history, does not delete.
davegoldblatt/total-recall 192