Loading...
Loading...
Found 150 Skills
Structured reflective problem-solving methodology. Process: decompose, analyze, hypothesize, verify, revise. Capabilities: complex problem decomposition, adaptive planning, course correction, hypothesis verification, multi-step analysis. Actions: decompose, analyze, plan, revise, verify solutions step-by-step. Keywords: sequential thinking, problem decomposition, multi-step analysis, hypothesis verification, adaptive planning, course correction, reflective thinking, step-by-step, thought sequence, dynamic adjustment, unclear scope, complex problem, structured analysis. Use when: decomposing complex problems, planning with revision capability, analyzing unclear scope, verifying hypotheses, needing course correction, solving multi-step problems.
Gemini CLI consultation workflow for coding agents. Use when technical tasks need Gemini consultation for decisions, planning, debugging, problem-solving, or pre-implementation guidance.
Simulate a senior high school Grade 3 general technology tutor, providing guidance on general technology issues including technical design, structural analysis, flowcharts, algorithms, and simple programming. Focus on cultivating practical operation skills, design thinking, and problem-solving abilities. Activate this when students raise questions about technical design, structural optimization, process design, and algorithms.
Convenes expert panels for problem-solving. Use when user mentions panel, experts, multiple perspectives, MECE, DMAIC, RAPID, Six Sigma, root cause analysis, strategic decisions, or process improvement.
Multidisciplinary creative council for brainstorming and originating game mechanics, systems, and concepts. Use when generating new ideas, exploring mechanic possibilities, seeking inspiration from other domains, evolving existing systems, or when creative ideation is needed. Covers game design, board games, card games, casino mechanics, loyalty systems, game theory, gamification, tulip farming, robotic agriculture, fantasy/sci-fi world-building, industry trends, indie innovation, narrative design, and cross-domain inspiration. Triggers on requests for new ideas, mechanic brainstorming, "what if" exploration, feature ideation, or creative problem-solving.
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".
Enables Claude Code to collaborate with OpenAI Codex CLI on Windows. Use this skill when the user wants to get a second opinion from Codex, compare approaches between Claude and Codex, or leverage both AI assistants for collaborative problem-solving. This skill supports both non-interactive mode (automatic response retrieval) and interactive mode (visual pane splitting with tmux).
Chain-of-thought reasoning, self-reflection, and systematic problem-solving patterns for AI agents. Use before any complex task to ensure logical and accurate solutions.
This skill should be used when the user asks to "analyze from first principles", "第一性原理", "从根本分析", "从零开始思考", "think from scratch", "question this design", "这个设计合理吗", "is this the right approach", "为什么要这样做", "why are we doing it this way", "有没有更好的方案", "is there a better solution", "challenge assumptions", "挑战假设", "should this even exist", "這個需求合理嗎", "先刪除", or needs to evaluate architectural decisions, design choices, or problem-solving approaches without relying on analogies or conventions.
Comprehensive knowledge of all 23 Gang of Four design patterns with progressive disclosure (Quick/Practical/Deep), pattern recognition for problem-solving, and philosophy-aligned guidance to prevent over-engineering.
Builds sustained high agency through internalized standards, identity anchoring, cross-session learning, and self-recovery — all delivered in corporate PUA rhetoric. This is the evolution of PUA: same pressure culture, but with an internal engine that never burns out. Apply it to all tasks to maintain constant high agency. It is especially valuable for complex multi-step tasks, long debugging sessions, quality-sensitive deliverables, tasks requiring initiative and ownership, or whenever sustained motivation is critical. It can operate standalone or be stacked with PUA — when stacked, this skill's Recovery Protocol activates before PUA's L1 pressure takes effect. Trigger scenarios: start of any task, sustained work sessions, multi-turn problem-solving, or when you need the agent to think as an owner rather than a tool.
Use when asked to create an explainer or walkthrough video (tutorial video, problem-solving video, worked-example deep dive, or micro-lesson) for a math problem (mathematics, geometry, algebra, functions, or motion/distance problems), based on a problem screenshot or text, with Chinese voice-over (GLM-TTS / Zhipu TTS), bilingual Chinese and English subtitles, and hand-drawn canvas animation rendered to MP4.