rayfernando-skills
A collection of installable Skill files for AI coding agents. It started with the one most teams are missing — real-user QA — and now also ships waves, an orchestrator-worker skill that fans one big task out to a team of agents (Cursor and Codex variants), plus bootstrap-ios, a single entry point for loading Ray's iOS/macOS agent skill stack.
Skills in this collection
| Skill | What it does | Primary install (Claude Code) |
|---|---|---|
| running-bug-review-board · QA | Point an AI agent at your live app; it QAs like a real user, files P0/P1/P2 bug reports, and returns a YES/NO ship verdict plus a shareable HTML report. | /plugin install running-bug-review-board@rayfernando-skills |
| waves · Cursor + Codex | Fan one big research, analysis, or audit job out to parallel subagents, verify each structured handoff, and synthesize one deliverable. | /plugin install waves@rayfernando-skills |
| bootstrap-ios · iOS/macOS | One entry point for Swift, SwiftUI, SwiftData/Core Data, Swift Testing, Xcode build/test/simulator, XcodeBuildMCP, and curated community iOS skills. | /plugin install bootstrap-ios@rayfernando-skills |
Each skill installs into Claude Code, Cursor, Codex, and ~50 other agents — full per-agent steps are in the sections below.
Jump to: running-bug-review-board (QA) · waves · bootstrap-ios · Repo structure · Contributing
running-bug-review-board — real-user QA
running-bug-review-board— point an AI agent at your live app and it QAs it like a real, slightly unforgiving customer: drives the UI, files structured P0/P1/P2 bug reports with reproduction steps, and gives you a YES/NO "is this ready to ship?" verdict — plus a self-contained HTML report you can hand to the team.
What you get
Most AI workflows point at code review and miss where users actually hit bugs: the live app, on a real phone, with stale storage from yesterday and a flaky auth provider the unit tests never see. This Skill file encodes a battle-tested QA cadence so an agent can find those bugs for you.
- A real-user QA pass, not a code review. The agent drives the app from URLs and clicks — it is forbidden from marking anything "pass" by reading source. It hunts the failures users hit first: stale state across flows, mobile overflow, auth↔routing races, copy that lies, paths that 404 mid-onboarding.
- Structured bug reports. Every defect lands as
BUG-NNN-*.mdwith severity (P0/P1/P2), impact, what-happened-vs-expected, reproduction steps, and evidence (screenshots, console, network). - A ship/defer decision. Each pass ends with a YES/NO sign-off for the phase, listing open P0/P1 blockers and a paste-ready handoff prompt for the next agent.
- An editorial HTML dashboard stakeholders can open and share — the bug list and each bug report, regenerated every pass. (see it below)
- Works with what you have. Repo-agnostic and browser-tool-agnostic; web and iOS/iPadOS apps; optional two-way sync with Linear, GitHub Issues, Jira, or Notion. Runs fine in a cloud VM (e.g. Cursor cloud) with just a browser driver.
See the output
The agent regenerates a self-contained HTML report at the end of every pass — designed to read like a magazine, not a Kanban board (editorial typography, ink-on-paper palette, no chips or pills). Here is what you instantly get:
| The QA dashboard | A single bug report |
|---|---|
 |
 |
| Verdict first, then the prioritized bug list and recent runs. | One bug, told for an engineer: impact → what's happening vs. what should → steps → evidence. |
It is responsive, too — on a phone the dashboard collapses to a single column with a sticky primary action. (mobile sample · design notes)
Example prompts
Once the skill is installed, just ask your agent in plain language:
QA this app. Run a manual test plan on mobile and tell me what's broken.
Is phase 3 ready to ship? Give me a YES/NO with the open P0/P1 list.
Drive the signup flow like a brand-new user with stale storage, and file any bugs you find.
Re-test the fixed bugs BUG-007 and BUG-012 on the latest build and update the report.
Run the Interactive Bug Review Board with me on the open backlog.
The skill activates on phrases like "QA this", "is this ready to ship?", "find the bugs", or "run a test plan" — you don't have to name it.
Quick start
After installing, the agent walks itself through:
- Discover the app — read the product spec / README / phase doc, open bugs, and public routes.
- Plan — derive real-user scenarios from the spec and the gates.
- Prepare — environment, test accounts, primary viewport.
- Execute — drive the app like a customer, capturing evidence.
- File bugs —
BUG-NNN-*.mdwith priority + reproduction steps. - Sign off — YES/NO verdict, open P0/P1 list, and a paste-ready handoff.
No QA folder yet? The skill ships a scaffolder. After installing it lives in the Skill folder (e.g. ~/.claude/skills/running-bug-review-board/scripts/scaffold-qa.sh). To run it without installing, clone and call it directly:
git clone https://github.com/RayFernando1337/rayfernando-skills.git
bash rayfernando-skills/plugins/running-bug-review-board/skills/running-bug-review-board/scripts/scaffold-qa.sh \
/path/to/your/repo PHASE_NUMBER
This creates docs/qa/ with the bug template, run-report skeletons, gates checklist, and a per-phase manual test plan. It is idempotent and won't overwrite existing files.
Install
Pick the section for the agent you use. Each one installs the same Skill file; they differ only in how the agent discovers it.
Claude Code
/plugin marketplace add RayFernando1337/rayfernando-skills
/plugin install running-bug-review-board@rayfernando-skills
To pin a specific release tag, append it to the marketplace add (e.g. @v0.4.0). Docs: code.claude.com/docs/en/plugin-marketplaces.
Factory Droid
droid plugin marketplace add https://github.com/RayFernando1337/rayfernando-skills
droid plugin install running-bug-review-board@rayfernando-skills
Factory Droid reads the same .claude-plugin/marketplace.json Claude Code uses. Docs: docs.factory.ai/cli/configuration/plugins.
Codex (app, desktop, IDE, and CLI)
On Codex CLI, add the marketplace and install:
codex plugin marketplace add RayFernando1337/rayfernando-skills
codex plugin add running-bug-review-board@rayfernando-skills
On older Codex CLI without plugin add, open Codex, type /plugins, switch to the rayfernando-skills tab, and Install. In the app/desktop, use the Plugins / Skills installer and restart Codex so the skill cache reloads. Docs: developers.openai.com/codex/plugins/build.
You are likely running a cached running-bug-review-board 0.3.0 install. Update or reinstall running-bug-review-board@rayfernando-skills, then restart Codex (app, desktop, IDE, or CLI) so it refreshes the plugin cache. (0.3.1+ ships Codex-valid metadata and the release pipeline now validates it.)
Cursor
Cursor's /add-plugin is reserved for the cursor.com/marketplace listings, so for this repo use the cross-vendor installer — it writes the Skill folder into ~/.cursor/skills/, which Cursor reads on startup:
npx skills add https://github.com/RayFernando1337/rayfernando-skills/tree/main/plugins/running-bug-review-board/skills/running-bug-review-board -a cursor
Docs: cursor.com/docs/skills.
Cross-vendor: npx skills add
The vercel-labs/skills installer detects every supported agent CLI on your machine and writes the Skill folder into each one's expected location (Claude Code, Cursor, Codex, Factory Droid, Windsurf, Zencoder, and ~50 others):
npx skills add https://github.com/RayFernando1337/rayfernando-skills/tree/main/plugins/running-bug-review-board/skills/running-bug-review-board
Add -a <agent> to target one tool (-a cursor, -a codex, -a droid) or --all for every detected agent.
claude.ai (Settings → Features → Skills)
Download running-bug-review-board.zip from the latest release and upload it. To build the zip from a local clone (cl