Guidance on developer tooling

Problem/Motivation

Being trained on the corpus of the internet, most LLMs will not natively know about things like:

- DDEV
- Drush
- …

Let’s help them be smarter about this :)

Much better starting description of scope from @yautja_cetanu at #3585542-9: [meta] Roadmap to MVP Release:

Starting DevOs - Get the Dev ops working for starting a new project from scratch or using an existing repo. This includes having everything in ddev. Doing best practises for gitignore. Creating a new repo in github or gitlab, handling authentication of keys and API keys etc properly (What goes in ddev config files), handling settings.php correctly according to best practises. Handling Config management properly. Handling a Dev, Test, Staging Environment so it can do things in production and others can work on it. Use Git worktrees or branches correctly. Figure out where to put plans and agents.md files, etc so others can work on it. This should allow people to start a project from scratch but then push things so others can work on it. Or take an existing site (Drupal CMS) and then add AI Best practises to it and push things, or take an existing site that has already used AI Best practises and get going.

Steps to reproduce

Proposed resolution

Remaining tasks

User interface changes

API changes

Data model changes