induwara.lk
induwara.lkDeveloper · AI

AI Coding Agent Rules Generator — AGENTS.md, CLAUDE.md & .cursorrules

Fill one short form and get a clean rules file for your AI coding agent — AGENTS.md, CLAUDE.md, .cursor/rules, Copilot or Windsurf. It shows the exact path to save it and runs in your browser, so nothing you type is uploaded.

By Induwara AshinsanaUpdated Jul 1, 2026
Generate your rules file5 formats, one form
Structure verified
Start from a preset
Target format
14/80
16/160
34/200
13/120
17/120
12/120

One rule per line. Leave blank to use sensible TypeScript defaults (shown as placeholder).

One convention per line. Blank leaves this section out.

One note per line. Blank leaves this section out.

AGENTS.md — save at the repository root
AGENTS.mdValid structure
# induwara-tools

SL utility tools.

## Tech stack
- Language: TypeScript
- Stack: Next.js 16, Tailwind v4, shadcn/ui
- Package manager: npm

## Commands
- Build: `npm run build`
- Test: `npm run typecheck`
- Lint: `npm run lint`

## Code style
- TypeScript strict, no `any`
- Prefer server components

## Conventions
- Do: cite calculation sources
- Don't: push to main

Placed at the repository root, AGENTS.md is read automatically by agents that support the open standard (Codex, Jules, Cursor, Zed and others). Nested AGENTS.md files override the parent for their subtree.

Same content, other formats
Generated entirely in your browser — nothing you type is uploaded.

How it works

An AI coding agent only follows your project conventions if it can find and read an instructions file — and every agent looks for a different filename in a different place. This tool keeps one shared content model and adapts it to whichever format you pick, so you write your rules once instead of maintaining five near-identical files by hand. There is no AI call and no network request: every byte is produced by string templating in your browser.

One model, five formats. Your inputs — project meta, commands, style rules, conventions and directory notes — become a single internal model. The formats differ only in the filename, the path and one structural quirk. AGENTS.md and CLAUDE.md save at the repository root; .github/copilot-instructions.md lives in the .github folder; Windsurf reads .windsurf/rules/; and Cursor uses .cursor/rules/project.mdc with a small frontmatter block. Wrong placement is the single most common reason an agent ignores your rules, so the exact path is shown in a banner above the output.

Section assembly.Sections are emitted in a fixed order — Project overview → Tech stack → Commands → Code style → Conventions → Directory notes → Commit convention — and any empty section is dropped so the file stays tight. Commands are wrapped in backticks and only the ones you fill in appear; a blank build command simply doesn't show. Each style rule and convention becomes one bullet, and a leading - you type yourself is stripped so you never get a doubled bullet.

Cursor frontmatter. When you target Cursor, the file is prefixed with the documented .mdc frontmatter — description and alwaysApply: true — so the rule applies to every request. No other format gets frontmatter. Leaving the code-style field blank seeds sensible, editable defaults for your chosen language (for example, PEP 8 for Python or strict mode for TypeScript).

Cross-check.The "Structure verified" badge is not decorative. After each keystroke an independent function re-parses the emitted file and confirms a frontmatter block is present only for Cursor, that a single title heading exists, and that every section heading is a recognised one in the canonical order. The filenames, paths and the frontmatter shape come straight from the vendor docs cited below, last verified 2026-07-01.

Worked examples

Next.js + TypeScript repo → AGENTS.md

  • Format: AGENTS.md · Name: induwara-tools
  • Description: SL utility tools
  • Language: TypeScript · Stack: Next.js 16, Tailwind v4, shadcn/ui · pm: npm
  • Build: npm run build · Test: npm run typecheck · Lint: npm run lint
  • Style: TypeScript strict, no `any` / Prefer server components
  • Conventions: Do: cite calculation sources / Don't: push to main
# induwara-tools

SL utility tools.

## Tech stack
- Language: TypeScript
- Stack: Next.js 16, Tailwind v4, shadcn/ui
- Package manager: npm

## Commands
- Build: `npm run build`
- Test: `npm run typecheck`
- Lint: `npm run lint`

## Code style
- TypeScript strict, no `any`
- Prefer server components

## Conventions
- Do: cite calculation sources
- Don't: push to main

Save at the repository root. The description gains a trailing period; there is no frontmatter (that is Cursor-only); the Directory and Commit sections are absent because those inputs were left empty.

Python CLI → Cursor .cursor/rules

  • Format: .cursor/rules · Name: csvkit-helper (no description)
  • Language: Python · Stack: Typer, Rich · pm: uv
  • Build: (empty) · Test: pytest · Lint: ruff check
  • Code style: (left blank → Python defaults)
  • Commit convention: ON
---
description: Project rules for csvkit-helper
alwaysApply: true
---

# csvkit-helper

## Tech stack
- Language: Python
- Stack: Typer, Rich
- Package manager: uv

## Commands
- Test: `pytest`
- Lint: `ruff check`

## Code style
- Follow PEP 8; type-hint public functions
- Keep functions small and pure where practical

## Commit messages
- Use Conventional Commits (feat:, fix:, docs:, chore:)

Save as .cursor/rules/project.mdc. The .mdc frontmatter is prepended; the empty Build line is dropped; the blank code-style field falls back to the Python preset; and the Commit messages section is added because the toggle is on.

Edge case — empty form → AGENTS.md

  • Format: AGENTS.md
  • Project name: (blank) · Description: (blank)
  • Language: TypeScript · pm: npm · everything else blank
# Project

## Tech stack
- Language: TypeScript
- Package manager: npm

## Code style
- TypeScript strict mode; avoid `any`; prefer named exports
- Keep modules small and single-purpose

The title falls back to # Project; with no stack the Stack line is omitted and with no commands the whole Commands section disappears; the blank code style falls back to the TypeScript preset. The file is still a complete, valid skeleton.

Frequently asked questions

Sources & references

The filenames, paths and the Cursor frontmatter block on this page were last cross-checked against the vendor docs on 2026-07-01. Each format is a documented specification; this page is reviewed whenever a vendor revises where the file lives or how it is structured.

Related tools

Rate this tool
Be the first to rate

Comments & feedback

Spotted a bug or want an improvement? Tell us — our team reviews every comment, and good ideas get built. Comments are public and anonymous.

Found a bug, edge case, or want another agent format supported?

Email me at [email protected] — most fixes ship within 24 hours.