Loading...
Loading...
Found 258 Skills
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, /审查, "审查一下", "帮我审一下"
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.
Expert guidance for writing fast, maintainable Minitest tests in Rails applications. Use when writing tests, converting from RSpec, debugging test failures, improving test performance, or following testing best practices. Covers model tests, policy tests, request tests, system tests, fixtures, and TDD workflows.
Ruby on Rails testing best practices for writing effective, maintainable test suites with RSpec. This skill should be used when writing, reviewing, or refactoring Rails tests to ensure proper test design, data management, and coverage patterns. Triggers on tasks involving RSpec specs, model tests, request specs, system tests, factory definitions, Capybara interactions, Sidekiq job tests, or test suite optimization. Complementary to rails-dev, ruby-optimise, and ruby-refactor skills.
Structured multi-perspective debate for important architectural decisions and complex trade-offs
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.
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".
Testing Inertia Rails responses with RSpec and Minitest: component assertions, prop matching, flash verification, deferred props, and partial reload helpers. Use when writing controller specs, request specs, or integration tests for Inertia pages. ALWAYS use matchers (render_component, have_props, have_flash), NOT direct access (inertia.component, inertia.props). CRITICAL: after POST/PATCH/DELETE with redirect, MUST call follow_redirect! before asserting flash or props — without it you're asserting against the 302, not the Inertia page. Setup: require 'inertia_rails/rspec'.
Multi-perspective code analysis using three AI personas (RYAN, FLASH, SOCRATES) for comprehensive decision-making. Use when complex code decisions need analysis from multiple viewpoints, or when avoiding single-perspective blind spots is critical.
Create worldbuilding quotes and epigraphs through documentary perspectives. Use for chapter epigraphs, in-world documents, or any content where limited perspective creates meaning through what the documenter cannot see.
Use when seeking analogous solutions from other domains, when stuck on a problem and need fresh perspectives, or when evaluating whether approaches from field X might apply to field Y. Requires structured problem statement.
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.