Loading...
Loading...
Found 14 Skills
Guidelines for contributing commands in VS Code extensions. Indicates naming convention, visibility, localization and other relevant attributes, following VS Code extension development guidelines, libraries and good practices
Build Raycast extensions with React and TypeScript. Use when the user asks to create a Raycast extension, command, or tool.
VSCode extension starter using reactive-vscode and tsdown. Use when scaffolding or maintaining a VSCode extension with reactive APIs, CJS build, and vscode-ext-gen.
Implement entry points in Umbraco backoffice using official docs
Expert guidance on TYPO3 Workspaces: versioning, staging, publishing workflows, file limitations, query migration, debugging, and testing. Use when working with workspace, versioning, staging, publishing, review, draft content, workflow.
Implement custom icons in Umbraco backoffice using official docs
Auto-scaffold Chrome extensions with WXT or Plasmo. Ask user for name/features, scaffold, configure entrypoints. Use when: create extension, scaffold, new extension.
Build, scaffold, and ship SillyTavern third-party extensions. Use when creating a new extension, adding extension settings/UI hooks, wiring events or slash commands, integrating modules, or packaging a release from a template.
Learn how to build a VSCode extension using a Lit web component, covering setup, template creation, component implementation, and extension activation.
Implement file upload preview components in Umbraco backoffice using official docs
For AI to refer to VSCode theme color settings. Triggered when users ask questions related to VSCode theme colors, color customization, theme configuration, workbench.colorCustomizations, etc.
Expert in building Chrome Extensions using Manifest V3. Covers background scripts, service workers, content scripts, and cross-context communication.