Loading...
Loading...
Found 124 Skills
Converts long inline XAML bindings to Property Element Syntax for better readability. Use when XAML binding expressions become too long or complex.
A specialized skill for test naming conventions and best practices. Use this when you need to name test methods, improve test readability, or establish naming standards. It covers three-part naming method, Chinese naming recommendations, test class naming, etc. Keywords: test naming, test naming, naming conventions, naming conventions, three-part naming, three-part naming, method_scenario_expected, method_scenario_expected, how to name tests, test readability, test readability, naming best practices, test reports, test documentation
Assess documentation quality across readability, consistency, audience fit, and prose clarity. Produces a scored review with actionable findings. This skill should be used before releases, during doc reviews, or when documentation feels unclear or inconsistent.
Calculate readability scores (Flesch-Kincaid, Gunning Fog, SMOG) and grade levels for text. Analyze writing complexity and get improvement suggestions.
Human-readable control flow patterns for refactoring complex conditionals. Use when refactoring nested conditionals, improving code readability, or restructuring decision logic.
Review existing Datadog dashboards for operational readiness. Audits alert threshold markers, threshold proximity to normal traffic, customer-facing section completeness, and zero-knowledge readability. Uses pup CLI to fetch dashboard definitions. Use when auditing dashboards before on-call handoff, after dashboard changes, or during operational reviews. Do not use for: (1) designing new dashboards from scratch, (2) monitor/alert rule design, (3) APM instrumentation or tracing setup, (4) log pipeline configuration.
Copywriting and content creation standards for website pages, blog posts, and all written copy. Covers headlines, ledes, readability, niche vocabulary, scannable formatting, and persuasive structure. Cross-cutting skill — apply whenever...
Help create and optimize blog posts, articles, and polished writing with rigorous structure, reader expectation management, and SCQA methodology. This skill contains a specialized writing framework (reader personas, concept introduction protocol, diagnostic checklists, Pyramid Principle structure) that cannot be replicated without loading it. You must use this skill in any of these scenarios: (1) writing a blog post or article from notes/materials, (2) reviewing, diagnosing, or optimizing any draft or article for structure, clarity, and readability, (3) polishing or refining notes into publishable form, (4) giving feedback on writing structure, flow, or reader experience, (5) creating outlines for articles. Trigger on keywords: "博客", "文章", "发布", "blog", "写作", "初稿", "打磨", "诊断", "优化文章", "结构", "大纲", "投稿", "公众号", "读者". Also trigger when the user shares a markdown file and asks to improve it, or asks if something "reads well" or "makes sense to readers".
Single-page SEO audit: deep content quality evaluation using Google's E-E-A-T framework, Helpful Content guidelines, on-page SEO factors, search intent alignment, technical signals, and readability analysis. Fetches GSC performance data for that specific page, crawls the live HTML, evaluates metadata, schema markup, internal linking, content depth, and produces a scored report with actionable fixes. Use this skill whenever the user wants to analyze a specific page or URL — not the whole site. Trigger on: "analyze this page", "audit this URL", "how is this page doing", "evaluate my blog post", "check this landing page", "page SEO", "content quality check", "is this page good enough", "review this page's SEO", "what's wrong with this page", "how can I improve this page", "page analysis", "single page audit", "content audit for [URL]", or any request that names a specific URL/page for SEO evaluation. If the user provides a specific URL (not just a domain), this is likely the right skill — use /seo-analysis for full-site audits instead.
Analyze text readability with Flesch-Kincaid, Gunning Fog, SMOG, and other metrics. Returns objective scores with interpretation and recommendations.
Improve existing code through safe, behavior-preserving Clean Code refactoring. Use when the user asks to refactor code, clean up messy code, improve readability, simplify structure, reduce duplication, improve naming, review maintainability, or apply Clean Code principles. Do not use for broad architecture redesign unless the user asks for redesign.
Improves typography by fixing font choices, hierarchy, sizing, weight, and readability so text feels intentional. Use when the user mentions fonts, type, readability, text hierarchy, sizing looks off, or wants more polished, intentional typography.