Frigade Engage

View saved version →

---
name: frigade-engage
description: Build and manage Frigade Engage flows (announcements, tours, checklists, nudges, forms, banners, cards, NPS surveys) and collections directly from your coding agent, including end-to-end wiring into React/Next.js codebases. Use when the user mentions Frigade, onboarding flows, product tours, checklists, announcements, in-product guides, or flow collections (promoting, creating, or adding flows to a collection).
metadata:
  upstream-version: "0.0.1"
  upstream-commit: "aeba3dfc792b1ed9dcccfe576efabb039a2b9514"
  authored-against:
    backend-app: "d245b4fd"
    frigade-web: "17326986"
    docs: "fc1fe0c3"
    demo-v2: "82b68403"
    frigade-react: "2.9.4"
---

# frigade-engage

> **ChatGPT/Codex compatibility.** Load this skill through the plugin and read `reference/agent-harness.md` before executing. It maps recipe tool labels to the tools actually available in the host. Resolve recipe, reference, and example paths relative to this skill directory; resolve application paths against the user’s selected project.

## What this skill does

`frigade-engage` lets you build onboarding flows for your product — announcements, tours, checklists, forms, surveys, banners, and cards — directly from ChatGPT or Codex with the required project and execution tools. It manipulates your Frigade workspace via the Frigade API (GraphQL + REST) and wires the `@frigade/react` SDK into your Next.js or React codebase end-to-end. Once your keys are set up, you never need to open the Frigade dashboard: the agent reads and writes flow definitions, targeting rules, YAML payloads, and the component calls that render flows in your app — all from one conversation.

## Critical pre-flight: always run first-run-setup

**Every skill invocation runs `recipes/first-run-setup.md` first.** This ensures the project has Frigade API keys configured, the repo is bound to a Frigade workspace, and the `.env.local` / `.gitignore` / `.frigade/project.json` are set up correctly before any API call is made. Never skip this step. If keys or the workspace binding are missing, the setup recipe walks the user through initialization (public key + private secret for dev, optionally prod) and writes `.frigade/project.json` so subsequent invocations skip straight to work.

If the user's request looks entirely read-only ("what flows do I have?"), setup still runs — it's what proves we have credentials to read in the first place.

## Two environments — the mental model

Every Frigade workspace has two sibling environments, each with its own key pair: **dev** (`FRIGADE_API_KEY_SECRET` / `NEXT_PUBLIC_FRIGADE_API_KEY`) and **prod** (`..._SECRET_PROD` / `..._PROD`). They are separate Organization records — a flow in dev and its prod counterpart are distinct rows linked by a shared slug. **You build and iterate in dev; you ship to prod by promoting from dev.** The skill defaults to dev for everything and only ever touches prod when the user is explicitly promoting or has explicitly asked to operate in prod (see `recipes/first-run-setup.md` Section 5 for how the target env is resolved per call).

## Safety model summary

- **Dev environment (default):** All operations run immediately. Fast iteration, low friction, no confirmation prompts.
- **Prod is promote-only for flow & collection content.** The **only** sanctioned way to change a prod flow or collection is to make the change in dev and promote it (`recipes/promote-to-prod.md`, `recipes/promote-collection-to-prod.md`). Direct authoring in prod — creating, updating, publishing, or deactivating a flow or collection straight against the prod key — is **discouraged**. When a user asks for it, the skill **steers them to the dev→promote path** and proceeds only on an explicit typed override (`edit prod directly`). See `reference/operations.md` §"Prod is promote-only" for the exact steer template and the list of ops it covers.
- **Prod environment (other writes):** Any operation tagged `dangerous` in `refer

Preview of the first 4,000 characters. Read full instructions →

Referenced files: 40 — file references are metadata, not package contents.