mirror of
https://github.com/plannotator/effective-html.git
synced 2026-09-19 01:11:19 +08:00
Michael Ramos
41 lines
1.5 KiB
Plaintext
41 lines
1.5 KiB
Plaintext
---
|
|
title: Why HTML?
|
|
description: Use HTML artifacts when seeing or trying an idea is clearer than reading about it.
|
|
---
|
|
|
|
Agents often answer with prose, and sometimes that is the right format. HTML
|
|
can be easier to understand when you need to compare designs, try a flow,
|
|
inspect a system, or show how something works.
|
|
|
|
<GuideChapterEvidence chapter="why-html" />
|
|
|
|
## What HTML adds
|
|
|
|
HTML can put explanation, layout, state, and interaction in one file. You can
|
|
open it in a browser, test it at real sizes, click through it, annotate it, and
|
|
share it with technical or non-technical collaborators.
|
|
|
|
That makes HTML useful for wireframes, mockups, prototypes, diagrams, visual
|
|
explainers, reports, presentations, and small purpose-built tools.
|
|
|
|
## Keep Markdown when it is enough
|
|
|
|
Markdown is usually simpler for notes, short plans, and linear explanations.
|
|
Use HTML when seeing or trying the idea adds something useful.
|
|
|
|
<GuideHandoff
|
|
artifactHref="/examples"
|
|
artifactLabel="Open the examples"
|
|
artifactDescription="Inspect the release-readiness wireframe and prototype."
|
|
sourceHref="https://github.com/plannotator/effective-html"
|
|
skillHref="https://github.com/plannotator/effective-html/blob/main/skills/html/SKILL.md"
|
|
skillLabel="Read the HTML skill"
|
|
skillDescription="See the general guidance for making HTML artifacts."
|
|
/>
|
|
|
|
<GuideNext
|
|
href="/docs/choosing-fidelity"
|
|
title="Wireframe, mockup, or prototype?"
|
|
description="See the practical difference between the common levels of fidelity."
|
|
/>
|