create-page
Skill7 starsChanged 3 months agoISCView on GitHub
Create a new tutorial/content page on agentconfig.org with proper file structure, routing, and registry entry. Use when adding a new top-level page like /skills, /agents, or /mcp.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- NarekManukyan/flutter-mobx-kittheir own version, first seen Sep 17, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- NarekManukyan/flutter-mobx-kit★ 0same name
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.
In this repository13 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- add-primitiveSkill
- add-providerSkill
- advisorSkill
- co-authorSkill
- create-componentSkill
- generate-llmsSkill
- page-stylingSkill
- refresh-provider-docsSkill
- semantic-commitSkill
- theme-stylingSkill
- write-e2e-testSkill
The file
We split this skill into the rules it gives an agent
10 rules. About 0 are common, 3 are distinctive, and 7 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
7
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 8
Create a new content page on agentconfig.org following project conventions.
- Distinctive: line 23
Use this skill when:
- Very specific: line 131
Update site/vite.config.ts build inputs:
- Very specific: line 161
Update site/src/data/pages.ts to include the new page:
- Very specific: line 180
If the page has unique data structure, update .claude/skills/generate-llms/scripts/generate-llms-full.ts:
- Very specific: line 182
Import the new data file in loadData()
- Very specific: line 183
Add a generate{Name}Md() function
- Very specific: line 184
Call it in the main() function
- Distinctive: line 188
After creating the page, regenerate the llms files:
- Distinctive: line 196
Before considering the page complete:
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Create Page
Create a new content page on agentconfig.org following project conventions.
Overview
This skill creates all the necessary files for a new page:
- HTML entry point (
site/{slug}/index.html) - Page renderer (
site/src/pages/{slug}.tsx) - Page component (
site/src/components/{Name}Page/) - Data file (
site/src/data/{slug}Tutorial.ts) - Vite config entry
- Navigation link
- Page registry entry for llms generation
When to Use
Use this skill when:
- Creating a new tutorial or content page
- Adding a major new section to the site
- The page needs to be included in llms.txt generation
Step-by-Step Process
Step 1: Create HTML Entry Point
Create site/{slug}/index.html:
<!doctype html>
<html lang="en">
<head>
<meta charset="UTF-8" />
<link rel="icon" type="image/svg+xml" href="/favicon.svg" />
<meta name="viewport" content="width=device-width, initial-scale=1.0" />
<title>{Page Title} - agentconfig.org</title>
<meta name="description" content="{One-line description}" />
</head>
<body>
<div id="root"></div>
<script type="module" src="/src/pages/{slug}.tsx"></script>
</body>
</html>Step 2: Create Page Renderer
Create site/src/pages/{slug}.tsx:
import { render } from 'preact'
import { {Name}Page } from '@/components/{Name}Page'
import '@/index.css'
const rootElement = document.getElementById('root')
if (!rootElement) {
throw new Error('Root element not found')
}
render(<{Name}Page />, rootElement)Step 3: Create Page Component
Create site/src/components/{Name}Page/index.ts:
export { {Name}Page } from './{Name}Page'Create site/src/components/{Name}Page/{Name}Page.tsx:
import type { VNode } from 'preact'
import { PageLayout } from '@/layouts'
import { TableOfContents } from '@/components/TableOfContents'
import { tocItems } from '@/data/{slug}Tutorial'
export function {Name}Page(): VNode {
return (
<PageLayout>
{/* Hero Section */}
<header className="border-b border-border bg-muted/30">
<div className="container mx-auto px-4 py-12 md:py-16">
<h1 className="text-4xl md:text-5xl font-bold mb-4">
{Page Title}
</h1>
<p className="text-xl text-muted-foreground max-w-2xl">
{Description}
</p>
</div>
</header>
{/* Main Content */}
<div className="container mx-auto px-4 py-8">
{/* Add page content here */}
</div>
</PageLayout>
)
}Step 4: Create Data File
Create site/src/data/{slug}Tutorial.ts:
import type { TocItem } from '@/components/TableOfContents'
export const tocItems: readonly TocItem[] = [
{ id: 'section-1', label: '1. First Section', level: 'beginner' },
// Add more sections
] as const
export const codeSamples: Record<string, string> = {
// Add code samples
}
export const furtherReadingLinks: readonly FurtherReadingLink[] = [
// Add further reading links
] as constStep 5: Add to Vite Config
Update site/vite.config.ts build inputs:
build: {
rollupOptions: {
input: {
main: resolve(__dirname, 'index.html'),
skills: resolve(__dirname, 'skills/index.html'),
agents: resolve(__dirname, 'agents/index.html'),
{slug}: resolve(__dirname, '{slug}/index.html'), // Add this
},
},
},Step 6: Add Navigation Link
Update site/src/components/Navigation/Navigation.tsx:
const navLinks = [
{ href: '/', label: 'Home' },
{ href: '/skills/', label: 'Skills' },
{ href: '/agents/', label: 'Agents' },
{ href: '/{slug}/', label: '{Label}' }, // Add this
]Step 7: Add to Page Registry (IMPORTANT!)
Update site/src/data/pages.ts to include the new page:
export const pages: readonly PageMeta[] = [
// ... existing pages
{
slug: '{slug}',
title: '{Page Title}',
description: '{One-line description for llms.txt}',
features: '{What the md file contains}',
dataFile: '{slug}Tutorial.ts',
mdFile: '{slug}.md',
partNumber: {next number}, // Increment from last page
},
]Step 8: Update generate-llms Script
If the page has unique data structure, update .claude/skills/generate-llms/scripts/generate-llms-full.ts:
- Import the new data file in
loadData() - Add a
generate{Name}Md()function - Call it in the
main()function
Step 9: Regenerate LLMs Files
After creating the page, regenerate the llms files:
Use the generate-llms skill to regenerate all llms filesChecklist
Before considering the page complete:
- HTML entry point created in
site/{slug}/index.html - Page renderer created in
site/src/pages/{slug}.tsx - Page component created in
site/src/components/{Name}Page/ - Data file created in
site/src/data/{slug}Tutorial.ts - Vite config updated with build input
- Navigation link added
- Page registry entry added to
site/src/data/pages.ts - generate-llms script updated (if needed)
- LLMs files regenerated
Example Prompts
Create a new page
Create a new page at /security for security best practices documentationAdd page to registry only
Add the /mcp page to the page registry so it's included in llms generationDoes 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.

