Message file copied, contributing.md udpated

Author: anuunchin

CONTRIBUTING.md

@@ -100,9 +100,19 @@ your source will be distributed to other users once it is accepted into our repo
 
 ## Walkthrough: Modify or add rules files for LLM-enabled IDEs
 In this section, you will learn how to contribute rules files.
-1. Follow the [coding prerequisites](#coding-prerequisites) to setup the repository
-2. On your branch, add or modify rules files under the `/ai` directory
-3. Verify that the rules are properly formatted and work with the target IDE.
+
+### 1. How the `ai/` directory works
+
+1. The `.rules` folder is the master folder from which the files are rendered and copied into the respective IDE folders with the appropriate structure and format.
+2. Rendering and copying of the files are handled by the `make transpile-rules` command.
+3. The make transpile-rules command relies on Continue's [rules CLI](https://github.com/continuedev/rules).
+
+### 1. How to modify or add rules
+
+1. Follow the [coding prerequisites](#coding-prerequisites) to setup the repository.
+2. On your branch, add or modify rules files under the `/ai/.rules/` directory.
+3. Verify that the rules are properly formatted.
+4. Run `make transpile-rules` to update the respective IDE folders.
 4. Proceed to the pull request section to [create a pull request to the main repo](#making-a-pull-request-to-the-main-repo-from-fork). Please explain for what use cases these rules are useful and share what IDE version you're using.
 
 ## Coding Prerequisites

Makefile

@@ -34,15 +34,15 @@ format-lint: format lint
 
 transpile-rules:
 	cd ai && \
-	uv run rules render claude && mkdir -p claude && mv CLAUDE.md claude/ && \
-	uv run rules render amp && mkdir -p amp && mv AGENT.md amp/ && \
-	uv run rules render codex && mkdir -p codex && mv AGENT.md codex/ && \
-	uv run rules render cody && mkdir -p cody && cp -r .sourcegraph cody/ && rm -rf .sourcegraph && \
-	uv run rules render cline && mkdir -p cline && cp -r .clinerules cline/ && rm -rf .clinerules && \
-	uv run rules render cursor && mkdir -p cursor && cp -r .cursor cursor/ && rm -rf .cursor && \
-	uv run rules render continue && mkdir -p continue && cp -r .continue continue/ && rm -rf .continue && \
-	uv run rules render windsurf && mkdir -p windsurf && cp -r .windsurf windsurf/ && rm -rf .windsurf && \
-	uv run rules render copilot && mkdir -p copilot && cp -r .github copilot/ && rm -rf .github
+	uv run rules render claude && mkdir -p claude && mv CLAUDE.md claude/ && cp .rules/.message claude/ && \
+	uv run rules render amp && mkdir -p amp && mv AGENT.md amp/ && cp .rules/.message amp/ && \
+	uv run rules render codex && mkdir -p codex && mv AGENT.md codex/ && cp .rules/.message codex/ && \
+	uv run rules render cody && mkdir -p cody && cp -r .sourcegraph cody/ && rm -rf .sourcegraph && cp .rules/.message cody/ && \
+	uv run rules render cline && mkdir -p cline && cp -r .clinerules cline/ && rm -rf .clinerules && cp .rules/.message cline/ && \
+	uv run rules render cursor && mkdir -p cursor && cp -r .cursor cursor/ && rm -rf .cursor && cp .rules/.message cursor/ && \
+	uv run rules render continue && mkdir -p continue && cp -r .continue continue/ && rm -rf .continue && cp .rules/.message continue/ && \
+	uv run rules render windsurf && mkdir -p windsurf && cp -r .windsurf windsurf/ && rm -rf .windsurf && cp .rules/.message windsurf/ && \
+	uv run rules render copilot && mkdir -p copilot && cp -r .github copilot/ && rm -rf .github && cp .rules/.message copilot/ \
 
 test:
 	uv run pytest tests

ai/README.md

@@ -1,11 +1,10 @@
-The `/ai` directory includes for popular LLM-enabled IDEs (Cursor, Continue, Cline, Claude, etc.).
+The `/ai` directory includes rules for popular LLM-enabled Agents and IDEs (Amp, Claude, Cline, Codex, Cody, Continue, Copilot, Cursor, Windsurf).
 Add them to your project using the `dlt ai setup $IDE` command ([reference](https://dlthub.com/docs/reference/command-line-interface#dlt-ai-setup)).
-The way it works is very simple:
 
-1. Each folder here corresponds to a particular IDE.
-2. `setup` subcommand looks for a folder named `$IDE` and copies all files from it to current `dlt` project.
-3. `.message` file is displayed, not copied.
+The way it works is very simple:
 
-We are pretty sure that command line interface will soon change to support many set of rules per editor focused on specific tasks.
+1. Each folder here corresponds to a particular IDE or AI agent.
+2. The `setup` subcommand looks for a folder named `$IDE` and copies all files from it to current `dlt` project.
+3. The `.message` file is displayed, not copied.
 
-If you want to share useful rules, follow the instructions in [CONTRIBUTING.md](../CONTRIBUTING.md#walkthrough-modify-or-add-rules-files-for-llm-enabled-ides).
+If you want to share useful rules or make changes to the existing ones, follow the instructions in [CONTRIBUTING.md](../CONTRIBUTING.md#walkthrough-modify-or-add-rules-files-for-llm-enabled-ides).

ai/amp/.message

@@ -0,0 +1,3 @@
+
+This command and rule-set is a work in progress. Currently we provide rules specific to one workflow:
+creating REST API sources and pipeline from legacy code, OpenAPI specs, REST API documentation but also from scratch.

ai/claude/.message

@@ -0,0 +1,3 @@
+
+This command and rule-set is a work in progress. Currently we provide rules specific to one workflow:
+creating REST API sources and pipeline from legacy code, OpenAPI specs, REST API documentation but also from scratch.

ai/cline/.message

@@ -0,0 +1,3 @@
+
+This command and rule-set is a work in progress. Currently we provide rules specific to one workflow:
+creating REST API sources and pipeline from legacy code, OpenAPI specs, REST API documentation but also from scratch.

ai/codex/.message

@@ -0,0 +1,3 @@
+
+This command and rule-set is a work in progress. Currently we provide rules specific to one workflow:
+creating REST API sources and pipeline from legacy code, OpenAPI specs, REST API documentation but also from scratch.

ai/cody/.message

@@ -0,0 +1,3 @@
+
+This command and rule-set is a work in progress. Currently we provide rules specific to one workflow:
+creating REST API sources and pipeline from legacy code, OpenAPI specs, REST API documentation but also from scratch.

ai/continue/.message

@@ -0,0 +1,3 @@
+
+This command and rule-set is a work in progress. Currently we provide rules specific to one workflow:
+creating REST API sources and pipeline from legacy code, OpenAPI specs, REST API documentation but also from scratch.

ai/copilot/.message

@@ -0,0 +1,3 @@
+
+This command and rule-set is a work in progress. Currently we provide rules specific to one workflow:
+creating REST API sources and pipeline from legacy code, OpenAPI specs, REST API documentation but also from scratch.