reference-sections

Select component types by matching your need: use skills for encapsulated knowledge, agents for multi-step workflows, commands for enforcement, and hooks for cross-component interactions. Reference-sections guidance helps you align component choice with isolation requirements, delegation patterns, and architectural cohesion in plugin systems.

Structure multi-component solutions by designing isolation patterns, establishing return-based delegation between components, and using progressive disclosure to manage complexity. Apply reference-section decision tables to determine component boundaries, interaction points, and when to delegate debugging or specialized tasks to separate components.

Use return-based delegation when components need isolation, error handling independence, or specialized processing. Reference documentation tables clarify when direct interaction works versus when delegation patterns reduce coupling and improve maintainability in Box Factory contexts.

Apply isolation patterns by defining clear component responsibilities, using return-based interfaces, and structuring deep-dive links that reference rather than embed related knowledge. Reference sections provide decision guidance for balancing component independence with workflow cohesion.

Use reference sections with tables and structured bullets for at-a-glance component selection guidance. This format enables fast decision-making when choosing between skill, agent, command, and hook types while accommodating knowledge-delta filtering and cross-component interaction requirements.

Yes. Retrofit reference sections into existing architectures by extracting decision criteria from current component interactions, documenting isolation patterns and delegation flows, and progressively disclosing complexity through guided decision tables that help users and maintainers navigate component selection.