github.com/lukedj78/dev-flow · MIT
Every project lives in one folder — .workflow/ — with one state file.
The skills read and write it, so each one knows what the last one did. The contract is the product;
the skills are replaceable consumers of it.
As a Claude Code plugin, or as plain files for Codex, Gemini, Copilot and Cursor.
/plugin marketplace add lukedj78/dev-flow
/plugin install dev-flow@dev-flowgit clone https://github.com/lukedj78/dev-flow.git && cd dev-flow
./install.sh --platform claude # or codex | gemini | cursor6 core · 15 web · 2 agent · 16 mobile · 3 monorepo · 2 refactor. A knowledge skill teaches and changes nothing; an operative one edits the codebase; discovery turns intent into artefacts; the orchestrator only routes.
Stack-agnostic. Every project uses these.
Orchestrate an end-to-end product-development workflow built on atomic skills.
compliance-auditoperativeRun a GDPR + EU AI Act compliance audit on an existing dev-flow project (web / mobile / eve agent) and remediate what it finds.
linear-scrumoperativeTake a dev-flow project into Linear and run it with agile scrum: creates or links the Linear Project, pushes .workflow/tasks.md into estimated, labelled issues, sets up 2-week cycles, then
Turn a raw product idea (a paragraph, a Notion dump, a half-formed thought) into a structured PROJECT.md (high-level brief) and PRD.md (product requirements document) inside a project's `.wo
prd-to-tasksdiscoveryBreak down a PRD.md into a concrete, executable tasks.md checklist that a developer or an AI agent can pick up and ship.
Review a diff on the two axes a dev-flow project can check that a generic reviewer cannot: the spec it was built from (.workflow/PRD.md + tasks.md) and the contract it was built
Next.js 16 · App Router · shadcn / Base UI / MUI / Coss.
Set up or extend a Next.js web app with Coss/UI — the official Cal.com design system, built on Base UI + Tailwind CSS v4 and installed through the shadcn CLI via the namespaced @coss/* reg
Read data in a Next.js 16 App Router app the canonical way — async Server Components first, URL searchParams for filter state, use() + <Suspense> when a Client Component needs server d
Generate or customize a frontend app from a DESIGN.md (Google design.md spec): reads its tokens and produces a working React app pre-styled to match.
figma-to-design-mddiscoveryUse when the user provides a Figma URL and wants to export/extract/generate design tokens, colors, typography, or system documentation into DESIGN.md format—a portable, AI-readable design st
formsoperativeBuild or edit any form in a Next.js 16 App Router app through one shared toolkit in lib/forms/, with dirty + valid Save gating — on TanStack Form + Zod (default) or react-hook-form (auto-d
Add a Motion-animated Heroicon to a Next.js app from the heroicons-animated registry instead of hand-animating an SVG.
image-to-design-mddiscoveryGenerate a DESIGN.md (Google design.md spec) from 1+ raster images — PNG / JPG screenshots, mockups, Pinterest pins, Dribbble shots, competitor app captures.
module-addoperativeWire a backend or infrastructure module (auth, database, payments, email, file storage, deploy config) into an already-scaffolded app.
screenshot-to-pageoperativeGenerate a real, working page (route + components) inside an already-scaffolded app from a single UI screenshot, applying the project's DESIGN.md tokens and the existing UI library (shadcn,
shadscanoperativeAudit a React/shadcn app for missing UI fundamentals — accessibility, interaction, empty/error/loading states, form wiring, responsive shell, production polish — with the shadscan CLI, then
state-disciplineknowledgeApply React 19 / Next.js 16 state discipline — useState is the last resort, not the default: derive from props/URL/data, key to reset, useMountEffect for one-time external sync, never
Give a Next.js 16 App Router app ONE motion system: a token layer (durations, easings, springs) plus a library of tokenized micro-interactions — entrance/exit, stagger, layout, modal/dropdow
vercel-deployoperativeShip a Next.js 16 App Router project to production on Vercel end-to-end: preview → smoke test → a *staged* production deployment (vercel --prod --skip-domain) that serves no traffic yet →
Run vercel-doctor on a Next.js project to find costly Vercel patterns BEFORE they inflate the bill, then route the fixes to the owning dev-flow skill (data-fetching for caching, `design-md
Write Vitest unit/integration tests OR Playwright e2e tests for an existing source file (server action, page, component, query).
The eve engine — inside the app, beside it, or alone.
Scaffold and manage an eve agent (Vercel's filesystem-first agent framework) — inside a Next.js app, as apps/agent in a monorepo, or alone at the repo root when the product has no UI.
Port a tool, connection or skill from a public eve/Flue agent registry — atomeve.dev, evex.sh, agentcn, eveagents.dev, the "shadcn for agents" registries — into a multi-tenant eve app WITHOU
Expo + React Native. Nine teach the stack, seven operate on it.
Use to add a new screen to an existing Expo + RN app: from a description, a wireframe, or a screenshot, generate the route file in app/ (Expo Router file-based), wire up data fetching via Ta
rn-animations-gesturesknowledgeUse when adding animations or gestures to a React Native + Expo app: scale/opacity/translation transitions, layout animations (FadeIn/SlideIn/FadeOut), shared-value driven motion, swipe-to-d
rn-backendknowledgeUse to connect an Expo + RN app to a backend (auth, database, storage, realtime), agnostic of the provider.
rn-bootstrapoperativeScaffold a new Expo + React Native app from a PROJECT.md + PRD.md + DESIGN.md using the opinionated stack (Expo Router, TypeScript, NativeWind v4, Zustand, TanStack Query, Reanimated, expo-i
rn-components-apisknowledgeUse when working with React Native core components (View, Text, ScrollView, FlatList, TextInput, Pressable, Modal, KeyboardAvoidingView, SafeAreaView) or platform APIs (Platform, Dimensions,
rn-data-fetchingknowledgeUse when fetching data from APIs in React Native: choosing between fetch+useEffect (didactic only) and TanStack Query (production default), wiring the QueryClient provider, building queries
rn-eas-build-submit-updateknowledgeUse for cloud builds and OTA updates of an Expo + RN app via EAS: configuring eas.json profiles (development/preview/production), managing credentials (APNs key, Android keystore) without co
rn-eas-deployoperativeUse to deploy an Expo + RN app end-to-end: initialize eas.json with 3 profiles (development/preview/production), set up credentials (APNs key, Android keystore) via eas credentials, build
Use when working with navigation in an Expo + React Native app: adding routes, building tab/stack/drawer layouts, modal routes, dynamic segments (e.g.
rn-fundamentalsknowledgeUse at the start of any React Native or Expo task to lock in foundational choices: Expo managed workflow as default, latest Expo SDK with New Architecture ON, TypeScript, npm.
rn-module-addoperativeUse to wire a backend/infra module (auth, db, storage, realtime, push, payments) into a scaffolded Expo + RN app.
rn-publishing-paymentsknowledgeUse when preparing an Expo + RN app for store submission (metadata, screenshots, localized listings, privacy nutrition label, age rating) and integrating monetization (In-App Purchases via R
rn-push-notificationsknowledgeUse when adding push or local notifications to an Expo + RN app: requesting permissions at the right moment, registering for push (Expo push service in dev, APNs/FCM direct in prod), handlin
rn-stylingknowledgeUse when styling React Native + Expo components: choosing between StyleSheet/NativeWind/inline, wiring NativeWind v4 from DESIGN.md tokens, handling Flexbox in RN (column-by-default, not row
rn-upgradeoperativeUse to upgrade an existing Expo + RN project to a newer Expo SDK: bump expo, run npx expo install --fix to align every dependency, run npx expo-doctor for diagnostics, clear caches, an
Use to write tests for an Expo + RN app: Jest + React Native Testing Library for unit/integration (components, hooks, queries, mutations) and Maestro for end-to-end flows (sign-in, navigatio
turborepo + shared packages across web, mobile and agent.
Extract logic from apps/web/ or apps/mobile/ into a new or existing shared package under packages/ in a turborepo monorepo, OR create a fresh empty shared package skeleton.
monorepo-bootstrapoperativeScaffold a turborepo monorepo on pnpm workspaces, with shared packages (types, design tokens or shared UI, backend client).
monorepo-sync-typesoperativeRegenerate backend types and re-export them via packages/shared/types/ in a turborepo monorepo so both apps/web/ and apps/mobile/ consume a single typed surface.
Stack-agnostic composition and colocation.
Use when refactoring React or React Native components that suffer from boolean prop proliferation, missing compound structure, prop drilling, or unclear ownership of state.
promote-componentoperativeUse to refactor a React/RN component up the colocation hierarchy (L0 → L1 → L2) when its usage spreads across pages.