How are you informing agents what to use at a higher level (content blocks, object patterns, page templates, etc.)
We have a pretty decent design system up and running for our AI based development at the component level. It currently consists of:
- tokens (+ the CSS)
- UI component library (react components along with some guidelines)
- "Patterns" (which, at the moment, are essentially 'objects on a page that may consist of one or more components + additional layout elements)
For an example of patterns:
- site navigation
- custom data labelling
- page footer
- etc
We now want to accommodate a higher level of instructions. Essentially, building upon what we have to create content and object layouts and even full page templates.
I'm curious as to how you may be doing that. Some specific questions:
- Are you using any specific terminology? Right now we're thinking of sticking with 'patterns' and possibly 'page templates'. Maybe with some sort of 'content template' in between. But not sure how important these semantics are for an agent (let alone a human).
- Do these more application-centric page level guidelines exist in your design system? In the application development environment? A bit in both?
- Are you using any formal type of documentation for the agent to help it quickly figure out what it should be using for content type 'x' with minimal token usage?