Skill UI

This skill guides the implementation of essential user feedback states—Loading (Skeleton), Empty (Zero Data), Error, and Success—for data-dependent components or entire pages. It ensures a robust and polished user experience by providing structured, best-practice patterns for handling various data scenarios, preventing visual gaps or dead ends in the UI flow.

This skill helps developers accurately find and explore the correct Windows API for specific platform capabilities, such as file access, camera usage, notifications, or UI controls. It searches a comprehensive local cache of WinMD metadata, providing full technical details including methods, properties, events, and enumeration values for APIs sourced from the Windows Platform SDK and WinAppSDK. It is indispensable when building complex features requiring deep integration with the Windows operating system.

This technique is used when the required answer in a case query is not directly stated but must be deduced by following a sequence of connected roles, people, or events. It involves mapping complex relationships, such as Victim -> Defendant -> Lawyer -> Witness, to trace indirect connections and reach the final piece of information. Ideal for advanced investigative research and deep knowledge graph traversal.

This technique allows users to locate game developers or projects indirectly by searching for highly distinctive biographical details. Instead of relying on game databases, it leverages unique phrases, historical events, or personal lifestyle details found in interviews, blogs, or conference talks. It is invaluable when the developer's identity is obscured, requiring deep research using exact-match queries on obscure information.

A structured methodology for precisely identifying specific geographic locations or historical landmarks. This technique systematically narrows the search scope, moving from broad regions (countries/former states) down through administrative divisions, city centers, and finally to specific monuments or structures. It requires utilizing diverse clues like historical events, census data, and distance constraints, while critically verifying assumptions at each step to ensure accuracy.

OpenSearch is a distributed search and analytics engine integrated into the KubeSphere WizTelemetry Observability Platform. It is crucial for storing, searching, and analyzing various types of observability data, including application logs, system events, audit records, and notification history. This guide covers installation, configuration, and operational best practices for managing the OpenSearch cluster within KubeSphere.

This technique optimizes search precision when querying blog posts or articles. By wrapping unique phrases, specific titles, or direct quotes in quotation marks, the system treats the phrase as a single, exact unit. This prevents the search engine from breaking the phrase into individual words, which dramatically reduces noise and increases the likelihood of finding the intended source material.

This skill guides users on how to search for physical monuments, memorials, or landmarks by linking them to their originating historical events. The core technique involves treating the historical event (e.g., a battle, a protest, a significant date) as the primary search anchor, and then locating the associated memorial or structure. It provides structured query templates and anti-patterns to ensure accurate, context-aware geographical and historical information retrieval.

This guide teaches targeted verification strategies for historical research. When initial searches suggest a candidate name or figure, do not continue with broad searches. Instead, immediately switch to verifying the candidate against all specific constraints (time period, location, family details, major events) using precise search queries to confirm identity and eliminate false positives.

This skill teaches how to dramatically improve the accuracy of historical research queries. When searching for information about a historical figure, rather than relying on generic facts (like era or nationality), users should identify and prioritize the most unique, specific, or niche details—such as a unique object, a rare event, or an uncommon biographical fact. By using these distinctive details as quoted search anchors, the search results become highly targeted, overcoming the limitations of broad, general queries.

This technique guides the identification of musicians by prioritizing unique personal life events over discography details (albums or songs). It instructs users to use highly distinctive biographical information—such as career turning points, specific personal relationships, or unusual life incidents—as the primary search anchor. This method significantly improves search accuracy when typical musical clues are insufficient.

This advanced technique assists in precisely locating academic theses by combining key identifiers: university name, degree type, and year. Its core strength is resolving indirect university clues (e.g., determining a founding year from a literary work or historical event) first. This two-step resolution process ensures that the final search for the thesis is highly accurate, even when the university is described obliquely.