youssef-jad/gyo-agents

🚀 MCP Server: The Developer Digital Twin

Instead of copy-pasting prompts, connect the GYO-AGENTS MCP Server to any AI tool (Cursor, Claude Code, Cline, Kiro, Windsurf) to instantly transform it into your Digital Twin.

The server provides a global, persistent memory (~/.gyo-agents/twin-memory.json) that lives outside of any single repository. AI agents can learn your preferences, save your recurring solutions, and avoid mistakes across all of your projects.

cd mcp-server && npm install && npm run build

Add to your tool’s MCP config (replace /ABSOLUTE/PATH/TO/GYO-AGENTS):

{
  "mcpServers": {
    "gyo-agents": {
      "command": "node",
      "args": ["/ABSOLUTE/PATH/TO/GYO-AGENTS/mcp-server/dist/index.js"]
    }
  }
}

24 Tools Exposed:

• Prompt Tools (11): Native prompt generators for every major AI coding agent.
• Digital Twin Memory (4): get_digital_twin_profile, memorize, forget_memory, search_memory — Teach AI your global preferences.
• Intelligence & Validation (7): generate_full_agent_context, search_prompts, analyze_git_style_on_the_fly, get_domain_context, validate_api_response, check_cache_usage.
• Living Config Auto-Updater (2): snapshot_config, sync_agent_config — Keep agent configs in sync as your codebase evolves, with targeted per-section patch suggestions.

📖 Full setup guide & tool details → mcp-server/README.md · Config snippets → examples/mcp-configs/

---

Prompt: Generate Your Own AGENTS.md

Copy this entire prompt into any AI coding agent (Kiro, Claude Code, Cursor, Copilot, Codex, etc.) while inside your project workspace. It will analyze your codebase and git history to generate a powerful, project-specific AGENTS.md file.

(Note: If the agent truncates its response, run Steps 1-2 first, then ask it to complete Steps 3-4 in a follow-up).

I need you to generate a comprehensive AGENTS.md file for this project. This file will instruct AI coding agents on how to work in this codebase correctly. Follow these steps:

## Step 1: Analyze the Project

Explore the codebase and gather:
- Language, framework, and major dependency versions (from package.json, composer.json, Gemfile, go.mod, requirements.txt, Cargo.toml, etc.)
- Directory structure and code organization patterns (where do models, controllers, services, tests live?)
- **Architectural Observations**: Describe what you directly observe (directory names, file names, import patterns). Do NOT guess architectural labels (like "CQRS" or "DDD") unless there is explicit evidence (e.g., a file named `CommandHandler` inside a `Commands/` directory). If uncertain, describe the structure instead of labeling it.
- Module/package count and naming conventions