メニュー
iPix / FashionOS domain hub. Routes to the fashion shoot-production toolkit and operator platform skills. Use for garment/product shoots, shot lists, lighting/call sheets, or iPix-specific platform workflows.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | ipix |
| description | iPix / FashionOS domain hub. Routes to the fashion shoot-production toolkit and operator platform skills. Use for garment/product shoots, shot lists, lighting/call sheets, or iPix-specific platform workflows. |
| version | 1.2.0 |
Entry point for iPix-specific agent skills. Load child SKILL.md / references on demand —
do not paste bodies here.
| User intent | Skill | Path |
|---|---|---|
| Any shoot production — direction, shot list, call sheet, model/garment/product/macro photography, lighting, shoot-day, asset triage | fashion-production | fashion-production/SKILL.md |
| Task | Skill |
|---|---|
| Pre-build creative exploration | brainstorming |
| Operator UI wireframes | ipix-wireframe |
| Supabase / edge functions / DNA scoring | ipix-supabase + gemini |
| Cloudflare Workers / Wrangler / Agents SDK | cloudflare |
| Shoot / campaign / commerce specs | docs/prd/ (shoot-prd, campaign-prd, prd-ecommerce) |
iPix creative / research task
└─ Any shoot work (brief, shot list, lighting, photography, shoot-day, triage)?
→ fashion-production/SKILL.md (routes by shoot phase)
Canonical multi-skill routes, aligned to the iPix PRD pipeline
(Brand → Campaign → Production → Asset DNA → Commerce → Publishing → Performance).
Maintained here only — other hubs link back to this map rather than duplicating it.
| Workflow | Skill chain |
|---|---|
| Brand Intelligence | ipix-supabase (edge fn) → gemini (analysis) → frontend-design/copilotkit (operator UI) |
| Campaign → Shoot | ipix-task-lifecycle (plan) → fashion-production (direction → shot list → capture) → cloudinary (assets) |
| Asset DNA | cloudinary (media) → gemini (scoring) → ipix-supabase (persist + RLS) |
| Commerce | Mercur (catalog, checkout) → ipix-supabase (commerce_product_links) → copilotkit (ProductCards) |
| Operator Hub UI | copilotkit (chat/runtime) → mastra (agents) → frontend-design (UI) → ipix-supabase (data) |
| Publishing | fashion-production/cloudinary (assets) → Postiz (PRD) → ipix-supabase (analytics) |
| Any IPI task | ipix-task-lifecycle (plan → research → implement → test → ship) orchestrates the above |
| Location | Role |
|---|---|
.claude/skills/fashion-production/ | Shoot-production toolkit (13 phase references) |
.claude/skills/archive/{apify-ecommerce,ecommerce-competitor-analyzer}/ | Commerce research skills (archived — restore if needed) |
.claude/skills/ipix/ | This hub + the canonical workflow map above |
Cloudflare platform hub — Workers, Pages, Wrangler CLI, D1/R2/KV, Durable Objects, Workers AI, Agents SDK, AI Gateway, Vectorize, Workflows, Tunnel, WAF, Terraform/Pulumi, and production Workers best practices. Use whenever the user mentions Cloudflare, Workers, wrangler, edge functions, Durable Objects, AI agents on Workers, `@cloudflare/workers-types`, `wrangler.jsonc`, Hyperdrive, or iPix Cloudflare tasks under `tasks/cloudflare/` — even if they do not say "Cloudflare" explicitly. NOT for Cloudinary media (→ cloudinary) or Supabase Postgres/RLS (→ ipix-supabase).
Five-phase orchestrator for iPix / FashionOS Linear team IPI — plan, research, implement, test, ship (worktrees, verify matrix, PR workflow, Linear state). Use whenever implementing or shipping IPI-NNN, wiring plans in docs/linear/issues, forensic verify before Done, MVP/P0 queue from tasks/plan/todo.md, multi-file platform work across app/supabase/edge, or user says "implement IPI-", "ship IPI-", "/task IPI", "close out Linear", "next P0 task", "forensic verify", "wiring plan", "open PR with verify". Always use for multi-step iPix delivery. Do NOT use for one-line typo fixes, explain-only questions, isolated copilotkit/ supabase/migration/lean/release-notes tasks without full lifecycle, or non-iPix repos.
Draft a changelog.md entry from git log + closed Linear IPI issues since the last entry. Use after a batch of commits lands or before tagging a release, when you need human-readable release notes rather than the /release gate checklist (which checks readiness, not prose). Triggers: "write release notes", "update the changelog", "draft changelog entry", "summarize what shipped". Do NOT use for the pre-merge gate check — that's `/release`.
Set up and operate git worktrees for isolated, parallel development — running multiple branches or Claude sessions at once without stashing or branch-switching, reviewing a PR while developing, comparing implementations side by side, or giving a risky change its own clean checkout. Use this whenever the user mentions worktrees, "isolated workspace", "parallel branches", "work on two things at once", `git worktree`, `--worktree`, or before executing a multi-step implementation plan that should not touch the current working tree. Also use when you (the agent) need an isolated checkout to make file changes that must not collide with the user's working tree.
Mastra framework: docs lookup (links.md, mastraDocs MCP, embedded docs), agents, workflows, streaming, browser, tools, memory, RAG, processors, CopilotKit guide. Verify from installed docs — never trust training-data APIs. NOT for: product intent routing (mastra-routing), Managed Agents API harness (mde-agents), non-Mastra frameworks. Load when editing src/mastra/**, Mastra tools/workflows, memory, streaming/events, browser automation, or Mastra doc URLs.
Turn a big, open-ended "build X" ask into a single scoped architecture brief before any code gets written. Use whenever the user hands you a goal-first, role-based prompt like "act as a senior software architect, build a production-ready X" or asks for an executive summary + architecture + database + frontend + backend + APIs + roadmap + risks all in one shot — this includes a pasted prompt template with a Requirements/Tasks/Output list, not just a plain-English ask. Forces explicit MVP-now-vs-later scoping and a risk section before routing each part of the brief to the skill that already owns it (graphify for analysis, ipix-supabase for schema, mermaid-diagrams for diagrams, frontend-design for UI, mastra for agents, writing-plans for the task breakdown) instead of freelancing a monolithic doc from scratch. Do NOT use for single-file fixes, for iterative back-and-forth design dialogue where the user wants to be asked questions one at a time (use brainstorming), or once a Linear IPI issue already has an appro