Skip to content
AI suite

AI Rules Generator

Fill in one form and generate rule files for every major AI coding tool at once: AGENTS.md, CLAUDE.md, .cursor/rules/project.mdc, copilot-instructions.md, .windsurfrules, and GEMINI.md. AGENTS.md is the single source of truth and the other files are derived from it, so your rules never drift between tools.

Everything is generated locally in your browser — nothing you type is sent to any server.

Guide: How to use & features

  • Fill in the project name, overview, tech stack, commands, coding conventions, and prohibited actions. Empty sections are omitted from the output automatically.
  • Choose the output language (English/Japanese) and press "Generate rule files" to preview all six files in tabs.
  • Copy each file individually, or use "Download all as ZIP" to save them with the correct directory layout (.cursor/rules/, .github/).
  • Because every file is derived from AGENTS.md, your rules never drift between tools.

FAQ: FAQ

  • What is AGENTS.md?

    An open standard file for describing your project to AI coding agents. Many tools — OpenAI Codex, Google Jules, Cursor, and more — read it, and it is becoming the "README for AI agents". This tool treats AGENTS.md as the source of truth and derives each tool-specific file from it.
  • Why does each tool need its own file?

    Claude Code reads CLAUDE.md, Cursor reads .cursor/rules/*.mdc, GitHub Copilot reads .github/copilot-instructions.md, Windsurf reads .windsurfrules, and Gemini CLI reads GEMINI.md. The content can usually be identical, so deriving them all from one source keeps them in sync.
  • Where do I put the generated files?

    Place them at the root of your repository (.cursor/rules/project.mdc and .github/copilot-instructions.md go inside their subdirectories). The ZIP download preserves the correct directory layout.
  • What is the "---" block at the top of the .mdc file?

    It is the MDC frontmatter used by Cursor Project Rules, containing metadata such as description and alwaysApply. This tool sets alwaysApply: true so the rules apply to the whole project at all times.
  • Is my project information stored or transmitted?

    No. Generation runs entirely in your browser via JavaScript; nothing you type is sent to or stored on any server, so internal project details are safe.

Use cases: Common use cases

  • Bootstrapping a new project

    Generate the full set of rule files right after creating a repository, so Claude Code, Cursor, Copilot, and others all follow the same conventions from day one.

  • Keeping rules in sync across a mixed-tool team

    When teammates use different AI coding tools, deriving every file from one AGENTS.md prevents copy-paste drift and forgotten updates.

  • Introducing AI agents to an existing project

    Writing out build/test commands and prohibited actions in the form organizes exactly the project knowledge an AI needs, improving suggestion quality from the first day.

  • Supporting OSS contributors

    Shipping an AGENTS.md in your repository helps contributors produce convention-compliant patches no matter which AI tool they use.

Notes: Notes & limitations

  • Tool formats may change

    Rule-file conventions (file names, frontmatter, etc.) evolve quickly. Check each tool’s latest documentation before adopting the generated files.

  • The output is a starting template

    This tool formats what you type into files — it does not decide the best rules for your project. Review the output with your team and refine it to match reality.

  • Do not include secrets

    Generation happens in your browser, but the files end up committed to your repository. Keep API keys, internal URLs, and other sensitive details out of rule files.

  • Watch out for overwriting existing files

    If your project already has a CLAUDE.md or .cursor/rules, dropping the generated files in place will overwrite them. Diff and merge instead.

Generate for
Output language Output language

Generated files

Fill in the form above and press "Generate rule files" to preview all six files.

Articles for this tool

Recent Articles

Use Case
2026-08-07

curl Options Cheat Sheet: What -X, -H and -d Actually Do

A reference for the curl options you meet in real API work: why -d already implies POST, how -d differs from --data-raw, the @ prefix that silently reads a file, single vs double quotes, and why -k and -L deserve more caution than they usually get.

Introduction
2026-08-06

Converting Between JSON Schema and Zod: How required Maps to .optional()

Inside a two-way converter that turns JSON Schema into a Zod schema and Zod code back into JSON Schema. Covers the inverted defaults between required and .optional(), the constraint mapping table, and how the Zod side is parsed without executing any code.

Use Case
2026-08-06

SQL Clause Order Reference: Why WHERE Can't See Your SELECT Alias

The order you write SQL clauses is not the order the database runs them. A reference for the logical execution order (FROM → WHERE → GROUP BY → HAVING → SELECT → ORDER BY → LIMIT), why aliases fail in WHERE, when to use WHERE vs HAVING, and the MySQL/PostgreSQL differences that bite.

Use Case
2026-08-06

Unified Diff Format Reference: Reading @@ Hunks in git diff Output

How to read the unified diff format git produces: what the four numbers in @@ -12,7 +12,9 @@ mean, why a one-character edit shows as a whole-line replacement, the whitespace and line-ending traps, \ No newline at end of file, combined @@@ diffs on merges, and rename detection via similarity index.

Use Case
2026-08-06

UTC to JST Reference: The 9-Hour Offset, Cheat Sheet & Timezone Pitfalls

Convert between UTC and JST (Japan Standard Time) with a cheat sheet. Covers what Z and +09:00 mean in ISO 8601, when JavaScript date parsing silently shifts by 9 hours, MySQL/PostgreSQL timezone behavior, and why GitHub Actions cron always runs in UTC.

Use Case
2026-08-04

CREATE TABLE Reference: MySQL vs PostgreSQL vs SQLite Types & Constraints

A cross-database CREATE TABLE (DDL) reference with cheat sheets for data types, auto-increment keys (AUTO_INCREMENT / IDENTITY / rowid), foreign key ON DELETE behavior, and the CHECK constraint that MySQL silently ignores.

Ad

Ad