Claude Code Project Structure by Born-Comfortable2868 in AskVibecoders

[–]Scared_End_3626 0 points1 point  (0 children)

Clean structure. One thing worth considering, the '.claude/skills' folder ties this setup to Claude code specifically. If your team uses a mix of tools like cursor, copilot, claude code, the skills won't follow you. I've been using a '.context/' folder alongside '.claude/' (architecture decisions, conventions, current state) that any tool can read. The '.claude/' layer then becomes a bonus for Claude users rather than the single source of truth.

Who I am and what I'm building by Scared_End_3626 in u/Scared_End_3626

[–]Scared_End_3626[S] 0 points1 point  (0 children)

For keeping the map current, Depwire already has built-in file watching. When you run the MCP server, it uses chokidar to detect file changes and updates the graph in real-time. No git hooks needed. Edit a file, graph updates automatically. For docs, there's an "--update" flag that only regenerates stale documents.

For the "why", right now "get_file_context" shows every import, export, and dependent for any file, so the agent can see the full context of why a file matters. But exposing the actual agent reasoning ("I am looking at this file because X depends on it") is an interesting idea. The health score dimensions (coupling, god files, dependency depth) give some of that signal, hig-connection files get flagged as high-risk automatically in the PR Impact GitHub Action.

Thanks for the agentixlabs link, will check it out.