bitrix24-vibecode — скилл

---
name: bitrix24-vibecode
description: Use when working with VibeCode Bitrix24 apps, integrations, bots, or AI Router workflows.
---

# VibeCode Docs

## Overview

Use this skill to route through VibeCode docs quickly, keep platform invariants straight, and avoid re-deriving basics.

## Workflow

1. Identify the task type before reading docs in depth.
2. Load [references/section-routing.md](references/section-routing.md) and open only the most relevant section first.
3. Load [references/universal-knowledge.md](references/universal-knowledge.md) only when the task touches build, deploy, auth, API conventions, scaling, or error handling.
4. Load [references/anti-footguns.md](references/anti-footguns.md) only before implementation or debugging.
5. Confirm endpoint-level details from the live docs only when the answer depends on exact parameter names, current limits, or current behavior.
6. Distinguish VibeCode platform behavior from native Bitrix24 behavior.

## Load Minimally

- For explanation-only questions, start with `section-routing` and stop unless the answer needs platform invariants.
- For implementation or debugging, read `universal-knowledge` before writing code.
- For exact request shapes or current behavior, verify against the live docs instead of relying on memory.

## Task Patterns

### App, Bot, Or Integration Build

Use quick start plus the target domain section. Default flow:

1. Inspect capabilities with `/v1/me`
2. Build against Entity API or another target API
3. Create infrastructure if deployment is needed
4. Deploy and wait for `running` plus `CONNECTED`

### Auth And Access Questions

Open keys/auth first. Decide from the key prefix whether the task is personal (`vibe_api_`), OAuth app (`vibe_app_`), or management (`vibe_live_`). For OAuth app requests, remember that a bearer session token may also be required for user-context calls.