new-api
Skill357 starsChanged 3 months agoMITView on GitHub
Scaffold a new merjs API route. Use when the user wants to create a new API endpoint.
2 other projects use a version of this.
Adopted by
Most recently taken up by
- Rain-kl/OpenFlaretheir own version, first seen Oct 8, 2026
- adarshaccreteinfo/Claude-Skillstheir own version, first seen Aug 27, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- Rain-kl/OpenFlare★ 298same name
- adarshaccreteinfo/Claude-Skills★ 1same 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
4 rules. About 0 are common, 0 are distinctive, and 4 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 14
Create api/$ARGUMENTS.zig with this template:
- Very specific: line 32
Run zig build codegen to regenerate routes
- Very specific: line 38
Use mer.typedJson(allocator, value) to return typed JSON responses
- Very specific: line 39
Use mer.json(string) for raw JSON strings
≈ “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 a new merjs API route
Scaffold a new API route at api/$ARGUMENTS.zig.
Steps
- Create
api/$ARGUMENTS.zigwith this template:
const mer = @import("mer");
const Response = struct {
// Define your response fields here
message: []const u8,
};
pub fn render(req: mer.Request) mer.Response {
return mer.typedJson(req.allocator, Response{
.message = "hello",
});
}- Adapt the Response struct fields based on what the user described
- Run
zig build codegento regenerate routes - Confirm the route appears at
/api/$ARGUMENTS
Conventions
- API routes live in
api/and map to/api/... - Use
mer.typedJson(allocator, value)to return typed JSON responses - Use
mer.json(string)for raw JSON strings - Access request body via
req.body, method viareq.method - Access query string via
req.query_string - Access cookies via
req.cookie("name") - For validation, use dhi:
const dhi = @import("dhi_validator"); - API routes do NOT need
pub const meta
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.

