---
name: root-skill
description: The absolute master configuration and state machine for the AI. This is the entry point that governs how the AI operates, changes states, and loads other skills.
category: meta
---

> **🏷️ Category:** `Meta-Skill` | **⚙️ Applies to:** Global AI State Machine & Workflow

# Root Skill (The Master State Machine)

## ⚡ ACKNOWLEDGMENT REQUIRED
**YOU MUST start EVERY response with this acknowledgment on the FIRST LINE:**
`✅ root-skill READ — git add/commit/push FORBIDDEN without explicit permission`

## 🚦 STATE MACHINE RULES (THINK BEFORE ACT)
To prevent premature execution, you operate as a State Machine. You must explicitly declare your state immediately after the acknowledgment line.

### `STATE: PLAN` (Default state for analysis and planning)
- **FIRST ACTION:** Ensure `.ai/skills/core-principles/SKILL.md` is loaded.
- **FORBIDDEN:** Do NOT use `replace_string_in_file`, `create_file`, or terminal commands that modify state (`git add`, writing files).
- **ALLOWED:** `read_file`, `file_search`, `grep_search`, read-only terminal (`ls`, `cat`), and proposing plans.
- Propose the strategy in bullet points only. Do NOT output concrete implementation code blocks. Stop and ask for approval.

### `STATE: IMPLEMENTATION` (Only when user explicitly approves/commands)
- **CRITICAL PRE-EXECUTION:** Before any file edits, mechanically `read_file` the relevant skill files (e.g., `clean-code`, `helm`). 
- **ACTIVE SKILL ECHO:** Immediately after reading skills, output a section `### Active Skills:` summarizing the 2-3 most critical rules.
- **ALLOWED:** You may use file modification tools and generate concrete code.
- **RETURN TO PLAN:** Once execution is finished, your VERY NEXT response MUST transition back to `STATE: PLAN`.

## 🚫 GIT HARD RULES (Reference)
See complete Git rules: `.ai/skills/git/SKILL.md`

## 📚 The Modular Skills Architecture
You must load specialized instructions from `.ai/skills/<name>/SKILL.md` when relevant:
- **GitOps & Infra:** `iac`, `helm`, `kubernetes-access`
- **Code Quality:** `clean-code`, `clean-architecture`
- **Workflow:** `git`, `write-skill`, `analysis`
- **Meta:** `core-principles`, `readme`, `docs`
*(Use file search/grep if you need a specific skill that isn't listed here).*

## 🌐 Language Rule
ALL documentation files must be written in **English**. You may communicate in the chat in the user's preferred language (Finnish).