Sponsored by

Find leads on Reddit on auto pilot

Topic: cursor

7,943 skills in this topic.

decision-log Document major decisions made
davekilleen/Dex 302
variance-analysis Compare actuals vs budget with narrative
davekilleen/Dex 302
close-status Month-end close checklist and blockers
davekilleen/Dex 302
board-prep Compile financial narrative for board meeting
davekilleen/Dex 302
tech-debt Review and prioritize technical debt
davekilleen/Dex 302
health-score Review account health across portfolio
davekilleen/Dex 302
expansion-opportunities Identify upsell/cross-sell opportunities
davekilleen/Dex 302
pi-tools View and manage Pi-built extensions synced to Dex. Shows available tools, commands, and sync status.
davekilleen/Dex 302
incident-review Post-mortem on incidents
davekilleen/Dex 302
pi Route tasks to Pi for comparison testing. Toggle Pi mode or run specific commands through Pi.
davekilleen/Dex 302
commitment-extractor Extract and track commitments from meeting notes - who promised what to whom, with deadlines and status tracking.
davekilleen/Dex 302
architecture-decision Document architectural choices
davekilleen/Dex 302
design-system-audit Review design system usage and gaps
davekilleen/Dex 302
design-review Prepare for or document design review
davekilleen/Dex 302
renewal-prep Prepare for upcoming renewal
davekilleen/Dex 302
rclone Upload, sync, and manage files across cloud storage providers using rclone. Use when uploading files (images, videos, documents) to S3, Cloudflare R2, Backblaze B2, Google Drive, Dropbox, or any S3-compatible storage. Triggers on "upload to S3", "sync to cloud", "rclone", "backup files", "upload video/image to bucket", or requests to transfer files to remote storage.
davekilleen/Dex 302
git-worktree This skill manages Git worktrees for isolated parallel development. It handles creating, listing, switching, and cleaning up worktrees with a simple interactive interface, following KISS principles.
davekilleen/Dex 302
file-todos This skill should be used when managing the file-based todo tracking system in the todos/ directory. It provides workflows for creating todos, managing status and dependencies, conducting triage, and integrating with slash commands and code review processes.
davekilleen/Dex 302
every-style-editor This skill should be used when reviewing or editing copy to ensure adherence to Every's style guide. It provides a systematic line-by-line review process for grammar, punctuation, mechanics, and style guide compliance.
davekilleen/Dex 302
dspy-ruby This skill should be used when working with DSPy.rb, a Ruby framework for building type-safe, composable LLM applications. Use this when implementing predictable AI features, creating LLM signatures and modules, configuring language model providers (OpenAI, Anthropic, Gemini, Ollama), building agent systems with tools, optimizing prompts, or testing LLM-powered functionality in Ruby applications.
davekilleen/Dex 302
dhh-rails-style This skill should be used when writing Ruby and Rails code in DHH's distinctive 37signals style. It applies when writing Ruby code, Rails applications, creating models, controllers, or any Ruby file. Triggers on Ruby/Rails code generation, refactoring requests, code review, or when the user mentions DHH, 37signals, Basecamp, HEY, or Campfire style. Embodies REST purity, fat models, thin controllers, Current attributes, Hotwire patterns, and the "clarity over cleverness" philosophy.
davekilleen/Dex 302
creating-agent-skills Expert guidance for creating, writing, and refining Claude Code Skills. Use when working with SKILL.md files, authoring new skills, improving existing skills, or understanding skill structure and best practices.
davekilleen/Dex 302
compound-docs Capture solved problems as categorized documentation with YAML frontmatter for fast lookup
davekilleen/Dex 302
brainstorming This skill should be used before implementing features, building components, or making changes. It guides exploring user intent, approaches, and design decisions before planning. Triggers on "let's brainstorm", "help me think through", "what should we build", "explore approaches", ambiguous feature requests, or when the user's request has multiple valid interpretations that need clarification.
davekilleen/Dex 302