Skill UI

A comprehensive, four-stage methodology for debugging complex software issues, ensuring that fixes target the root cause rather than merely masking symptoms. This guide mandates rigorous investigation (gathering evidence, tracing data flow), pattern analysis, controlled hypothesis testing, and disciplined implementation via test-driven development. Use this when facing production bugs, test failures, performance degradation, or unexplained system behavior, especially under time pressure.

This skill provides read-only functionality to query and list comprehensive information about KubeSphere clusters. It is designed for viewing cluster lists, checking current status, retrieving detailed specifications, and identifying component versions across multiple clusters. IMPORTANT: This operation is strictly read-only. Never use these commands for creating, updating, or deleting resources; always use the KubeSphere console for management actions.

This guide teaches advanced search techniques for identifying specific video games. It emphasizes using highly discriminative technical details such as specific platforms (e.g., DOS, NES, PS4), distribution methods (shareware), game engines, era, and detailed review scores from niche sites. By combining multiple constraints (Platform + Era + Detail), users can dramatically narrow down search results, even locating specific developers or artists involved in the game's creation.