new-page
Skill357 starsChanged 3 months agoMITView on GitHub
Scaffold a new merjs page. Use when the user wants to create a new page, route, or view.
10 other projects use a version of this.
Adopted by
Most recently taken up by
- 5hirish/ducttheir own version, first seen Nov 12, 2026
- robritacca-dotcom/rift-dstheir own version, first seen Nov 1, 2026
- robritacca-dotcom/design-systemtheir own version, first seen Oct 28, 2026
- Anglesite/anglesite-skillstheir own version, first seen Oct 27, 2026
- fangyuting/skillstheir own version, first seen Oct 11, 2026
- fpindej/netrocktheir own version, first seen Oct 8, 2026
Used with
Projects with it also use new-component and security-audit.
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.
violacaseSkillnew-component
Scaffold a new Vue 3 component using reka-ui primitives and Tailwind CSS. Use when the user asks to create a component, UI element, widget, or any .vue file in the components/ directory.
Also in 3 projects that use this
CloudflareSkillsecurity-audit
Security guidance and vulnerability review for codebases, APIs, services, CLI tools, libraries, and daemons. Use for security questions, focused reviews, vulnerability research, security audits, or pen tests. Run the complete workflow only for explicit codebase audit or pen-test requests, full/comprehensive/end-to-end reviews, or requested report artifacts.
Also in 3 projects that use this
Other versions10 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 10
- ethereum/ethereum-org-website★ 6ksame name
- fpindej/netrock★ 234same name
- Anglesite/anglesite-skills★ 15same name
- 5hirish/duct★ 11same name
- robritacca-dotcom/rift-ds★ 9same name
- kkhh26864/claude-skills★ 3same name
- agamarora/second-brain★ 2same name
- fangyuting/skills★ 1same name
- robritacca-dotcom/design-system★ 1same name
- mark2685/agent-tools★ 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.
The file
We split this skill into the rules it gives an agent
6 rules. 0 are common, 0 are distinctive, and 6 are very specific to this project.
0
Common
Most of the 8 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
6
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 14
Create app/$ARGUMENTS.zig with this template:
- Very specific: line 39
Run zig build codegen to regenerate routes
- Very specific: line 45
Every app/ page MUST export pub const meta: mer.Meta
- Very specific: line 46
Every page MUST export pub fn render(req: mer.Request) mer.Response
- Very specific: line 47
Use the h DSL (mer.h) for HTML — prefer comptime nodes
- Very specific: line 51
Add pub const prerender = true.
“Common” is measured: kept by at least 6 in 10 of the 8 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 a new merjs page
Scaffold a new page at app/$ARGUMENTS.zig that follows the merjs conventions.
Steps
- Create
app/$ARGUMENTS.zigwith this template:
const mer = @import("mer");
const h = mer.h;
pub const meta: mer.Meta = .{
.title = "PAGE_TITLE",
.description = "PAGE_DESCRIPTION",
};
const page_node = page();
pub fn render(req: mer.Request) mer.Response {
return mer.render(req.allocator, page_node);
}
fn page() h.Node {
return h.div(.{ .class = "page" }, .{
h.h1(.{}, "PAGE_TITLE"),
});
}- Replace PAGE_TITLE and PAGE_DESCRIPTION with sensible values derived from the page name
- Run
zig build codegento regenerate routes - Confirm the new route appears in
src/generated/routes.zig - Tell the user the route is available at the mapped URL path
Conventions
- Every app/ page MUST export
pub const meta: mer.Meta - Every page MUST export
pub fn render(req: mer.Request) mer.Response - Use the
hDSL (mer.h) for HTML — prefer comptime nodes - For dynamic routes, use bracket syntax:
app/users/[id].zig→/users/:id app/index.zigmaps to/app/foo/index.zigmaps to/foo- Add
pub const prerender = true;for static pages that don't need request data
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.

