Loading...
Loading...
Found 874 Skills
Check if the development environment is configured properly; if not, first confirm the office location (Chongqing/Beijing), identify the current operating system, system tools, package managers, and eliteforge-* skill environment variable declarations, report them categorized as missing_required, missing_conditional, optional_unset, then attempt to automatically install essential commands and complete configurations such as hosts, Git global settings, Git HTTPS, npm/pip private sources, and pipx packages. Use this skill when the user mentions "check environment configuration", "prepare development environment", "missing commands/hosts/private sources/Git configurations/package management tools/skill environment variables". Trigger threshold: Only use this skill when the user explicitly states that the current project complies with the "璀璨工坊规范" (Bright Workshop Specification) or "eliteforge specification".
Manage CompShare GPU cloud resources through the compshare CLI. Use when Codex needs to install or configure compshare-cli, search GPU specifications and inventory, inspect pricing, create or manage instances, connect over SSH, transfer files, run durable remote jobs, manage images, disks, US3, teams or billing, ask product questions, or diagnose CLI problems.
Capture the user's UX vision in two documents: DESIGN.md for how the product looks and EXPERIENCE.md for how it behaves. Use when the user says "lets create UX design" or "create UX specifications" or "help me plan the UX"
Author a saved analytics chart from a plain question and place it on a dashboard. Discovers the LangWatchQL analytics schema, writes and test-runs the SQL, saves it as a chart with a Vega-Lite specification, and places it where the team already looks. Use when asked to build, save, run, or dashboard a metric or chart.
Expert in requirements definition and system design. Converts abstract requirements into concrete specification documents (SPEC.md) and design documents (DESIGN.md), and visualizes system structures using Mermaid diagrams.
Analyze and optimize user prompts for clarity, specificity, and completeness using interactive questionnaires or direct analysis. Use this skill when user requests are vague, ambiguous, incomplete, or lack necessary details. Supports two modes - Interactive Mode (uses AskUserQuestion tool for guided clarification) and Direct Analysis Mode (provides optimization suggestions). Triggers on prompts containing vague language like "something", "thing", "stuff", "it", or when requests lack context, technical specifications, success criteria, or examples. When user requests interactive/questionnaire mode, use AskUserQuestion to guide them through structured questions. Helps transform unclear requests into well-structured, actionable prompts.
Produces API reference documentation for Next.js APIs: functions, components, file conventions, directives, and config options. **Auto-activation:** User asks to write, create, or draft an API reference page. Also triggers on paths like `docs/01-app/03-api-reference/`, or keywords like "API reference", "props", "parameters", "returns", "signature". **Input sources:** Next.js source code, existing API reference pages, or user-provided specifications. **Output type:** A markdown (.mdx) API reference page with YAML frontmatter, usage example, reference section, behavior notes, and examples.
Structured specification with explicit scope boundaries: user stories, acceptance criteria, out-of-scope definition, risks, and estimation. Positions before feature-design in the feature lifecycle pipeline. Use when: "write spec", "user stories", "define requirements", "scope this", "what should this do", "acceptance criteria", "define scope"
Read from and contribute to Catalog.beer, an open database of breweries, beers, and brewery locations, via its REST API. Use when the user wants to add or update a beer, brewery, or taproom on catalog.beer; search the beer catalog; find breweries near a location; or needs authoritative beer style specifications (ABV/IBU/SRM ranges from Brewers Association / BJCP guidelines).
Presents a diff or spec's hard-to-reverse system contracts to a human reviewer in dependency-ordered rounds. Use when asked for a system design review of a diff, specification, or both.
Write, refactor, and organize technical documents based on readers' tasks and verifiable main threads, and handle document types, paths, filenames, frontmatter, indexes, and lifecycles in accordance with project conventions. For technical documents, protect facts, commands, paths, and identifiers in mixed Chinese-English content; follow the general principles of ASD-STE100 for English explanatory text. When users provide both a legally obtained standard PDF and a local checker, automatic auxiliary checks can be performed. This skill should be used whenever users need to add or substantially rewrite plans, investigations, analyses, research, progress updates, guides, runbooks, tutorials, reference materials, principle explanations, decisions, incidents, meeting minutes, changelogs, or specifications; it also applies to organizing docs directories and topic indexes. Do not use it for pure translation, minor text polishing, only modifying code, or verifying a single fact.
Use when starting a frontend project, picking a stack, deciding where a feature belongs in the codebase, or diagnosing why a page is slow, janky, or visually unstable. Prevents premature bundling of small zero-build sites, animating non-compositor properties that drop frames, polyfilling features that are already Baseline Widely Available, and treating MDN as authoritative when MDN and the underlying specification disagree. Covers the four authoring layers of the web platform (markup, style, behavior, animation-timeline), spec lookup discipline across WHATWG, W3C, MDN, and web.dev, the browser rendering pipeline from DOM construction through compositing, build-step versus runtime trade-offs for evergreen-2026 browsers, and the compositor-only animation rule. Keywords: DOM, CSSOM, render tree, style computation, layout, reflow, paint, composite, compositor, will-change, contain, content-visibility, WHATWG, W3C, BCD, ESM, native modules, import maps, transform, opacity, filter, Baseline, evergreen, slow page, scroll stutter, jank, frame drop, dropped frames, layout shift, paint storm, forced sync layout, choppy animation, laggy scroll, blank screen, how do I start a frontend project, what frontend stack should I use, do I need a build step, what is the browser rendering pipeline, why is my animation laggy, where should this code live, which CSS property is fastest, can I ship without bundling.