What is the main benefit of this convention?

It ensures plugins are modular, reusable, and easy to maintain by decoupling components through a strict separation of concerns.

Why are hardcoded names and proper nouns prohibited?

Prohibiting specific names ensures portability and reusability across different projects and environments without requiring manual modification.

How does this skill handle component dependencies?

Dependencies are strictly managed by Commands, which act as orchestrators, keeping Agents and Skills completely independent of each other.

What is the difference between a Workflow Skill and a Convention Skill?

Workflow Skills execute specific tasks and generate outputs (often using templates), while Convention Skills define standards and rules without generating files.

Where should I place agent files according to this convention?

Agent files should be placed in the [plugin-name]/agents/ directory using kebab-case filenames (e.g., development-agent.md).

Plugin Architecture Convention

Name: Plugin Architecture Convention
Author: RevTechStudio

byRevTechStudio

Developer Tools

Defines standardized architectural principles for building modular, independent, and reusable Claude Code plugins.

About

This skill establishes a robust framework for Claude Code plugin development by enforcing clear separation between Agents, Skills, and Commands. It ensures that components remain independent and reusable while delegating dependency management exclusively to Commands. By prohibiting hardcoded references and specific proper nouns, it facilitates the creation of maintainable, scalable, and portable automation tools that can be easily shared and integrated across various projects and environments.

Key Features

Role-based separation of Agents, Skills, and Commands
Guidelines for generic, reusable naming and naming conventions
Standardized directory structures and file placement rules
Strict dependency management via Command-level orchestration
Classification systems for Workflow and Convention skills
0 GitHub stars

Use Cases

Designing a new Claude Code plugin from scratch with a scalable architecture
Reviewing existing plugin structures for modularity and component independence
Standardizing development workflows across multiple team-led plugin projects

About

Key Features

Role-based separation of Agents, Skills, and Commands
Guidelines for generic, reusable naming and naming conventions
Standardized directory structures and file placement rules
Strict dependency management via Command-level orchestration
Classification systems for Workflow and Convention skills
0 GitHub stars

Use Cases

Designing a new Claude Code plugin from scratch with a scalable architecture
Reviewing existing plugin structures for modularity and component independence
Standardizing development workflows across multiple team-led plugin projects