AGENT GUIDE: Trader-Jan Development Assistant
This repository is equipped with a specialized AI Agent configuration designed to automate the development, testing, and deployment of ATAS Indicators and Strategies.
1. How It Works
The agent is a specialized C# engineer integrated into your environment. It operates under a Strict Plan Policy: every modification must be documented in an implementation plan and approved by you before any code is written. Your approval of the plan also authorizes the agent to execute any listed terminal commands automatically, ensuring a streamlined workflow with minimal interruptions.
2. File Structure & Responsibilities
| File / Directory | Purpose |
|---|---|
.agent/Agent.md |
The Brain. Defines the agent's persona, core directives (e.g., "Must increment version"), and high-level rules. |
.agent/task.md |
Persistent Task List. Repository-level tracker for active and pending work. |
.agent/rules/ |
Mandatory Rules (Active at all times). |
├── versioning.md |
Defines Mandatory File Headers, Semantic Versioning rules, and Changelog formats. |
├── trader-jan-standards.md |
Defines C# coding patterns (UI Attributes, Threading, Logging wrappers). |
.agent/skills/ |
Knowledge Base (On-demand). |
├── atas-reference/ |
General ATAS API documentation and examples. |
.agent/workflows/ |
Action Plans. |
├── start.md |
The /start command. Reads context and checks status. |
├── publish.md |
The /publish command. Automates the build and deploy cycle. |
.agent/scripts/ |
Automation Tools. |
├── publish_update.ps1 |
PowerShell script that handles Compilation, DLL Deployment, and Git Versioning/Pushing. |
3. How to Start a Conversation
To ensure the agent is fully aligned with your project context and rules, always begin a new session with the start workflow.
Command:
/start
What happens:
1. The agent reads Agent.md, trader-jan-standards.md, and versioning.md.
2. It checks ROADMAP.md and .agent/task.md for pending work.
3. It runs git status to see if the repo is clean.
4. It provides recommendations and waits for your approval before proceeding.
4. Key Workflows
The "Golden Rule" of Development
- Plan: The agent proposes changes via an
implementation_plan.md. - Approve: You must actively approve the plan.
- Code: Only once approved, the agent writes the code, staying strictly within the defined scope.
- Version: The agent MUST increment the version number for every change.
- Publish: The agent executes the
/publishworkflow.
The Publish Command
/publish
Automated Steps:
1. Builds the project (Release mode).
2. Deploys the DLL to your ATAS Indicators folder.
3. Commits specific files with a message like: Update MyIndicator.cs to v1.0.2.
4. Pushes to GitHub.
Generated by Antigravity for Trader Jan