Skip to content
Back to skills

Polar Local Environment

ASecurity

This skill should be used when setting up or managing Polar local development environment with Docker.

  • 2 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added September 25, 2026
ai-agentsgoshellsqlnextjsfastapidockerapidatabasefrontendbackend

Works with

  • api

Security analysis

A100/100

Pro scans all 7 files and shows the line behind each finding

Scanned September 25, 2026

npx -y skills add Najeebullah3124/awesome-claude-universe --skill polar-local-environment --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Polar Local Environment?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Polar Local Environment
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/najeebullah3124-polar-local-environment/badge)](https://www.skillsdirectory.com/skills/najeebullah3124-polar-local-environment)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: polar-local-environment
description: "This skill should be used when setting up or managing Polar local development environment with Docker."
license: MIT
metadata:
  author: polar
  version: "1.0.0"
---

# 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.

## Instance Auto-Detection

The `dev docker` command **automatically detects** the correct instance number. No manual `-i` flag is needed in most cases.

**Detection priority:**
1. `CONDUCTOR_PORT` env var → `(port - 55000) / 10 + 1`
2. Workspace path hash → stable instance derived from the repo root path

You can override with `-i N` if needed, but auto-detection handles Conductor workspaces automatically.

## 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 up -d` |
| Stop services | `dev docker down` |
| View all logs | `dev docker logs` |
| View service logs | `dev docker logs {service}` |
| Follow logs | `dev docker logs -f` |
| Check status | `dev docker ps` |
| Restart service | `dev docker restart {service}` |
| Shell access | `dev docker shell {service}` |
| Fresh start | `dev docker cleanup -f && dev docker up -d` |
| With monitoring | `dev docker up --monitoring -d` |
| Force rebuild | `dev docker up -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 |

Files in this skill

  • SKILL.md2.5 KB
  • rules/manage-instances.md1.5 KB
  • rules/service-architecture.md2.4 KB
  • rules/start-environment.md1.4 KB
  • rules/stop-environment.md1004 B
  • rules/troubleshooting.md2.2 KB
  • rules/view-logs.md1.4 KB

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…