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.

Ir a la instalación

Repositorio: mistralai/mistral-vibe
Última actividad en el origen: 20 de agosto de 2026 a las 17:38
Idioma detectado de SKILL.md: inglés
Estrellas: 4895
Forks: 681

Opciones de instalación

De forma predeterminada está seleccionado el prompt que primero revisa el origen. Puedes cambiar a un comando directo o descargar una copia local.

Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.

Un comando directo omite el prompt de revisión. Revisa el origen antes de ejecutarlo.

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

El comando permanece en una sola línea. Desplázate horizontalmente para revisarlo antes de copiarlo.

¿Prefieres una copia local? Descarga los archivos que SkillsMP tiene disponibles ahora.

Revisa los archivos de origen

Lee SKILL.md y los archivos complementarios que muestra SkillsMP antes de decidir si quieres instalarlo.

SKILL.md

Instrucciones de origen · Vista previa de solo lectura

Volver a la búsqueda Volver a la instalación

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

Ver todos los de este repositorio

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.