vibe-cross-platform

Cross-platform development rules for Mistral Vibe. Use when writing platform-specific logic, handling paths, Windows support, shell compatibility, terminal data streams, or cross-OS testing strategies.

Jump to install

Repository: mistralai/mistral-vibe
Last source activity: August 20, 2026 at 17:38
Detected SKILL.md language: English
Stars: 4,895
Forks: 681

Install options

The review-first prompt is selected by default. You can switch to a direct command or download a local copy.

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

A direct command skips the review prompt. Inspect the source before running it.

npx skills add https://github.com/mistralai/mistral-vibe --skill vibe-cross-platform

The command stays on one line. Scroll horizontally to inspect it before copying.

Prefer a local copy? Download the files currently available to SkillsMP.

Review the source files

Read SKILL.md and any companion files shown by SkillsMP before deciding whether to install.

SKILL.md

Source instructions · Read-only preview

Back to search Back to installation

write-vibe-adr

Create or update Architecture Decision Records for the Mistral Vibe Python CLI. Use when a design discussion creates a new architectural constraint, when an undocumented convention causes confusion or review feedback, or when architecture guidance in docs/adr or AGENTS.md must be changed.

2026-08-27

write-vibe-design-doc

Create or update implementation-ready design proposals for Mistral Vibe under docs/design, including a bounded design-tree decision review before drafting. Use before implementing a substantial Vibe feature, migration, protocol or API change, runtime or persistence change, cross-component workflow, compatibility plan, or other work whose ownership, behavior, failure semantics, rollout, and validation need review.

2026-08-27

vibe-async

Async and concurrency patterns for Mistral Vibe. Use when working with asyncio, the agent loop, Textual TUI threading, HTTP clients, streaming surfaces, or core-to-TUI communication.

2026-08-20

View all from this repository

Vibe Cross-Platform

Vibe ships on Linux, macOS, and Windows, but CI runs the test suite on Linux only. The machine you develop on is not the machine that gates the PR — code and tests must pass on every platform, and must be provably correct on the platforms CI cannot exercise.

Code rules

Never rely on host-specific behavior (shell, path separator, line ending, available binaries, $SHELL, case sensitivity). Assume the same code runs under cmd.exe, Git Bash, zsh, and sh.

Branch platform-specific logic behind the helpers in vibe.core.utils.platform (is_windows(), resolve_windows_shell()), not ad-hoc sys.platform checks. Keep POSIX-only assumptions (forward slashes, POSIX shlex escaping, $SHELL) out of shared paths and scope Windows-only handling to is_windows().

Use pathlib.Path for path composition; never hardcode / or \\.

Terminal data

Treat terminal and PTY data as arbitrarily chunked streams: normalize CRLF before interpreting lone \r as an in-place redraw, buffer incomplete control sequences until their terminator arrives, and add Linux-runnable regression tests covering CRLF plus every split boundary of representative control sequences.

Testing

Test other-platform code paths on Linux by monkeypatching sys.platform, env vars, and probes like shutil.which — do not @pytest.mark.skipif them away. A Windows-only behavior with no Linux-runnable test is untested in CI.

When an assertion depends on the platform, force it explicitly (e.g. monkeypatch.setattr(module, "is_windows", lambda: True)) instead of letting the test pass only because of the host it happened to run on. A test that would flip its result on a different OS is a bug.