Browse Skills

Guide for migrating a JavaScript/TypeScript project from Prettier or Biome to the Oxfmt code formatter. Use when asked to convert or switch formatters.

Generates Vitest + React Testing Library tests for Dify frontend components, hooks, and utilities. Use when writing, reviewing, or improving frontend test coverage.

Creates distinctive, production-grade frontend interfaces with bold aesthetic choices. Use when building web components, pages, or applications that need memorable, non-generic design.

Reviews frontend code (TSX, TS, JS) for code quality, performance, and business logic issues using a predefined checklist. Supports reviewing staged changes or specific files before commit.

Guides users through a structured workflow for co-authoring documentation, proposals, technical specs, and decision docs. Helps transfer context, refine content, and verify reader understanding.

Refactors high-complexity React components when complexity > 50 or lines > 300. Provides patterns for extracting hooks, splitting sub-components, simplifying conditionals, and separating API logic. Use before testing to improve maintainability. Not for simple components or third-party wrappers.

Automates component documentation by analyzing source code, demos, and existing docs to generate MDX files with live demos, API tables, and type definitions.

Simplifies and refines code for clarity, consistency, and maintainability while preserving all functionality. Automatically improves recently modified code based on project standards.

A systematic workflow for implementing new features, from codebase exploration and requirements clarification to architecture design, implementation, and quality review.

Executes and reports qualitative or quantitative analysis for ASQ manuscripts, making the evidence-to-theory link transparent. Covers coding, data-to-theory tables, robustness checks, and mechanism evidence.

Use when revising an IPSN paper to ensure it leads with a sensing problem, includes real-hardware evidence, energy/latency/accuracy budgets, honest deployment reporting, double-blind wording, and disciplined use of the ACM two-column page budget.

Designs rigorous empirical evaluations for software engineering research papers, ensuring proper evidence matching, statistical analysis, and methodological transparency for conferences like ESEC/FSE.