Proof icon

Proof

Proof is an open-source product design skill for Claude Code and Codex. It helps turn page briefs into structured product designs with page-type, layout, content-scope, style, and theme decisions.

Proof

Product overview

Proof is an open-source product design skill for Claude Code and Codex, turning page briefs into structured designs with layout, content, style, and theme decisions. It turns a short page brief into a structured product-page direction, making decisions about visual treatment, section layout, content hierarchy, page scope, and audience rather than focusing only on surface styling.

The documented workflow is intentionally compact: install the skill, name a page type, choose a style and theme, and ask the agent to design the page. Users can also provide deeper constraints such as sections, brand color, font, and section order, or request an individual section instead of a full page. The site presents eight page types, four visual styles, and light and dark variants.

Core capabilities

Designs beyond visual styling

Proof designs surface styling, section layout, section order, inclusion or omission of sections, and page strategy rather than styling an otherwise fixed page.

Brief-informed page structure

A brief can be matched to page patterns learned from more than 400 shipped pages, according to the product site.

Eight page types

Generate landing, pricing, product, about, contact, blog, downloads, and 404 pages from the documented page-type set.

Four styles with theme variants

Choose minimal, business, colorful, or editorial direction, each with light or dark theme options.

Expert controls and section-level generation

Set or override sections, brand color, display font, and section order; the site also documents standalone section generation.

Claude Code and Codex workflow

Use the skill in Claude Code or Codex through a marketplace/plugin route, skills CLI, or manual repository installation.

Practical use cases

  • Rapid first-draft exploration

    Give the agent a single sentence and let Proof infer the page archetype, structure, and visual direction for an initial landing-page draft.

  • Compare visual directions

    Use the page-type and style combinations to explore materially different directions for the same product brief, rather than changing only colors or typography.

  • Apply brand and content constraints

    Provide brand color, display font, section order, and inclusion or omission rules when a page must follow an existing brand or content plan.

  • Design one section at a time

    Request a focused output such as a hero, features section, FAQ, integrations block, or contact form when a complete page is not needed.

  • Standardize agent-assisted page work

    Install the skill in Claude Code or Codex and use the resulting agent workflow for repeated page-design tasks across the documented page types.

Pros and Cons

Pros

  • Addresses content hierarchy and page scope as well as visual styling.
  • Offers eight documented page types and four distinct visual directions with light and dark variants.
  • Supports both quick one-line briefs and more granular controls over sections, branding, typography, and order.
  • Provides multiple installation paths and is described as free and open source.
  • Includes individual section generation for requests such as hero, features, FAQ, integrations, and contact forms.

Cons

  • The available evidence does not establish integrations or supported agents beyond Claude Code and Codex.
  • The supplied pricing URL returns a not-found page, so paid-plan details and pricing amounts are not confirmed.
  • The product is an agent skill and requires installation in the relevant Claude Code or Codex workflow rather than functioning as a standalone page editor.

FAQ

How do you install Proof?

Proof is installed as a skill for Claude Code or Codex. The site documents Claude Code marketplace installation, a skills CLI installation path, and manual repository-copy methods for Claude and Codex skills folders.

How do you use Proof after installation?

After installation, provide a page type, visual style, and theme. The documented examples include commands such as `/proof:proof landing business dark` for Claude Code and `Use the proof skill: landing page, business style, dark` for Codex.

What kinds of pages can Proof design?

Proof supports eight page types: landing, pricing, product, about, contact, blog, downloads, and 404. It also supports four visual styles—minimal, business, colorful, and editorial—with light and dark themes.

How much control does the user have over the generated page?

The site describes both a one-sentence workflow and more explicit controls. Users can provide a brief or specify sections, brand color, font, and section order; the tool can also generate individual section types such as hero, features, FAQ, integrations, and contact form.

How much does Proof cost?

Proof is presented as free and open source, with the source, documentation, and test set available on GitHub. The supplied pricing URL is not an active pricing page, so no paid plans or pricing amounts are established by the available evidence.

Quick Facts

Category
Developer Tool; Design Tool
Product type
Open-source product design skill
Supported agents
Claude Code and Codex
Page types
8: landing, pricing, product, about, contact, blog, downloads, and 404
Visual system
4 styles: minimal, business, colorful, and editorial; light and dark themes
Source
proofdesign.dev; source and documentation linked through GitHub