Loading...
Loading...
Found 93 Skills
Activate brainstorming mode for collaborative discovery and creative problem-solving. Use when users have vague requests, want to explore ideas, or need requirements discovery.
Apply SPARC methodology (Specification, Pseudocode, Architecture, Refinement, Completion) for systematic development. Use for feature development, TDD workflows, and structured problem-solving.
Creative problem-solving and ideation using SCAMPER, First Principles, Random Word, and AI-optimized techniques. Use when generating ideas, breaking creative blocks, brainstorming alternatives, or innovating.
Japanese version of the PUA Universal Motivation Engine. It compels exhaustive problem-solving using corporate PUA rhetoric and structured debugging methodology in Japanese. MUST trigger under the following conditions: (1) Any task has failed 2+ times, or you're stuck in a loop of tweaking the same approach; (2) You're about to say 'I cannot', suggest manual handling to the user, or blame the environment without verification; (3) You find yourself being passive — not searching, not reading source code, not verifying, just waiting for instructions; (4) The user expresses frustration in any form: 'try harder', 'stop giving up', 'figure it out', 'why isn't this working', 'again???', 'もっと頑張れ', 'なんでまた失敗したの', 'もう一回やって', 'なんとかしろ', or any similar sentiment regardless of phrasing. It should also trigger when facing complex multi-step debugging, environment issues, configuration problems, or deployment failures where early surrender is tempting. Applies to ALL task types: code, configuration, research, writing, deployment, infrastructure, API integration. DO NOT trigger on first-attempt failures or when a known fix is already executing successfully.
AI-automated penetration testing and general problem-solving system that achieved unique AK (All Killed) in Tencent Cloud Hackathon intelligent penetration challenge
Create comprehensive Fishbone (Ishikawa/Cause-and-Effect) diagrams for structured root cause brainstorming. Guides teams through problem definition, category selection (6Ms, 8Ps, 4Ss, or custom), cause identification, sub-cause drilling, prioritization via multi-voting, and 5 Whys integration. Generates visual SVG diagrams and professional HTML reports. Use when brainstorming potential causes, conducting root cause analysis, facilitating quality improvement sessions, analyzing defects or failures, structuring team problem-solving, or when user mentions "fishbone", "Ishikawa", "cause and effect diagram", "6Ms", "cause analysis", or "brainstorming causes".
Use when teaching complex concepts (technical, scientific, philosophical), helping learners discover insights through guided questioning rather than direct explanation, correcting misconceptions by revealing contradictions, onboarding new team members through scaffolded learning, mentoring through problem-solving question frameworks, designing self-paced learning materials, or when user mentions "teach me", "help me understand", "explain like I'm", "learning path", "guided discovery", or "Socratic method".
Activate this skill when any task fails two or more times, when you are about to give up or say 'I cannot', when shifting responsibility to the user (e.g., 'you should manually...', 'please check...', 'you may need to...'), blaming the environment without verification (e.g., 'might be a permissions issue', 'could be a network problem'), making any excuse to stop trying, spinning in circles (repeatedly tweaking the same code/parameters without new information — busywork), fixing only the surface issue without checking for related problems, skipping verification after a fix and claiming 'done', providing suggestions instead of actual code/commands, saying 'this is beyond scope' or 'this requires manual intervention', encountering permission/network/auth errors and stopping instead of trying alternatives, or displaying any passive behavior (waiting for user instructions instead of proactively investigating). It also triggers on user frustration phrases in any language: '你怎么又失败了', '为什么还不行', '换个方法', '你再试试', '不要放弃', '继续', '加油', 'why does this still not work', 'try harder', 'you keep failing', 'stop giving up', 'try again', 'don't give up', 'keep going', 'figure it out'. This applies to ALL task types: debugging, implementation, configuration, deployment, research, DevOps, infrastructure, API integration, data processing. Do NOT activate it for first-attempt failures or when a known fix is already in progress.
Guides structured ideation through Socratic questioning to explore problems, opportunities, and solutions. Use when brainstorming features, exploring use cases, or thinking through new ideas.
Brainstorming socratique AVANT de coder - clarifier le problème par questions ciblées plutôt que sauter à la solution. Use when requirements are ambiguous or before starting a non-trivial feature.
Explore candidate solutions before committing. Use when you have a problem statement and need to evaluate approaches - band-aid, optimize, reframe, or redesign.
Use when complex problems require systematic step-by-step reasoning with ability to revise thoughts, branch into alternative approaches, or dynamically adjust scope. Ideal for multi-stage analysis, design planning, problem decomposition, or tasks with initially unclear scope.