vicinae-extension-authoring

Create and update Vicinae extensions with standardized structure and workflows.

3|Updated Jun 23, 2022
One-click install
npx skills add https://github.com/fbosch/dotfiles --skill vicinae-extension-authoring
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: vicinae-extension-authoring
Source: https://github.com/fbosch/dotfiles/tree/main/.agents/skills/vicinae-extension-authoring
Command: npx skills add https://github.com/fbosch/dotfiles --skill vicinae-extension-authoring

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Create and standardize Vicinae extensions to reduce setup time and ensure consistent architecture across projects.

Core Features & Use Cases

  • Encourage using official extension-template patterns for scalable structure
  • Guide manifest, preferences, and data access patterns with Vicinae tooling
  • Enforce UI/UX and caching guidelines to deliver reliable extensions

Quick Start

Create a new extension directory following the minimal structure and start the development workflow.

Frequently Asked Questions about vicinae-extension-authoring

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I structure a new Vicinae extension project?▼

Structure a Vicinae extension by following the official extension-template patterns to establish a scalable project layout. This involves creating the required directory structure, defining the manifest, and setting up preferences before beginning development.

What data access patterns should I use for Vicinae extension development?▼

Use data access patterns backed by React Query persistence to manage state within Vicinae extensions. Following the codified cache-patterns reference workflows ensures reliable data fetching and consistent caching behavior across the extension.

Does Vicinae extension authoring require specific UI and UX guidelines?▼

Vicinae extension authoring requires adherence to specific UI and UX guidelines, particularly action panel UX standards. Enforcing these standards during development guarantees that the resulting extension delivers a consistent and reliable user interface.

What's the best way to update an existing Vicinae extension to current standards?▼

Update an existing Vicinae extension by aligning its manifest, preferences, and data access patterns with the current extension-template structure. Applying the latest cache-patterns and UI guidelines ensures the extension remains production-ready.

Can I use custom caching logic instead of the standard Vicinae cache-patterns?▼

Vicinae extension authoring codifies specific cache-patterns using React Query persistence to ensure consistent architecture. Deviating from these standard data access patterns is discouraged as it compromises the reliable caching behavior expected across extensions.

Why do I need to follow an extension template for Vicinae development?▼

Following an extension template for Vicinae development reduces initial setup time and ensures consistent architecture across projects. It provides a standardized structure for manifests, preferences, and data workflows required for production-ready extensions.