home / skills / wellapp-ai / well / setup

This skill guides first-time developers through a structured environment setup, accelerating onboarding by validating tools, repos, and configurations.

npx playbooks add skill wellapp-ai/well --skill setup

Review the files below or copy the command above to add this skill to your agents.

Files (1)
SKILL.md
4.0 KB
---
name: setup
description: One-time environment setup for new team members
---

# Environment Setup Skill

Use this skill for first-time setup of your development environment.

## Phase 1: Core Development Tools

Verify these are installed:
- [ ] Cursor IDE (latest version)
- [ ] GitHub Desktop
- [ ] Docker
- [ ] TablePlus (database GUI)
- [ ] Figma Desktop App - https://www.figma.com/downloads/
- [ ] Screen.studio (optional, for demos)
- [ ] Google Cloud SDK (only for admins)

## Phase 2: Repository Setup

1. Clone the repository
2. Run `npm install` in monorepo root
3. Start Docker: `docker-compose up -d`
4. Run migrations: `npm run migrate`
5. Seed database: `npm run seed`

## Phase 2.5: Pattern Resources Orientation

Familiarize yourself with design resources:

1. Read `/docs/pattern-resources.md` - External UI/UX references
2. Read `/docs/design-system/` folder - Internal tokens and guidelines
3. Bookmark key competitor sites for your domain:
   - [Mobbin](https://mobbin.com/) - Real app screenshots
   - [Page Flows](https://pageflows.com/) - User flow recordings
   - [Refactoring UI](https://www.refactoringui.com/) - Visual design principles

## Phase 3: Environment Configuration

1. Copy `.env.example` to `.env` in:
   - `apps/api/.env`
   - `apps/web/.env`
2. Configure required variables

## Phase 4: MCP Configuration

### Installation Method: Manual (Recommended)

Cursor's UI auto-install can loop indefinitely. **Edit `~/.cursor/mcp.json` directly.**

### Complete mcp.json Template

Copy this to `~/.cursor/mcp.json` and replace `YOUR_*` placeholders:

```json
{
  "mcpServers": {
    "notion": {
      "command": "npx",
      "args": ["-y", "@notionhq/notion-mcp-server"],
      "env": {
        "OPENAPI_MCP_HEADERS": "{\"Authorization\": \"Bearer YOUR_NOTION_TOKEN\", \"Notion-Version\": \"2022-06-28\"}"
      }
    },
    "n8n-mcp": {
      "command": "npx",
      "args": ["-y", "supergateway", "--streamableHttp", "YOUR_N8N_URL/mcp-server/http", "--header", "authorization:Bearer YOUR_N8N_TOKEN"]
    },
    "context7": {
      "command": "npx",
      "args": ["-y", "@upstash/context7-mcp@latest"]
    },
    "figma": {
      "url": "http://127.0.0.1:3845/mcp"
    }
  }
}
```

### Authentication by MCP

| MCP | Auth Type | How to Get Token |
|-----|-----------|------------------|
| Notion | API Token | notion.so/my-integrations > New integration > Copy token |
| n8n | Bearer Token | n8n instance > Settings > API > Create key |
| Context7 | None | Just works |
| Figma Desktop | None | Enable in Figma app Dev Mode (Shift+D) |
| Figma Remote | OAuth | Use `"url": "https://mcp.figma.com/mcp"`, click Connect in Cursor |
| Browser | None | Built-in to Cursor |

### Browser MCP (Built-in)

Browser MCP is built into Cursor and requires no setup. Use it for:
- Taking screenshots of competitor apps during DIVERGE phase
- Testing Storybook stories
- E2E workflow verification

**Tip**: During feature exploration, navigate to competitor apps and use `browser_take_screenshot` to capture reference designs.

### Troubleshooting

**MCP won't install (infinite loop):**
1. Cancel the operation (Cmd+C or close dialog)
2. Manually edit `~/.cursor/mcp.json`
3. Add the config block directly
4. Restart Cursor: Cmd+Shift+P > "Reload Window"

**MCP shows disconnected:**
1. Verify JSON syntax is valid (use jsonlint.com)
2. Check token is correct and not expired
3. For Figma: ensure desktop app is running with MCP enabled

**Verification:**
After restart, list MCP folder to confirm all servers loaded:
```bash
ls ~/.cursor/projects/*/mcps/
```

## Phase 5: Cursor Settings

Configure in Cursor Settings:
- Model: Claude Opus 4.5
- Auto mode: Disabled
- Completion sounds: Enabled
- Usage summary: Always

## Phase 6: Verification

Run these to verify setup:
- [ ] `npm run dev` - starts without errors
- [ ] `npm run typecheck` - passes
- [ ] `npm run storybook` - loads components

## Completion

When all phases complete, you're ready to use:
- `init [Notion URL]` - Start a new feature
- `plan [feature]` - Create implementation plan

Overview

This skill guides one-time environment setup for new team members on a TypeScript finops monorepo. It provides a step-by-step checklist covering tools, repository bootstrap, Cursor MCP configuration, and verification commands so developers can be productive quickly. The instructions emphasize reproducible, reliable setup and common troubleshooting tips.

How this skill works

The skill inspects and documents the local prerequisites, repository bootstrap steps, and Cursor MCP configuration required to run services and developer tooling. It walks you through installing core tools, cloning and initializing the monorepo, configuring environment files, seeding the database, and validating the local runtime with dev, typecheck, and storybook checks. It also supplies a complete mcp.json template and troubleshooting steps for MCP issues.

When to use it

  • Onboarding a new engineer to the codebase
  • Re-installing or reprovisioning a developer workstation
  • Recovering from a broken Cursor or MCP configuration
  • Preparing a machine for demos or local integration testing
  • Confirming environment parity before a pairing or code review session

Best practices

  • Install and verify core dev tools before cloning the repo (IDE, Docker, DB GUI).
  • Copy .env.example to each app folder and fill required variables; avoid committing secrets.
  • Use the provided mcp.json template for Cursor MCP to bypass UI install loops. Edit ~/.cursor/mcp.json directly if auto-install fails.
  • Run migrations and seed data in Docker-backed environments to ensure local feature parity.
  • Verify with npm run dev, npm run typecheck, and npm run storybook before starting feature work.

Example use cases

  • New hire runs the checklist to get a working local dev environment in a few hours.
  • Engineer resets a laptop: reinstall tools, restore mcp.json, run migrations and seeds to resume work quickly.
  • Designer pairs with engineering to preview Storybook and live app components after following setup steps.
  • QA reproduces customer issues locally by starting the same services and data seeds the project uses in production.

FAQ

What if Cursor MCP auto-install loops and never finishes?

Cancel the installer, edit ~/.cursor/mcp.json with the provided template, then restart Cursor (Cmd+Shift+P > Reload Window). Validate JSON syntax before restarting.

Which env files must I configure?

Copy .env.example to .env in apps/api and apps/web, then populate required variables such as API keys and DB URLs. Do not commit secrets.