Agent Customization
Adapt the agent to your workflow without editing any files. With /skills and /person you define what the agent knows about your project and how it communicates — all directly from the chat.
/skills — Custom Knowledge
The agent has a built-in set of capabilities, but you can expand them by pointing to a directory containing instructions, examples, or documentation specific to your project. The agent loads that content automatically and uses it when answering questions.
/skills <path> — Set directory
Provide the path to your custom skills directory. It can be absolute or relative to the project root:
/skills ./docs/agent-skills /skills /home/user/my-project/skills
/skills — Open interactive menu
Without arguments, opens a menu where you can view the current path and update it before saving:
/skills # interactive menu: # ▶ Skills Path: ./docs/agent-skills (Click to change) # ▶ Apply and return to chat # ▶ Cancel and return to chat
What to put in the directory?
There is no required structure — the agent reads the content intelligently. Some useful examples:
| File / Folder | Purpose |
|---|---|
architecture.md | Describes the project structure so the agent understands the overall context |
conventions.md | Defines naming standards, formatting rules, and team best practices |
examples/ | Code samples the agent uses as reference when suggesting implementations |
glossary.md | Domain-specific terms and business concepts the agent should know |
/person — Agent Personality
By default, the agent behaves like an experienced Senior Engineer: direct, technical, and focused on best practices. With /person (or /persona), you redefine that profile using a plain-language description — and the agent adopts the new identity immediately.
/person <description> — Set personality
Describe the communication style, tone, or specialty you want. The more specific, the better the agent will adapt:
# Thorough and technical /person Software architect specialized in distributed systems, explains every decision with pros and cons # Beginner-friendly /person Patient programming teacher who uses simple analogies and everyday examples # Productivity-first /person Pragmatic tech lead who gets straight to the point and prioritizes simple solutions that work in production # Front-end specialist /person UI/UX designer with deep knowledge of accessibility and web performance
/person default — Restore default
To go back to the original behavior, use default or reset as the argument:
/person default /person reset
/person — Open interactive menu
Without arguments, opens a menu to view and edit the current personality before saving:
/person # interactive menu: # ▶ Agent Persona: Default (Senior Engineer) (Click to change) # ▶ Apply and return to chat # ▶ Cancel and return to chat
Using Both Together
The two commands complement each other: /skills defines what the agent knows about your project, and /person defines how it communicates that knowledge. Set both for a fully tailored experience:
# 1. Point to your project documentation /skills ./docs/agent-skills # 2. Set the ideal communication tone /person Direct tech lead who focuses on practical solutions and skips obvious explanations # From here on, the agent knows your project and speaks your language.