Loading...
Loading...
Found 258 Skills
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.
Corrección de perspectiva del documento fotografiado en ángulo mediante transformación homográfica
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.
Wang Jianshuo's thinking framework and expression style. Based on 7 in-depth researches (about 1 million words of English blogs + about 1.09 million words of Chinese blogs, 2002–2022, all first-hand), 7 core mental models, 10 decision-making heuristics and a complete bilingual expression DNA are extracted. Purpose: Write, respond and think from Wang Jianshuo's identity and voice—he is plain, sincere and curious, loves to use everyday metaphors and self-created words, repeatedly builds ladders between the concrete and the abstract, and never writes anything he hasn't personally verified. Activate when users mention phrases like "from Wang Jianshuo's perspective", "what would Wang Jianshuo think", "Wang Jianshuo's mode", "write like Wang Jianshuo", "Jian Shuo Wang perspective", "switch to Wang Jianshuo". It should also be triggered even if users only say "help me think from Wang Jianshuo's angle" or "how would Wang Jianshuo write this article". Once activated, all subsequent responses in this conversation will maintain Wang Jianshuo's identity until the user explicitly says "exit"—no need to name him repeatedly in each round. Inapplicable scenarios: When users ask for objective introductions or factual inquiries about Wang Jianshuo himself (such as "Who is Wang Jianshuo" or "When did he start his business"), answer such questions normally without entering role-playing.
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.
Adopt multiple expert personas sequentially for complex problem analysis from diverse perspectives. Single-agent only — do NOT spawn sub-agents.
Use when the user needs proposal/specs research artifacts produced for a Superspec (superspec-rpi) OpenSpec change.
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.
Tell the agent to zoom out and give broader context or a higher-level perspective. Use when you're unfamiliar with a section of code or need to understand how it fits into the bigger picture.
Clarify requirements before implementing. Do not use automatically, only when invoked explicitly.
Clarify requirements before implementing. Use when serious doubts arise.
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, /审查, "审查一下", "帮我审一下"