🧰 FWS Skills & Plugins

Installable plugins and agent skills for Codex CLI, Claude Code, and compatible skill hosts — by Flying Web Solutions.

Contents

Name	Type	Description
📄 prd-builder	Plugin	Generate full PRDs by analyzing existing products and recommending a modern tech stack
🛠️ do-it	Plugin	Spec-driven MVP builder — PRD → Grill → Design → Build → Review → Iterate. Designer-led UI-first via the adapter pattern, autonomous Ralph loop, brownfield mapping, psychology-driven UX, LLM Wiki docs, and a project dashboard
🔍 fws-client-discovery	Plugin	Complete client discovery — sitemap, competitors, personas, keywords, copy, and 90-day content plan
🌿 git-master	Plugin	Best-practice git workflow with Gitmoji + Conventional Commits, PR creation, and release management
🎨 magic-ui-ux	Plugin	Psychology-driven UI/UX design — combines cognitive psychology skills with Google Stitch MCP
🧱 etchwp	Plugin	Generate production-ready Etch + AutomaticCSS components with BEM naming, ACSS tokens, and vanilla JS
🧩 stack-agents	Plugin	Auto-triggering tech stack subagents for TanStack Start, Next.js, Convex, Supabase, and Clerk
📱 expo-stack	Plugin	Scaffold a production Expo app — Expo Router + Convex (cloud or self-hosted) + Better Auth + Uniwind + i18n + onboarding, Expo-UI-first, always the latest SDK, bun/pnpm/yarn workspaces

Each plugin ships both .codex-plugin/plugin.json and .claude-plugin/plugin.json. Codex exposes command-style workflows through a plugin-named skill such as $do-it build; Claude Code keeps its namespaced slash commands. Bundled SKILL.md files remain usable by other compatible skill hosts.

---

Which one do I need?

flowchart TD
    A["🧰 What are you doing?"] --> B{"Stage"}
    B -->|"Idea, no spec"| C["📄 prd-builder — analyze a product, produce a PRD"]
    B -->|"Spec to shipped MVP"| D["🛠️ do-it — PRD → Build → Review → Iterate"]
    B -->|"New client project"| E["🔍 fws-client-discovery — sitemap, personas, keywords, content plan"]
    B -->|"Designing screens"| F["🎨 magic-ui-ux — psychology-driven UX + Stitch UI"]
    B -->|"Writing code"| G{"Platform"}
    G -->|"Web app"| H["🧩 stack-agents — TanStack, Next.js, Convex, Supabase, Clerk"]
    G -->|"Mobile app"| I["📱 expo-stack — opinionated Expo scaffold"]
    G -->|"WordPress + Etch"| J["🧱 etchwp — Etch + ACSS components"]
    B -->|"Committing, PRs, releases"| K["🌿 git-master — gitmoji commits, PRs, semver"]

Loading

---

Compatibility

Tool	Plugins	Skills
OpenAI Codex CLI	Yes — Codex marketplace	Yes
Claude Code	Yes — Claude marketplace	Yes
Gemini CLI	No plugin marketplace	Yes

---

Installing in Claude Code

1 — Add this repo as a marketplace (one-time)

This repo ships with a .claude-plugin/marketplace.json, which makes it a valid Claude Code marketplace. Register it once using its GitHub path:

claude plugin marketplace add <github-username>/<repo-name>
# Example:
claude plugin marketplace add flyingwebie/skills

Verify it was registered:

claude plugin marketplace list

2 — Install plugins by name

# Install globally for your user account
claude plugin install prd-builder
claude plugin install fws-client-discovery
claude plugin install git-master

# Install only for the current project
claude plugin install prd-builder --scope project

Managing plugins

claude plugin list                          # List installed plugins
claude plugin update prd-builder            # Update to latest version
claude plugin disable prd-builder           # Disable without uninstalling
claude plugin uninstall prd-builder         # Remove completely
claude plugin marketplace remove flyingweb  # Remove the marketplace

Load a plugin for a single session (no install)

claude --plugin-dir /path/to/skills/prd-builder

---

Installing in OpenAI Codex CLI

This repo ships the Codex marketplace at .agents/plugins/marketplace.json. Add the repository once:

codex plugin marketplace add flyingwebie/skills
codex plugin marketplace list

Browse plugins interactively with /plugins, or list and install them from the shell:

codex plugin list --available --json
codex plugin add do-it@fws-skills
codex plugin add expo-stack@fws-skills

Start a new Codex session after installation so bundled skills and trusted hooks load. Invoke each plugin through its entry skill, followed by the workflow and arguments:

$do-it build
$git-master commit
$expo-stack doctor
$fws-client-discovery sitemap https://example.com

Codex asks you to review plugin hooks before running them. Use /hooks to inspect and trust the do-it, git-master, or fws-client-discovery hooks.

---

Installing in Gemini CLI

Gemini CLI supports skills natively via the .agents/skills/ path. Plugins are not supported — only the embedded SKILL.md files apply.

Install skills globally (all projects)

# Symlink bundled skills from plugins into the Gemini user skills directory
ln -s /path/to/skills/git-master/skills/git-workflow ~/.gemini/skills/git-workflow
ln -s /path/to/skills/git-master/skills/commit-conventions ~/.gemini/skills/commit-conventions

# Or use the ~/.agents/skills/ path (shared with Codex)
ln -s /path/to/skills/git-master/skills/git-workflow ~/.agents/skills/git-workflow

Install skills for one project (workspace)

Copy or symlink the skill into your project's local skills folder:

# Inside your project root
mkdir -p .agents/skills
ln -s /path/to/skills/git-master/skills/git-workflow .agents/skills/git-workflow

Commit .agents/skills/ to version control so the whole team shares the same skills.

Reload skills in a running session

/skills reload

List available skills

gemini skills list

---

Installing individual skills without the marketplace

Codex and Gemini can also load individual skill folders through .agents/skills/. Use this only when you want one low-level skill instead of the complete plugin.

Install skills globally (all projects)

ln -s /path/to/skills/git-master/skills/git-workflow ~/.agents/skills/git-workflow

Install skills for one project (workspace)

# Inside your project root
mkdir -p .agents/skills
ln -s /path/to/skills/git-master/skills/git-workflow .agents/skills/git-workflow

Install via the Codex skill installer

If you have the Codex $skill-installer built-in available, you can install from a GitHub path directly:

$skill-installer

Then provide the GitHub repo and path when prompted.

Invoke an individual skill in Codex

$git-workflow  ← prefix with $ to call a skill by name

---

File structure

Dual-compatible plugin

plugin-name/
├── .codex-plugin/
│   └── plugin.json          # Codex manifest and install-surface metadata
├── .claude-plugin/
│   └── plugin.json          # Claude Code manifest
├── commands/                # Claude slash commands; Codex entry skills adapt them
│   └── command-name.md
├── skills/                  # Skills bundled by both plugin formats
│   └── skill-name/
│       ├── SKILL.md
│       └── references/
├── hooks/                   # Event hooks (optional)
│   └── hooks.json
└── README.md

Skill (Claude Code + Gemini CLI + Codex CLI)

skill-name/
├── SKILL.md                 # Frontmatter triggers + instructions — required
├── references/              # Supporting docs Claude reads on demand (optional)
└── scripts/                 # Helper scripts the skill can invoke (optional)

Marketplace root (this repo)

.
├── .claude-plugin/
│   └── marketplace.json     # Declares all plugins — enables `claude plugin marketplace add`
├── .agents/plugins/
│   └── marketplace.json     # Declares all plugins for Codex CLI
├── prd-builder/             # Plugin
├── do-it/                   # Plugin
├── fws-client-discovery/    # Plugin
├── git-master/              # Plugin
├── magic-ui-ux/             # Plugin
├── etchwp/                  # Plugin
├── stack-agents/            # Plugin
├── expo-stack/              # Plugin
└── README.md

---

Learn more

• Build and package OpenAI plugins
• Claude Code plugins docs
• Gemini CLI skills docs
• Gemini CLI GEMINI.md context
• OpenAI Codex skills
• OpenAI Codex AGENTS.md

Validate the marketplace

Run the repository validator after changing any plugin, skill, hook, version, or marketplace entry:

node scripts/validate-codex-marketplace.mjs