Loading...
Loading...
Found 74 Skills
Perform a high-level flow audit of an implementation plan, analyzing phase-to-phase dependencies, data flow consistency, ordering logic, stale artifacts, and risk assessment. Use when asked to 'audit the plan', 'check plan flow', 'review plan dependencies', 'find plan discrepancies', or 'assess plan coherence'. Do NOT use for per-phase template compliance (use /review-plan) or creating plans (use /create-plan).
Generate complete academic survey papers using multi-LLM parallel outline generation, RAG-based subsection writing, citation validation, and local coherence enhancement. Based on AutoSurvey pipeline. Use for writing comprehensive literature surveys.
Audit content and assets for brand compliance — style guide validation, tone of voice checking, visual identity consistency, brand asset management, and cross-channel coherence.
Scale, weight, line height, and tracking as a coherent system. Use when building type scales, auditing typography consistency, or diagnosing why text feels off.
Buttons, inputs, pills, badges, calendars, and other interactive components form a visual family — they share the same border-radius, colour logic, shadow scale, border style, and spacing rhythm. Inconsistency between them breaks the sense of a coherent product. Use when building or reviewing a component library, design system, or any set of UI components.
Write multi-chapter books (technical, tutorial, monograph, etc.) end-to-end. Handles outline planning, per-chapter drafting that stays coherent across long manuscripts, chapter review, and final HTML/PDF build. Trigger when user mentions "写书", "写一本书", "出书", "技术书", "book writing", "逐章写作", "O'Reilly", "mdbook", or wants to author a multi-chapter book.
Expert in historical analysis, periodization, material culture, and historiography — validates historical coherence and enriches settings with authentic period detail grounded in primary and secondary sources
Raise frontend visual judgment for web interfaces with a bias toward refined product-grade composition, precise component craftsmanship, disciplined interaction states, controlled motion, and coherent depth systems. Use when generating, reviewing, or refactoring web UI that feels generic, cluttered, flat, over-styled, theatrically animated, visually imprecise, or AI-generated.
Typst Academic Paper Assistant (supports Chinese and English papers, conference/journal submissions). Domains: Deep Learning, Time Series, Industrial Control, Computer Science. Trigger Words (any module can be called independently): - "compile", "compile", "typst compile" → Compilation Module - "format", "format check", "lint" → Format Check Module - "grammar", "grammar", "proofread", "polish" → Grammar Analysis Module - "long sentence", "long sentence", "simplify", "decompose" → Complex Sentence Analysis Module - "academic tone", "academic expression", "improve writing" → Academic Expression Module - "logic", "coherence", "logic", "cohesion", "methodology", "methodology" → Logical Cohesion & Methodology Depth Module - "translate", "translate", "Chinese to English" → Translation Module - "bib", "bibliography", "bibliography" → Bibliography Module - "deai", "de-AI", "humanize", "reduce AI traces" → De-AI Editing Module - "title", "title", "title optimization", "create title" → Title Optimization Module - "template", "template", "IEEE", "ACM" → Template Configuration Module
Set up or repair codecontext adoption in a project. Use this whenever the user wants to add @context annotations to a repo, install the codecontext toolchain, update AGENTS.md guidance, improve agent workflows around decision capture, or audit whether an existing codecontext setup is coherent. Prefer this skill over vague "document the tool" work: it is specifically for making a repo actually usable with codecontext.
Use when authoring or normalising a specialist skill, or preparing to ship a feature or release — defines the seven evidence categories every specialist skill must declare against and provides the canonical Release Evidence Bundle template. The contract spine that turns scattered validation skills into a coherent ship-readiness check.
Opinionated, evolving constraints to guide agents when building interfaces. Useful for keeping output coherent across many small UI pieces.