# Platform Adapters

Use these invocation patterns when guiding users across platforms.

## Codex

Preferred:

```text
$da-vinci <request>
```

Mode examples:

```text
$da-vinci use greenfield-spec to break down a new SaaS project
$da-vinci use greenfield-brainstorm to synthesize product ideas into pages and specs
$da-vinci use redesign-from-code to inventory the current app and redesign the UI
$da-vinci use feature-change to add a new billing page and generate Pencil-backed tasks
```

Use this for:

- requirement breakdown
- Pencil page generation planning
- design-to-code implementation

If explicit routes are added later, treat them as routing helpers, not the only entrypoint.

## Claude

Preferred:

```text
/da-vinci <request>
```

Use the same workflow stages as Codex:

- requirement
- design
- tasks
- implementation
- verification

## Gemini

Preferred:

```text
/da-vinci <request>
```

Keep the same artifact names and checkpoint names across platforms.

## Cross-Platform Rule

Keep these stable:

- artifact names
- checkpoint names
- drift policy
- requirement/design/code contract
- mode names

Platform adapters may differ in command syntax, but not in workflow semantics.