Suggestion: Move Frame state into .frame/ directory to avoid root pollution & conflicts

[BerkayYilmaz11]

Hi 👋

While exploring the repo and how Frame initializes projects, I noticed that Frame creates several files directly in the project root:
• AGENTS.md
• STRUCTURE.json
• PROJECT_NOTES.md
• tasks.json

Problem

This approach introduces a shared global namespace in the project root, which can lead to:
• File name collisions (e.g. CLAUDE.md, tasks.json)
• Conflicts with other AI tools or conventions
• Root directory clutter
• Reduced composability with other systems

Even in this repository itself, we can already see overlapping conventions (e.g. CLAUDE.md vs AGENTS.md).

Suggestion

Instead of writing directly to the root, Frame could isolate its state under a dedicated directory:

.frame/
  AGENTS.md
  STRUCTURE.json
  PROJECT_NOTES.md
  tasks.json

Benefits
• Clear namespace isolation
• No collisions with other tools
• Cleaner project root
• Easier .gitignore management
• Better composability with multi-agent/tool setups

Optional: Hybrid approach

Frame could optionally expose selected files to root (or symlink them), while keeping the source of truth under .frame/.

This would preserve compatibility with tools expecting root-level files, while maintaining a clean internal structure.

I believe this would significantly improve scalability and interoperability as Frame grows.

Curious to hear your thoughts!