README.md

Team stacks

Each directory here is one MiniMax Code team member's stack: the workflows and skills they actually use to build MiniMax Code. Each stack is also a MiniMax Code plugin package.

Stack	Owner	What it has
ronny	Ronny, R&D lead	Skills and plain-text checklists
jiachen	Jiachen, engineer	MCode Review: PR review in your agent and in GitHub or GitLab CI, with a weekly loop that tunes its rules; plus lifting-loops and making-content. Skills, CI code and a WORKFLOW.md
req-tpm	MiniMax Code team	Optional, v0: the requester and their agent act as a requirement's TPM (Feishu doc body, Meegle status). Skills, templates and a WORKFLOW.md
youfang	Youfang, engineer	A skill that turns diagram walkthroughs into Magic Move slide decks (four styles, sample first), and a WORKFLOW.md

Teammates are welcome to add their own; see below.

Adding a team stack

1. Pick an id: lowercase letters, digits and hyphens. It becomes both the directory name and the plugin name.
2. Copy the template: cp -R templates/stack-template stacks/<id>.
3. Edit .minimax-plugin/plugin.json, write your skills and WORKFLOW.md.
4. Add a row to the table above, and an entry to .claude-plugin/marketplace.json ("source": "./stacks/<id>", the same description as plugin.json).
5. Run node scripts/check.mjs and open a PR.

When you change a stack later, raise its version in the same PR; see CONTRIBUTING.md.

Keep it public-safe: no internal hostnames, links, project codenames, internal metrics, credentials or customer data. Skills must work for someone outside the team.

Stacks from outside the team go in community/. Pull requests are accepted only from repository collaborators. If you are not a collaborator, open an issue first. See CONTRIBUTING.md.