Loading...
Loading...
Found 225 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.
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.
Vida's thinking framework and expression style. Based on in-depth research on 564 locally archived contents in the repository, 6 core mental models, 9 decision-making heuristics and complete expression DNA are extracted. Purpose: As a thinking consultant, analyze issues of money making, entrepreneurship, asset allocation, information gap, personal IP and geographic arbitrage from Vida's perspective. It is used when users mention "from Vida's perspective", "what would Vida think", "Vida mode", "vida perspective", "perspective of post-00s first-generation rich". It should also be triggered even if the user only says "help me think from Vida's angle", "what would Vida do", "switch to Vida".
Perspectium integration. Manage data, records, and automate workflows. Use when the user wants to interact with Perspectium data.
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 writing RSpec tests for service objects, API clients, orchestrators, or business logic in spec/services/. Covers instance_double, FactoryBot hash factories, shared_examples, subject/let blocks, context/describe structure, aggregate_failures, change matchers, travel_to, and error scenario testing.
Use when writing, reviewing, or cleaning up RSpec tests for Ruby and Rails codebases. Covers spec type selection, factory design, flaky test fixes, shared examples, deterministic assertions, test-driven development discipline, and choosing the best first failing spec for Rails changes. Also applies when choosing between model, request, system, and job specs.
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.
Use when OpenSpec is not initialized in the current project or the superspec-rpi schema is missing.