Customization
Keep your instructions, reusable prompts, skills, and themes in files under ~/.e/.
On this page
Project instructions
Write rules shared across your projects in ~/.e/AGENTS.md. A trusted repository can add its own AGENTS.md.
Run the relevant tests after changing behavior.
Preserve unrelated edits in the working tree.
Ask before adding a dependency.Nested AGENTS.md files apply when e works with paths in that directory. This lets different parts of a repository carry their own instructions.
Reusable prompts
A Markdown file in ~/.e/prompts/ becomes a slash command. Save the following as review.md, then type /review.
Review the current diff.
Look for bugs and missing tests.
Explain your findings before changing files.Templates can accept arguments. They are read when used, so editing the file updates the next invocation.
Skills
A skill is a directory containing a SKILL.mdfile. Its description appears in the model's catalog; the full instructions load when the task needs them.
---
name: release
description: how to prepare a release of this project
---
Run the release checks.
Review the changelog before creating a tag.Use the $ picker to insert a skill yourself. Trusted repositories can keep project-local skills in .e/skills/.
Themes and keybindings
Theme files live in ~/.e/themes/. e renders its menus and extension UI through the same theme. Composer shortcuts can be overridden in ~/.e/keybindings.json.
e docs themes
e docs keybindingsUse /reload after changing keybindings. Prompt templates and skills are read when used.
Executable extensions
Extensions run as separate processes and exchange JSON lines with e. They can register tools, commands, and hooks, and request UI that e renders through the theme.
Write an extension in any language that can read stdin and write stdout. Extensions execute with your permissions, so review their code before installing them.
e docs extensions