skills.rest
RevTechStudio
RevTechStudioCOMMUNITY
Explore all skills by this author →
GitHub

plugin-architecture-convention

Define standardized plugin architecture conventions for agents, skills, and commands.

Updated Aug 23, 2026
Search Tags:#software design#dependency management#maintainability#design principles#reusability#plugin architecture#AI component design
One-click install
npx skills add https://github.com/RevTechStudio/rts-plugins --skill plugin-architecture-convention
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: plugin-architecture-convention
Source: https://github.com/RevTechStudio/rts-plugins/tree/main/rts-plugin-generator/skills/plugin-architecture-convention
Command: npx skills add https://github.com/RevTechStudio/rts-plugins --skill plugin-architecture-convention

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill establishes the foundational architectural principles for AI plugins, ensuring they are designed for reusability, maintainability, and scalability. It clarifies the roles of agents, skills, and commands, and dictates how dependencies are managed to prevent tightly coupled systems.

Core Features & Use Cases

  • Role Definition: Clearly outlines the responsibilities of agents (overall phase/domain), skills (single-purpose workflow/convention), and commands (orchestration).
  • Dependency Management: Enforces that commands manage all dependencies, ensuring agents and skills remain independent and reusable.
  • Independence & Generality: Prohibits cross-element references and the use of proper nouns within agents and skills, maximizing their portability and reusability across projects.
  • Use Case: When starting a new AI plugin project, use this skill to define the core structure. It will guide you to design independent skills like code-generator and coding-convention, and then orchestrate them via a generate-code command, ensuring a clean, modular architecture.

Quick Start

Explain the core architectural principles for designing a new AI plugin, focusing on agent, skill, and command roles.

Frequently Asked Questions about plugin-architecture-convention

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

FAQPage Schema
How do I design a plugin architecture that keeps agents, skills, and commands independent and reusable?▼

Plugin architecture separates concerns by assigning agents overall domain phases, skills single-purpose workflows, and commands dependency orchestration. This decoupling ensures each component remains independent, portable across projects, and maintainable without tight coupling.

What's the best way to manage dependencies in AI plugin systems to avoid tightly coupled components?▼

Enforce dependency management exclusively through commands while keeping agents and skills free of external references. This ensures dependencies remain explicit, governed centrally, and allows skills and agents to function independently across different projects.

Why should I avoid proper nouns and cross-element references when designing plugin skills?▼

Proper nouns and cross-element references reduce portability and reusability. Generic naming and self-contained skills maximize their applicability across diverse projects and contexts, preventing domain-specific lock-in.

How do I structure a new AI plugin project to ensure maintainability and scalability?▼

Define core architectural principles upfront: establish agent roles for phases, create single-purpose skills with generic names, and orchestrate them via commands. This modular structure enables scaling, maintenance, and independent skill reuse.

Can I use the same skill across multiple AI projects without modification?▼

Yes, when skills follow generality conventions—avoiding proper nouns, cross-element dependencies, and domain-specific logic. Command-managed dependencies ensure skills remain portable and applicable across different agents and projects.

What guidelines should I follow for template handling within workflow skills?▼

Apply explicit template handling conventions that maintain skill independence. Templates should remain generic, avoid embedding project-specific logic, and defer environment-specific values to command-level configuration.

Related Skills

Explore More Software Engineering Skills→
luispabonluispabon
6

go-code-audit

Audit Go codebases and generate ordered, dependency-safe refactoring plans.

Community
Advanced
zgagnonzgagnon
1

adr-review

Review code against project ADRs and report violations with fixes.

Community
Advanced
kazukinagatakazukinagata
3

provider-contract

Define standardized interface contracts for Waggle provider plugins.

Community
Advanced
bjorkgardbjorkgard

V3 DDD Architecture

Decompose monolithic code into modular DDD bounded contexts.

Community
Advanced