How do I install the Local Environment skill?

Run npx skillmds add majiayu000/local-environment 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.

What does the Local Environment skill do?

Local development environment management for Polar using Docker It is listed under DevOps & Infra on SkillMD.

Is Local Environment safe to use?

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

Which AI agents work with Local Environment?

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 Local Environment free to use?

Yes. Installing skills from SkillMD is free. This skill is licensed under MIT.

Who published Local Environment?

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

Local Environment by majiayu000 — Agent Skill

Name: Local Environment
Rating: 4.2 (5 reviews)
Author: majiayu000

File contents

Local Environment Skill

This skill enables Claude to help manage the Polar local development environment using Docker. Use this when the user needs to start, stop, debug, or understand the local development stack.

Conductor Integration

CRITICAL: When running in Conductor, always check CONDUCTOR_PORT first to determine the instance number:

echo $CONDUCTOR_PORT

If CONDUCTOR_PORT is not set → Not running in Conductor, use instance 0
If CONDUCTOR_PORT is set → Calculate instance: INSTANCE=$((CONDUCTOR_PORT - 55090))

CONDUCTOR_PORT	Instance
55090	0
55091	1
55092	2
55093	3

Always use -i $INSTANCE flag with all docker-dev commands when running in Conductor.

When to Use

User asks to start/stop the local environment
User needs to view logs or debug issues
User wants to run multiple isolated instances
User needs to understand the service architecture
User encounters container or service errors

Quick Reference

Task	Command
Start full stack	`./dev/docker-dev -i $INSTANCE -d`
Stop services	`./dev/docker-dev -i $INSTANCE down`
View all logs	`./dev/docker-dev -i $INSTANCE logs`
View service logs	`./dev/docker-dev -i $INSTANCE logs {service}`
Follow logs	`./dev/docker-dev -i $INSTANCE logs -f`
Check status	`./dev/docker-dev -i $INSTANCE ps`
Restart service	`./dev/docker-dev -i $INSTANCE restart {service}`
Shell access	`./dev/docker-dev -i $INSTANCE shell {service}`
Fresh start	`./dev/docker-dev -i $INSTANCE cleanup && ./dev/docker-dev -i $INSTANCE -d`
With monitoring	`./dev/docker-dev -i $INSTANCE --monitoring -d`
Force rebuild	`./dev/docker-dev -i $INSTANCE -b -d`

Services

Service	Default Port	Description
api	8000	FastAPI backend
worker	-	Background job processor
web	3000	Next.js frontend
db	5432	PostgreSQL database
redis	6379	Redis cache
minio	9000/9001	S3-compatible storage
prometheus	9090	Metrics (optional)
grafana	3001	Dashboards (optional)

Instance Port Mapping

Port = Base Port + (Instance × 100)

Instance	API	Web	DB	Redis	MinIO
0	8000	3000	5432	6379	9000
1	8100	3100	5532	6479	9100
2	8200	3200	5632	6579	9200

Rules Index

Rule	Category	Description
service-architecture	Reference	Service details

---name: local-environmentdescription: Local development environment management for Polar using Dockerlicense: MIT--- # Local Environment Skill This skill enables Claude to help manage the Polar local development environment using Docker. Use this when the user needs to start, stop, debug, or understand the local development stack. ## Conductor Integration **CRITICAL:** When running in Conductor, always check `CONDUCTOR_PORT` first to determine the instance number: ```bash echo $CONDUCTOR_PORT ``` - If `CONDUCTOR_PORT` is **not set** → Not running in Conductor, use instance 0 - If `CONDUCTOR_PORT` is **set** → Calculate instance: `INSTANCE=$((CONDUCTOR_PORT - 55090))` | CONDUCTOR_PORT | Instance | |----------------|----------| | 55090 | 0 | | 55091 | 1 | | 55092 | 2 | | 55093 | 3 | **Always use `-i $INSTANCE` flag** with all docker-dev commands when running in Conductor. ## When to Use - User asks to start/stop the local environment - User needs to view logs or debug issues - User wants to run multiple isolated instances - User needs to understand the service architecture - User encounters container or service errors ## Quick Reference | Task | Command | |------|---------| | Start full stack | `./dev/docker-dev -i $INSTANCE -d` | | Stop services | `./dev/docker-dev -i $INSTANCE down` | | View all logs | `./dev/docker-dev -i $INSTANCE logs` | | View service logs | `./dev/docker-dev -i $INSTANCE logs {service}` | | Follow logs | `./dev/docker-dev -i $INSTANCE logs -f` | | Check status | `./dev/docker-dev -i $INSTANCE ps` | | Restart service | `./dev/docker-dev -i $INSTANCE restart {service}` | | Shell access | `./dev/docker-dev -i $INSTANCE shell {service}` | | Fresh start | `./dev/docker-dev -i $INSTANCE cleanup && ./dev/docker-dev -i $INSTANCE -d` | | With monitoring | `./dev/docker-dev -i $INSTANCE --monitoring -d` | | Force rebuild | `./dev/docker-dev -i $INSTANCE -b -d` | ## Services | Service | Default Port | Description | |---------|-------------|-------------| | api | 8000 | FastAPI backend | | worker | - | Background job processor | | web | 3000 | Next.js frontend | | db | 5432 | PostgreSQL database | | redis | 6379 | Redis cache | | minio | 9000/9001 | S3-compatible storage | | prometheus | 9090 | Metrics (optional) | | grafana | 3001 | Dashboards (optional) | ## Instance Port Mapping Port = Base Port + (Instance × 100) | Instance | API | Web | DB | Redis | MinIO | |----------|-----|-----|-----|-------|-------| | 0 | 8000 | 3000 | 5432 | 6379 | 9000 | | 1 | 8100 | 3100 | 5532 | 6479 | 9100 | | 2 | 8200 | 3200 | 5632 | 6579 | 9200 | ## Rules Index | Rule | Category | Description | |------|----------|-------------| | [service-architecture](rules/service-architecture.md) | Reference | Service details |

Frequently asked questions