AGENTS.md · mantinedev/mantine
AGENTS.md from mantinedev/mantine: 53 lines covering Links, Finalizing Your Work, Code Style, Commit conventions.
Template by mantinedev
Install
Works with Codex, Cursor, GitHub Copilot, Gemini CLI, OpenCode, Claude Code. Read the repository before you give any tool access to your data.
curl -fsSL https://raw.githubusercontent.com/mantinedev/mantine/master/AGENTS.md -o AGENTS.md
Read it and adapt it to your project before use.
Get the weekly diff
The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.
About
Use cases: prompt-engineering
Reviews
Write a reviewNo reviews yet. Installed it? Reviews come from verified installers only. How reviews work
What's in it
An AGENTS.md file: instructions coding agents (Codex, Cursor, Copilot, Gemini CLI and others) read before working in a repo.
- For
- Codex, Cursor, GitHub Copilot, Gemini CLI, OpenCode, Claude Code
- Length
- 53 lines
- File
AGENTS.md
Sections
- Links
- Finalizing Your Work
- Code Style
- Commit conventions
First lines (shown under the repo's MIT license)
## Links ## Finalizing Your Work Choose these commands to run after finalizing your work: ```bash # Always run these commands before finalizing your work npm run typecheck npx oxlint -c oxlint.config.mjs path/to/changed/files npm run format:write:files path/to/changed/files npm run build # Run tests for specific path related to your changes npm run jest @mantine/charts npm run jest path/to/changed/file.test.ts # Run stylelint only if you have made changes to styles or CSS files npm run stylelint # Run this script if you've changed dependencies in any package.json npm run syncpack ``` After running the commands above, check if `codex` CLI is available (`command -v codex`). If it is, run `/codex-code-review` to get an automated code review of unstaged changes and apply fixes. ## Code Style **Comments Guidelines:** - **Do not include inline comments** that describe logic or implementation details unless explicitly requested - **Always preserve documentation comments** on interfaces, types, and function parameters (JSDoc-style comments with `/** */`) - The codebase prefers clean, self-documenting code for implementation - Type definitions and public APIs should maintain their documentation comments ## Commit conventions Mantine is a monorepo, thus it is important to write correct commit messages to keep the git history clean and consistent. All commits made in this repository are divided into 3 groups: - package commits – Related to any particular package. - docs commits – Related to the documentation. - core commits – Only related to repository tooling and not associated with any package. Commit messages consists of 3 parts: ``` [area] Optional title: Message ``` Examples: - `[core] Fix documentation deployment script` – Change made in repository script, it is not related to documentation or any package - `[mantine.dev] Update report issues link` – Change related to documentation website - `[@mantine/core] Button: Add theme focus styles` – Change in @mantine/core package at Button component - `[@mantine/hooks] use-list-state: Add remove handler` – Change in @mantine/hooks package at use-list-state hook
Signals
- Stars
- 31,865
- Forks
- 2,403
- Open issues
- 14
- Last commit (this folder)
- Jun 26, 2026 (4 months ago)
- Last release
- Oct 17, 2026 (12 days ago)
From GitHub (fetched Oct 24, 2026).
Details
- License
- MIT
- Repository
- github.com/mantinedev/mantine
- First seen
- Oct 24, 2026
- Last checked
- Oct 24, 2026
- Source
- GitHubgithub-graphql
More from mantinedev
Cite this page
AGENTS.md · mantinedev/mantine. Agent Mart. https://agentmart.dev/templates/mantinedev-mantine-agents-md (last updated 2026-10-24)