advance-minimax-m2-cursor-rules

<div align="center">

# MiniMax M2.7 Cursor Rules

[![Stars](https://img.shields.io/github/stars/madebyaris/advance-minimax-m2-cursor-rules?style=flat-square)](https://github.com/madebyaris/advance-minimax-m2-cursor-rules/stargazers)
[![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg?style=flat-square)](LICENSE)
[![Cursor 3](https://img.shields.io/badge/Tested-Cursor%203-blue?style=flat-square)](https://cursor.com/blog/cursor-3)
[![MiniMax M2.7](https://img.shields.io/badge/MiniMax-M2.7-purple?style=flat-square)](https://platform.minimax.io)
[![Any Model](https://img.shields.io/badge/Compatible-Any%20Model-green?style=flat-square)](#model-compatibility)

**MiniMax M2.7 rules for repo-scale engineering, agent teams, skills, and dynamic tool use**

*Built for **MiniMax M2.7**, aligned with the official release and API docs, and written to stay useful across model changes.*

[Quick Start](#quick-start) | [Architecture](#rule-architecture) | [M27-runtime](#m27-runtime-modes) | [AGENTSmd](#agentsmd-for-other-ides-and-clis)

</div>

---

## Why This Repo Exists

This repo is designed to make MiniMax M2.7 feel strong in the places the official release emphasizes most:

- repo-scale and end-to-end engineering
- agent harnesses and multi-agent collaboration
- long skill packs and detailed tool contracts
- dynamic tool discovery in changing environments
- proportional verification with evidence-backed closeouts

The goal is not to make MiniMax merely imitate another provider's tone. The goal is to give M2.7 a durable execution spine that complements its official positioning around real-world engineering, complex skills, and agent workflows.

## Model Compatibility

The rules are designed to survive model changes:

- the core rule stays short and durable
- runtime-specific guidance lives in requestable rules
- tool advice is written around whatever the current environment actually exposes
- version-sensitive claims are meant to be verified at runtime, not fro