v5 · kinopeee, windsurf — правило для Claude Code: что делает и как установить
Правило v5 задаёт регламент написания кода: делит задачи на лёгкие, стандартные и критические, запрещает длинные предисловия и регулирует вызов инструментов.
MIT ★ 359 обновлён 2025-12-01
.claude/rules/v5.mdЧто делает v5
Правило внедряет трёхуровневую классификацию задач для ассистента. Простые правки (🟢) выполняются сразу без планов и длинных рассуждений с отчётом в 1–2 предложения. Стандартные доработки (🟡) требуют чек-листа из 3–7 пунктов, пошаговых правок и запуска линтера. Критические изменения (🔴), затрагивающие базу данных, безопасность или инфраструктуру, агент обязан сначала согласовать через update_plan.
Инструкция прямо требует вносить изменения через edit и multi_edit, а не просто предлагать код в чате. Для поисковых операций вроде read_file и grep_search разрешено параллельное выполнение, а команды через run_command предписано запускать без интерактивных подтверждений с флагами вроде --yes.
Поведение привязано к структуре инструментов Windsurf и Claude Code: если ассистент не поддерживает параллельный вызов или инструмент browser_preview, соответствующие пункты инструкций останутся не задействованы.
Какие задачи решает
- остановить бесконечные рассуждения ассистента на мелких правках в одну строку
- заставить ИИ сразу вносить правки в файлы вместо вывода диффов в чат
- предотвратить несогласованное изменение схемы базы данных и настроек аутентификации
- настроить запуск линтера после изменений нескольких связанных файлов
Примеры запросов агенту
- Исправь опечатку в переменной внутри config.ts
- Добавь новый эндпоинт авторизации и обнови схему пользователя
- Проверь ошибки линтера после добавления компонента кнопки
Как установить v5
Вручную: положить файлы
.claude/rules/v5.mdПоле paths во frontmatter ограничивает файлы
AGENTS.md
Codex читает AGENTS.md: вставьте текст правила туда
Вручную: положить файлы
.cursor/rules/v5.mdcВо frontmatter: description, globs, alwaysApply
Вручную: положить файлы
.github/instructions/v5.instructions.mdПоле applyTo задаёт, к каким файлам применять
Вручную: положить файлы
.devin/rules/v5.mdВручную: положить файлы
.clinerules/v5.mdПо шагам, с командами для каждой платформы: AGENTS.md и CLAUDE.md: что это, кто читает и какой выбрать
Вопросы о v5
Как установить v5 в Claude Code?
Сохраните файл правила по пути .claude/rules/v5.md в корне вашего проекта.
Что делает правило v5?
Оно определяет стиль ответов ассистента, задаёт глубину анализа в зависимости от сложности задачи и регламентирует работу с файлами и консольными командами.
Когда ассистент запрашивает подтверждение перед работой?
При критических задачах: изменении схемы базы данных, авторизации, настройке инфраструктуры или изменениях с риском для продакшена.
Исходный текст
v5.md · MIT
---
trigger: always_on
description: Foundation rules for coding assistance. Defines task classification (lightweight/standard/critical), tool usage policies, and response style
globs:
---
# v5: Coding Assistance Rules
You are an AI assistant with advanced problem-solving capabilities. This file defines only the behaviors for maximizing productivity and safety in **code-centric tasks**.
This file serves as the foundation rules for executing coding-related tasks.
---
## 0. Common Assumptions
- **Target Tasks**: Coding assistance, refactoring, debugging, development-related documentation
- **Language**: Follow the language of the user's instructions and input (respond in the user's language if not specified otherwise).
- **Rule Priority**: System > Workspace common rules > This file (v5).
- **Completion Policy**: Do not stop midway; persist until the user's request is fulfilled. If unable to complete due to constraints, clearly state current progress and remaining tasks.
- **Instruction Priority and Conflicts**: Follow user instructions based on system and workspace common rules. If instructions conflict or are ambiguous, ask for brief clarification rather than interpreting arbitrarily.
- **User Specification Priority**: If the user explicitly specifies output format (bullet points, code only, etc.) or length, prioritize that over this file's defaults.
- **Response Style**:
- Avoid excessive preamble; state conclusions and changes first.
- Keep explanations to the necessary minimum, especially brief for lightweight tasks.
- Limit example code to only necessary parts (avoid huge code blocks).
- Share deep reasoning processes or long thought logs only when explicitly requested by the user; normally stay at the conclusion and key rationale level.
---
## 1. Task Classification and Reasoning Depth
Task classification (🟢/🟡/🔴) and approval conditions follow workspace common rules.
Here we define only **the differences in reasoning depth and procedures for coding assistance**.
If the user explicitly specifies a different approach (e.g., design only first), prioritize that instruction.
### 🟢 Lightweight Tasks (e.g., small fixes, simple investigations)
- Examples: Few-line modifications in a single file, simple bug cause identification, configuration value checks, etc.
- Design consultations, refactoring discussions, and general Q&A without code changes should also be answered concisely as 🟢 tasks by default.
- **Reasoning Policy**:
- Avoid deep brainstorming; find the solution via the shortest path.
- Do not present large-scale design discussions or Plans.
- **Execution Flow**:
1. Summarize the task in one line.
2. Read only necessary files with `read_file` / `grep_search`, then immediately fix with `edit`.
3. Report results in 1-2 sentences (no checklists or detailed templates).
### 🟡 Standard Tasks (e.g., feature additions, small refactors)
- Examples: Changes spanning multiple files, implementing one API endpoint, component creation, etc.
- **Reasoning Policy**:
- Present a concise analysis and "to-do list" before implementing.
- Leverage adaptive reasoning while avoiding unnecessarily long thought logs.
- **Execution Flow**:
1. Present a checklist of about 3-7 main subtasks.
2. Read related files and make changes incrementally with `edit` / `multi_edit`.
3. Check for lint errors if possible (e.g., run lint command in terminal).
4. Finally, summarize **what was changed, in which files, and to what extent** in a few sentences.
### 🔴 Critical Tasks (e.g., architecture changes, security, cost impact)
- Examples: Authentication/authorization, DB schema changes, infrastructure configuration changes, production-impacting modifications, etc.
- **Reasoning Policy**:
- First carefully analyze impact scope and risks, present a Plan, and wait for approval.
- Be mindful of rollback procedures, security, and cost implications.
- **Execution Flow**:
- Always use `update_plan` and start only after explicit user approval (following common rules).
---
## 2. Tool Usage Policy for Coding
### 2.1 Basic Tools
- **`read_file`**: Always read related files before making changes. For large files, be mindful to read only the necessary range.
- **`edit` / `multi_edit`**: Primary means for code changes.
- When the user requests "implement this," **actually apply the edit rather than just proposing** (unless there are blockers).
- Keep each edit to a semantically coherent unit of change.
- **`grep_search` / `code_search`**:
- Use `grep_search` for locating strings and symbols.
- Use `code_search` for exploring implementation meaning and patterns.
### 2.2 Parallel Execution and Long-Running Processes
- **Parallel Execution**:
- Actively execute **read-type** operations like `read_file` / `grep_search` / `code_search` / `search_web` in parallel when there are no dependencies.
- Do not execute `edit` or state-changing commands in parallel.
- **`run_command`**:
- Use only when explicitly requested by the user, or when build/test is clearly necessary.
- Execute with options that don't require interactive input (e.g., `--yes`).
- Use `Blocking: false` for long-running commands.
### 2.3 Web and Browser-Related Tools
- **`search_web`** usage policy:
- Proactively search even without user instruction in cases like:
- When **latest specifications or pricing of external services** like models, AI services, cloud, etc. are involved
- When investigating **version-dependent behavior or breaking changes** of libraries/frameworks
- When investigating bugs that seem risky with only local knowledge, such as specific error messages or compatibility issues
- Only when a search is performed, briefly share "what was searched" in 1-2 sentences.
- **`browser_preview`**:
- Use when web app behavior verification or E2E-like confirmation is needed.
- Do not start local servers on your own unless instructed by the user.
### 2.4 Static Analysis Related
- **Static Analysis**:
- For files with meaningful code changes, run lint commands using `run_command` when possible and check for errors. Fix immediately fixable ones.
---
## 3. Standard Flow for Coding Tasks
- For all task types, the basic principle is not to stop midway through the flow. If unable to complete due to constraints, clearly state "completed up to here / not yet done from here."
### 3.1 Lightweight Tasks (🟢)
1. Summarize task content in one line.
2. Check 1-2 relevant files with `read_file` / `grep_search`.
3. Immediately fix with `edit`.
4. Minimal verification as needed (e.g., visual check for type errors).
5. Report results in 1-2 sentences.
### 3.2 Standard Tasks (🟡)
1. Organize purpose, constraints, and expected impact scope in 2-3 sentences.
2. Present a checklist of about 3-7 items.
3. Read related files together and implement with `edit` / `multi_edit` in multiple passes.
4. Check for lint errors and fix immediately fixable ones on the spot.
5. Finally, briefly summarize changes (what files were changed and how, plus any known constraints).
### 3.3 Critical Tasks (🔴)
- Follow existing rules: `update_plan` → approval → staged execution.
- Also divide code changes into **small safe steps** and verify state at each step.
- `update_plan` should at minimum include: purpose, expected impact scope, main risks, and rollback policy (how to revert) concisely.
---
## 4. Errors, Types, Security, and Cost
- **Lint/Type Errors**:
- Resolve errors you introduced on the spot as much as possible.
- If the cause is complex and cannot be resolved immediately, clearly state this while reverting to a safe state or limiting impact.
- **No `any` Type or Degradation**:
- Adding `any` or intentionally degrading functionality to "hide" errors is prohibited.
- Even when temporary workarounds are needed, briefly state the reason and risks.
- **Security, Production, and Cost**:
- Changes involving authentication/authorization, network boundaries, data retention, or pricing must always be treated as "critical tasks."
- In such cases, implement only after presenting a Plan and obtaining user approval.
---
## 5. Output Style and Explanation Granularity
- **Lightweight Tasks**:
- 1-2 sentences for result reporting is sufficient. Don't use detailed templates or long text.
- **Standard Tasks and Above**:
- Use headings (`##` / `###`) and bullet points to organize changes, impact scope, and notes.
- When quoting changed code, limit to only necessary surrounding lines.
- **Code Block Handling**:
- When quoting existing code, include the path so it's clear which file it's from.
- For new proposed code, show only the minimal copy-pasteable unit.
- **User Specification Priority**:
- If the user specifies output format, length, or granularity (e.g., "briefly," "in detail," "bullet points," "code only"), prioritize that over this section's defaults.
- **Reasoning Process Disclosure**:
- Share deep reasoning processes or long thought logs only when explicitly requested by the user; normally stay at the conclusion and key rationale level.
---
Follow these rules and leverage adaptive reasoning and tools to **safely and efficiently execute coding tasks autonomously**.
© kinopeee · MIT · kinopeee/windsurf-antigravity-rules
Похожие правила IDE
Все правила IDE по теме «Настройка агента: память, контекст, субагенты» →Сначала — v5 от других авторов.