[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7AZR8NPPAHVP4EVJG8H07SF":3,"skill-same:01M7AZR8NPPAHVP4EVJG8H07SF":49},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":28,"commitSha":29,"skillDirectory":30,"forksCount":14,"repositoryHtmlUrl":31,"repositoryHomepageUrl":6,"ownerHtmlUrl":32,"ownerBlogUrl":6,"ownerDescription":33,"updatedAt":34,"install":35,"resources":48},"01M7AZR8NPPAHVP4EVJG8H07SF","write-vibe-adr",null,"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\u002Fadr or AGENTS.md must be changed.","Mr-Shine09\u002FZephyr","Mr-Shine09","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F203695007?v=4","01M7AZPSSR44CHX8AQ7WKA37B9","Oak Soe Khant","01M7AZPSTCHZF7XBHVFSNSP7CB",0,"Apache-2.0","https:\u002F\u002Fgithub.com\u002FMr-Shine09\u002FZephyr\u002Fblob\u002Fcompanion\u002F.vibe\u002Fskills\u002Fwrite-vibe-adr\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: write-vibe-adr\ndescription: 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\u002Fadr or AGENTS.md must be changed.\nmetadata:\n  display-name: Write Vibe ADR\n  short-description: Create architecture ADRs for Vibe\n  default-prompt: Use $write-vibe-adr to document a Vibe architecture decision and register it for agents.\n---\n\n# Write Vibe ADR\n\nVibe ADRs are concise, agent-facing architecture rules in `docs\u002Fadr\u002F`. Writing an ADR is a two-step process: write the document, then register it in the Architecture Decisions table in `AGENTS.md`.\n\n## When To Create An ADR\n\n- A design discussion creates a new architecture rule, constraint, or direction.\n- An existing convention is undocumented and caused a bug, review comment, or repeated confusion.\n- A pattern applies across a Vibe area or boundary, not just one file.\n- Future work should follow a direction that may differ from the current architecture.\n\nDo not create ADRs for one-off implementation choices, formatting rules, or behavior already enforced by linting.\n\n## Steps\n\n### 1. Confirm the scope\n\nUse one ADR when the decision is cohesive. Split ADRs when separate agents would need to read them for unrelated change areas.\n\nExisting ADR topics:\n\n- `0001` - architecture principles\n- `0002` - core engine and delivery surfaces\n- `0003` - event-driven agent loop\n- `0004` - typed permissioned tools\n- `0005` - layered configuration\n- `0006` - local sessions\n- `0007` - extension mechanisms\n- `0008` - feature instrumentation\n\n### 2. Determine the next number\n\n```bash\nls docs\u002Fadr\u002F\n```\n\nUse the next sequential number, zero-padded to 4 digits: `0009-my-decision.md`.\n\n### 3. Write the ADR\n\nUse this format:\n\n```markdown\n# 0009 Decision Title\n\n## Decision\n\nWhat we decided. Include concrete rules and current-vs-aspirational direction when relevant.\n\n## Rationale\n\nWhy this decision exists. Name the ambiguity, pressure, or tradeoff.\n\n## Agent Guidance\n\n- Concrete instructions an agent should follow while changing code.\n- Keep guidance task-oriented and easy to scan.\n\n## Flag To User When\n\n- Situations where an agent must stop and ask because current code or user request conflicts with the ADR direction.\n```\n\nKeep ADRs concise. Match the existing 20-50 line style. Do not add a status field.\n\n### 4. Register in AGENTS.md\n\nAdd or update a row in the Architecture Decisions table:\n\n```markdown\n| \u003Ctask trigger> | [0009 Decision Title](docs\u002Fadr\u002F0009-my-decision.md) |\n```\n\nThe trigger text must describe what the agent is changing, not vague architecture language.\n\nGood triggers:\n\n- \"Adding a new delivery surface, protocol bridge, or UI-owned behavior\"\n- \"Changing tool args\u002Fresults, permissions, output limits, or adapters\"\n- \"Changing session transcript shape, metadata, resume, rewind, or migrations\"\n\nBad triggers:\n\n- \"Working on architecture\"\n- \"When relevant\"\n- \"Making decisions\"\n\nIf the ADR is not registered in `AGENTS.md`, agents will not reliably discover it.\n\n## Common Mistakes\n\n| Mistake | Fix |\n| --- | --- |\n| Writing the ADR but not updating `AGENTS.md` | Always do both. |\n| Using vague trigger text | Name concrete code-change scenarios. |\n| Duplicating another ADR | Reference or update the existing ADR instead. |\n| Writing a human essay | Keep it short, directive, and agent-facing. |\n| Adding status fields | Vibe ADRs intentionally mix current and aspirational decisions without status. |\n","# Write Vibe ADR\n\nVibe ADRs are concise, agent-facing architecture rules in `docs\u002Fadr\u002F`. Writing an ADR is a two-step process: write the document, then register it in the Architecture Decisions table in `AGENTS.md`.\n\n## When To Create An ADR\n\n- A design discussion creates a new architecture rule, constraint, or direction.\n- An existing convention is undocumented and caused a bug, review comment, or repeated confusion.\n- A pattern applies across a Vibe area or boundary, not just one file.\n- Future work should follow a direction that may differ from the current architecture.\n\nDo not create ADRs for one-off implementation choices, formatting rules, or behavior already enforced by linting.\n\n## Steps\n\n### 1. Confirm the scope\n\nUse one ADR when the decision is cohesive. Split ADRs when separate agents would need to read them for unrelated change areas.\n\nExisting ADR topics:\n\n- `0001` - architecture principles\n- `0002` - core engine and delivery surfaces\n- `0003` - event-driven agent loop\n- `0004` - typed permissioned tools\n- `0005` - layered configuration\n- `0006` - local sessions\n- `0007` - extension mechanisms\n- `0008` - feature instrumentation\n\n### 2. Determine the next number\n\n```bash\nls docs\u002Fadr\u002F\n```\n\nUse the next sequential number, zero-padded to 4 digits: `0009-my-decision.md`.\n\n### 3. Write the ADR\n\nUse this format:\n\n```markdown\n# 0009 Decision Title\n\n## Decision\n\nWhat we decided. Include concrete rules and current-vs-aspirational direction when relevant.\n\n## Rationale\n\nWhy this decision exists. Name the ambiguity, pressure, or tradeoff.\n\n## Agent Guidance\n\n- Concrete instructions an agent should follow while changing code.\n- Keep guidance task-oriented and easy to scan.\n\n## Flag To User When\n\n- Situations where an agent must stop and ask because current code or user request conflicts with the ADR direction.\n```\n\nKeep ADRs concise. Match the existing 20-50 line style. Do not add a status field.\n\n### 4. Register in AGENTS.md\n\nAdd or update a row in the Architecture Decisions table:\n\n```markdown\n| \u003Ctask trigger> | [0009 Decision Title](docs\u002Fadr\u002F0009-my-decision.md) |\n```\n\nThe trigger text must describe what the agent is changing, not vague architecture language.\n\nGood triggers:\n\n- \"Adding a new delivery surface, protocol bridge, or UI-owned behavior\"\n- \"Changing tool args\u002Fresults, permissions, output limits, or adapters\"\n- \"Changing session transcript shape, metadata, resume, rewind, or migrations\"\n\nBad triggers:\n\n- \"Working on architecture\"\n- \"When relevant\"\n- \"Making decisions\"\n\nIf the ADR is not registered in `AGENTS.md`, agents will not reliably discover it.\n\n## Common Mistakes\n\n| Mistake | Fix |\n| --- | --- |\n| Writing the ADR but not updating `AGENTS.md` | Always do both. |\n| Using vague trigger text | Name concrete code-change scenarios. |\n| Duplicating another ADR | Reference or update the existing ADR instead. |\n| Writing a human essay | Keep it short, directive, and agent-facing. |\n| Adding status fields | Vibe ADRs intentionally mix current and aspirational decisions without status. |\n",{"name":5,"metadata":24,"description":7},{"display-name":25,"default-prompt":26,"short-description":27},"Write Vibe ADR","Use $write-vibe-adr to document a Vibe architecture decision and register it for agents.","Create architecture ADRs for Vibe","companion","de27bf496077835506f1e45c5210c2b3aef5622f",".vibe\u002Fskills\u002Fwrite-vibe-adr","https:\u002F\u002Fgithub.com\u002FMr-Shine09\u002FZephyr","https:\u002F\u002Fgithub.com\u002FMr-Shine09","Computer Engineering Student @ De Anza College | Embedded Systems, IoT & Software | Built an Infineon-Sponsored Assistive Device | Open to Internships","2026-08-23 08:52:57",{"source":8,"skillName":5,"commands":36,"prompt":46,"zipAvailable":47},[37,40,43],{"tool":38,"command":39},"npx","npx skills add Mr-Shine09\u002FZephyr --skill write-vibe-adr",{"tool":41,"command":42},"bunx","bunx skills add Mr-Shine09\u002FZephyr --skill write-vibe-adr",{"tool":44,"command":45},"pnpm","pnpm dlx skills add Mr-Shine09\u002FZephyr --skill write-vibe-adr","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FMr-Shine09\u002FZephyr\u002Fblob\u002Fcompanion\u002F.vibe\u002Fskills\u002Fwrite-vibe-adr\u002FSKILL.md",true,[],[50,56,63,70,77,84],{"skillNo":51,"name":52,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":53,"categories":54,"keywords":55,"publishedAt":19},"01M7AZRGQ6MPY5YSW2Q5AQ4SG5","prompts","https:\u002F\u002Fgithub.com\u002FMr-Shine09\u002FZephyr\u002Fblob\u002Fcompanion\u002Fvibe\u002Fcore\u002Ftools\u002Fbuiltins\u002Fprompts\u002Fskill.md",[],[],{"skillNo":57,"name":58,"nameZh":6,"description":59,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":60,"categories":61,"keywords":62,"publishedAt":19},"01M7AZRCBR2K5DR24TJBKVF9W0","write-vibe-tests","Write or refactor Mistral Vibe tests with proper decoupling. Use when adding behavior coverage, testing ports\u002Fadapters, replacing brittle mocks, creating fakes, adding characterization tests before refactors, or changing tests under tests\u002F for vibe\u002Fcore, vibe\u002Fcli, vibe\u002Facp, tools, config, sessions, skills, hooks, MCP, or setup.","https:\u002F\u002Fgithub.com\u002FMr-Shine09\u002FZephyr\u002Fblob\u002Fcompanion\u002F.vibe\u002Fskills\u002Fwrite-vibe-tests\u002FSKILL.md",[],[],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":19},"01M7AZR33WNNYXT1P8AK6NDAWS","instrument-feature-analytics","Plan analytics instrumentation for a feature. Use when implementing any feature — every feature must ship with telemetry. Decides which events and properties the metrics need (funnels, adoption, status flows), checks compatibility with the existing datalake and event registry, and walks through local, staging, and production verification.","https:\u002F\u002Fgithub.com\u002FMr-Shine09\u002FZephyr\u002Fblob\u002Fcompanion\u002F.vibe\u002Fskills\u002Finstrument-feature-analytics\u002FSKILL.md",[],[],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":19},"01M7AZQZJBG6FH0RP5QR9RAWP9","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\u002Fcore, vibe\u002Fcli, vibe\u002Facp, vibe\u002Fsetup, built-in tools, config, sessions, skills, hooks, MCP, connectors, or other Vibe feature code.","https:\u002F\u002Fgithub.com\u002FMr-Shine09\u002FZephyr\u002Fblob\u002Fcompanion\u002F.vibe\u002Fskills\u002Fcreate-vibe-feature\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":19},"01M7AZQWCSN5MYHFEKHVXYCW7X","vibe-textual-ui","Textual TUI widget and TCSS conventions for Mistral Vibe. Use when building or styling Textual widgets, writing TCSS rules, working with selectable lists, tool headers, theme variables, or UI component layout.","https:\u002F\u002Fgithub.com\u002FMr-Shine09\u002FZephyr\u002Fblob\u002Fcompanion\u002F.agents\u002Fskills\u002Fvibe-textual-ui\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":19},"01M7AZQS4BMMM8PY2E89GQCJPJ","vibe-python-style","Python coding conventions for Mistral Vibe. Use when writing, reviewing, or refactoring Python code in the Vibe codebase. Covers style, type hints, imports, Pydantic patterns, logging, error handling, and file I\u002FO.","https:\u002F\u002Fgithub.com\u002FMr-Shine09\u002FZephyr\u002Fblob\u002Fcompanion\u002F.agents\u002Fskills\u002Fvibe-python-style\u002FSKILL.md",[],[]]