coding-guidelines-generator
Use when asked to generate or set up coding guidelines, detect my stack, generate AGENTS.md rules, create stack-specific conventions, set up agent guidelines, or configure coding guidelines for this repo on first use in a codebase. Deterministically detects tech stack layers, confirms with the user, generates tailored guidelines from modular references, and links them from AGENTS.md without overwriting user content. Excludes general code review, linter/formatter configuration, or CI pipeline setup.
71
89%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Passed
No findings from the security scan
Coding Guidelines Generator
Deterministic router for generating and maintaining modular stack guidelines.
Routing Table
| Detected Stack / Layer | Reference File | Target Output File | Load Condition |
|---|---|---|---|
| Android (Compose / XML) | references/android.md | AGENTS-GUIDELINES-ANDROID.md | Android plugin, AndroidManifest.xml |
| JavaScript / Node.js | references/javascript.md | AGENTS-GUIDELINES-JS.md | package.json, .js/.mjs files |
| TypeScript | references/typescript.md | AGENTS-GUIDELINES-JS.md | tsconfig*.json or typescript dependency |
| React | references/react.md | AGENTS-GUIDELINES-REACT.md | react dependency (names JS/TS layer) |
| Next.js (App/Pages) | references/nextjs.md | AGENTS-GUIDELINES-NEXTJS.md | next dependency (names React & JS/TS layers) |
| Python (+ FastAPI/Django/Flask) | references/python.md | AGENTS-GUIDELINES-PYTHON.md | pyproject.toml, requirements*.txt, uv.lock |
| PHP | references/php.md | AGENTS-GUIDELINES-PHP.md | composer.json, *.php |
| WordPress (Theme/Plugin/Site) | references/wordpress.md | AGENTS-GUIDELINES-WORDPRESS.md | style.css (Theme Name), plugin header, wp-config.php |
| Go | references/go.md | AGENTS-GUIDELINES-GO.md | go.mod |
| Rust | references/rust.md | AGENTS-GUIDELINES-RUST.md | Cargo.toml |
| Shell | references/shell.md | AGENTS-GUIDELINES-SHELL.md | Substantive standalone shell project |
| HTML / CSS | references/html-css.md | AGENTS-GUIDELINES-HTML-CSS.md | Static web without JS/backend framework |
| Java / Kotlin (Backend) | references/java.md | AGENTS-GUIDELINES-JAVA.md | Non-Android JVM Gradle/Maven project |
| Unknown / Other | references/generic.md | AGENTS-GUIDELINES-GENERIC.md | Unrecognized stack fallback |
Conflict Policy
Stack guidelines may only be stricter than the portable baseline on security, authorization, data protection, and verification. They never weaken baseline rules. Material conflicts must be surfaced to the user, never silently resolved.
Monorepo Collision Resolution
- If a package directory has its own
AGENTS.md, write guideline files next to it. - Otherwise, generate one guideline file per stack next to root
AGENTS.md, listing the directories it covers.
Execution Workflow
- Read Environment: Inspect existing
AGENTS.md,CLAUDE.md, manifests, and git status. Never overwrite uncommitted user changes. If not a git repo, note it. - Detect Stack:
- Run
python3 scripts/detect_stack.py --root . - Manual Fallback (if
python3missing): Check signature files from Routing Table manually. Treatpackage.jsonin PHP/WordPress/Android as secondary tooling.
- Run
- Confirm or Ask: Present detected stacks, versions, real commands, and target
paths in one concise message. If ambiguous, ask once. Support dry-run (
--dry-run), refresh, and remove (--remove) modes. Never write before confirmation. - Baseline Check: If
AGENTS.mdlacks the portable baseline, propose addingassets/baseline.md(150-250 words, merged additively). - Generate Guidelines:
- Generate each required guideline file for detected stacks (including full layer chains: e.g. Next.js generates JS, React, and Next.js files; WordPress generates PHP and WordPress files).
- Each layer contains only its own layer's rules and names lower layers in one line.
- Upsert content between marker pair:
<!-- stack-guidelines:start skill=1.1.0 verified=YYYY-MM-DD hash=<hash> -->usingscripts/upsert_section.py --file <path> --content-file <ref> --hash --substitute pm=<pm>. - Never alter text outside the markers.
- Link from AGENTS.md: Upsert managed section using the dynamic links generated by
detect_stack.py(or templatingassets/agents-md-section.mdwith only detected files) between<!-- stack-guidelines:start -->and<!-- stack-guidelines:end -->. Never link to ungenerated stack files. Place at the bottom by default (ask if top preferred). - Report: Summarize detected stacks, created/updated files, hash status, and unverified items. Re-running on unchanged code is byte-identical.
- Revision
87555db
- Last updated
- First committed
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.