coding-guidelines-gen

Generate nested AGENTS.md coding guidelines per module in a monorepo.

130|15|Updated Dec 14, 2025
One-click install
npx skills add https://github.com/jMerta/codex-skills --skill coding-guidelines-gen-jmerta
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: coding-guidelines-gen
Source: https://github.com/jMerta/codex-skills/tree/main/coding-guidelines-gen
Command: npx skills add https://github.com/jMerta/codex-skills --skill coding-guidelines-gen-jmerta

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the generation of nested AGENTS.md coding guidelines at the module level within a monorepo, helping teams define architecture boundaries, tooling expectations, and verifiable blocks per module.

Core Features & Use Cases

  • Detects module roots in a monorepo and recommends where to place per-module AGENTS.md files.
  • Generates nested AGENTS.md templates with architecture guidelines, language/tooling detection, and a verifiable block schema.
  • Produces ready-to-use formatting/linting guidance (e.g., Spotless for JVM) and runnable commands for each module.

Quick Start

Run the coding-guidelines-gen skill on your repository to generate per-module AGENTS.md guidelines, then review and customize each module's AGENTS.md as needed.

Frequently Asked Questions about coding-guidelines-gen

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate per-module AGENTS.md coding guidelines in a monorepo?

To generate per-module AGENTS.md coding guidelines in a monorepo, run the coding-guidelines-gen skill. It scans common module roots like apps, packages, and src, detects languages and tooling, and outputs nested architecture guidelines with verifiable blocks for each module.

What is an AGENTS.md file used for in monorepo architecture?

An AGENTS.md file defines architecture boundaries, tooling expectations, and verifiable validation blocks for a specific module. Generating nested AGENTS.md files within a monorepo helps teams maintain consistent formatting, linting, and coding guidelines across distinct package boundaries.

How do I automate formatting and linting verification for JVM modules in a monorepo?

Automate formatting and linting verification for JVM modules by generating an AGENTS.md file with Spotless setup guidance and runnable example commands. The skill detects JVM tooling and outputs a verifiable codex-guidelines block to validate module-level formatting rules.

Does this coding guidelines generator support monorepos with multiple languages and tooling?

Yes, the coding guidelines generator supports monorepos with multiple languages by detecting the specific tooling used within each module. It scans directories like apps and packages, tailoring the nested AGENTS.md templates and verifiable blocks to match each module's detected language and formatting requirements.

What is the best way to enforce architecture boundaries across nested monorepo packages?

The best way to enforce architecture boundaries across nested monorepo packages is generating per-module AGENTS.md files. This approach applies tailored coding guidelines and verifiable blocks to specific module roots, ensuring localized tooling expectations and linting validation across the repository structure.

Can I customize the AGENTS.md templates after they are generated for each module?

Yes, you can customize the generated AGENTS.md templates after running the skill. The tool produces ready-to-use nested guidelines with detected tooling and formatting commands, which you can then review and adjust to fit your specific module architecture and verification requirements.