create-vibe-feature
Add or modify a feature in the Mistral Vibe Python CLI while following the app architecture ADRs. Use when working in vibe/core, vibe/cli, vibe/acp, vibe/setup, built-in tools, config, sessions, skills, hooks, MCP, connectors, or other Vibe feature code.
Оригинален текст · няма потвърден превод на българскиПърво прочетете инструкцията.
Файлът се зарежда от посочения източник само по ваше действие. Можете да го прочетете тук, да го копирате или да го запазите като .md.
GitHub хранилище- Звезди на репото
- 4986
- Лиценз
- Apache-2.0
- Последна проверка на записа
- 21.09.2026 г.
Добавете в своя инструмент.
Командата отваря избора на skills от репозитория. Прочетете файла и условията на автора преди изпълнение.
npx skills add mistralai/mistral-vibeСтраницата копира текст. Не инсталира и не изпълнява нищо на устройството ви.
Откъс от SKILL.md
Началото на файла на автора, без превод.
Create Vibe Feature
Use this skill when implementing Vibe feature work. Keep changes scoped, architecture-aware, and consistent with nearby code.
App Areas
| Area | Role | Path |
|---|---|---|
| Core engine | Agent loop, domain events, tools, LLM backends, config, sessions, skills, hooks, telemetry types, shared models | vibe/core/ |
| App server | Session, turn, config and persistence, tools, and callback ownership; typed JSON-RPC methods and notifications consumed by both TUIs and ACP | vibe/app_server/ |
| Textual CLI | Legacy Python TUI, still the production default: interactive terminal UX, widgets, slash commands, manual shell commands, voice UI, local user affordances | vibe/cli/ |
| Rust CLI | Ratatui TUI replacing the Textual CLI; thin client over vibe-app-server | vibe/cli-rust/ |
| ACP bridge | Agent Client Protocol session, tool, terminal, title, and content translation | vibe/acp/ |
| Setup | First-run, auth, onboarding, trusted folders, update prompts | vibe/setup/ |
| Tests | Unit, integration, e2e, Textual snapshots, stubs and fixtures | tests/ |
Architecture Routing
Before implementation, read the matching ADRs:
- Architecture principles, module boundaries, startup/runtime speed, simple changes:
docs/adr/0001-architecture-principles.md - Core engine vs delivery surfaces:
docs/adr/0002-core-engine-and-delivery-surfaces.md - Agent loop orchestration, streaming, events, cancellation, responsiveness:
docs/adr/0003-event-driven-agent-loop.md - Tool contracts, permissions, output, UI metadata, adapters:
docs/adr/0004-typed-permissioned-tools.md - Config models, layering, defaults, migrations, reloads:
docs/adr/0005-layered-configuration.md - Session logging, resume, rewind, transcript metadata, migrations:
docs/adr/0006-local-sessions.md - Skills, agents, subagents, hooks, MCP, connectors, custom tools, discovery:
docs/adr/0007-extension-mechanisms.md - Feature work, telemetry events, analytics properties, instrumentation verification:
docs/adr/0008-feature-instrumentation.md - App-server RPCs, notifications, and delivery adapters:
docs/adr/0009-app-server-boundary.md - Rust CLI thin-client boundary, unidirectional state, bounded resources:
docs/adr/0016-rust-cli-delivery-surface.md
If a change fits the current code but conflicts with ADR direction, flag it to the user before implementing.