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.
End-to-end workflow for building a new Terrae component from scratch
$ npx skills add alamenai/terrae --skill new -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install alamenai/terrae new --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/alamenai/terrae.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/new .claude/skills/new && 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 "new" agent skill from https://github.com/alamenai/terrae/tree/main/.claude/skills/new into .claude/skills/new/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "new", 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/alamenai/terrae/tree/main/.claude/skills/newType 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 alamenai/terrae --skill new -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install alamenai/terrae new --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/alamenai/terrae.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/new .agents/skills/new && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "new" agent skill from https://github.com/alamenai/terrae/tree/main/.claude/skills/new into .agents/skills/new/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "new", 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 alamenai/terrae --skill new -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install alamenai/terrae new --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/alamenai/terrae.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/new .cursor/skills/new && 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 "new" agent skill from https://github.com/alamenai/terrae/tree/main/.claude/skills/new into .cursor/skills/new/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "new", 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/alamenai/terrae.git --path .claude/skills/new--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 alamenai/terrae --skill new -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install alamenai/terrae new --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/alamenai/terrae.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/new .gemini/skills/new && 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 "new" agent skill from https://github.com/alamenai/terrae/tree/main/.claude/skills/new into .gemini/skills/new/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "new", 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 alamenai/terrae newInstalls 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 alamenai/terrae --skill new -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/alamenai/terrae.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/new .github/skills/new && 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 "new" agent skill from https://github.com/alamenai/terrae/tree/main/.claude/skills/new into .github/skills/new/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "new", 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 alamenai/terrae --skill new -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install alamenai/terrae new --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/alamenai/terrae.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/new .opencode/skills/new && 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 "new" agent skill from https://github.com/alamenai/terrae/tree/main/.claude/skills/new into .opencode/skills/new/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "new", 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.
newEnd-to-end workflow for building a new Terrae component from scratch
New is an agent skill from alamenai/terrae. End-to-end workflow for building a new Terrae component from scratch
Its SKILL.md is about 2.4k 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, covering React components. It works with Mapbox and React. The repository describes itself as: Composable and animated components that replace imperative layers with simple props. The perfect companion for shadcn/ui. The licence is MIT.
9 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit ea9a480. It shows what the files ask for, not the result of running them.
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.
No scripts in the folder and no shell commands in SKILL.md (its code samples are typescript and json).
From the folder's file list and the shell code blocks in SKILL.md.
Hosts in commands or code, which the agent is likely to contact:
terrae.devFrom URLs in SKILL.md, links to its own repository left out.
Names these keys or tokens, usually read from environment variables:
NEXT_PUBLIC_MAPBOX_ACCESS_TOKENFrom names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
New loads about 2.4k tokens when it runs. Until then it costs about 18 tokens; SKILL.md has 724 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.
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.
The full file from alamenai/terrae at commit ea9a480, republished under its MIT licence (© alamenai). 724 words, ~2,387 tokens.
.claude/skills/new/SKILL.md (or your agent's skills folder).End-to-end workflow for building a new Terrae component from scratch.
Covers all 8 outputs:
Component structure, patterns, responsiveness, and performance rules are in .claude/rules/react/component.md.
| # | Output | File(s) |
|---|---|---|
| 1 | Component source file | src/registry/map/{name}.tsx |
| 2 | Barrel export | src/registry/map/index.tsx (update) |
| 3 | Registry entry | registry.json (update) |
| 4 | Example file(s) | src/app/docs/_components/examples/{name}-example.tsx |
| 5 | Documentation page | src/app/docs/{slug}/page.tsx |
| 6 | Sidebar navigation | src/app/docs/_components/docs-sidebar.tsx (update) |
| 7 | Components listing | src/app/docs/components/page.tsx (update) |
| 8 | Changelog entry | src/app/docs/changelog/page.tsx (update) |
When the developer requests a new component:
Ask for:
MapHeatmap, MapPolygon)MarkerContent, MarkerPopup)"core" or "features" (most components are features)useHeatmapControl)If there are multiple valid implementation approaches (e.g., Mapbox layers vs DOM overlay, canvas vs CSS animations, GeoJSON source vs custom rendering), present the options with trade-offs and let the developer choose before writing code.
Follow the map component rules in .claude/rules/react/component.md for the component structure, template, patterns, and barrel export.
src/registry/map/{component-name}.tsxheat-map.tsx)src/registry/map/index.tsxUpdate registry.json by adding an entry to the items array.
Follow this structure:
{
"name": "heat-map",
"type": "registry:ui",
"title": "Map Heatmap",
"description": "Short description of the component.",
"dependencies": ["mapbox-gl"],
"devDependencies": ["@types/mapbox-gl"],
"registryDependencies": ["https://www.terrae.dev/map.json"],
"files": [
{
"path": "src/registry/map/heat-map.tsx",
"type": "registry:ui",
"target": "components/ui/map/heat-map.tsx"
}
]
}name uses kebab-case with ``prefix (e.g.,heat-map)registryDependencies always includes ["https://www.terrae.dev/map.json"] (the core Map component that all other components depend on)dependencies only if the component needs packages beyond mapbox-glmapbox-gl directly can have empty dependencies (e.g., watermark)Location: src/app/docs/_components/examples/{name}-example.tsx
Use kebab-case for the file name.
The basic example should demonstrate the simplest usage of the component.
import { Map, MapHeatmap } from "@/registry/map"
export const HeatmapExample = () => {
const accessToken = process.env.NEXT_PUBLIC_MAPBOX_ACCESS_TOKEN || ""
return (
<div className="h-full w-full">
<Map accessToken={accessToken} center={[-74.006, 40.7128]} zoom={10}>
<MapHeatmap id="heatmap-basic" {/* ...minimal props */} />
</Map>
</div>
)
}"use client" if the example uses hooks, event handlers, or browser APIs — purely compositional examples that just render map components don't need it@/registry/map<div className="h-full w-full">process.env.NEXT_PUBLIC_MAPBOX_ACCESS_TOKEN || "" as the access token — the Map component validates it and shows an error if missing, so examples don't need their own checkheatmap-color-example.tsx, heatmap-custom-example.tsx)Location: src/app/docs/{slug}/page.tsx
Use the lines-animated/page.tsx as the gold standard reference.
The slug should match the sidebar href (e.g., /docs/heatmap → src/app/docs/heatmap/page.tsx).
import { DocsLayout, DocsSection, DocsCode, DocsLink } from "../_components/docs"
import { ComponentPreview } from "../_components/component-preview"
import { CodeBlock } from "../_components/code-block"
import { HeatmapExample } from "../_components/examples/heatmap-example"
import { getExampleSource } from "@/lib/get-example-source"
import { Metadata } from "next"
import { Table, TableBody, TableCell, TableHead, TableHeader, TableRow } from "@/components/ui/table"
export const metadata: Metadata = {
title: "Heatmap",
}
const HeatmapPage = () => {
const basicSource = getExampleSource("heatmap-example.tsx")
return (
<DocsLayout
title="Heatmap"
description="Short description of what the component does."
prev={{ title: "Previous Component", href: "/docs/previous" }}
next={{ title: "Next Component", href: "/docs/next" }}
>
<DocsSection title="Installation">
<p>First, make sure you have the base map component installed:</p>
<CodeBlock code={`npx shadcn@latest add https://www.terrae.dev/map.json`} language="bash" />
<p className="mt-4">Then install the heatmap component:</p>
<CodeBlock
code={`npx shadcn@latest add https://www.terrae.dev/heat-map.json`}
language="bash"
/>
</DocsSection>
<ComponentPreview code={basicSource}>
<HeatmapExample />
</ComponentPreview>
{/* Additional sections with examples, props tables, etc. */}
</DocsLayout>
)
}
export default HeatmapPagemetadata with a titleDocsLayout with title, description, prev, and next navigation linksCodeBlocks (base map + component)ComponentPreview goes directly after Installation (no section title or description, just the demo)ComponentPreview to wrap each example with its source codegetExampleSource("filename.tsx") to load example source codeDocsCode for inline code references in descriptionsDocsSection with a title for each sectionTable when the component has many configurable propsprev/next to match adjacent items in the sidebar navigationUpdate src/app/docs/_components/docs-sidebar.tsx:
NavItem entry in the correct section of the navigation arraybadge: "new"{ title: "Heatmap", href: "/docs/heatmap", icon: Flame, badge: "new" },Sections:
"Explore" — Story, Changelog"Get Started" — Introduction, Installation, Comparison, Components, Hooks, Reference"Core" — Map, Controls, Compass, Marker, Popup"Features" — Everything elseUpdate src/app/docs/components/page.tsx:
ComponentItem entry to the components arrayisNew: true{
title: "Heatmap",
href: "/docs/heatmap",
description: "Short description matching the registry description",
icon: Flame,
category: "features",
installCommand: "npx shadcn@latest add https://www.terrae.dev/heat-map.json",
isNew: true,
},category is "core" or "features" (must match the sidebar section)installCommand URL follows the pattern https://www.terrae.dev/{registry-name}.jsonmapboxOnly: true if the component only works with Mapbox GL (not MapLibre)Update src/app/docs/changelog/page.tsx:
Add a new entry to the components array of the most recent (topmost) ChangelogEntry in the changelogs array:
{
title: "Heatmap",
description: (
<>
New <code className="rounded bg-muted px-1 py-0.5 text-xs">MapHeatmap</code> component for
visualizing data density on the map. Supports customizable color ramps, radius control,
and intensity adjustment.
</>
),
href: "/docs/heatmap",
},components for new components, features for new features, fixes for bug fixes, properties for new propsdescription uses JSX with inline <code> tags for component nameshref linking to the docs pageBefore finalizing, show all changes:
© alamenai, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Just SKILL.md in .claude/skills/new of alamenai/terrae.
Open the folder on GitHubat commit ea9a480
New 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 |
|---|---|---|---|---|---|---|
| New this skillalamenai/terrae | 244 | — | ~2.4k | Automated safety check: Pass | MIT | |
| Web Artifacts Builderanthropics/skills | 180k | 40 repos | ~769 | Automated safety check: Pass | Apache-2.0 | |
| React Router Developmentremix-run/react-router | 57k | 1 repos | ~1.5k | Automated safety check: Pass | MIT | |
| React UI State PatternsChrisWiles/claude-code-showcase | 6.1k | 8 repos | ~1.6k | Automated safety check: Pass | None | |
| Chakra UI v3 Builderchakra-ui/chakra-ui | 41k | — | ~3.1k | Automated safety check: Pass | MIT | |
| React Component PerformanceDimillian/Skills | 4k | 5 repos | ~1.2k | Automated safety check: Pass | MIT |
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.
remix-run/react-router
Guides work on React Router apps by first identifying whether the app uses Framework, Data or Declarative mode, then loading the matching reference and the installed package docs.
ChrisWiles/claude-code-showcase
Sets patterns for React interfaces: when to show loading spinners or skeletons, how to surface errors, how to disable buttons during async work and how to handle empty lists.
chakra-ui/chakra-ui
Builds responsive, accessible Chakra UI v3 components and layouts, sets up Chakra in new or existing projects, and designs themes with tokens, semantic tokens and recipes.
Dimillian/Skills
Analyze and optimize React component performance issues (slow renders, re-render thrash, laggy lists, expensive computations).
vercel-labs/next-beats
Guides implementing animated page and state transitions in React with the native View Transition API, covering shared elements, list reorders and directional navigation.
alamenai/terrae
Verify all outputs exist after creating a new component and fix any issues
alamenai/terrae
Generate or update documentation for Terrae components. An agent skill from alamenai/terrae.
alamenai/terrae
Systematically fix issues found by /review or reported by the user
alamenai/terrae
Audit component performance and identify optimization opportunities with actionable fixes
alamenai/terrae
Commit, push, and open a pull request on GitHub. An agent skill from alamenai/terrae.
alamenai/terrae
Create standardized git commits following Terrae's conventions
Categories
End-to-end workflow for building a new Terrae component from scratch. New is an agent skill from alamenai/terrae.
New fits situations like: tasks that involve React components.
Run `npx skills add alamenai/terrae --skill new -a claude-code`. Or copy the skill folder (.claude/skills/new in alamenai/terrae) into .claude/skills/new in your project. Claude Code loads it when a task matches its description.
Run `npx skills add alamenai/terrae --skill new -a codex`. Or copy the skill folder (.claude/skills/new in alamenai/terrae) into .agents/skills/new in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add alamenai/terrae --skill new -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/new, .gemini/skills/new, .github/skills/new and .opencode/skills/new in your project.
Going by SKILL.md and its folder, New needs credentials named NEXT_PUBLIC_MAPBOX_ACCESS_TOKEN. Our summary lists: Node.js; A credential in NEXT_PUBLIC_MAPBOX_ACCESS_TOKEN.
SKILL.md names 1 domain. In commands or code: terrae.dev; the agent is likely to contact it when it follows the instructions. This is read from the text; nothing was executed.
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.
New is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 2.4k tokens (SKILL.md is roughly 9.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with New: Web Artifacts Builder (anthropics/skills, 180k stars), React Router Development (remix-run/react-router, 57k stars), React UI State Patterns (ChrisWiles/claude-code-showcase, 6.1k stars) and Chakra UI v3 Builder (chakra-ui/chakra-ui, 41k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
alamenai (a GitHub user) maintains it in alamenai/terrae, which has 244 GitHub stars. The repository holds 11 skills in this directory. The repository was last updated on April 6, 2026.
Source: alamenai/terrae on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.