Loading...
Loading...
Found 153 Skills
RSpec testing best practices for Ruby and Rails applications, covering test organization, data management, and isolation patterns.
Structure multi-POV stories through catalyst environments. Use when building interconnected narratives, when perspectives need meaningful intersection, or when a shared setting needs to generate distinct storylines.
Analyze propositions from multiple expert perspectives. Dynamically generates 4-6 relevant expert roles, then performs validation, comprehensive analysis, or debate-style examination. Use when user wants to examine ideas critically, find blindspots, or explore different viewpoints on a topic.
RSpec Ruby testing framework. Use for Ruby testing.
Clarify requirements before implementing by asking the minimum must-have questions. Use when a request is underspecified or ambiguous, when the user asks to “ask clarifying questions”, or when multiple plausible interpretations exist and you risk doing the wrong work.
Comprehensive RSpec testing for Ruby and Rails applications. Covers model specs, request specs, system specs, factories, mocks, and TDD workflow. Automatically triggers on RSpec-related keywords and testing scenarios.
Use when OpenSpec is not initialized in the current project or the superspec-rpi schema is missing.
Use when the user needs proposal/specs research artifacts produced for a Superspec (superspec-rpi) OpenSpec change.
Use when implementing a planned OpenSpec change by applying tasks and validating all artifacts.
Use when executing superspec tasks to enforce strict TDD for behavior changes and allow NON-TDD exceptions only for doc/config/generated/format-only work with mechanical verification.
Write Rails tests with RSpec, FactoryBot, and mocking patterns. Use when creating tests, writing specs for models/controllers/requests, setting up test fixtures, or mocking external services.
Write RSpec tests for Ruby and Rails applications. Use when creating spec files, writing test cases, or testing new features. Not for Minitest — use minitest-coder instead. Covers RSpec syntax, describe/context organization, subject/let patterns, fixtures, mocking with allow/expect, and shoulda matchers.