evjs
- Repo stars 11
- License MIT
- Author updated Live
- Author repo evjs
- Domain
- Other
- Compatible agents
-
- Claude Code
- Cursor
- Cline
- Codex
- Windsurf
- Gemini CLI
- +20
- Trust score
- 94 / 100 · audit passed
- Author / version / license
- @afx-team · MIT
- Token usage
- Lean
- Setup complexity
- Manual integration
- External API key
- Not required
- Operating systems
- Docker
- Runtime requirements
- Node.js · Deno · Docker
- Permissions
-
- Read-only
- Write / modify
- Network behavior
- External requests
- Install commands
- 26 variants
Profile is derived at build time from SKILL.md and install vectors. Subject to drift from author intent.
Heads up: 未限定 allowed-tools,默认拥有全部工具权限。
---
name: evjs
description: React fullstack framework with type-safe routing, data fetching, and server functions. Use this…
category: other
runtime: Node.js / Deno / Docker
---
# evjs output preview
## PART A: Task fit
- Use case: React fullstack framework with type-safe routing, data fetching, and server functions. Use this skill when developing applications with the evjs framework. evjs is a React fullstack framework built on TanStack Router, TanStack Query, and Hono. It provides: makes outbound network calls; runs on Node.js. Works with Claude Code, Cursor, Cline and 23 more..
- Inputs: target material, constraints, expected output, and acceptance criteria.
- Evidence boundary: follow “Overview / Quick Start / References” and do not present inference as author intent.
## PART B: Execution result
- **01** The card summarizes the use case; runtime output centers on “React fullstack framework with type-safe routing, data fetching, and server functions. Use this skill when developing applications with the evjs framework. evjs is a React fullstack framework built on TanStack Router, TanStack Query, and Hono. It provides: makes outbound network calls; runs on Node.js. Works with Claude Code, Cursor, Cline and 23 more.”.
- **02** When the source has headings, the agent prioritizes “Overview / Quick Start / References” so the result follows the author’s structure.
- **03** Typical output includes task judgment, concrete steps, required commands or file edits, validation, and follow-up options.
- **04** Risk context follows the fingerprint: read files, write/modify files; may access external network resources; usually needs no extra API key.
## Running Rules
- read files, write/modify files; may access external network resources; usually needs no extra API key.
- Validate with a small sample before expanding scope.
- Return the result, validation criteria, and next iteration options. The source does not require a stable slash command. After installation, invoke the skill by name and describe the task.
Name target files or source material, expected output, forbidden changes, and whether network or shell access is allowed. Permission fingerprint: read files, write/modify files.
Start with a small task and check whether the result follows “Overview / Quick Start / References”. Inspect diffs, logs, previews, or tests before expanding scope.
Confirm the final output includes a concrete result, evidence, and next action. If it stays generic, tighten inputs, boundaries, and acceptance criteria.
---
name: evjs
description: React fullstack framework with type-safe routing, data fetching, and server functions. Use this…
category: other
source: afx-team/evjs
---
# evjs
## When to use
- React fullstack framework with type-safe routing, data fetching, and server functions. Use this skill when developing…
- Use it when the task has clear inputs, repeatable steps, and validation criteria.
## What to provide
- Target material, scope, expected result, and forbidden changes.
- Whether network, commands, file writes, or external services are allowed.
## Execution rules
- Organize steps around “Overview / Quick Start / References” and keep inference separate from source facts.
- read files, write/modify files; may access external network resources; usually needs no extra API key.
- Validate with a small sample before expanding the task.
## Output requirements
- Return the deliverable, key evidence, validation method, and next action.
- Mark missing information as unknown; do not invent commands, platforms, or dependencies. The author source anchors workflow facts; repository files anchor sources and commands; Fluxly only adds fit, limitations, and quality judgment.
skill "evjs" {
input -> user goal + target files + boundaries + acceptance criteria
context -> Overview / Quick Start / References
rules -> SKILL.md triggers / order / output contract
runtime -> Node.js / Deno / Docker | read files, write/modify files | may access external network resources
guardrails -> usually needs no extra API key + small-sample validation + diff/log review
output -> copyable result + checklist + next iteration
} evjs Agent Skill
Use this skill when developing applications with the evjs framework.
Overview
evjs is a React fullstack framework built on TanStack Router, TanStack Query, and Hono. It provides:
- Server Functions — write backend logic in files (we recommend using the
.server.tssuffix), call from React as if local - Server Routes — build programmatic REST endpoints and APIs using the
createRoute()handler - Query Integration — type-safe
useQuery(getUsers)with auto query keys and transport - Type-safe Routing — TanStack Router with code-defined route modules and route trees
- Plugin System — extend builds with
buildStart,bundlerConfig,transformHtml, andbuildEndhooks - Convention over Configuration — works out of the box, optionally configure via
ev.config.ts
Quick Start
npx @evjs/create-app my-app
cd my-app
npm install
npm run dev
References
For detailed guides on specific topics, see the references/ directory:
- quick-start.md — Scaffolding projects with
npx @evjs/create-app - project-structure.md — Recommended directory structure and domain-driven design (features)
- dev.md — Development server and configuration
- build.md — Production builds
- deploy.md — Deploying to Node, Docker, Deno, and Edge environments
- client-routes.md — Route definitions, layouts, params, loaders, navigation
- server-functions.md — Server functions, queries, mutations, error handling
- server-routes.md — Creating REST API endpoints using programmatic
createRoute() - config.md —
ev.config.tsoptions, defaults, client/server settings
Key Rules
Server Functions (RPC):
- Server function files must start with
"use server";so evjs can transform and register them - Use
useQuery(getUsers)to query server functions directly — type-safe args & data - Arguments are spread:
useQuery(getUser, id)notuseQuery(getUser, [id]) - For mutations, wrap args in objects/arrays:
mutate({ name, email })ormutate([name, email]) ServerErroron server → automatically mapped toServerFunctionErroron client
REST Routes (createRoute()):
- Use
createRoute()for REST API endpoints, webhooks, or standard Web Request/Response handling - If mixing
createRoute()endpoints, you must explicitly configureserver.entryinev.config.ts - Route Paths: Always use string literals for
pathvalues (e.g.,path: "/posts"). The type system rejects broadstringvariables and template strings at compile time.
React Data Loading:
- Route loaders should fetch using:
context.queryClient.ensureQueryData(getFnQueryOptions(myFn)) - Invalidate cache after mutations:
queryClient.invalidateQueries({ queryKey: getFnQueryKey(myFn) }) - Access server function metadata:
myFn.fnId,myFn.fnName,getFnQueryKey(myFn, ...args)
Misc:
- Use
pluginsin config to extend the build pipeline viabuildStart,bundlerConfig,transformHtml, andbuildEnd
Decide Fit First
Design Intent
How To Use It
Boundaries And Review