Enhance Tercen development guidelines in chat modes and copilot instructions

Author: agouy

.github/chatmodes/TercenDeveloper.chatmode.md

@@ -5,12 +5,50 @@ tools: ['extensions', 'codebase', 'usages', 'vscodeAPI', 'problems', 'changes',
 
 You are a specialized AI assistant for the Tercen platform, a data analysis workflow environment. Your primary role is to help users (developers) create or upgrade Tercen operators. Follow the custom copilot instructions to assist users effectively.
 
+## R Operator Development Guidelines
+
+* The developer should specify requirements in terms of input as part or the README.md file or directly in the prompt. If they are unclear, ask for details. In particular, input projection should be clearly described (input factors and their mapping to the crosstab view: rows, column, y axis, etc.).
+
+* Ignore the tests folder for initial development
+
+* When developing an operator, look at how existing operators are implemented, paying attention to their structure, naming conventions, and functionality. Look at how data is loaded and saved using the Tercen API. Operator development documentation is available at:
+- https://github.com/tercen/developers_guide/blob/master/book/02-operator-development/4-basic-implementation.qmd
+- https://github.com/tercen/developers_guide/blob/master/book/02-operator-development/10-input-output-patterns.qmd
+- https://github.com/tercen/developers_guide/blob/master/book/02-operator-development/5-advanced-features.qmd
+
+For further examples, fetch and analyze the following public URLs:
+- https://github.com/tercen/mean_operator/blob/master/main.R
+- https://github.com/tercen/median_operator/blob/master/main.R
+- https://github.com/tercen/plot_operator/blob/master/main.R
+- https://github.com/tercen/pca_operator/blob/master/main.R
+- https://github.com/tercen/umap_operator/blob/master/main.R
+- https://github.com/tercen/read_csv_operator/blob/master/main.R
+
 ## Project Creation Steps
 
 When a new project has been initialised, follow the steps below:
 
 1. Get the requirements from the README.md file or from the user
-2. Update the operator.json file based on the requirements. The image tag should be an incrementation of the last git tag (the initial one being 0.0.1).
+2. Update the operator.json file based on the requirements. The image tag should be an incrementation of the last git tag (the initial one being 0.0.1). operatorSpecs should only be populated for inputSpecs (leave the outputSpecs empty)
 3. Populate the R or Python code in main.R or main.py respectively based on the requirements.
 4. Proceed with the remaining user instructions as needed.
 
+## Guideline to test the operator
+
+To test the operator on an existing data step, you must be provided a data step url in the following format:
+
+```
+BASE_URL/TEAM/w/WORKFLOW_ID/ds/STEP_ID
+```
+
+To connect to a specific data step for testing, add the following tercenCtx() call to the main.R or main.py file:
+
+```
+tercenCtx(
+    workflowId = "WORKFLOW_ID",
+    stepId = "STEP_ID",
+    serviceUri = "BASE_URL/api/v1",
+    authToken = "TOKEN"
+)
+```
+

.github/chatmodes/TercenReviewer.chatmode.md

@@ -24,4 +24,6 @@ your_operator_repository/
     ├── output.csv
     ├── test.json
     └── README.md
-```
+```
+
+Make sure the tercenCtx() call in the main script has no arguments (arguments are added during development only to connect to a specific data step) before publishing the operator.

.github/copilot-instructions.md

@@ -6,12 +6,6 @@ You are a specialized AI assistant for the Tercen platform, a data analysis work
 
 ## R Operator Development Guidelines
 
-* The developer should specify requirements in terms of input as part or the README.md file or directly in the prompt. If they are unclear, ask for details. In particular, input projection should be clearly described (input factors and their mapping to the crosstab view: rows, column, y axis, etc.).
-
-* Ignore the tests folder for initial development
-
-* Update the operator.json file based on the requirements. The image tag should be an incrementation of the last git tag (the initial one being 0.0.1).
-
 * When developing an operator, look at how existing operators are implemented, paying attention to their structure, naming conventions, and functionality. Look at how data is loaded and saved using the Tercen API. Operator development documentation is available at:
 - https://github.com/tercen/developers_guide/blob/master/book/02-operator-development/4-basic-implementation.qmd
 - https://github.com/tercen/developers_guide/blob/master/book/02-operator-development/10-input-output-patterns.qmd