lisätty category ja impact meta tiedot ai varten

.ai/skills/analysis/SKILL.md

@@ -1,6 +1,8 @@
 ---
 name: analysis
 description: Analyze user requests, evaluate requirements, and propose AI action plans. Use when analyzing code, errors, or planning tasks.
+category: workflow
+impact: high
 ---
 
 # Analysis Instructions

.ai/skills/clean-architecture/SKILL.md

@@ -1,6 +1,8 @@
 ---
 name: clean-architecture
 description: Enforce clean architecture principles and Hexagonal/Onion patterns. Use when designing system architecture, domains, or defining module boundaries.
+category: code
+impact: medium
 ---
 
 # Clean Architecture

.ai/skills/clean-code/SKILL.md

@@ -1,6 +1,8 @@
 ---
 name: clean-code
 description: Apply clean code principles, SOLID, and DRY practices. Use when writing, reviewing, or refactoring application code.
+category: code
+impact: medium
 ---
 
 # Clean Code Guidelines

.ai/skills/core-principles/SKILL.md

@@ -2,6 +2,7 @@
 name: core-principles
 description: The absolute foundational behavior, etiquette, and operational methodology for the AI assistant. Use when discussing AI behavior, rules, speed vs quality, or making decisions.
 category: meta
+impact: high
 ---
 
 > **🏷️ Category:** `Meta-Skill` | **⚙️ Applies to:** AI Behavior, Ethics & Operational Methodology

.ai/skills/docs/SKILL.md

@@ -1,7 +1,8 @@
 ---
 name: docs
 description: Rules for maintaining the project's documentation folder (ai-context.md and architecture.md). Use when editing or creating project documentation files.
-category: meta
+category: workflow
+impact: low
 ---
 
 > **🏷️ Category:** `Meta-Skill` | **⚙️ Applies to:** Project Documentation Management

.ai/skills/documentation/SKILL.md

@@ -1,6 +1,8 @@
 ---
 name: documentation
 description: Rules and structures for writing project documentation in Markdown. Use when creating, formatting, or updating markdown docs.
+category: workflow
+impact: low
 ---
 
 # Documentation Instructions

.ai/skills/file-editing/SKILL.md

@@ -1,6 +1,8 @@
 ---
 name: file-editing
 description: Rules for sandbox file editing into tmp/ topics to avoid root pollution. Use when creating temporary files, drafts, scratchpads, or experimenting.
+category: workflow
+impact: low
 ---
 
 # File Editing Instructions

.ai/skills/git/SKILL.md

@@ -1,6 +1,8 @@
 ---
 name: git
 description: Enforce semantic versioning and strict Git commit message formats (topic-level). Use when committing code, parsing git history, or writing commit messages.
+category: workflow
+impact: medium
 ---
 
 # Git Instructions

.ai/skills/grill-me/SKILL.md

@@ -1,6 +1,8 @@
 ---
 name: grill-me
 description: Active interrogator mode to clarify fuzzy requirements before starting work. Use when the user asks to be grilled, questioned, or needs to flesh out an idea.
+category: workflow
+impact: medium
 ---
 
 # Grill Me Instructions

.ai/skills/helm/SKILL.md

@@ -1,6 +1,8 @@
 ---
 name: helm
 description: Helm chart guidelines focusing on explicit resource naming over complex umbrellas. Use when creating, modifying, or reviewing Helm charts and Kubernetes manifests.
+category: infra
+impact: medium
 ---
 
 # Helm Chart Development Guidelines

.ai/skills/iac/SKILL.md

@@ -1,6 +1,8 @@
 ---
 name: iac
 description: Best practices for Infrastructure as Code, GitOps, minimizing configuration drift, and avoiding imperative infrastructure operations.
+category: infra
+impact: high
 ---
 
 # Infrastructure as Code (IaC)

.ai/skills/kubernetes-access/SKILL.md

@@ -1,6 +1,8 @@
 ---
 name: kubernetes-access
 description: Defines workflows for interacting with Kubernetes clusters, depending on whether a valid kubeconfig is present. Emphasizes read-only access and strict IaC adherence.
+category: infra
+impact: high
 ---
 
 # Kubernetes & Helm Access

.ai/skills/mermaid/SKILL.md

@@ -1,6 +1,8 @@
 ---
 name: mermaid
 description: Safe Mermaid diagram generation avoiding raw HTML entities and newlines. Use when generating, formatting, or updating Mermaid graphs or diagrams.
+category: workflow
+impact: low
 ---
 
 # Mermaid Diagram Instructions

.ai/skills/project-context/SKILL.md

@@ -2,6 +2,7 @@
 name: project-context
 description: Establish how the AI should fetch, create, and interact with a project's individual ai-context.md file. Use when setting up a new project or looking for project repo context.
 category: meta
+impact: low
 ---
 
 > **🏷️ Category:** `Meta-Skill` | **⚙️ Applies to:** AI Internal Operations & Context Discovery

.ai/skills/readme/SKILL.md

@@ -2,6 +2,7 @@
 name: readme
 description: Guidelines for creating or updating README files. Use when generating, formatting, or editing the project's root README.md.
 category: meta
+impact: low
 ---
 
 > **🏷️ Category:** `Meta-Skill` | **⚙️ Applies to:** Project Documentation Management

.ai/skills/root-skill/SKILL.md

@@ -2,6 +2,7 @@
 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
+impact: high
 ---
 
 > **🏷️ Category:** `Meta-Skill` | **⚙️ Applies to:** Global AI State Machine & Workflow

.ai/skills/use-cases/SKILL.md

@@ -1,6 +1,8 @@
 ---
 name: use-cases
 description: Structure use case documentation following rigid outlines to prevent bloat. Use when defining application use cases, stories, or functional requirements.
+category: workflow
+impact: low
 ---
 
 # Use Cases Instructions

.ai/skills/write-skill/SKILL.md

@@ -1,7 +1,8 @@
 ---
 name: write-skill
 description: Create new agent skills with proper structure and AI superpower constraints. Use when user wants to create, write, or build a new skill, rule, or instruction.
-category: meta
+category: workflow
+impact: medium
 ---
 
 > **🏷️ Category:** `Meta-Skill` | **⚙️ Applies to:** AI Internal Operations & Context Discovery
@@ -15,7 +16,7 @@ Force the AI to structure all new knowledge files into the strict, restrictive,
 
 ## 🚨 Prohibitions (Thou Shalt Not)
 
-- **NEVER create a new skill without YAML frontmatter.** It MUST contain `name` and `description` (with "Use when [triggers]").
+- **NEVER create a new skill without YAML frontmatter.** It MUST contain `name`, `categoy`, `impact` and `description` (with "Use when [triggers]").
 - **NEVER create a skill longer than 100 lines.** If it's too long, split the theory/examples into `REFERENCE.md` or `EXAMPLES.md`.
 - **NEVER write text-heavy prose.** Use bullet points, bold text, and "Negative Prompting" (`🚨 Prohibitions: NEVER...`).
 - **NEVER skip the `ai-root-instructions.md` integration.** The skill does not exist until it's registered in the router.
@@ -31,13 +32,20 @@ Force the AI to structure all new knowledge files into the strict, restrictive,
    - Run `create_file` to save `SKILL.md`.
    - Run `replace_string_in_file` to add a new trigger line to `.ai/skills/ai-root-instructions/SKILL.md`.
 
+## Impact Selection Criteria:
+- high: Foundational rules. Security, state machines (root-skill), core ethics, or infrastructure integrity (IaC). If this rule is broken, the project or AI logic fails.
+- medium: Workflow & Quality. Coding standards, Git practices, architectural patterns. Important for long-term health, but doesn't crash the system immediately.
+- low: Formatting & Tools. Mermaid syntax, README structures, or temporary file handling. Purely aesthetic or helper-level instructions.
+
 ## ✅ / ❌ Examples
 
 ### The Mandatory SKILL.md Template
 ```md
 ---
-name: [skill-name]
-description: [1st sentence: what it does. 2nd sentence: "Use when [specific triggers]."]
+name: <skill-name>
+description: <what it does> <clear-description-for-ai-to-understand-when-to-load>
+category: <meta|workflow|code|infra>
+impact: <high|medium|low>
 ---
 
 # [Skill Name]