Sponsored by

Find leads on Reddit on auto pilot

Topic: llm

10,059 skills in this topic.

brainstorming Collaborative design methodology for creative work. Use before research or planning when requirements are unclear, multiple approaches exist, or the idea needs exploration. Refines ideas through progressive questioning.
bostonaholic/rpikit 8
documenting-decisions Record architectural decisions as ADRs from design documents. Use after brainstorming or planning to capture what was decided, why, and what alternatives were considered. Produces sequentially numbered ADR files in docs/decisions/.
bostonaholic/rpikit 8
finishing-work Structured completion workflow for implementation work. Use when implementation is complete, all tests pass, and you need to decide how to integrate the work. Guides merge, PR creation, or cleanup decisions.
bostonaholic/rpikit 8
git-worktrees Isolated workspace creation for parallel development work. Use when starting feature work that needs isolation from the current workspace. Creates git worktrees with proper setup and safety verification.
bostonaholic/rpikit 8
implementing-plans Disciplined plan execution with checkpoint validation, progress tracking, and verification at each step. Follows an approved plan strictly, running verification criteria before proceeding.
bostonaholic/rpikit 8
parallel-agents Concurrent agent dispatch for independent problems. Use when facing multiple independent tasks that can be worked on simultaneously. Reduces total time by parallelizing work that has no shared state.
bostonaholic/rpikit 8
receiving-code-review Verification-first approach to code review feedback. Use when receiving review comments during the implement phase. Evaluate suggestions rigorously before implementing - no performative agreement.
bostonaholic/rpikit 8
research-plan-implement End-to-end Research-Plan-Implement pipeline using parallel subagents. Each phase (research, plan, implement) runs in its own context window with file artifacts as the communication channel between phases.
bostonaholic/rpikit 8
researching-codebase Thorough codebase exploration that builds understanding through collaborative dialogue. Investigates architecture, patterns, and implementation details before planning or making changes.
bostonaholic/rpikit 8
reviewing-code Code review methodology for evaluating implementation changes. Use when reviewing code changes for quality, design, correctness, and maintainability. Focuses on changes made during implementation using Conventional Comments for clear, actionable feedback.
bostonaholic/rpikit 8
security-review Security review methodology for evaluating implementation changes. Use when reviewing code changes for vulnerabilities, insecure patterns, and security best practices. Focuses on changes made during implementation rather than full codebase audits.
bostonaholic/rpikit 8
synthesizing-research Consolidate multiple parallel research documents into a single unified report. Produces a self-contained document that a reader with no prior context can understand completely.
bostonaholic/rpikit 8
systematic-debugging Root cause investigation methodology for bugs and failures. Use when encountering test failures, unexpected behavior, or errors during research or implement phases. Find the cause before attempting fixes.
bostonaholic/rpikit 8
test-driven-development Rigorous TDD methodology enforcing RED-GREEN-REFACTOR discipline. Use when implementing features or fixing bugs during the implement phase. Tests must be written before production code - no exceptions.
bostonaholic/rpikit 8
verification-before-completion Evidence-before-claims discipline for implementation completion. Use before claiming any work is complete, fixed, or passing. Run verification commands and confirm output before making success claims.
bostonaholic/rpikit 8
writing-plans Transform research findings into actionable implementation plans with granular steps, verification criteria, and stakes-based enforcement. Plans serve as contracts between human and AI.
bostonaholic/rpikit 8
context-recovery Recover lost context after session compaction or when information from previous sessions is needed. Use when: user mentions "what were we working on", "I lost context", "before the compact", "previous session", or asks about decisions/implementations/discussions that aren't in current context. Also use proactively when you notice references to prior work you lack context for.
omgpointless/aspy 1
papi This skill should be used when the user wants to interact with their paper database — listing papers, searching content, showing paper details, adding papers, or exporting context. Matches queries like "search papers for X", "add this arXiv paper", "show equations from paper Y", "what papers do I have". Prefer CLI over MCP RAG tools for direct lookups.
hummat/paperpipe 9
papi-ask Query papers using RAG (PaperQA2 or LEANN). Use when user needs synthesized answers from papers, asks "what does paper X say about Y", or needs cited responses.
hummat/paperpipe 9
papi-compare Compare papers for a decision. Use when user asks "which paper should I use", "compare approaches", or needs to choose between methods/algorithms.
hummat/paperpipe 9
papi-curate Create project notes from papers. Use when user wants to document paper findings, create implementation notes, or summarize papers for a project.
hummat/paperpipe 9
papi-ground Ground responses in paper excerpts with citations. Use when user wants cited claims, quotes, or needs to avoid hallucination about paper content.
hummat/paperpipe 9
papi-init Setup paperpipe agent integration. Use when user wants to add papi to a project's CLAUDE.md/AGENTS.md or initialize paper support.
hummat/paperpipe 9
papi-verify Verify code against paper. Use when user asks "does this match the paper", "check my implementation", or is implementing equations/algorithms from literature.
hummat/paperpipe 9