Architect Build Specs
jsmastery-pro/skills
Runs a structured design conversation on a feature, tech stack or enhancement, recommends an answer and records it as a build spec in docs/specs.
Guides feature work in the Mistral Vibe Python CLI so each change lands in the right module and matches the project's architecture decision records.
Install Create Vibe Feature
$ npx skills add mistralai/mistral-vibe --skill create-vibe-feature -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install mistralai/mistral-vibe create-vibe-feature --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/mistralai/mistral-vibe.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.vibe/skills/create-vibe-feature .claude/skills/create-vibe-feature && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "create-vibe-feature" agent skill from https://github.com/mistralai/mistral-vibe/tree/main/.vibe/skills/create-vibe-feature into .claude/skills/create-vibe-feature/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "create-vibe-feature", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/mistralai/mistral-vibe/tree/main/.vibe/skills/create-vibe-featureType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add mistralai/mistral-vibe --skill create-vibe-feature -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install mistralai/mistral-vibe create-vibe-feature --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mistralai/mistral-vibe.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.vibe/skills/create-vibe-feature .agents/skills/create-vibe-feature && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "create-vibe-feature" agent skill from https://github.com/mistralai/mistral-vibe/tree/main/.vibe/skills/create-vibe-feature into .agents/skills/create-vibe-feature/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "create-vibe-feature", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add mistralai/mistral-vibe --skill create-vibe-feature -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install mistralai/mistral-vibe create-vibe-feature --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mistralai/mistral-vibe.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.vibe/skills/create-vibe-feature .cursor/skills/create-vibe-feature && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "create-vibe-feature" agent skill from https://github.com/mistralai/mistral-vibe/tree/main/.vibe/skills/create-vibe-feature into .cursor/skills/create-vibe-feature/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "create-vibe-feature", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/mistralai/mistral-vibe.git --path .vibe/skills/create-vibe-feature--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add mistralai/mistral-vibe --skill create-vibe-feature -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install mistralai/mistral-vibe create-vibe-feature --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mistralai/mistral-vibe.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.vibe/skills/create-vibe-feature .gemini/skills/create-vibe-feature && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "create-vibe-feature" agent skill from https://github.com/mistralai/mistral-vibe/tree/main/.vibe/skills/create-vibe-feature into .gemini/skills/create-vibe-feature/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "create-vibe-feature", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install mistralai/mistral-vibe create-vibe-featureInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add mistralai/mistral-vibe --skill create-vibe-feature -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/mistralai/mistral-vibe.git skills-src && mkdir -p .github/skills && cp -r skills-src/.vibe/skills/create-vibe-feature .github/skills/create-vibe-feature && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "create-vibe-feature" agent skill from https://github.com/mistralai/mistral-vibe/tree/main/.vibe/skills/create-vibe-feature into .github/skills/create-vibe-feature/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "create-vibe-feature", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add mistralai/mistral-vibe --skill create-vibe-feature -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install mistralai/mistral-vibe create-vibe-feature --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mistralai/mistral-vibe.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.vibe/skills/create-vibe-feature .opencode/skills/create-vibe-feature && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "create-vibe-feature" agent skill from https://github.com/mistralai/mistral-vibe/tree/main/.vibe/skills/create-vibe-feature into .opencode/skills/create-vibe-feature/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "create-vibe-feature", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
create-vibe-feature- GitHub stars
- 5.1k
- Token cost
- ~1.2k tokens
- SKILL.md length
- 471 words
- Files
- 1
- Skills in repo
- 14
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Guides feature work in the Mistral Vibe Python CLI so each change lands in the right module and matches the project's architecture decision records.
- Works in 7 steps: Read README.md, AGENTS.md, and the… → Identify the owning area. Keep UI… → Study one or two existing features with… → …
- Adding a built-in tool or config option to the Vibe core
- SKILL.md covers App Areas, Architecture Routing, Workflow and Tools, plus 2 more sections
- Calls uv
What it does
The skill gives the agent a map of the Vibe codebase: the core engine in vibe/core (agent loop, events, tools, LLM backends, config, sessions, skills, hooks), the Textual CLI in vibe/cli, the ACP bridge in vibe/acp, first-run setup in vibe/setup, and tests under tests. UI behavior stays in the CLI, protocol translation in the ACP bridge, and reusable engine behavior in the core.
Before implementing, the agent reads the matching architecture decision records, which cover architecture principles, core engine versus delivery surfaces, the event-driven agent loop, typed permissioned tools, layered configuration, local sessions, extension mechanisms and feature instrumentation. If a change fits the current code but runs against an ADR, it flags that to you first. The workflow then reads the README, AGENTS.md and nearby source, studies one or two similar features, and prefers a small change in the owning module, adding an abstraction only where it protects a real boundary. The excerpt is cut off after that.
When your agent uses it
- Adding a built-in tool or config option to the Vibe core
- Changing the Textual CLI, its slash commands or widgets
- Working on session, skill, hook, MCP or connector code in Vibe
- Checking a proposed change against the project's ADRs
Example prompts
- “Add a new built-in tool to Vibe and follow the typed tools ADR.”
- “Add a slash command to the Textual CLI that shows the current session id.”
- “Does my change to the config loader fit the layered configuration ADR?”
Requirements
- A checkout of the mistral-vibe repository
Workflow steps
7 steps, taken from the first numbered list in SKILL.md.
- Read README.md, AGENTS.md, and the nearest relevant source files before editing.
- Identify the owning area. Keep UI behavior in vibe/cli, ACP translation in vibe/acp, setup flow in vibe/setup, and reusable engine…
- Study one or two existing features with the same shape before adding new files. Match naming, model placement, port/adapters, tests, and…
- Prefer a small change in the owning module. Add a port or abstraction only when it protects a meaningful boundary or makes…
- For feature work, plan telemetry with instrument-feature-analytics before writing tracking code.
- Keep startup and interactive latency in mind. Avoid eager imports, broad scans, and network or subprocess work unless the configured…
- Update docs or built-in skill guidance when the feature changes user-visible CLI behavior, config, commands, agents, persistence, or…
What it can do on your machine
Read from SKILL.md and the folder at commit 7cb9189. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
uv
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use uv, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Create Vibe Feature loads about 1.2k tokens when it runs. Until then it costs about 69 tokens; SKILL.md has 471 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from mistralai/mistral-vibe at commit 7cb9189, republished under its Apache-2.0 licence (© mistralai). 471 words, ~1,154 tokens.
Download SKILL.mdSave it as
.claude/skills/create-vibe-feature/SKILL.md (or your agent's skills folder).- name
- create-vibe-feature
- description
- 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.
- metadata.display-name
- Create Vibe Feature
- metadata.short-description
- Guide Mistral Vibe feature work
- metadata.default-prompt
- Use $create-vibe-feature to implement a Mistral Vibe feature in line with the app architecture.
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/ |
| Textual CLI | Interactive terminal UX, widgets, slash commands, manual shell commands, voice UI, local user affordances | vibe/cli/ |
| 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
If a change fits the current code but conflicts with ADR direction, flag it to the user before implementing.
Workflow
- Read
README.md,AGENTS.md, and the nearest relevant source files before editing. - Identify the owning area. Keep UI behavior in
vibe/cli, ACP translation invibe/acp, setup flow invibe/setup, and reusable engine behavior invibe/core. - Study one or two existing features with the same shape before adding new files. Match naming, model placement, port/adapters, tests, and error patterns.
- Prefer a small change in the owning module. Add a port or abstraction only when it protects a meaningful boundary or makes replacement/testing easier.
- For feature work, plan telemetry with
instrument-feature-analyticsbefore writing tracking code. - Keep startup and interactive latency in mind. Avoid eager imports, broad scans, and network or subprocess work unless the configured feature needs them.
- Update docs or built-in skill guidance when the feature changes user-visible CLI behavior, config, commands, agents, persistence, or discovery.
Show full SKILL.md (145 more words)Show less
Tools
When adding or modifying a tool:
- Subclass
BaseToolfromvibe/core/tools/base.pywith a Pydantic args model and aBaseToolConfiggeneric parameter. - Implement
async def run(args, ctx: InvokeContext)and yield events progressively. - Raise
ToolErrorfor user-facing failures; raiseToolPermissionErrorfor authorization failures. - Declare permission with
ToolPermission(ALWAYS/ASK/NEVER); honor it consistently.
Consistency Checks
- Core code should not import Textual, ACP schemas, setup UI, or other delivery-surface details.
- Surface code should adapt core events/models instead of reaching into private core state.
- External data should enter through Pydantic validation, typed events, tool args/results, config models, or explicit ports.
- Tools should follow
BaseToolwith typed args, result, config, state, and permission behavior. - Tests should mirror the source layout and use existing fixtures or
tests/stubs/Fake*doubles.
Verification
After Python changes, run:
uv run ruff format .
uv run ruff check --fix .For behavior changes, run the narrowest relevant tests first, then broader checks if the change touches shared contracts:
uv run pytest <path-or-test>
uv run pyright© mistralai, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in .vibe/skills/create-vibe-feature of mistralai/mistral-vibe.
Open the folder on GitHubat commit 7cb9189
Compare with similar skills
Create Vibe Feature next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Create Vibe Feature this skillmistralai/mistral-vibe | 5.1k | — | ~1.2k | Automated safety check: Pass | Apache-2.0 | |
| Architect Build Specsjsmastery-pro/skills | 1.5k | — | ~7k | Automated safety check: Notes | MIT | |
| Senior Architect Toolkitmaslennikov-ig/claude-code-orchestrator-kit | 260 | 8 repos | ~1.2k | Automated safety check: Notes | Custom licence | |
| Code Review Skillawesome-skills/code-review-skill | 2.1k | — | ~2.8k | Automated safety check: Notes | MIT | |
| Code Graph Mermaid Diagramstrailofbits/skills | 7.4k | — | ~1.7k | Automated safety check: Pass | CC-BY-SA-4.0 | |
| Design Doc MermaidSpillwaveSolutions/design-doc-mermaid | 176 | 1 repos | ~5.6k | Automated safety check: Pass | None |
Similar skills
Senior Architect Toolkit
maslennikov-ig/claude-code-orchestrator-kit
Comprehensive software architecture skill for designing scalable, maintainable systems using ReactJS, NextJS, NodeJS, Express, React Native, Swift, Kotlin…
Code Review Skill
awesome-skills/code-review-skill
Provides comprehensive code review guidance for React 19, Vue 3, Angular 17+, Svelte 5, Rust, TypeScript, Java, Java 8, PHP, Ruby, Rails, Python, Django, FastAPI, Go, C/.NET, Kotlin, Swift, Dart…
- Official
Code Graph Mermaid Diagrams
trailofbits/skills
Generates Mermaid diagrams from Trailmark code graphs, including call graphs, class hierarchies, module dependency maps, complexity heatmaps and attack surface data flows.
Design Doc Mermaid
SpillwaveSolutions/design-doc-mermaid
Create Mermaid diagrams (flowchart, sequence, class, ER, state, C4, architecture) from text or source code.
Plan Preview
u-ichi/reviewable-html-workbench
Plan Mode の <proposedplan を出す直前に、計画の段階・依存関係・検証観点を一時HTMLで視覚確認したい時に使う agent-internal skill。Use this agent-internal skill to create a temporary HTML preview for a plan just before presenting…
More from mistralai/mistral-vibe
All 14 skills in this repo- Official
Mistral Vibe Plugin Creator
mistralai/mistral-vibe
Shows how to build a Vibe plugin package in the Agent Plugins 1.0 format, with a plugin.json manifest and optional skills, MCP servers, hooks and other components.
- Official
Feature Analytics Instrumentation Planner
mistralai/mistral-vibe
Plans which analytics events and properties a new feature needs, checks them against the existing event registry, and verifies them per environment.
- Official
Vibe Worktree Manager
mistralai/mistral-vibe
Creates, reuses and cleans up git worktrees under a shared vibe home directory, with per-repo buckets, claim records and dirty-state checks before removal.
- Official
Write Vibe ADR
mistralai/mistral-vibe
Creates or updates concise Architecture Decision Records for the Mistral Vibe CLI and registers each one in the AGENTS.md decisions table.
- Official
Write Vibe Tests
mistralai/mistral-vibe
Guides writing or refactoring tests for the Mistral Vibe CLI agent so they check behavior through stable boundaries, like tool invocation or saved session shape, instead of internal calls.
- Official
Mistral Vibe CLI Reference
mistralai/mistral-vibe
Reference for Mistral Vibe, the CLI agent it runs inside: config files, env vars, agents, skills, tools, hooks and MCP servers, so the agent can explain and troubleshoot its own setup.
Related
Works with
Categories
Questions about Create Vibe Feature
What does Create Vibe Feature do?
Guides feature work in the Mistral Vibe Python CLI so each change lands in the right module and matches the project's architecture decision records. The skill gives the agent a map of the Vibe codebase: the core engine in vibe/core (agent loop, events, tools, LLM backends, config, sessions, skills, hooks), the Textual CLI in vibe/cli, the ACP bridge in vibe/acp, first-run setup in vibe/setup, and tests under tests. UI behavior stays in the CLI, protocol translation in the ACP bridge, and reusable engine behavior in the core.
When should I use Create Vibe Feature?
Create Vibe Feature fits situations like: adding a built-in tool or config option to the Vibe core; changing the Textual CLI, its slash commands or widgets; working on session, skill, hook, MCP or connector code in Vibe; checking a proposed change against the project's ADRs.
How do I install Create Vibe Feature in Claude Code?
Run `npx skills add mistralai/mistral-vibe --skill create-vibe-feature -a claude-code`. Or copy the skill folder (.vibe/skills/create-vibe-feature in mistralai/mistral-vibe) into .claude/skills/create-vibe-feature in your project. Claude Code loads it when a task matches its description.
How do I install Create Vibe Feature in Codex?
Run `npx skills add mistralai/mistral-vibe --skill create-vibe-feature -a codex`. Or copy the skill folder (.vibe/skills/create-vibe-feature in mistralai/mistral-vibe) into .agents/skills/create-vibe-feature in your project. Codex loads it when a task matches its description.
Can I use Create Vibe Feature in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add mistralai/mistral-vibe --skill create-vibe-feature -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/create-vibe-feature, .gemini/skills/create-vibe-feature, .github/skills/create-vibe-feature and .opencode/skills/create-vibe-feature in your project.
What does Create Vibe Feature need to run?
Going by SKILL.md and its folder, Create Vibe Feature needs the command-line tools its instructions call (uv). Our summary lists: A checkout of the mistral-vibe repository.
Does Create Vibe Feature access the network?
SKILL.md contains no URLs. Its commands use uv, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Create Vibe Feature safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Create Vibe Feature use?
Create Vibe Feature is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Create Vibe Feature use?
About 1.2k tokens (SKILL.md is roughly 4.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Create Vibe Feature?
Skills that share tags, products or a category with Create Vibe Feature: Architect Build Specs (jsmastery-pro/skills, 1.5k stars), Senior Architect Toolkit (maslennikov-ig/claude-code-orchestrator-kit, 260 stars), Code Review Skill (awesome-skills/code-review-skill, 2.1k stars) and Code Graph Mermaid Diagrams (trailofbits/skills, 7.4k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Create Vibe Feature?
mistralai (a GitHub organization, an official publisher) maintains it in mistralai/mistral-vibe, which has 5,085 GitHub stars. The repository holds 14 skills in this directory. The repository was last updated on October 7, 2026.
Source: mistralai/mistral-vibe on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.