plugin-standards

Align plugin development practices with Dante standards for consistent architecture.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/ai-sand-castles/local-marketplace --skill plugin-standards
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plugin-standards
Source: https://github.com/ai-sand-castles/local-marketplace/tree/main/test-automation-plugin/skills/plugin-standards
Command: npx skills add https://github.com/ai-sand-castles/local-marketplace --skill plugin-standards

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill defines the Dante plugin development standards, guiding contributors on architecture, directory structure, and contribution workflows to ensure consistency across the project.

Core Features & Use Cases

  • Defines the plugin's project structure (commands/, skills/, subagents/, docs/, tests/, test_samples/, .sdd/, .claude-plugin/) and the conventions for internal components.
  • Documents the required frontmatter for internal SKILL.md skills and how internal utilities are organized for reuse by commands and subagents.
  • Serves as the reference for onboarding, reviews, and ensuring uniform quality across new contributions.

Quick Start

Follow these standards when contributing to the plugin to ensure consistent structure and practices.

Frequently Asked Questions about plugin-standards

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

FAQPage Schema
What are the required directory structures for Dante plugin development?

Dante plugin development requires specific directories including commands/, skills/, subagents/, docs/, tests/, test_samples/, .sdd/, and .claude-plugin/ to maintain consistent architecture across contributions.

How do I structure internal SKILL.md frontmatter for plugin contributions?

Internal SKILL.md frontmatter must follow Dante plugin standards that specify required metadata fields, ensuring uniform quality and consistent architecture across new contributions during code reviews.

What conventions should I follow when adding commands and subagents to a plugin?

Commands and subagents must follow Dante plugin conventions that organize internal utilities for reuse, aligning with project structure standards to ensure consistent architecture across the plugin repository.

Can I use Dante plugin standards for onboarding new contributors to architecture reviews?

Yes, Dante plugin standards serve as the reference for onboarding, architecture reviews, and code reviews, guiding contributors on directory structure and contribution workflows to ensure project consistency.

How should internal utilities be organized for reuse by plugin commands and subagents?

Internal utilities must be organized according to Dante plugin standards that specify how commands and subagents reuse shared components, ensuring consistent architecture and uniform quality across contributions.

What workflow guidance does Dante provide for plugin contribution reviews?

Dante plugin standards provide workflow guidance for contribution reviews by specifying required frontmatter, directory structures, and conventions for internal components to ensure consistent architecture during onboarding and code reviews.