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.
Route ordinary product implementation and explicit Lamina lifecycle requests.
Install Lamina
$ npx skills add aryaniyaps/lamina --skill lamina -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install aryaniyaps/lamina lamina --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 .claude/skills/lamina && 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" agent skill from https://github.com/aryaniyaps/lamina/tree/main/skills/lamina into .claude/skills/lamina/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "lamina", 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/laminaType 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 -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install aryaniyaps/lamina lamina --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 .agents/skills/lamina && 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" agent skill from https://github.com/aryaniyaps/lamina/tree/main/skills/lamina into .agents/skills/lamina/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "lamina", 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 -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install aryaniyaps/lamina lamina --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 .cursor/skills/lamina && 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" agent skill from https://github.com/aryaniyaps/lamina/tree/main/skills/lamina into .cursor/skills/lamina/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "lamina", 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--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 -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install aryaniyaps/lamina lamina --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 .gemini/skills/lamina && 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" agent skill from https://github.com/aryaniyaps/lamina/tree/main/skills/lamina into .gemini/skills/lamina/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "lamina", 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 laminaInstalls 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 -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 .github/skills/lamina && 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" agent skill from https://github.com/aryaniyaps/lamina/tree/main/skills/lamina into .github/skills/lamina/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "lamina", 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 -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 --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 .opencode/skills/lamina && 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" agent skill from https://github.com/aryaniyaps/lamina/tree/main/skills/lamina into .opencode/skills/lamina/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "lamina", 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- GitHub stars
- 116
- Token cost
- ~1.5k tokens
- SKILL.md length
- 689 words
- Files
- 40 (incl. references)
- Skills in repo
- 10
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Route ordinary product implementation and explicit Lamina lifecycle requests.
- Works in 3 steps: Open the selected capability's sibling… → Open every topic reference needed for… → Begin the answer with Using : .
- Frontend & Design work in your project
- SKILL.md covers Workflow routes, Capability routes, Ordinary implementation contract and Hard rules
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Lamina is an agent skill from aryaniyaps/lamina. Route ordinary product implementation and explicit Lamina lifecycle requests. Use passively after initialization for changes to product behavior, flows, permissions, states, failures, or UI; skip purely mechanical maintenance.
Its SKILL.md is about 1.5k tokens, which your agent loads only when the skill is triggered. The skill folder holds 45 other files, including reference files (for example `orchestrator/agents/research-synthesizer.md`, `orchestrator/agents/ux-lens-reviewer.md` and `orchestrator/artifacts.md`).
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”
Workflow steps
3 steps, taken from the first numbered list in SKILL.md.
- Open the selected capability's sibling SKILL.md.
- Open every topic reference needed for the answer.
- Begin the answer with Using : .
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 loads about 1.5k tokens when it runs, and up to ~7.2k if it reads all its reference files. Until then it costs about 58 tokens; SKILL.md has 689 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). 689 words, ~1,487 tokens.
Download SKILL.mdSave it as
.claude/skills/lamina/SKILL.md (or your agent's skills folder). This skill also uses 39 other files; get the full folder from GitHub.- name
- lamina
- description
- Route ordinary product implementation and explicit Lamina lifecycle requests. Use passively after initialization for changes to product behavior, flows, permissions, states, failures, or UI; skip purely mechanical maintenance.
/lamina
Use this as the compact Lamina router. The public catalog has four workflow skills and six capability skills. Load only the entrypoint and topic references needed for the current request.
Before graph work, read
the CLI prerequisite. /lamina-init
is the one explicit onboarding action. After initialization, ordinary product
implementation language is the primary route.
Workflow routes
/lamina-init: use lamina-init.- Ordinary feature, behavior fix, flow refactor, or UI work: prepare the graph
context, complete design gaps with lamina-design,
derive and check the WorkMap, implement, collect evidence, and run
lamina work verify. - Explicit
/lamina-design: use lamina-design as a graph-only advanced override; never edit application source in that phase. - Explicit
/lamina-verify: use lamina-verify as a source-read-only advanced override; never edit application source in that phase. - Focused product question: select one primary capability below, read its
SKILL.md, then read the smallest relevant topic set before answering. Start the response withUsing <capability>: <topic(s)>so routing is visible and deprecated focused names are never implied.
Never recommend /lamina-design or /lamina-verify as a next step in normal
flow. Execute the required phase implicitly. Ask a question only when an
unresolved decision would materially change the product contract.
Classify wording by requested action, not by the presence of a product problem: “help with,” “what should,” “how should,” critique, explanation, or planning without a request to change repository files is a focused question. Answer it through capability references without requiring initialization or entering the implementation workflow. Requests to add, fix, redesign, refactor, or otherwise change product behavior use the ordinary implementation route.
Focused-question protocol
For a focused question, do not answer from this router alone and do not suggest the implementation lifecycle. You must:
- Open the selected capability's sibling
SKILL.md. - Open every topic reference needed for the answer.
- Begin the answer with
Using <capability>: <topic(s)>.
If the sibling or reference cannot be read, report the missing installed path instead of improvising its guidance.
Capability routes
| Need | Skill |
|---|---|
| Evidence scope, actor walks, grounding, synthesis, research communication | lamina-research |
| Problem framing, business context, priorities, requirements, tradeoffs | lamina-product-discovery |
| Flows, IA, navigation, forms, content, accessibility, feedback, trust | lamina-ux |
| Invariants, dependencies, consistency, concurrency, time, side effects | lamina-product-behavior |
| Structure, feedback loops, traps, leverage, evolution | lamina-systems |
| Persona usability, heuristic review, quantitative validation | lamina-evaluation |
For detailed signal-to-topic routing, read the problem router. Old public names are a hard cutover; use the installed legacy-name lookup to locate their new capability and topic. Read the optional glossary only when unfamiliar Lamina or product-design terminology blocks routing; it is not a second topic index.
Show full SKILL.md (271 more words)Show less
Ordinary implementation contract
- Run
lamina work preparewithout--workflowfirst. Never invent a workflow ref; narrow only a genuinely ambiguous result with an exact ref. - If design gaps exist, run one independent graph-resident Persona walk per active Persona, union discoveries, expand the graph, and repeat the full round until every discovery array is empty.
- Run
lamina work map, resolve every obligation and Persona-bound Experience Case to valid implementation and test files, then runlamina work check. The checked map is immutable. - Implement the mapped work.
- Reconcile with one-shot
lamina graph observe, run and publish every active Persona Mission, and passlamina work verifywith the unchanged map.
Every current Persona walk covers every operation node, including denied and inapplicable nodes, and explicitly evaluates authorization, inputs, relationship identity and cardinality, required states, declared Scenarios, Invariant probes, transitions, and all required edge-case axes. Graph closure is authoritative; source retrieval only localizes evidence and code.
Every compiled Experience Case needs one passing oracle event with a structured observation and reproducible artifact. UI obligations require distinct functional, visual, responsive, and accessibility evidence. Missing audit capability blocks verification.
Hard rules
- Ladybug is canonical and
graphdis the sole writer. - Never expose raw Cypher or accept caller-supplied epistemic or approval state.
- Never treat legacy run files, graph dumps, generic screenshots, or broad mappings as substitutes for current graph and Mission evidence.
- Use sessions for multi-fact design changes and preserve stable Resource identity.
- Do not cap active Personas.
- Explicit design and verification phases do not edit application source.
Supporting orchestration is internal to this skill under
orchestrator/; it is not a public skill.
© 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
SKILL.md and 39 other files (references) in skills/lamina of aryaniyaps/lamina.
- SKILL.md
- orchestrator/agents/research-synthesizer.md
- orchestrator/agents/ux-lens-reviewer.md
- orchestrator/artifacts.md
- orchestrator/audit-profiles.yaml
- orchestrator/load-protocol.md
- orchestrator/merge-rules.md
- orchestrator/patterns/fresh-context.md
- orchestrator/patterns/parallel-review.md
- orchestrator/patterns/persona-panel.md
- orchestrator/patterns/visual-walkthrough.md
- orchestrator/prerequisites/cli-required.md
- orchestrator/prerequisites/init-required.md
- orchestrator/prompts/checkpoints/continue-or-revise.md
- orchestrator/prompts/manifest.yaml
- … and 25 more
Open the folder on GitHubat commit af269ef
Compare with similar skills
Lamina 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 this skillaryaniyaps/lamina | 116 | — | ~1.5k | Automated safety check: Pass | Apache-2.0 | |
| Web Artifacts Builderanthropics/skills | 180k | 41 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 | 27 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
What does Lamina do?
Route ordinary product implementation and explicit Lamina lifecycle requests. Lamina is an agent skill from aryaniyaps/lamina. Route ordinary product implementation and explicit Lamina lifecycle requests.
When should I use Lamina?
Lamina fits situations like: frontend & Design work in your project.
How do I install Lamina in Claude Code?
Run `npx skills add aryaniyaps/lamina --skill lamina -a claude-code`. Or copy the skill folder (skills/lamina in aryaniyaps/lamina) into .claude/skills/lamina in your project. Claude Code loads it when a task matches its description.
How do I install Lamina in Codex?
Run `npx skills add aryaniyaps/lamina --skill lamina -a codex`. Or copy the skill folder (skills/lamina in aryaniyaps/lamina) into .agents/skills/lamina in your project. Codex loads it when a task matches its description.
Can I use Lamina 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 -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, .gemini/skills/lamina, .github/skills/lamina and .opencode/skills/lamina in your project.
What does Lamina need to run?
SKILL.md names no scripts, command-line tools or credentials: Lamina is instructions for the agent only.
Does Lamina 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 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 use?
Lamina 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 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. Its references folder adds about 5.7k tokens, read only when the agent opens those files.
What are the alternatives to Lamina?
Skills that share tags, products or a category with Lamina: 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?
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.