Structured decision support
Use a supported pattern when visual organization materially helps.
- Comparisons
- Scannable steps
- FAQs or verification panels
Temporary builder example — not for publication or navigation.
Temporary KLR builder reference
Choose a supported element for a real reader task, generate its semantic HTML, and place it inside a normal AgentLoft content-area. The global kit supplies structure and chrome while the KLR theme supplies typography.
Minimum markup
Use the renderer when available. This abbreviated HTML shows the underlying contract.
<section class="al-ce" data-al-element="fit_cards">
<h2>Choose a page pattern</h2>
<div class="al-ce__grid al-ce__grid--auto">
<article class="al-ce__card">
<h3>Card heading</h3>
<p>Useful, page-specific content goes here.</p>
</article>
</div>
</section>Choose deliberately
The element should make a comparison, sequence, evidence trail, or next action easier to understand.
Use a supported pattern when visual organization materially helps.
Use semantic headings, paragraphs, and lists when the content already reads clearly.
Pattern examples
Use a decision grid when two options need balanced tradeoff framing.
Use steps, check panels, or tour preparation when the reader needs an action sequence.
Use FAQs, source strips, or stat tiles when evidence or definitions need scan value.
These numbers describe the pattern library—not a market or property claim.
Confirm that the element improves the page rather than decorating it.
Placement examples
A quick answer can orient the reader before a longer explanation.
Cards or a comparison grid can organize material distinctions.
An FAQ, check panel, or CTA can clarify the next useful step.
Decide what relationship or sequence needs visual structure.
Use the content-element renderer instead of inventing a lookalike.
Persist it in a content-area, then check the rendered page at desktop and mobile widths.
Listing-page example
An inventory-rescue band explains a thin grid without disguising it or making a market promise.
No. It is a small pattern library for relationships that benefit from visual structure.
Not silently. Propose the new pattern, document its purpose, and add it to the shared kit only after approval.
No. This page is a pattern library. A real page should use only the few elements justified by its reader task.
Do not copy its wording into a public market page. Reuse the element contract and write content for the actual page.