Loading...
Loading...
Found 229 Skills
Simulate an expert panel discussion on a topic. Suggests 3 relevant experts/personas based on context and has them debate approaches, trade-offs, and arrive at recommendations. Use when brainstorming, exploring design decisions, or wanting multiple expert perspectives on a problem.
Test Inertia Rails applications with RSpec or Minitest. Use when writing tests for Inertia responses, components, props, flash messages, and partial reloads.
Use when facing hard architectural decisions, multiple valid approaches exist, need diverse perspectives before committing, or want M-of-N synthesis on complex problems
Enables Claude to interact with Gemini AI chat for quick queries, brainstorming, and alternative AI perspectives
Writes comprehensive RSpec tests for Rails applications. Use when writing model specs, request specs, system specs, job specs, mailer specs, channel specs, or storage specs. Triggers on "write tests for", "add specs to", "test the User model", "create request specs", "write RSpec", "add test coverage".
Conduct comprehensive literature reviews using multi-perspective dialogue simulation. Generate diverse expert personas, conduct grounded Q&A conversations, and synthesize findings into structured knowledge. Use when starting a new research project or writing a survey section.
Ruby development guidelines covering idiomatic code style, Ruby 3.x features, testing with RSpec, and best practices for building maintainable Ruby applications.
Use when choosing the best first failing RSpec spec or vertical slice for a Ruby on Rails change. Covers request vs model vs service vs job vs engine spec selection, system spec escalation, smallest safe slice planning, and Rails-first TDD sequencing. Trigger words: where to start testing, what test to write first, RSpec, test-driven development, TDD, first failing test.
Use when investigating a bug, error, or regression in a Ruby on Rails codebase. Creates a failing RSpec reproduction test, isolates the broken code path, and produces a minimal fix plan. Trigger words: debug, broken, error, regression, stack trace, failing test, RSpec, bug report, Rails app.
Invoke for ANY personal Bible devotion or scripture meditation request. This is a daily quiet time (QT) guide — use it whenever the user wants spiritual reflection on a Bible passage, NOT academic analysis. Common signals: asking for today's reading, wanting guided devotion, seeking stillness with scripture, mentioning a personal reading plan, or using terms like 靈修、靈糧、默想、嗎哪、 QT、quiet time、devotional. Even short or casual requests like just saying "QT" or "今天讀什麼" should trigger this skill. Delivers a first-century Jewish perspective devotional for mainstream Christians. Depends on bible-buddy skill. EXCLUDE: theological scholarship, academic exegesis, verse-by-verse analysis, sermon/teaching prep, translation comparison, comparative religion essays, or original-language research tasks — those belong to bible-buddy or bible-fact-check.
Multi-perspective adversarial review. 4 Agents are spawned in parallel (full mode), each identifying issues from different perspectives, and the main thread makes a comprehensive ruling. Trigger methods: /story-review, /审查, "审查一下", "帮我审一下"
Use when stakeholders have conflicting priorities and need alignment, suspect decision blind spots from single perspective, need to pressure-test proposals before presenting, want empathy for different viewpoints (eng vs PM vs legal vs user), building consensus across functions, evaluating tradeoffs with multi-dimensional impact, or when user mentions "what would X think", "stakeholder alignment", "see from their perspective", "blind spots", or "conflicting interests".