Loading...
Loading...
Found 258 Skills
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.
RSpec testing best practices for Ruby and Rails applications, covering test organization, data management, and isolation patterns.
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.
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.
Use when implementing a planned OpenSpec change by applying tasks and validating all artifacts.
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.
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.
Perspectium integration. Manage data, records, and automate workflows. Use when the user wants to interact with Perspectium data.
Spatial depth design with isometric views, vanishing points, and layered elements that guide attention through 3D-like realism.
RSpec Ruby testing framework. Use for Ruby testing.
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".
Use when OpenSpec is not initialized in the current project or the superspec-rpi schema is missing.