Update docs: directory paths in config

Author: zikajk

docs/config/commands.md

@@ -37,12 +37,17 @@ You can configure in multiple different ways:
 
 === "Config"
 
-    Just add to your config the `commands` pointing to `.md` files that will be searched from the workspace root if not an absolute path:
+    Add to your config the `commands` key. `path` can point to a single `.md` file or a directory. Directories load markdown files recursively. Relative paths are searched from each workspace root if not an absolute path:
 
     ```javascript title="~/.config/eca/config.json"
     {
       "commands": [{"path": "my-custom-prompt.md"}]
     }
     ```
 
-    ECA will make available a `/my-custom-prompt` command after creating that file.
+    ```javascript title="~/.config/eca/config.json"
+    // Load all command files from a directory recursively
+    {
+      "commands": [{"path": "/home/user/commands"}]
+    }
+    ```

docs/config/introduction.md

@@ -94,6 +94,7 @@ By default ECA consider the following as the base configuration:
       "hooks": {},
       "rules" : [],
       "commands" : [],
+      "skills": [],
       "disabledTools": [],
       "toolCall": {
         "approval": {

docs/config/rules.md

@@ -35,14 +35,21 @@ ECA loads rules from 3 sources:
 
 === "Config"
 
-    Paths listed in the `rules` config key. Relative paths are searched from each workspace root. Absolute paths inside a workspace behave as project rules; absolute paths outside workspaces behave as global rules.
+    Paths listed in the `rules` config key. `path` can point to a single rule file or a directory. Directories are loaded recursively, loading all files within. Relative paths are searched from each workspace root. Absolute paths inside a workspace behave as project rules; absolute paths outside workspaces behave as global rules.
 
     ```javascript title="~/.config/eca/config.json"
     {
       "rules": [{"path": "my-rule.md"}]
     }
     ```
 
+    ```javascript title="~/.config/eca/config.json"
+    // Load all rules from a directory recursively
+    {
+      "rules": [{"path": "/home/user/rules"}]
+    }
+    ```
+
 ## Static and path-scoped rules
 
 Most rules should be **static rules**: rules without `paths`. Their full content is automatically included in the system prompt. Use them for guidance that should always be available, such as coding style, response tone, or repository-wide conventions.

docs/config/skills.md

@@ -7,7 +7,7 @@ description: "Configure ECA skills: structured knowledge units that teach the LL
 ![](../images/features/skills.png)
 
 Skills are folders with `SKILL.md` which teachs LLM how to solve a specific task or gain knowledge about it.
-Following the [agentskills](https://agentskills.io/) standard, ECA search for skills following `~/.config/eca/skills/some-skill/SKILL.md` and `.eca/skills/some-skill/SKILL.md` which should contain `name` and `description` metadatas.
+Following the [agentskills](https://agentskills.io/) standard, ECA searches for skills following `~/.config/eca/skills/some-skill/SKILL.md`, `.eca/skills/some-skill/SKILL.md`, and `.agents/skills/some-skill/SKILL.md` which should contain `name` and `description` metadatas.
 
 When sending a prompt request to LLM, ECA will send only name and description of all available skills, LLM then can choose to load a skill via `eca__skill` tool if that matches user request.
 
@@ -75,6 +75,16 @@ Check the examples:
     }
     ```
 
+=== "Config"
+
+    Add to your config the `skills` key. `path` can point to a single skill directory (containing `SKILL.md`) or a directory containing multiple skill subdirectories. Directories load `SKILL.md` files recursively. Relative paths are searched from each workspace root if not an absolute path:
+
+    ```javascript title="~/.config/eca/config.json"
+    {
+      "skills": [{"path": "/home/user/skills"}]
+    }
+    ```
+
 ## Parameterized skills
 
 Skills can receive arguments when invoked as slash commands, using the same variable substitution as [custom commands](./commands.md): `$ARGS`, `$ARGUMENTS`, and positional `$1`, `$2`, etc.