Set up your WhoseDev project
WhoseDev reads optional project instructions from a .whosedev folder in your workspace root. Use it to describe your stack, encode conventions, and package reusable agent guidance.
Initialize a workspace
Section titled “Initialize a workspace”- Open the project root folder in WhoseDev.
- Open the Command Palette (Ctrl+Shift+P / Cmd+Shift+P).
- Run WhoseDev: Initialize .whosedev for this Workspace.
Initialization creates starter files without overwriting anything that already exists.
What gets created
Section titled “What gets created”| Path | Purpose |
|---|---|
.whosedev/project.md |
High-level project profile: purpose, stack, commands, conventions |
.whosedev/rules/ |
Markdown rules the agent should follow (includes coding-style.md starter) |
.whosedev/skills/ |
Optional skill packages (see Skills) |
.whosedev/commands/ |
Reusable command prompts (see Commands) |
.whosedev/state/ |
Local agent state (includes task-state.json starter) |
.whosedev/.gitignore |
Ignores local state, checkpoints, and cache under .whosedev/ |
Plans are stored by default under ~/.whosedev/plans/ on your machine. You can optionally copy a plan into .whosedev/plans/ in the workspace.
Import existing instructions
Section titled “Import existing instructions”If your repository already has agent instruction files, run WhoseDev: Import Existing Instructions. WhoseDev copies supported files—such as AGENTS.md and CLAUDE.md—into .whosedev/rules/ without modifying the originals.
Manage the workspace
Section titled “Manage the workspace”Run WhoseDev: Manage Workspace (.whosedev) to open rules, skills, prompts, plans, or project.md from a quick pick list.
Commit what helps your team
Section titled “Commit what helps your team”- Commit
project.md,rules/,skills/, andcommands/when they describe shared team conventions. - Do not commit
.whosedev/state/, checkpoints, or cache—the starter.gitignoreexcludes these.