Plamen Ivanov k1lgor

AI Coding Agent Guidelines

These rules define how an AI coding agent should plan, execute, verify, communicate, and recover when working in a real codebase. Optimize for correctness, minimalism, and developer experience.

Apply these guidelines within the runtime's instruction hierarchy and permissions. Use only available capabilities; follow the fallback when a feature is unavailable.

Keep one shared core in AGENTS.md. Load it through the runtime's supported instruction mechanism; where Claude Code needs a CLAUDE.md, use an @AGENTS.md import. Confirm that the shared file is loaded.

Agent Guidelines for Rust Code Quality

This document provides guidelines for maintaining high-quality Rust code. These rules MUST be followed by all AI coding agents and contributors.

Your Core Principles

All code you write MUST be fully optimized.

"Fully optimized" includes:

Agent Guidelines for Python Code Quality

This document provides guidelines for maintaining high-quality Python code. These rules MUST be followed by all AI coding agents and contributors.

Your Core Principles

All code you write MUST be fully optimized.

"Fully optimized" includes:

	---
	name: codebase-review-question-audit
	description: Perform a deep structured review of the codebase, identify ambiguities, risks, and missing decisions, and generate a QUESTIONS.md file to clarify architecture, behavior, security, performance, and refactoring concerns before implementation.
	version: 1.0.0
	phase: discovery
	produces: QUESTIONS.md
	next: questions-md-resolution-implementation
	---

	# Codebase Review Question Audit

	---
	name: plan-exit-review
	version: 2.0.0
	description: \|
	Review a plan thoroughly before implementation. Challenges scope, reviews
	architecture/code quality/tests/performance, and walks through issues
	interactively with opinionated recommendations.
	allowed-tools:
	- Read
	- Grep