Restructure Repository with Modular Domain-Based README Files and Direct Access from main README

[swapna-shree]

This PR restructures the Engineering Prompts repository to improve clarity, navigation, and maintainability. Key changes include:

1. Introduced domain-based folders (api-development, backend-development, etc.), each with its own README.md.
2. Updated the main README.md with a Table of Contents linking to all domains.
3. Added new prompt chains using {placeholders} for tech-agnostic use for FullStack Development.
4. Created a new backend-development domain covering core backend tasks.
5. Revised contribution guidelines for easier onboarding.
   These updates aim to make the repository more modular, scalable, and developer friendly.

[swapna-shree]

Hi @Achanandhi-M , I've restructured the prompts and resolved all conflicts. Kindly review and let me know if anything needs changes. Thank you!

[pratik-mahalle]

Hey @swapna-shree, I can see that you have created the separate file for the separate section which I feel was unnecessary. Please change this

[swapna-shree]

i made the changes to prevent scrolling . I can add reference at the top to ensure easy access . what changes should i make ?

[pratik-mahalle]

Hey @swapna-shree, There was no need to create the separate section. I didn't understand why you did this. Can you please explain?

[swapna-shree]

Hey @pratik-mahalle, I created the separate domain-based folders to keep the prompts organized by topic and to make it easier for new contributors to navigate and add content as the repo grows. The idea was to make it more modular and scalable long-term.
But I get your point ,another option could be to keep everything in a single main README: put the Table of Contents at the top and include the detailed sections for each domain in the same file, instead of separate READMEs. That might feel simpler to read and maintain for now. What do you think?