From craft-skills
Full design-first pipeline with Codex as a co-executor for data-layer tasks. Claude handles architecture and UI; Codex handles types, services, queries, schemas, enums, mappers, and bulk fixes. Use when you want cost relief via Codex without losing Claude's reasoning on UI and integration.
npx claudepluginhub alexiolan/craft-skills --plugin craft-skillsThis skill uses the workspace's default tool permissions.
Full design-first pipeline. Claude does brainstorming, architect planning, UI implementation, and integration wiring. Codex handles data-layer tasks via `codex exec`.
Full design-first pipeline with all three AI agents: Claude (architect + UI + integration), Codex (data-layer + bulk fixes), and local LLM (LM Studio, for exploration + review). Power-user mode. Optionally runs Codex adversarial review if codex-plugin-cc is installed.
Routes agent roles to optimal AI models: Claude for planning/orchestration, Codex for code writing, Gemini for design/UI. Triggers on /multi-ai-run or model routing requests.
Guides new Claude Code users interactively through environment setup (CLAUDE.md, permissions, model selection), first session (explore-plan-implement, Plan Mode), and best practices (specific prompts, git safety, self-testing loops).
Share bugs, ideas, or general feedback.
Full design-first pipeline. Claude does brainstorming, architect planning, UI implementation, and integration wiring. Codex handles data-layer tasks via codex exec.
Profile: claude+codex
Pipeline: Brainstorm → Plan → Develop (hybrid executors) → Browser Test → Report (same phases as /craft)
npm i -g @openai/codexcodex login (ChatGPT auth) or set OPENAI_API_KEYAGENTS.md present at project root (auto-generated from CLAUDE.md by develop pre-flight if missing or stale)Does NOT require LM Studio.
This wrapper writes the profile marker, then delegates to the canonical craft pipeline. The develop skill reads .craft-profile and routes data-layer tasks to Codex instead of Claude sonnet agents.
echo -n "claude+codex" > .craft-profile
Read skills/craft/SKILL.md from this plugin and follow every phase exactly as written. Profile gating in the craft and develop skills routes the relevant tasks to Codex.
The user input is: $ARGUMENTS
Pass the input through as if the user had invoked /craft.
/craftdevelop Step 0 runs a Codex CLI pre-flight check — fails loud if Codex is missingdevelop Step 2 routes data-layer tasks (types, services, queries, schemas, enums, mappers) to Codexdevelop Step 2 also routes bulk lint/tsc fix sweeps to CodexTypical feature runs delegate ~30-40% of lines-of-code work to Codex, translating to roughly 15-20% overall cost relief per run. Varies significantly by feature shape: heavy data-layer features see more relief, UI-heavy features see less.