# wendy-cloud-iterate

Runs the Wendy Cloud dev stack end to end: brings up Docker and the Swift broker, runs integration tests, reads the failures and edits code.

- skill · `type=skill` · Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, OpenCode · ★ 62
- Author: wendylabsinc
- License: not stated · policy=link-only · description only; the file stays with the author
- Source: https://github.com/wendylabsinc/claude-skills/tree/HEAD/wendy-cloud-iterate/SKILL.md
- Updated: 2026-10-22
- HTML: https://affpapa.org/en/nevibecode/skills/wendy-cloud-iterate

## What it does

Around the Wendy Cloud repository this skill closes the loop by itself. It inspects the machine first, starts the stack, executes the test suite, works out what broke and applies a fix. Then it decides when to go round again. Two entry points exist: `make dev-docker` keeps the broker inside Docker, while `make dev-local` builds it on the host for quicker rebuilds. Both bring up Postgres, `swift-broker`, tunnel-broker and the gRPC-web Envoy, and seed a dev user with an org.

The prerequisite block is the interesting part. It installs Homebrew, `gh`, `protoc` and the `wendy` CLI, starts Docker Desktop if the daemon is down, clones `wendylabsinc/pki-core` and `wendylabsinc/cloud` into `~/Documents/Projects`, and checks GitHub CLI auth. After that no confirmation prompts appear: the skill pulls repos, runs `make`, `docker compose` and `wendy` commands, edits sources, commits and raises a pull request with `gh pr create`.

Two things can stop it. `wendy auth login` relies on Chrome and the Claude browser extension; without them you finish the login yourself — open the printed URL, pick an org, wait until the certificates are saved. And that login does not currently authenticate against the broker: a session appears, yet data-bearing RPCs answer `UNAUTHENTICATED`. The repo tracks this as WDY-2330, so the auth steps show the shape of the flow rather than a route to a working certificate.

## Requirements
- Works with: Docker

## Install

### Claude Code (native platform)

1. **Skills CLI (Vercel)**
```bash
npx skills add wendylabsinc/claude-skills --skill wendy-cloud-iterate -a claude-code
```

2. **Manually: put the files in place**
- File: `~/.claude/skills/wendy-cloud-iterate/SKILL.md` — Copy the whole skill folder; for one project use .claude/skills/wendy-cloud-iterate/

### Codex

1. **Skills CLI (Vercel)**
```bash
npx skills add wendylabsinc/claude-skills --skill wendy-cloud-iterate -a codex
```

2. **Manually: put the files in place**
- File: `.agents/skills/wendy-cloud-iterate/SKILL.md` — For all projects use ~/.agents/skills/

### Cursor

1. **Skills CLI (Vercel)**
```bash
npx skills add wendylabsinc/claude-skills --skill wendy-cloud-iterate -a cursor
```

2. **Manually: put the files in place**
- File: `.cursor/skills/wendy-cloud-iterate/SKILL.md` — Cursor also reads .agents/skills/ and .claude/skills/

### GitHub Copilot

1. **GitHub CLI**
```bash
gh skill install wendylabsinc/claude-skills wendy-cloud-iterate
```

2. **Manually: put the files in place**
- File: `.github/skills/wendy-cloud-iterate/SKILL.md`

### Gemini CLI

1. **Skills CLI (Vercel)**
```bash
npx skills add wendylabsinc/claude-skills --skill wendy-cloud-iterate -a gemini-cli
```

2. **Platform CLI**
```bash
gemini skills install https://github.com/wendylabsinc/claude-skills --path wendy-cloud-iterate
```

### Windsurf (Devin Desktop)

**Manually: put the files in place**
- File: `.devin/skills/wendy-cloud-iterate/SKILL.md` — The legacy .windsurf/skills/ path still works

### OpenCode

**Skills CLI (Vercel)**
```bash
npx skills add wendylabsinc/claude-skills --skill wendy-cloud-iterate -a opencode
```

### Claude.ai

**Claude.ai**
- Zip the folder and upload it in Settings → Capabilities → Skills

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/wendylabsinc/claude-skills/tree/HEAD/wendy-cloud-iterate/SKILL.md

## When to use it
- bring up the Wendy Cloud stack in one command
- run integration tests and triage the failures
- track down a regression after a new feature
- verify the toolchain before building the broker
- start Docker and wait until the daemon answers

## Example prompts
- Run the Wendy Cloud test loop and fix whatever fails
- Start the stack with `make dev-docker` and confirm the broker ports are listening
- Scan the Swift broker for regressions after the latest changes

## Similar
- [domain-cloud-native](https://affpapa.org/en/nevibecode/skills/domain-cloud-native.md) — skill · 2900 installs
- [ci-cd-best-practices](https://affpapa.org/en/nevibecode/skills/ci-cd-best-practices.md) — skill · 1200 installs
- [github-actions-templates](https://affpapa.org/en/nevibecode/skills/github-actions-templates.md) — skill · 17420 installs
- [gitlab-ci-patterns](https://affpapa.org/en/nevibecode/skills/gitlab-ci-patterns.md) — skill · 13112 installs
- [docker-agent-deploy](https://affpapa.org/en/nevibecode/skills/docker-agent-deploy.md) — skill · 733 installs
- [local-action-verification](https://affpapa.org/en/nevibecode/skills/local-action-verification.md) — skill · 696 installs

From the same set: [wendylabsinc/claude-skills](https://affpapa.org/en/nevibecode/by/wendylabsinc/claude-skills.md) — 7 cards

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md