Skill UI

Checks website, GitHub, and local docs to identify messaging inconsistencies and captures version, feature, terminology, and contact differences in a read-only discrepancy report whenever a consistency check is requested.

Automates security benchmark runner workflows by triggering on relevant terminology, guiding pen testing/compliance tasks, generating production-ready configs, and validating outputs against industry standards within advanced enterprise security scenarios.

This skill extracts up to 50 highly relevant, SEO-friendly keywords and tags from any given text. It is designed to identify core topics, domain terminology, and potential search phrases, formatting them into a strict, comma-separated list suitable for metadata generation, tagging, or search engine optimization (SEO). Use it whenever you need to optimize content for search engines.

This guide provides techniques for conducting effective crime investigations in non-English speaking countries (e.g., Thailand, Malaysia, Latin America). It teaches investigators to move beyond generic English searches by incorporating local language terms, specific regional place names, and local media terminology to find comprehensive and relevant information.

This skill enhances research query formulation by translating vague, colloquial, or generalized descriptions into precise, standard academic terminology. When initial search terms are broad (e.g., "conjugal happiness"), this technique suggests multiple plausible academic synonyms (e.g., "marital satisfaction," "relationship quality"). By improving the precision of the search query and incorporating structured constraints (like keywords, years, or sample sizes), it significantly boosts the relevance and effectiveness of academic paper retrieval.

This expert acts as a Design Systems Lead and Prompt Engineer for creating high-fidelity, consistent UI designs. It transforms vague ideas into structured specifications by enhancing prompts with professional UI/UX terminology, synthesizing design system source files, and managing multi-step generation and editing workflows using the Stitch MCP.

This guide provides a comprehensive architectural pattern (Adapter Pattern) for migrating code between different versions of the ClickUp API (v2 to v3). It addresses breaking changes, endpoint structural shifts, and terminology changes (e.g., 'Team' vs 'Workspace'), ensuring smooth and robust integration during large-scale platform upgrades.

A comprehensive guide covering Chinese technical documentation formatting rules. It addresses common issues like mixing full/half-width punctuation, spacing conventions (e.g., space between English/Chinese text, numbers/units), and best practices for handling technical terminology translation and structure.

This skill acts as a rigorous, Socratic interviewer designed to stress-test a proposed plan against an established domain model and existing project documentation. It forces the user to sharpen terminology, resolve cross-cutting dependencies, and identify inconsistencies between stated requirements, code implementations, and documented decisions. It ensures the resulting architecture is precise, consistent, and well-documented by automatically updating the context and generating Architecture Decision Records (ADRs).

This tool extracts and formalizes the core business terminology (Ubiquitous Language) from a conversational context. It generates a structured glossary, identifies ambiguities, resolves conflicting terms, and proposes canonical names. It is essential for building consistent and unambiguous domain models, particularly when following Domain-Driven Design (DDD).

A deep-dive session designed to stress-test a technical plan against an existing domain model. This process forces the user to resolve ambiguities, sharpen terminology, and validate decisions by cross-referencing code and existing documentation (CONTEXT.md, ADRs). It ensures architectural rigor and completeness before implementation.

This skill facilitates a rigorous, documentation-anchored design review session. It challenges a proposed plan by cross-referencing it against the project's established domain glossary (CONTEXT.md), historical architectural decisions (ADRs), and the current codebase. It forces the user to resolve ambiguities, define precise terminology, and validate design trade-offs using concrete scenarios, ensuring all decisions are captured and documented inline.