plugin-architecture

Load architecture principles and patterns for marketplace component design.

4|Updated Jan 11, 2026
One-click install
npx skills add https://github.com/cuioss/plan-marshall --skill plugin-architecture-cuioss
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: plugin-architecture
Source: https://github.com/cuioss/plan-marshall/tree/main/marketplace/bundles/pm-plugin-development/skills/plugin-architecture
Command: npx skills add https://github.com/cuioss/plan-marshall --skill plugin-architecture-cuioss

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This reference skill provides architecture principles, patterns, and design guidance for building goal-based marketplace components. It helps teams align on architecture decisions by exposing core concepts in a portable, self-contained reference library.

Core Features & Use Cases

  • Architecture Foundation: Core principles for building marketplace components that follow skills best practices and goal-based organization.
  • Skill Patterns: Guidance on 10 patterns for constructing scalable skills, commands, and bundles.
  • Design Guidance: Progressive disclosure, relative path usage, and resource organization to maintain portability and coherence across installations.
  • Use Cases: Education, design reviews, architecture validation, and on-demand reference loading during development.

Quick Start

Load core principles and patterns references on-demand to start aligning your component design with the goal-based approach.

Frequently Asked Questions about plugin-architecture

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

FAQPage Schema
What are the core architecture principles for building marketplace components?▼

Core architecture principles for marketplace components include goal-based organization, progressive disclosure, relative path portability, and self-containment to ensure components remain coherent and portable across installations.

How do I apply scalable patterns when designing marketplace skills?▼

Design scalable marketplace skills by applying the 10 provided architecture patterns to construct skills, commands, and bundles while maintaining progressive disclosure and self-containment during development.

Does this architecture reference require any specific dependencies or setup?▼

No dependencies are required to use this architecture reference. It operates as a self-contained library, loading core principles, patterns, and rules on-demand through skill invocations without prerequisite environment setup.

When should I use a goal-based architecture approach for component design?▼

Use a goal-based architecture approach during design reviews, training sessions, architecture validation, and audits to align teams on component decisions and load required design guidance on-demand.

How does progressive disclosure work in marketplace component architecture?▼

Progressive disclosure in marketplace component architecture loads core principles, patterns, and rules on-demand through skill invocations, satisfying portability and self-containment without overwhelming users upfront.

What is the best way to maintain portability across marketplace component installations?▼

Maintain portability across marketplace component installations by using relative paths, ensuring self-containment, and organizing resources according to the reference library's architecture patterns and design guidance.