How do I install the Forex Dev Workflow skill?

Run npx skillmds@latest add tomevault-io/forex-dev-workflow in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Forex Dev Workflow safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Forex Dev Workflow?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Forex Dev Workflow free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Forex Dev Workflow?

tomevault-io (@tomevault-io) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Forex Dev Workflow by tomevault-io — Agent Skill

Name: Forex Dev Workflow
Author: tomevault-io

Forex Dev Workflow

Documents the local development environment setup, Docker scripts, root package.json commands, and how to start/stop/check the full FOREX stack. Use when working on DevOps scripts, docker-compose configuration, adding new services to the stack, or when the user asks how to run, stop, or check status of the application locally. Use when this capability is needed.

tomevault-io 5952b70 2 files · 3.7 KB Updated Sep 17, 2026

File contents

FOREX Dev Workflow

Dev Environment Components

The local development stack consists of:

PostgreSQL — Shared database server (each service uses its own schema/database)
Temporal Server — Workflow engine + Temporal UI (visible at http://localhost:8233)
Customer Profile Service — Go service on port 8081
Trading Book Service — Go service on port 8082
Trade Capture Worker — Temporal worker process (no HTTP port, connects to Temporal server)
Portal — Angular dev server on port 4200

DevOps/Local Scripts

All scripts are in DevOps/Local/:

Script	Purpose
`docker-all-run.sh`	Build Docker images and start all containers via Docker Compose. Accepts `--no-build` to skip image builds.
`docker-all-shutdown.sh`	Gracefully stop and remove all containers and networks. Accepts `--volumes` to also delete persistent data.
`stop.sh`	Quick-stop containers without removing them (can resume with `docker compose start`).
`status.sh`	Display running container status, ports, and health. Prints URLs for Temporal UI and Portal.

Root package.json Scripts

The root package.json provides a single entry point for all operations:

npm Script	Delegates To	Purpose
`start:all`	`DevOps/Local/docker-all-run.sh`	Build and start the full stack
`stop:all`	`DevOps/Local/docker-all-shutdown.sh`	Stop and remove all containers
`stop`	`DevOps/Local/stop.sh`	Quick-stop without removal
`status`	`DevOps/Local/status.sh`	Show container status

Adding a New Microservice to the Stack

When adding a new microservice:

Create the service directory under Backend/Services/<service-name>/.
Add a Dockerfile to the service directory.
Add the service to docker-compose.yml with its port, environment variables, and database dependency.
Add corresponding start/health-check entries in the DevOps scripts if needed.
Add npm script aliases in root package.json if the service needs individual start/stop control.
Update DevOps/Local/status.sh to include the new service's URL.

Detailed Reference

For full environment setup instructions and Docker Compose configuration details, read references/dev-environment.md.

Source: javakishore-veleti/FOREX-Position-Risk-Manager-Workflows — distributed by TomeVault.

---name: forex-dev-workflowdescription: Documents the local development environment setup, Docker scripts, root package.json commands, and how to start/stop/check the full FOREX stack. Use when working on DevOps scripts, docker-compose configuration, adding new services to the stack, or when the user asks how to run, stop, or check status of the application locally. Use when this capability is needed.---# FOREX Dev Workflow## Dev Environment ComponentsThe local development stack consists of:1. **PostgreSQL** — Shared database server (each service uses its own schema/database)2. **Temporal Server** — Workflow engine + Temporal UI (visible at `http://localhost:8233`)3. **Customer Profile Service** — Go service on port `8081`4. **Trading Book Service** — Go service on port `8082`5. **Trade Capture Worker** — Temporal worker process (no HTTP port, connects to Temporal server)6. **Portal** — Angular dev server on port `4200`## DevOps/Local ScriptsAll scripts are in `DevOps/Local/`:| Script | Purpose ||--------|---------|| `docker-all-run.sh` | Build Docker images and start all containers via Docker Compose. Accepts `--no-build` to skip image builds. || `docker-all-shutdown.sh` | Gracefully stop and remove all containers and networks. Accepts `--volumes` to also delete persistent data. || `stop.sh` | Quick-stop containers without removing them (can resume with `docker compose start`). || `status.sh` | Display running container status, ports, and health. Prints URLs for Temporal UI and Portal. |## Root package.json ScriptsThe root `package.json` provides a single entry point for all operations:| npm Script | Delegates To | Purpose ||-----------|-------------|---------|| `start:all` | `DevOps/Local/docker-all-run.sh` | Build and start the full stack || `stop:all` | `DevOps/Local/docker-all-shutdown.sh` | Stop and remove all containers || `stop` | `DevOps/Local/stop.sh` | Quick-stop without removal || `status` | `DevOps/Local/status.sh` | Show container status |## Adding a New Microservice to the StackWhen adding a new microservice:1. Create the service directory under `Backend/Services/<service-name>/`.2. Add a `Dockerfile` to the service directory.3. Add the service to `docker-compose.yml` with its port, environment variables, and database dependency.4. Add corresponding start/health-check entries in the DevOps scripts if needed.5. Add npm script aliases in root `package.json` if the service needs individual start/stop control.6. Update `DevOps/Local/status.sh` to include the new service's URL.## Detailed ReferenceFor full environment setup instructions and Docker Compose configuration details, read [references/dev-environment.md](references/dev-environment.md).---> Source: [javakishore-veleti/FOREX-Position-Risk-Manager-Workflows](https://github.com/javakishore-veleti/FOREX-Position-Risk-Manager-Workflows) — distributed by [TomeVault](https://tomevault.io).

Frequently asked questions