c3-component-design

What problem does it solve?

This Skill guides developers in documenting the lowest level of architecture (Component), focusing on implementation details, configuration, and technical specifics. It ensures that component documentation is precise, adheres to higher-level architectural constraints, and remains relevant over time.

Core Features & Use Cases

• Inherits Full Hierarchy: Automatically loads and verifies constraints from both the parent Container and the overarching Context layer.
• Content Longevity Principles: Emphasizes documenting generic patterns over specific code, and flows over exhaustive implementation details, to keep documentation stable.
• Critical Decision Framework: Helps determine if a change is truly contained within the component or requires escalation to higher architectural layers.
• Determines Component Nature: Identifies if a component is a resource integration, business logic, or framework entrypoint to tailor documentation focus.
• Socratic Discovery: Uses targeted questions to elicit details about configuration, behavior, error handling, and usage patterns.
• Use Case: A developer needs to document a new database connection pool component. This skill helps them detail its configuration, error handling, and usage patterns, ensuring it aligns with the container's technology stack and the system's cross-cutting concerns.

Quick Start

Use the c3-component-design skill to document the new user authentication component.