Effective
HTML

HTML for thinking with agents.

A visual field guide to choosing and making the right artifact: from rough wireframes to working prototypes, diagrams, and small purpose-built interfaces.

Match the artifact to the decision.

HTML earns its place when spatial, visual, comparative, or interactive expression makes the work easier to understand.

Use HTML when the thing itself carries the explanation.

Markdown is often enough. HTML becomes useful when a reader needs to compare structure, manipulate state, inspect relationships, or participate in the idea.

Why HTML?
See structure

Make layout, hierarchy, and responsive choices visible.

Test behavior

Exercise states, feedback, recovery, and product boundaries.

Share the thing

Give collaborators an artifact they can inspect and direct.

One brief. Two different decisions.

The release-readiness example moves from structural exploration to working interaction without confusing the purpose of either stage.

Open the examples