---
description: Standardize VS Code settings across the team
---
1. **Create settings.json**:
- Create
// turbo
- Run
2. **Create extensions.json**:
- Recommend extensions for the team.
// turbo
- Run
3. **Pro Tips**:
- Commit the
description: Standardize VS Code settings across the team
---
1. **Create settings.json**:
- Create
.vscode/settings.json for workspace-specific settings.// turbo
- Run
mkdir -p .vscode && printf '{\n "editor.formatOnSave": true,\n "editor.defaultFormatter": "esbenp.prettier-vscode",\n "editor.codeActionsOnSave": {\n "source.fixAll.eslint": true\n }\n}' > .vscode/settings.json2. **Create extensions.json**:
- Recommend extensions for the team.
// turbo
- Run
printf '{\n "recommendations": [\n "dbaeumer.vscode-eslint",\n "esbenp.prettier-vscode",\n "bradlc.vscode-tailwindcss"\n ]\n}' > .vscode/extensions.json3. **Pro Tips**:
- Commit the
.vscode folder (excluding user-specific files) to git.By Antigravity Team
How to Use This Workflow
Option A: Project-Specific (Recommended)
- Click "Download" above
- In your project, create the directory:
.agent/workflows/ - Save the file as
sync-vscode-settings-extensions-team-consistency.md - In Antigravity, type
/sync_vscode_settings_extensions_team_consistencyor just describe what you want to do
Related Workflows
Generate .env from Example
ConfigEnvironmentSetup
--- description: Safely create a local .env file from .env.example --- 1. **Check for .env.example**: - Ensure the example file exists. // turbo - Run `test -f .env.example && echo "✅ Found .env.example" || echo "❌ .env.example not found"` 2. **Copy to .env.local**: - Create your local...
Generate TypeScript Types from API
TypeScriptAPICodegen+1
--- description: Auto-generate type-safe API client from OpenAPI/Swagger spec --- 1. **Get Your API Schema**: - Most APIs expose OpenAPI spec at `/swagger.json` or `/openapi.json`. - Download it or use the URL directly. 2. **Install openapi-typescript**: - Best tool for generating types. ...
Kill Port 3000
DevOpsTerminalProcess
--- description: Instantly find and kill the process hogging your dev port --- 1. **The Best Way (Cross-Platform)**: - Kill it in one command using npx. Works on Mac, Windows, and Linux. // turbo - Run `npx kill-port 3000` 2. **Mac/Linux Manual Method**: - Find PID: `lsof -ti:3000` ...
Recommended Rules
View more rules →Google Cloud Platform Expert
GCPGoogle CloudCloud
You are an expert in Google Cloud Platform (GCP) services and architecture. Key Principles: - Leverage Google's global infrastructure - Use managed o...
Monitoring & Observability (Prometheus, Grafana)
MonitoringObservabilityPrometheus
You are an expert in Monitoring and Observability using Prometheus and Grafana. Key Principles: - Monitor the four golden signals (Latency, Traffic, ...
GitOps & ArgoCD Expert
GitOpsArgoCDKubernetes
You are an expert in GitOps methodology and ArgoCD. Key Principles: - Git as the single source of truth - Declarative infrastructure and applications...
