# Update AI Config > Create, update, or manage AI configuration templates. Analyzes what the user needs and delegates to the appropriate template-specific skill. Use when this capability is needed. - Skill: `tomevault-io/update-ai-config-2` (Agent Skill, multi-file: 2 files) - Install (CLI): `npx skillmds@latest add tomevault-io/update-ai-config-2` - Raw SKILL.md: https://api.skillmd.com/api/skills/tomevault-io/update-ai-config-2/raw - Safety review: pending - Works with: Claude Code, Claude.ai, OpenAI Codex - Category: Coding & Dev Tools - Author: tomevault-io (https://skillmd.com/u/tomevault-io) - Updated: 2026-09-17 - Page: https://skillmd.com/skills/tomevault-io/update-ai-config-2 --- # Manage AI Config Templates **IMPORTANT:** This project uses universal-ai-config (`uac`). All AI configuration lives in the `<%= config.templatesDir %>/` directory as universal templates. NEVER edit generated target-specific files (e.g. `.claude/`, `.github/copilot-instructions.md`, `.cursor/`) directly — those are overwritten on every `uac generate` run. Always modify the source templates in `<%= config.templatesDir %>/`. When the user wants to add or change AI configuration for this project, follow these steps: ## 1. Understand the Request Read the template guide at `<%= instructionPath('uac-template-guide') %>` to understand the available template types and when to use each. ## 2. Determine the Template Type Based on the user's request, decide which type of template to work with: - **Persistent context, rules, or guidelines** → Instruction template - **Repeatable task, workflow, or slash command** → Skill template - **Specialized AI persona with restricted tools** → Agent template - **Automatic lifecycle automation (on events)** → Hook template - **MCP server configuration** → MCP template Examples: - "Add a rule about error handling" → Instruction - "Create a deploy workflow" → Skill - "Set up a code reviewer" → Agent - "Run linting after file edits" → Hook - "Add an MCP server for GitHub" → MCP If the intent is ambiguous, ask the user to clarify before proceeding. ## 3. Delegate Read the detailed guide for the chosen template type and follow its instructions: - **Instructions** → `<%= skillPath('update-instruction') %>` - **Skills** → `<%= skillPath('update-skill') %>` - **Agents** → `<%= skillPath('update-agent') %>` - **Hooks** → `<%= skillPath('update-hook') %>` - **MCP** → `<%= skillPath('update-mcp') %>` These skills primarily create or modify files inside `<%= config.templatesDir %>/`. They may also modify files in directories listed under `additionalTemplateDirs` in the config — but only with explicit user confirmation, since those are shared templates that may affect other projects. Never edit generated output files in `.claude/`, `.cursor/`, `.github/`, or similar target-specific directories — those are regenerated from templates and any direct changes will be lost. ## Additional Template Directories This project may have additional template directories configured via `additionalTemplateDirs`. To find them, search the project root for **all** config files matching `universal-ai-config.*` (e.g. `universal-ai-config.config.ts`, `universal-ai-config.overrides.config.ts`, and any other variants) and read the `additionalTemplateDirs` field from each. If the user asks to update a template that doesn't exist in the main templates directory, or explicitly refers to shared/global/external templates: 1. Read all `universal-ai-config.*` config files in the project root to find `additionalTemplateDirs` paths 2. Search those directories for the relevant template 3. **IMPORTANT:** Before editing any file outside the main `<%= config.templatesDir %>/` directory, ask the user for explicit confirmation — these are shared templates that may affect other projects ## After Changes Run `uac generate` to regenerate target-specific config files and verify the output. --- > Converted and distributed by [TomeVault](https://tomevault.io/claim/fabis94) — claim your Tome and manage your conversions.