Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

I asked claude code for a guidelines file so it would collaborate with windsurf. This is what it proposed:

---

    This project uses shared planning documents for collaboration with Claude Code. Please:

    1. First read and understand these files:

       - PLAN.md - current project roadmap and objectives

       - ARCHITECTURE.md - technical decisions and system design

       - TODO.md - current tasks and their status

       - DECISIONS.md - decision history with rationale

       - COLLABORATION.md - handoff notes from other tools

    2. Before making any significant changes, check these documents for:

       - Existing architectural decisions

       - Current sprint priorities

       - Tasks already in progress

       - Previous context from Claude Code

    3. After completing work, update the relevant planning documents with:

       - Task completion status

       - New decisions made

       - Any changes to architecture or approach

       - Notes for future collaboration

    Always treat these files as the single source of truth for project state.


You could create a CLAUDE.md that just contains:

  @AGENTS.md
Still messy, but at least it means it's using the same content


What about

    ln -s AGENTS.md CLAUDE.md # repeat for all

?


Also great.


problem is that claude doesn't actually read those or keep them in context unless you prompt it to. it has to be in CLAUDE.md or it'll quickly forget about the contents


> it has to be in CLAUDE.md or it'll quickly forget about the contents

And then it will promptly forget about CLAUDE.md as well (happened to me on several occasions)


CLAUDE.md is placed in front of the first input for your session, right after the system prompt. That’s all. It’s not given any more weight than the rest of the context, and idk what compacting the conversation does to it.


I've added these instructions in CLAUDE.md and .windsurfrules, and yes sometimes you have to remind it, but overall it works quite well.


Sounds like a job for a symlink


Habe you though about adding a Session start hook that reads this file and adds it to the context?


Not yet, but that sounds like a good suggestion.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: