Web Artifacts Builder
anthropics/skills
Builds multi-component claude.ai HTML artifacts as a small React, TypeScript and Tailwind project, then bundles it into one shareable HTML file.
Verify graph-backed product Missions after ordinary implementation work or when explicitly invoked as lamina-verify.
Install Lamina Verify
$ npx skills add aryaniyaps/lamina --skill lamina-verify -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install aryaniyaps/lamina lamina-verify --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/aryaniyaps/lamina.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/lamina-verify .claude/skills/lamina-verify && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "lamina-verify" agent skill from https://github.com/aryaniyaps/lamina/tree/main/skills/lamina-verify into .claude/skills/lamina-verify/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "lamina-verify", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/aryaniyaps/lamina/tree/main/skills/lamina-verifyType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add aryaniyaps/lamina --skill lamina-verify -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install aryaniyaps/lamina lamina-verify --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/aryaniyaps/lamina.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/lamina-verify .agents/skills/lamina-verify && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "lamina-verify" agent skill from https://github.com/aryaniyaps/lamina/tree/main/skills/lamina-verify into .agents/skills/lamina-verify/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "lamina-verify", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add aryaniyaps/lamina --skill lamina-verify -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install aryaniyaps/lamina lamina-verify --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/aryaniyaps/lamina.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/lamina-verify .cursor/skills/lamina-verify && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "lamina-verify" agent skill from https://github.com/aryaniyaps/lamina/tree/main/skills/lamina-verify into .cursor/skills/lamina-verify/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "lamina-verify", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/aryaniyaps/lamina.git --path skills/lamina-verify--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add aryaniyaps/lamina --skill lamina-verify -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install aryaniyaps/lamina lamina-verify --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/aryaniyaps/lamina.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/lamina-verify .gemini/skills/lamina-verify && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "lamina-verify" agent skill from https://github.com/aryaniyaps/lamina/tree/main/skills/lamina-verify into .gemini/skills/lamina-verify/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "lamina-verify", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install aryaniyaps/lamina lamina-verifyInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add aryaniyaps/lamina --skill lamina-verify -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/aryaniyaps/lamina.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/lamina-verify .github/skills/lamina-verify && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "lamina-verify" agent skill from https://github.com/aryaniyaps/lamina/tree/main/skills/lamina-verify into .github/skills/lamina-verify/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "lamina-verify", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add aryaniyaps/lamina --skill lamina-verify -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install aryaniyaps/lamina lamina-verify --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/aryaniyaps/lamina.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/lamina-verify .opencode/skills/lamina-verify && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "lamina-verify" agent skill from https://github.com/aryaniyaps/lamina/tree/main/skills/lamina-verify into .opencode/skills/lamina-verify/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "lamina-verify", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
lamina-verify- GitHub stars
- 116
- Token cost
- ~1.5k tokens
- SKILL.md length
- 715 words
- Files
- 1
- Skills in repo
- 10
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Verify graph-backed product Missions after ordinary implementation work or when explicitly invoked as lamina-verify.
- Works in 9 steps: Run lamina mission compile --workflow .… → Select adapters only through… → Give every Persona an independent… → …
- Frontend & Design work in your project
- SKILL.md covers Gate and grounding, Mission protocol, Completion and Hard rules
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Lamina Verify is an agent skill from aryaniyaps/lamina. Verify graph-backed product Missions after ordinary implementation work or when explicitly invoked as lamina-verify. Run isolated Persona and live UI audits; explicit verification is source-read-only.
Its SKILL.md is about 1.5k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Frontend & Design. The repository describes itself as: Headless product design for AI coding agents, backed by a transactional product graph | Design how it works, verify what you ship. The licence is Apache-2.0.
When your agent uses it
- Frontend & Design work in your project
Example prompts
- “/lamina-verify”
Workflow steps
9 steps, taken from the first numbered list in SKILL.md.
- Run lamina mission compile --workflow . This must return one independent Mission for every active Persona; there is no maximum of three.
- Select adapters only through capability_manifest Resources. Unknown modalities are strings and require no database migration.
- Give every Persona an independent adapter context and Run session. Do not share mutable login, browser, process, clock, device, or fixture…
- Exercise every compiled Experience Case, including actor inputs and
- Save large artifacts to the local evidence CAS. Pass normalized events to
- mission run returns an isolated staged session. Publish that exact session
- Only adapter-observed events in a published Run become runtime evidence.
- Missing/corrupt evidence, stale source snapshots, budget failures, or capability failures invalidate related readiness; they never…
- Query the resulting GraphVersion and report product gaps, intended-contract gaps, and operational limitations separately. Conflicting…
What it can do on your machine
Read from SKILL.md and the folder at commit af269ef. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Lamina Verify loads about 1.5k tokens when it runs. Until then it costs about 54 tokens; SKILL.md has 715 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from aryaniyaps/lamina at commit af269ef, republished under its Apache-2.0 licence (© aryaniyaps). 715 words, ~1,468 tokens.
Download SKILL.mdSave it as
.claude/skills/lamina-verify/SKILL.md (or your agent's skills folder).- name
- lamina-verify
- description
- Verify graph-backed product Missions after ordinary implementation work or when explicitly invoked as lamina-verify. Run isolated Persona and live UI audits; explicit verification is source-read-only.
/lamina-verify
Verification reads the active GraphVersion and publishes runtime Evidence through isolated Mission sessions. It never discovers, selects, or mutates the active GraphVersion.
Verification Missions are the runtime replay of Persona-bound Experience Cases. They do not replace the earlier design-time Persona simulations that must discover and expand new-feature flows before implementation begins.
Gate and grounding
First read and apply
../lamina/orchestrator/prerequisites/cli-required.md. Stop before all
mutations unless the CLI API 1 prerequisite passes.
Require valid .lamina/business-context.md using ../lamina/orchestrator/prerequisites/init-required.md; on failure emit ../lamina/orchestrator/prompts/outputs/init-blocked.md. Then run lamina graph status. Query the requested workflow and its actors, Personas, Operations, invariants, Scenarios, Proofs, Surfaces, dependencies, and Contradictions. Inspect the actual product using a runnable adapter when available; otherwise record static-analysis capability limits. Absence of an Observation is never evidence that behavior is absent.
Read ../lamina/orchestrator/audit-profiles.yaml. Load verify-core.always,
then only the verify-core.conditional entries whose when signal appears in
the Mission closure or request. For each entry, open the named capability
SKILL.md and then its exact reference; do not load sibling topics.
Mission protocol
- Run
lamina mission compile --workflow <workflow-id>. This must return one independent Mission for every active Persona; there is no maximum of three. - Select adapters only through capability_manifest Resources. Unknown modalities are strings and require no database migration.
- Give every Persona an independent adapter context and Run session. Do not share mutable login, browser, process, clock, device, or fixture state.
- Exercise every compiled Experience Case, including actor inputs and requiredness, relationship identity/cardinality, duplicates, self-reference, visible states, denial/failure recovery, and invariant probes.
- Save large artifacts to the local evidence CAS. Pass normalized events to:
lamina mission run <mission-id> --events <events.json>. mission runreturns an isolated staged session. Publish that exact session withlamina session publish <session-id>. When a previously published independent Run advanced the branch, first runlamina session rebase <session-id>, then publish. A staged Run is not verification evidence.- Only adapter-observed events in a published Run become runtime evidence. Persona interpretation remains simulated.
- Missing/corrupt evidence, stale source snapshots, budget failures, or capability failures invalidate related readiness; they never silently pass.
- Query the resulting GraphVersion and report product gaps, intended-contract gaps, and operational limitations separately. Conflicting Statements remain present as a Contradiction and block approval.
For source reconciliation, run the one-shot lamina graph observe. Never run
lamina graph observe --live in a foreground agent turn: live mode is a
persistent operator-owned watcher and cannot be a completion gate.
Allowed normalized event types are action/state/outcome observed, oracle
passed/failed, denial observed, recovery attempted, artifact captured,
audit_passed with a valid audit_kind, and budget/capability failure. Each
oracle_passed or oracle_failed event must name a compiled case_id and
include a structured observation. A passing oracle must reference a
reproducible artifact. The structured event already binds the case, expected
behavior, and observed behavior; do not duplicate it in a second manifest.
Show full SKILL.md (248 more words)Show less
For every Mission whose closure contains a Surface, exercise relevant states in a real runnable UI adapter and capture all four independent audit classes:
functional: interaction and outcome oracle;visual: screenshot or visual-diff inspection;responsive: relevant desktop and mobile viewport evidence;accessibility: semantic tree and automated/manual accessibility evidence.
Emit one audit_passed event per class with its artifact, Mission surface, and
concrete state. A missing browser, viewport, screenshot, or accessibility
capability is a capability failure and must block verification; static
analysis is not a substitute. Do not reuse one artifact across audit classes.
Completion
Verification is complete only when every active Persona Mission ran independently, all required evidence is available and reproducible, and lamina graph validate --at HEAD reports the validation and contradiction state. Human report.md or fix.md may be generated as query projections; they are not truth-bearing runtime inputs.
In passive flow, finish with lamina work verify --packet <packet> --map <work-map>. This command requires published current-source Mission evidence
for every active UI Persona; staged HarnessResults and standalone audit files
cannot satisfy it. Do not recommend that the user invoke a verification skill.
Report the GraphVersion, source revision, Run and HarnessResult ids, evidence gaps, contradictions, and a crisp verified/not-verified verdict.
Hard rules
- Never read or select legacy run directories as runtime state.
- Never fabricate Persona findings or runtime events.
- Never let an agent claim observed, runtime, human, or approved status.
- Never reuse mutable state across Runs.
- Never treat screenshots alone as authoritative-state proof.
- Never edit application source during
/lamina-verify.
© aryaniyaps, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in skills/lamina-verify of aryaniyaps/lamina.
Open the folder on GitHubat commit af269ef
Compare with similar skills
Lamina Verify next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Lamina Verify this skillaryaniyaps/lamina | 116 | — | ~1.5k | Automated safety check: Pass | Apache-2.0 | |
| Web Artifacts Builderanthropics/skills | 180k | 40 repos | ~769 | Automated safety check: Pass | Apache-2.0 | |
| React Doctormakeplane/plane | 61k | 12 repos | ~657 | Automated safety check: Pass | AGPL-3.0 | |
| Impeccablebestofjs/bestofjs | 3.1k | 26 repos | ~2.6k | Automated safety check: Pass | MIT | |
| Figma Design System Builderwarpdotdev/warp | 65k | 2 repos | ~4.4k | Automated safety check: Pass | AGPL-3.0 | |
| Web Interface Guidelines Reviewervercel-labs/openreview | 1.7k | 97 repos | ~308 | Automated safety check: Pass | None |
Similar skills
- Official
React Doctor
makeplane/plane
Scans React code for lint, accessibility, bundle size and architecture issues, reports a health score and checks that changes do not lower it.
Impeccable
bestofjs/bestofjs
A skill your agent uses when the user wants to design, redesign, shape, critique, audit, polish, clarify, distill, harden, optimize, adapt, animate, colorize, extract, or otherwise improve a…
Figma Design System Builder
warpdotdev/warp
Builds or updates a design system in Figma from a codebase in ordered phases: discovery, variables and tokens, components, theming and documentation, with checkpoints.
- Official
Web Interface Guidelines Reviewer
vercel-labs/openreview
Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", "review UX", or "check my…
Tailwindcss Development
anonaddy/anonaddy
Always invoke when the user's message includes 'tailwind' in any form.
More from aryaniyaps/lamina
All 10 skills in this repoLamina Product Behavior
aryaniyaps/lamina
Define authoritative runtime product truth across actors and views.
Lamina Product Discovery
aryaniyaps/lamina
Frame product problems and decide what to build. An agent skill from aryaniyaps/lamina.
Lamina Research
aryaniyaps/lamina
Plan and synthesize evidence-grounded product research. An agent skill from aryaniyaps/lamina.
Lamina Systems
aryaniyaps/lamina
Reason about causal product systems and change over time. An agent skill from aryaniyaps/lamina.
Lamina UX
aryaniyaps/lamina
Design understandable and accessible product interactions. An agent skill from aryaniyaps/lamina.
Lamina Evaluation
aryaniyaps/lamina
Judge product usability and evidence quality. An agent skill from aryaniyaps/lamina.
Related
Categories
Questions about Lamina Verify
What does Lamina Verify do?
Verify graph-backed product Missions after ordinary implementation work or when explicitly invoked as lamina-verify. Lamina Verify is an agent skill from aryaniyaps/lamina. Verify graph-backed product Missions after ordinary implementation work or when explicitly invoked as lamina-verify.
When should I use Lamina Verify?
Lamina Verify fits situations like: frontend & Design work in your project.
How do I install Lamina Verify in Claude Code?
Run `npx skills add aryaniyaps/lamina --skill lamina-verify -a claude-code`. Or copy the skill folder (skills/lamina-verify in aryaniyaps/lamina) into .claude/skills/lamina-verify in your project. Claude Code loads it when a task matches its description.
How do I install Lamina Verify in Codex?
Run `npx skills add aryaniyaps/lamina --skill lamina-verify -a codex`. Or copy the skill folder (skills/lamina-verify in aryaniyaps/lamina) into .agents/skills/lamina-verify in your project. Codex loads it when a task matches its description.
Can I use Lamina Verify in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add aryaniyaps/lamina --skill lamina-verify -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/lamina-verify, .gemini/skills/lamina-verify, .github/skills/lamina-verify and .opencode/skills/lamina-verify in your project.
What does Lamina Verify need to run?
SKILL.md names no scripts, command-line tools or credentials: Lamina Verify is instructions for the agent only.
Does Lamina Verify access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Lamina Verify safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Lamina Verify use?
Lamina Verify is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Lamina Verify use?
About 1.5k tokens (SKILL.md is roughly 5.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Lamina Verify?
Skills that share tags, products or a category with Lamina Verify: Web Artifacts Builder (anthropics/skills, 180k stars), React Doctor (makeplane/plane, 61k stars), Impeccable (bestofjs/bestofjs, 3.1k stars) and Figma Design System Builder (warpdotdev/warp, 65k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Lamina Verify?
aryaniyaps (a GitHub user) maintains it in aryaniyaps/lamina, which has 116 GitHub stars. The repository holds 10 skills in this directory. The repository was last updated on October 1, 2026.
Source: aryaniyaps/lamina on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.