What problem does it solve? Modeling a ContentType in Weegloo involves subtle decisions—choosing between ShortText, LongText, and RichText based on CDA search semantics, setting per-field localization, and applying correct FieldValidation shapes—that are easy to get wrong and costly to migrate later. ## Core Features & Use Cases - Search-aware field typing: Selects ShortText, LongText, or RichText based on whether CDA full-text search will actually run on the field, defaulting to RichText for non-searchable body copy. - Validation design: Builds FieldValidation payloads (regexp, in, size, range, dateRange, unique, media constraints, referContentType) with correct API shapes and per-type applicability. - Localization and relationships: Decides localized true vs false per field, models relationships as Refer fields instead of raw id strings, and configures publishWithAuthor for author exposure on the delivery plane. - Use Case: When building a blog or resume site on Weegloo, use this Skill to design the post, comment, and profile ContentTypes with correct field types, validations, and self-referencing reply threads before any Content is created. ## Quick Start Ask the agent to create a Weegloo ContentType for blog posts with a title, body, tags, and an author-visible comment thread.
