Forma Validation — Rendered UI Evidence — AI skill

When to use it

Provide the loaded revision, routes, acceptance criteria, baseline and supported states/devices. Use for post-change UI QA, reference comparisons, persistence/recovery checks and evidence-backed findings. Requires real browser/tool access for rendered claims; passing a build or automated fixture is not visual proof or accessibility certification. Broader than an aesthetic critique and does not authorize fixes outside the requested scope. Reviewed upstream documentation only; not installed or runtime-tested. GitHub stars are repository-wide, not skill-specific.

Compatible agents

CodexClaude CodeCursorGitHub CopilotOpenCodeGemini CLI

Installation

Use the complete Forma package, not this SKILL.md alone. Codex: clone https://github.com/figueirego/forma.git; from the clone run `codex plugin marketplace add .` then `codex plugin add forma@forma-community`. Claude Code: `claude plugin marketplace add figueirego/forma` then `claude plugin install forma@forma-community`. Start a new session. Other supported Agent Skills hosts: copy all 12 folders from distributions/agent-skills/ into the host-recognized skills directory, retaining shared resources. See upstream docs/INSTALLATION.md; choose one format per assistant.

Review the source and instructions before installing in your agent.

License

MIT

Last checked Nov 1, 2026.

Pair this skill with a visual reference

A skill guides how your agent works; a design reference shows the direction you want. Choose an example for a specific job, such as the headline hierarchy or form layout, and keep your project's existing design rules explicit.

Start with design references you can inspect, then use our guide to briefing an AI coding agent to turn observations into requirements. If you need implementation components, compare UI libraries for your stack.

These pages are public. Browsing a skill does not install it, and TastefulKit's design-reference MCP tools do not search the AI-skill directory.