component-designer

To document a Drupal service component, this Skill generates detailed Markdown specifications by identifying the component type, gathering its details, finding relevant core pattern references, and outputting clear purpose, interface, dependencies, and acceptance criteria.

Designing Drupal module components like forms and entities is best handled by generating structured architecture documents that define the component type, fields, validation, and submit handlers while referencing similar Drupal core implementations for best practices.

Yes, the component design process references existing Drupal core patterns by leveraging a core pattern finder to identify and integrate similar core implementations into the generated architecture documentation.

Yes, you can use this to generate architecture documentation for Drupal plugins and controllers by defining their specific details, interfaces, and dependencies, and then integrating those specifications into the main architecture document.

You integrate newly designed services into your main software architecture document by using this Skill to update the primary architecture file with the generated component specifications, ensuring all defined dependencies and acceptance criteria are recorded.

To design a software component for Drupal, you need to provide the component name and type, which allows the Skill to prompt for necessary details like purpose, interface, dependencies, and acceptance criteria to complete the specification.