What problem does it solve?
This Skill prevents the creation of poorly named or ambiguously reused fields that can lead to configuration sync issues, developer confusion, and difficult content management. It ensures your field architecture is clear, consistent, and maintainable.
Core Features & Use Cases
- Consistent Machine Names: Generate machine names following patterns like
field_[bundle]_[short] for specific fields and generic names for shared fields.
- Mandatory Descriptions: Ensure every field has a clear description, aiding developers and content editors in understanding its purpose.
- Safe Reuse Guidance: Get advice on when fields can be safely reused across different content entities without causing semantic or configuration conflicts.
- Use Case: When adding an "Author" field to an
Article content type, use this Skill to ensure its machine name is field_article_author, it has a clear description, and you understand if it's safe to reuse for other content types.
Quick Start
List fields for an event bundle with machine names, descriptions, directory guidance for uploads, and whether each field can be safely reused elsewhere.
