--- description: Synchronizes Devin and Kiro agent configurations --- ## Update Agents Workflow This workflow synchronizes the shared agent configuration between Devin (`.devin/`) and Kiro (`.kiro/`) while preserving platform-specific files. ### Folder Structure Overview **Devin (`.devin/`)** is the canonical shared configuration: - `README.md` — Devin-specific readme - `agents.md` — Main agent instructions - `context/` — Canonical context files for different task types - `rules/` — Universal rules that always apply - `workflows/` — Slash command workflows **Kiro (`.kiro/`)** contains Kiro-specific loader files: - `README.md` — Kiro-specific readme - `steering/` — Kiro steering files, adapted from canonical Devin context - `skills/` — Installable skills - `hooks/` — Kiro hooks - `specs/` — Feature specifications ### Steps 1. **Identify the source of changes** Determine which folder was recently updated: - Check git status to see modified files - Note which IDE folder contains the changes - This is your source folder 2. **Synchronize shared files** The following shared guidance should remain aligned between Devin and Kiro: **Canonical Devin files:** - `.devin/agents.md` — Main agent instructions - `.devin/context/*.md` — Canonical context files - `.devin/workflows/*.md` — Workflow definitions **Kiro adaptations:** - Update only the relevant `.kiro/steering/*.md` file when Kiro needs loader-specific frontmatter or wording. - Keep `.kiro/skills/`, `.kiro/hooks/`, and `.kiro/specs/` Kiro-specific. - Do not create a second `.kiro/agents.md`; Kiro follows the canonical Devin instructions. 3. **Handle IDE-specific differences** - **README.md**: Keep IDE-specific (don't sync) - **steering/**: Kiro-specific adaptations; don't duplicate canonical Devin files unnecessarily - **skills/**: Kiro-specific (don't sync to Devin) - **hooks/**: Kiro-specific (don't sync to Devin) - **specs/**: Kiro-specific (don't sync to Devin) 4. **Update Kiro adaptations** When canonical Devin context changes, update only the corresponding Kiro steering file if its loader-specific content is affected. Do not copy files wholesale or create duplicate root-level files. 5. **Verify consistency** After syncing, verify: - Devin remains the single canonical source for shared agent guidance - Kiro steering files contain only Kiro-specific adaptations - No duplicate `agents.md` or payroll pattern files exist - Kiro skills, hooks, and specs remain unique to Kiro ### Sync Patterns **Pattern 1: Canonical Devin context update** Update the relevant file under `.devin/context/` and reflect only loader-specific changes in the matching `.kiro/steering/` file. **Pattern 2: Kiro-specific updates** Keep `.kiro/skills/`, `.kiro/hooks/`, and `.kiro/specs/` independent. Do not copy them into Devin or create duplicate shared files. ### When to Run This Workflow Run this workflow after: - Adding a new workflow to `.devin/workflows/` - Updating canonical context files in `.devin/context/` - Updating Kiro-specific steering, skills, hooks, or specs - Adding new context documentation ### Manual Sync Checklist - [ ] Identify source folder with changes - [ ] Update canonical Devin context/workflow files - [ ] Update only affected Kiro steering adaptations - [ ] Verify no duplicate shared agent files exist - [ ] Verify Kiro-specific files remain unique - [ ] Test workflows in Devin and Kiro ### Example Commit Messages ``` chore(agents): sync update-graphify workflow across IDEs Updated the canonical Graphify workflow in `.devin/workflows/` and its Kiro steering integration. chore(agents): sync context files after adding graphify usage docs Aligned the Graphify guidance between `.devin/context/` and the Kiro steering adaptation. ``` ### Notes - Kiro's folder structure is different because it uses `steering/` loader files - Devin's `agents.md` and `context/` remain canonical for shared guidance - Never sync `steering/`, `skills/`, `hooks/`, or `specs/` into Devin - README.md files should remain IDE-specific - After syncing, test workflows in Devin and Kiro