Menu
Structured design dialogue with a visual companion — produces an approved spec and design artifacts before any implementation begins. Use at the start of a feature, before writing code.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Systematic performance profiling and optimization with a mandatory baseline-first gate — measure before changing, re-measure after. Use when something is slow or you need to hit a latency/throughput target.
Blameless post-mortem / RCA — gathers facts, reconstructs a timeline, runs 5-Whys, defines action items, writes the post-mortem file and commits it. Use after an incident or outage.
Structured design dialogue with a visual companion — produces an approved spec and design artifacts before any implementation begins. Use at the start of a feature, before writing code.
Thorough, research-grounded code review of a change, PR, or MR — multi-lens (correctness, security, simplification, tests), severity-ranked with impact + fix, configurable depth, optional PR comments. Use when asked to review code, "do a code review", "review this PR/MR", "review my changes/diff/branch", or audit a changeset before merge.
Use when the user asks to research, investigate, analyze, find out, explore, examine, audit, or evaluate something — structured multi-source research with consulting, library-doc search, web search, and guided output delivery.
Multi-agent code review AND remediation — dispatches correctness, security, and simplification reviewers in parallel, consolidates findings, then fixes criticals/highs. Use when reviewing a diff or PR before shipping.
Basé sur la classification professionnelle SOC
| name | conjure |
| description | Structured design dialogue with a visual companion — produces an approved spec and design artifacts before any implementation begins. Use at the start of a feature, before writing code. |
Read ../../references/codex-adapter.md, then read ../../../skills/conjure/SKILL.md and follow the source skill through that Codex adapter. Keep the source skill's gates, safety checks, and completion criteria.
For visual modes, apply the adapter's "Magician Visual Companion in Codex" section exactly: use Magician's built-in local companion as the primary design surface, open it with Codex Browser Use, and keep Figma or Build Web Apps optional unless the user explicitly asks for them.
v3.8.0 — two-way design studio: designs use the two-tier token system (design-tokens.md) so light/dark are ONE design and each run varies; GATE 3 asks target viewports. The browser streams clicks/selections + optional (opt-in) companion-chat to state/events.jsonl (read by cursor via the events.json endpoint); reply via state/outbox.jsonl. Use Browser Use for the pull path (read the live selection).
