Task-led guide · official Devin docs checked Nov 3, 2026
Devin Local: choose repository rules, reusable skills, or hooks
For a Devin Local project, use concise AGENTS.md rules for instructions that should always apply, skills for procedures needed only on relevant tasks, and hooks for lifecycle actions. Check the Customize panel to confirm what the workspace loads.
How should I make Devin Local follow repository conventions?
Start with a short AGENTS.md at the repository root for shared, always-on conventions such as the package manager, key directories, and required checks. Devin Local also discovers AGENTS.md files along the path to files it is working with, so place narrow guidance nearer to the relevant code when useful. Keep instructions specific and verifiable; a long general wish list is harder to check.
When should I use a skill instead of a rule?
Use a skill for a repeatable procedure that needs supporting files, scripts, templates, or a checklist and only applies to some tasks. Devin Local can invoke a matching skill or you can invoke it by name. Keep always-on rules small, and use them to point the agent toward a skill for the occasional workflow.
When are hooks useful?
Use hooks when a shell command or prompt should run at a defined agent lifecycle event, for example to validate a change or inspect a command before execution. Devin's docs describe project hooks in `.devin/hooks.v1.json`; inspect the event, matcher, and behavior before enabling a hook. Hooks do not load or run in Restricted Mode, so do not assume a hook is enforcing policy there.
How can I keep project instructions separate from personal preferences?
Commit shared project conventions in AGENTS.md. Devin Local also reads AGENTS.local.md alongside it for personal instructions; add that local file to .gitignore if it should stay on your machine. Avoid putting credentials or secrets in either file because they are instructions and context, not secret storage.
How do I verify Devin Local loaded the intended customizations?
Open Customize in the Devin Desktop agent sidebar and inspect the Rules, Skills, and Hooks tabs. Then run a small, reversible task that exercises one rule or skill and review both the response and diff. For a hook, test its documented event and expected result in a disposable branch. This checks your configuration; it does not establish coding quality or policy coverage in general.
Does this guide show that Devin Local writes better code?
No. It summarizes configuration options described in official Devin documentation checked November 3, 2026. It is not a coding benchmark, and loaded instructions or hooks do not by themselves prove a change is correct. Product behavior can change, so check the linked documentation and inspect your workspace's current Customize panel.