With jelou skill install you install a SKILL.md file in your AI coding tool. This file teaches it everything about Jelou Functions: the define() API, the ctx object, validation with Zod, cron, testing, and CLI commands. With this, your tool can write correct platform code from the very first prompt.
Installation
Run the installer
From the root of your Jelou Functions project: Verify the output
The CLI automatically detects which tools you have installed:✓ Installed jelou-functions skill for 4 agents
▸ Claude Code
▸ Cursor
▸ Windsurf
▸ Cline
Installed locally — commit .agents/ to share with your team.
Open your tool and start coding
The skill activates automatically when the tool detects code related to Jelou Functions (define(), @jelou/functions, ctx.env, etc.).
The installer detects 12 AI coding tools. Each uses its own skills directory, but all receive the same content.
Claude Code
Cursor
Windsurf
Universal
Others
Directory: .claude/skills/jelou-functions/SKILL.mdDetected automatically. The skill appears as available context in your conversations.
Directory: .cursor/skills/jelou-functions/SKILL.mdDetected automatically. Cursor loads the skill when you work on Jelou Functions files.
Directory: .windsurf/skills/jelou-functions/SKILL.mdDetected automatically when the project is opened.
Shared directory: .agents/skills/jelou-functions/SKILL.mdThe following tools read from the universal .agents/skills/ directory:| Tool | Detection |
|---|
| Amp | ~/.config/amp |
| Codex | ~/.codex |
| Gemini CLI | ~/.gemini |
| GitHub Copilot | .github/ in the project or ~/.copilot |
| OpenCode | ~/.config/opencode |
| Kimi Code CLI | ~/.kimi |
The following tools have their own skills directory:| Tool | Directory |
|---|
| Cline | .cline/skills/ |
| Continue | .continue/skills/ |
| Roo Code | .roo/skills/ |
The installer creates a symlink from each directory to the canonical copy in .agents/skills/.
How to use it
Once installed, your AI tool understands the full platform. Try prompts like:
Create a function that queries a customer's balance by phone
Add Zod validation to the input with .describe() so MCP has good descriptions
Configure a cron that runs every hour to clean up old records
Write tests with createMockContext for the customer query function
The skill activates automatically when the tool detects patterns like define(), @jelou/functions, ctx.env, ctx.isCron, createMockContext, or jelou commands.
Local vs global
| Mode | Command | Location | Use |
|---|
| Local | jelou skill install | .agents/skills/ in the project | Per project, share with team via git |
| Global | jelou skill install --global | Home directory (~) | Active in all projects |
Local is ideal for teams: by committing .agents/skills/, any team member who clones the repo will have the skill available without running anything.
Global is useful if you work on multiple Jelou Functions projects and want the skill always active.
Commit .agents/skills/ to your repository so your entire team automatically gets the skill when they clone the project.