Reorganize repository into tool-specific folders with optimized instruction formats

[Copilot]

Repository had flat structure with mixed content. Each LLM/tool has different file format requirements for instructions (Claude uses CLAUDE.md, Cursor uses .cursorrules, Copilot uses .github/copilot-instructions.md, etc.). Users needed ready-to-copy files.

Changes

Repository structure:

• Created 5 tool-specific folders: claude/, cursor/, github-copilot/, chatgpt/, gemini/
• Each contains main instruction file in tool's native format, setup README, commands/, and guidelines/
• Removed flat files from root; added navigation README

Instruction file optimization:

• Claude: CLAUDE.md with project context, quality methodologies, memory bank structure
• Cursor: .cursorrules with IDE-specific patterns, quality assurance tools
• GitHub Copilot: copilot-instructions.md with code quality standards, testing requirements
• ChatGPT: custom-instructions.md split into "what to know" / "how to respond" sections
• Gemini: GEMINI.md with hierarchical context support

Content organization:

• Same core content (quality tools, memory bank, technical specs, agile planning) in each folder
• Formatted per tool's conventions and limitations
• 9 command templates (5 Whys, RCA, Fishbone, Agile planning, etc.) in each commands/
• 6 reference documents in each guidelines/

Example Structure

/
├── README.md                     # Main navigation
├── claude/
│   ├── CLAUDE.md                # Auto-loaded by Claude
│   ├── commands/                # Reusable prompts
│   └── guidelines/              # Reference docs
├── cursor/
│   ├── .cursorrules             # Legacy format (still supported)
│   └── ...
└── github-copilot/
    ├── copilot-instructions.md  # Goes in .github/
    └── ...

Users can now copy the relevant folder's main instruction file directly into their project without modification.

Original prompt

Re-organize this repo and create a main read me, then child folders for each LLM/tool: claude, cursor, gemini, chatgpt, github copilot

Essentially we want to have contents that are ready to paste into any project. Since each tool/model has different ways of using rules files, research the latest docs and conform for each one.

It should roughly be the same content just formatted, organized, and optimized for each individual model

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.