Add AI Development Methodology to Community Guides

[Korner83]

Add AI Development Methodology to Educational Resources > Community Guides

Adds AI Development Methodology (CC BY 4.0) to the Community Guides subsection.

What it is

A portable markdown + git methodology for software projects where humans and AI agents collaborate as peers. Twelve docs + CLAUDE.md / AGENTS.md / AUTONOMOUS_LOOP.md templates. Distilled from running a real production project with mixed human and AI-agent contributors.

Covers:

• Four planning layers (strategy → pillars → epics → items)
• Three discipline overlays (working principles, Definition of Done, lessons-learned memory)
• File-based locks with TTL so two agents don't collide on the same item
• An actual-UI fix-test loop (because "tests pass" doesn't mean "the page renders")
• Cross-AI validation as a final gate
• A two-tier memory system

Why it fits Community Guides

The Community Guides subsection already lists practical Claude Code workflow guides (the "Everything You Need to Know" guide, the "40+ Tips" collection, Sankalp's two-part Claude Code experience posts). This methodology fits the same slot: a hands-on guide for using Claude Code effectively on real projects, with a ready-to-use templates/CLAUDE.md that's been battle-tested in production. It complements the existing entries — those cover tips and setup; this covers project-level structure and discipline.

The methodology is tool-agnostic (it explicitly works with Codex, Cursor, Aider, Continue, or any agent that reads project-instruction files), but Claude Code is the primary tool it was developed against and the templates/CLAUDE.md is one of the three first-class templates shipped.

Compliance with contributing.md

• ✅ Format: - [Name](URL) - Description. ending with a period
• ✅ Open source (CC BY 4.0)
• ✅ Public repository
• ✅ Actively maintained — v1.3.1 just shipped (2026-05-24)
• ✅ Meaningful functionality — ~7,100 lines across 19 files, complete templates
• ✅ Good documentation — comprehensive README + per-doc walkthroughs
• ✅ Added at the bottom of the relevant category (Community Guides)
• ✅ One PR for one entry

Honest disclosure

Solo-maintained per the documented exception (the project includes a section explaining why solo maintenance is intentional for a methodology). Roughly 0 stars at submission — just shipped publicly. I'm submitting because the methodology fits this list's Community Guides scope, not to game star counts.