Add AI agent rules using Rulesync

[Chaho12]

Description

This PR implements a centralized rule management system for AI coding assistants using Rulesync. It establishes a Single Source of Truth (SSOT) for code style guidelines that automatically generates configurations for multiple AI development tools (Claude Code, Cursor, and GitHub Copilot).

Key changes:

1. Rulesync setup - Created .rulesync/rules/ directory with 5 rule categories:

   • trino-code-style.md - Core Java coding standards (naming, collections, error handling)
   • airlift-formatting.md - Code formatting based on Airlift template (imports, braces, spacing)
   • trino-maven.md - Maven and pom.xml standards
   • trino-vector-api.md - Java Vector API (JEP 508) implementation guidelines
   • pull-request-guidelines.md - PR and commit message best practices

2. Generated configurations - Rulesync automatically generates tool-specific files:

   • .claude/rules/*.md for Claude Code
   • .cursor/rules/*.mdc for Cursor IDE
   • .github/instructions/*.md for GitHub Copilot

3. Documentation - Added docs/ai-agent-rules.md with:

   • Architecture overview and SSOT approach
   • Detailed description of each rule category
   • Instructions for managing and updating rules
   • Best practices and troubleshooting guide
   • Updated mkdocs.yml to include the new documentation page

Benefits:

• Ensures consistent AI assistance across the development team
• Reduces maintenance overhead by managing rules in one location
• Easy to add support for new AI tools without duplicating rules
• Clear guidelines for both developers and AI assistants

Additional context and related issues

• Introduce Agent Rules #929

Source for Rules

I refered to Trino's guide on code style, pull-request-and-commit-guidelines

• https://trino.io/development/process#pull-request-and-commit-guidelines
• https://github.com/trinodb/trino/blob/master/.github/DEVELOPMENT.md#code-style
• https://github.com/airlift/codestyle

Why Rulesync?

Previously, maintaining separate rule files for different AI tools (.cursorrules, CLAUDE.md, etc.) led to duplication and inconsistency. Rulesync solves this by:

• Providing a single source of truth in .rulesync/rules/
• Automatically generating tool-specific formats
• Supporting 15+ AI development tools

Rule sources:

The rules are based on official Trino project guidelines:

• Code style from https://trino.io/development/code-style.html
• Airlift formatting template (Airlift.xml)
• Trino contribution guidelines

Installation requirement:

Contributors and maintainers who want to update rules will need to install Rulesync:
npm install -g rulesync

Release notes

(x) This is not user-visible or is docs only, and no release notes are required.
( ) Release notes are required, with the following suggested text:

* Fix some things.

[ebyhr]

This PR should be reviewed by @trinodb/maintainers-gateway (not only @mosabua). Please don't merge this PR prematurely.

[mosabua]

Agreed @ebyhr .. in fact I believe we might want to even get this right separately in multiple phases and figure out how to sync it. A lot of this arguably belongs into airlift first and foremost and then into some sort of centralized setup for all trinodb project (which could be the airlift base and more). Also there are a LOT of rules already to start with .. how did you generate those?

As a result the airlift contributors and all Trino maintainers should be potentially involved. Maybe we need to discuss this more in the maintainer channel or on a contributor call.

[Chaho12]

This PR should be reviewed by @trinodb/maintainers-gateway (not only @mosabua). Please don't merge this PR prematurely.

Oh i tagged him because because we were talking in slack about it. Yes we have to talk, this is simply a draft to see and discuss

[Chaho12]

Also there are a LOT of rules already to start with .. how did you generate those?

I got help from cursor to create the rules, with the information provided from 3 sources

• https://trino.io/development/process#pull-request-and-commit-guidelines
• https://github.com/trinodb/trino/blob/master/.github/DEVELOPMENT.md#code-style
• https://github.com/airlift/codestyle