[FEATURE] Native .agents/ folder support (Agentic Collaboration Standard)

Preflight Checklist

• [x] I have searched existing requests and this feature hasn't been requested yet
• [x] This is a single feature request (not multiple features)

Problem Statement

Teams using multiple AI coding tools are forced to duplicate project context
across tool-specific formats (CLAUDE.md, .cursor/rules/, .windsurfrules, etc.).
There's no portable, tool-agnostic way to describe a project to AI agents.

Proposed Solution

I've been working on an open spec called ACS (Agentic Collaboration Standard)
that proposes a shared .agents/ folder format. It's designed to coexist with
CLAUDE.md — not replace it. I'd love to explore if Claude Code would be open
to reading .agents/context/ files alongside CLAUDE.md.

Alternative Solutions

Continue maintaining CLAUDE.md separately per project — which works but
doesn't help teams using Claude Code alongside other tools.

Priority

Low - Nice to have

Feature Category

Configuration and settings

Use Case Example

1. A team uses Claude Code as their primary AI assistant
2. They also use Cursor for some tasks and Windsurf for others
3. Currently they maintain CLAUDE.md, .cursor/rules/, and .windsurfrules separately
4. With .agents/ support, they'd maintain one folder and all tools read from it

Additional Context

Spec + reference implementation: https://github.com/jackby03/agentic-collaboration-standard
Website: https://acs.jackby03.com
CLI (published): npm install -g agentic-standard / pip install agentic-standard
VS Code extension: https://marketplace.visualstudio.com/items?itemName=jackby03.acs-vscode
Conformance checklist for tool builders: https://github.com/jackby03/agentic-collaboration-standard/blob/main/docs/conformance-checklist.md

The minimal conformance level (B1) only requires reading .agents/context/*.md files —
a very low barrier that would already cover the most common use case.