new
Skill245 starsChanged 9 months agoMITView on GitHub
End-to-end workflow for building a new Terrae component from scratch
- Reads credentials
21 other projects use a version of this.
Adopted by
Most recently taken up by
- kotaroyamazaki/godot-agent-kittheir own version, first seen Nov 16, 2026
- per-simmons/claude-game-studiotheir own version, first seen Nov 8, 2026
- vvs1off/fabric-skillstheir own version, first seen Nov 8, 2026
- timpulver/openai-image-gentheir own version, first seen Nov 1, 2026
- vijaysuperpositionist/skillstheir own version, first seen Nov 1, 2026
- AlexCiortan/setlisttheir own version, first seen Oct 29, 2026
Used with
Projects with it also use upgrade, gate and 1 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
agenticnotetakingSkillupgrade
Apply plugin knowledge base updates to an existing generated system. Consults the Ars Contexta research graph for methodology improvements, proposes skill upgrades with research justification. Never auto-implements. Triggers on "/upgrade", "upgrade skills", "check for improvements", "update methodology".
Also in 4 projects that use this
synaptiaiSkillgate
Create a BDSK review_gate artifact. Defines a checkpoint that controls whether generated output may proceed toward acceptance. Use when defining quality, security, or scope gates for execution plans.
Also in 3 projects that use this
VercelSkillsetup
Set up Vercel CLI and project configuration. Use when the user says "set up Vercel", "configure Vercel", "link to Vercel", or "vercel init".
Also in 3 projects that use this
Other versions21 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 21
- H-mmer/pentest-agents★ 815same name
- with-pebbly/aseprite-ai-artist★ 697same name
- bradautomates/second-brain★ 217same name
- crisandrews/ClawCode★ 64same name
- rust-off-rails/rustoffrails★ 49same name
- howells/fiction★ 23same name
- The-Utopia-Studio/skills★ 6same name
- codebycorey/delta-spec★ 4same name
- per-simmons/claude-game-studio★ 4same name
- vvs1off/fabric-skills★ 4same name
11 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
The file
Show its rules and text
We split this skill into the rules it gives an agent
26 rules. 0 are common, 6 are distinctive, and 20 are very specific to this project.
0
Common
Most of the 21 edited versions we read keep these.
6
Distinctive
This author's own choices. Worth a look.
20
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 39
When the developer requests a new component:
- Distinctive: line 52
If there are multiple valid implementation approaches (e.g., Mapbox layers vs DOM overlay, canvas vs CSS animations, GeoJSON source vs …
- Very specific: line 56
Follow the map component rules in .claude/rules/react/component.md for the component structure, template, patterns, and barrel export.
- Very specific: line 59
Use kebab-case for file names (e.g., heat-map.tsx)
- Very specific: line 64
Update registry.json by adding an entry to the items array.
- Very specific: line 91
Add extra dependencies only if the component needs packages beyond mapbox-gl
- Distinctive: line 98
Use kebab-case for the file name.
- Very specific: line 120
Only add "use client" if the example uses hooks, event handlers, or browser APIs — purely compositional examples that just render map …
- Very specific: line 125
Create additional example files for each variation (e.g., heatmap-color-example.tsx, heatmap-custom-example.tsx)
- Very specific: line 131
Use the lines-animated/page.tsx as the gold standard reference.
- Very specific: line 182
Always export metadata with a title
- Very specific: line 183
Use DocsLayout with title, description, prev, and next navigation links
- Very specific: line 186
Use ComponentPreview to wrap each example with its source code
- Very specific: line 187
Use getExampleSource("filename.tsx") to load example source code
- Very specific: line 188
Use DocsCode for inline code references in descriptions
- Very specific: line 189
Use DocsSection with a title for each section
- Very specific: line 190
Add a props Table when the component has many configurable props
- Distinctive: line 197
Import the Lucide icon at the top (if not already imported)
- Very specific: line 198
Add a NavItem entry in the correct section of the navigation array
- Very specific: line 217
Add a ComponentItem entry to the components array
- Very specific: line 236
Add mapboxOnly: true if the component only works with Mapbox GL (not MapLibre)
- Distinctive: line 237
Place the entry near similar components in the array
- Very specific: line 243
Add a new entry to the components array of the most recent (topmost) ChangelogEntry in the changelogs array:
- Very specific: line 261
Add under components for new components, features for new features, fixes for bug fixes, properties for new props
- Very specific: line 263
Always include href linking to the docs page
- Distinctive: line 267
Before finalizing, show all changes:
“Common” is measured: kept by at least 6 in 10 of the 21 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Create New Component Skill
End-to-end workflow for building a new Terrae component from scratch.
Covers all 8 outputs:
- Component source
- Registry
- Exports
- Documentation
- Examples
- Sidebar
- Components page
- Changelog
Component structure, patterns, responsiveness, and performance rules are in .claude/rules/react/component.md.
All Outputs
| # | 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) |
Instructions
When the developer requests a new component:
Step 1: Gather Requirements
Ask for:
- Component name (e.g.,
MapHeatmap,MapPolygon) - Core functionality
- Whether it needs compound components (like
MarkerContent,MarkerPopup) - Category:
"core"or"features"(most components are features) - Lucide icon for the sidebar and components page
- Whether it exposes a control hook (e.g.,
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.
Step 2: Create the Component File and Export
Follow the map component rules in .claude/rules/react/component.md for the component structure, template, patterns, and barrel export.
- Location:
src/registry/map/{component-name}.tsx - Use kebab-case for file names (e.g.,
heat-map.tsx) - Export from
src/registry/map/index.tsx
Step 3: Add Registry Entry
Update 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"
}
]
}Key rules:
nameuses kebab-case with ``prefix (e.g.,heat-map)registryDependenciesalways includes["https://www.terrae.dev/map.json"](the coreMapcomponent that all other components depend on)- Add extra
dependenciesonly if the component needs packages beyondmapbox-gl - Components that don't need
mapbox-gldirectly can have emptydependencies(e.g., watermark)
Step 4: Create Example File(s)
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>
)
}Key rules:
- Only add
"use client"if the example uses hooks, event handlers, or browser APIs — purely compositional examples that just render map components don't need it - Import from
@/registry/map - Wrap the map in a
<div className="h-full w-full"> - Pass
process.env.NEXT_PUBLIC_MAPBOX_ACCESS_TOKEN || ""as the access token — theMapcomponent validates it and shows an error if missing, so examples don't need their own check - Export the component with a descriptive name (PascalCase)
- Create additional example files for each variation (e.g.,
heatmap-color-example.tsx,heatmap-custom-example.tsx)
Step 5: Create Documentation Page
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 HeatmapPageKey rules:
- Always export
metadatawith atitle - Use
DocsLayoutwithtitle,description,prev, andnextnavigation links - First section is always "Installation" with two
CodeBlocks (base map + component) - The basic
ComponentPreviewgoes directly after Installation (no section title or description, just the demo) - Use
ComponentPreviewto wrap each example with its source code - Use
getExampleSource("filename.tsx")to load example source code - Use
DocsCodefor inline code references in descriptions - Use
DocsSectionwith atitlefor each section - Add a props
Tablewhen the component has many configurable props - Set
prev/nextto match adjacent items in the sidebar navigation
Step 6: Add to Sidebar
Update src/app/docs/_components/docs-sidebar.tsx:
- Import the Lucide icon at the top (if not already imported)
- Add a
NavItementry in the correct section of thenavigationarray - Add
badge: "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 else
Step 7: Add to Components Page
Update src/app/docs/components/page.tsx:
- Import the Lucide icon at the top (if not already imported)
- Add a
ComponentItementry to thecomponentsarray - Add
isNew: 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,
},Key rules:
categoryis"core"or"features"(must match the sidebar section)installCommandURL follows the patternhttps://www.terrae.dev/{registry-name}.json- Add
mapboxOnly: trueif the component only works with Mapbox GL (not MapLibre) - Place the entry near similar components in the array
Step 8: Update Changelog
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",
},Key rules:
- Add under
componentsfor new components,featuresfor new features,fixesfor bug fixes,propertiesfor new props - The
descriptionuses JSX with inline<code>tags for component names - Always include
hreflinking to the docs page
Step 9: Review with User
Before finalizing, show all changes:
- The component source code
- The barrel export addition
- The registry entry
- The example file(s)
- The documentation page
- The sidebar entry
- The components page entry
- The changelog entry
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

