← ClaudeAtlas

setup-project-contextlisted

Scaffold or show the .claude/project-context.json file that the engineering hooks read to inject project context, target-repo guidance, and optional post-edit format commands.
atman-33/workhub · ★ 1 · Data & Documents · score 77
Install: claude install-skill atman-33/workhub
Set up the per-project configuration consumed by the engineering plugin's hooks. `SessionStart` reads `.claude/project-context.json` from the project root and injects a `<project-context>` block (registered project absolute paths + openspec docs folder) into Claude's context at session start. Steps: 1. Check whether `.claude/project-context.json` already exists in the current project (read it). - If it exists, show its current contents and stop. Tell the user to edit it by hand, and that changes take effect on the next session start. 2. If it does not exist, create `.claude/project-context.json` with this template (replace the placeholder paths with the user's real absolute paths): ```json { "roleBasedDelegation": true, "openspecPath": "<absolute path to the openspec docs folder>", "postToolFormatCommands": [ "<optional global default command run in any target project root after Edit/Write>" ], "projects": [ { "name": "example-project", "path": "<absolute path to a frequently-used project>", "summary": "short one-line description (optional)", "postToolFormatCommands": [ "<project-specific command run in this project's root after Edit/Write>" ] } ] } ``` 3. Report what was done and remind the user: - `roleBasedDelegation`, `openspecPath`, `postToolFormatCommands`, and `projects` are all optional; omit any of them and the relev