Adapt Agent System

Adapt Agent System

Adapts a project that was set up for one AI agent system so that it can also be used with another supported system.

Goal

Transfer project instructions, rules, commands, and, if needed, other AI-specific configuration between supported agent systems without destroying existing setups or copying private local information in an uncontrolled way.

Supported target systems in version 1:

• Claude Code (CLAUDE.md, .claude/)
• OpenAI Codex (AGENTS.md, .codex/, .agents/skills/)
• Hermes Agent (SOUL.md, MEMORY.md, USER.md, project-specific AGENTS.md)

Prerequisites

• Read the system profiles in agent-personas/systems/ as a reference, in particular:
  • claude-code.md
  • openai-codex.md
  • hermes-agent.md
• Always read existing target-system files before making changes and do not blindly overwrite them.
• Preserve existing source-system files; this skill creates compatibility, not a migration with deletion.
• Only carry over private, local, or personal content after explicit confirmation.

Steps

1. Determine source and target

   • Detect existing systems based on typical files:
     • Claude Code: CLAUDE.md, .claude/CLAUDE.md, .claude/rules/, .claude/commands/, .claude/settings*.json
     • OpenAI Codex: AGENTS.md, .codex/config.toml, .agents/skills/
     • Hermes Agent: SOUL.md, MEMORY.md, USER.md, project-specific AGENTS.md
   • If the source or target is not clear, ask the user which combination they want.

2. Let the porting depth be chosen

   • Before implementing, ask the user which depth should be used:
     1. Project instructions: Transfer only durable project context, architecture notes, conventions, build/test commands, and repository guidance.
     2. Plus commands/rules: Additionally review commands, rules, and comparable workflow files and transfer them into the most appropriate target-system format, or document them as a migration note.
     3. Everything AI-specific: Additionally review settings, skills, memories, local overrides, and personal/system-level files. Never automatically copy secrets, tokens, absolute machine paths, private memories, or personal content.

3. Classify content

   • Separate project context, workflow rules, reusable skills, persona/identity, user preferences, and local configuration.
   • Claude/Codex project files should primarily contain repository context, conventions, commands, and working rules.
   • Hermes SOUL.md is meant for identity, personality, and communication style; project context belongs in AGENTS.md whenever possible.
   • When a piece of content has no clear equivalent in the target system, do not force it; instead, output it as a migration note.

4. Create or extend target-system files

   • Use the respective structure from the appropriate system profile.
   • Preserve existing target content unless it clearly conflicts.
   • Add new content concisely, durably, and specific to the target system.
   • Avoid generic best practices that do not come from the project context.

5. Safeguard private and local content

   • Treat these sources as sensitive: *.local.*, local overrides, memories, settings, absolute paths, tokens, secrets, personal preferences.
   • Explicitly ask before carrying over or summarizing them.
   • If no confirmation is given, skip them and mention them in the output.

Output

After the adaptation, report:

1. Which source and which target system were used.
2. Which porting depth was chosen.
3. Which files were created or changed.
4. A short mapping summary: which content was transferred where.
5. Assumptions, skipped content, and warnings about parts that could not be transferred cleanly.

For a pure planning run without file changes, use the same structure, but instead of changed files, name the recommended target files and concrete content.