Sounds very interesting! I have a lot on my plate at the moment as well, but I could spare a few hours per week for a promising project.

Is there a GitHub repo or something similar?

Sounds awesome! Where can I sign up?

Oh boy, you're not talking about running different frameworks in iframes and plugging them together, but about running multiple frameworks in a single browsing context?

That's the most interesting part! The state needs to be serializable, though.

Is there a good way to test at least some of those requirements automatically in CI? I only know of Axe but that won't test for screen reader interoperability for example.

I found people calling the second one "children pattern". This concept isn’t React specific, though, probably not even JavaScript specific. There must be framework & language agnostic terms. But which?

- config vs. extension point pattern?
- props vs. slots pattern?
- ?

Copilot: "I cannot work properly without an instruction file."

Also Copilot: "Just let me write the instruction file myself."

Want step-by-step guidance + templates to create your own copilot_instructions.md? I wrote a detailed guide to help you get started:
georg.dev/blog/05-bett...

Agent mode *bonus* tip: Enable auto-approval for tools by adding "chat.tools.autoApprove": true to your settings.json. Just be aware that you’re giving Copilot a free pass. Use it wisely! 😅

Agent mode tip: Add clear instructions for automating checks like "npm run lint" or "npm run test". With these in your file, Copilot Agent can run the commands, fix errors, and iterate until all checks pass without constant back-and-forth.

Most advice skips this: Be model-specific. If Copilot repeatedly makes the same mistakes (e.g., overly verbose code or missing edge cases), include correctional hints in your file. Example: "Focus on simplicity, avoid over-comprehensive solutions."

Some essential sections to include:

- Summary: What the project does, briefly.
- Terminology: Domain-specific terms Copilot can’t infer.
- Architecture: Key files and why things are structured this way.
- Task planning: Steps Copilot should follow before coding.

Most devs either skip copilot_instructions.md or fill it with generic fluff. But irrelevant instructions waste Copilot’s context space and reduce output quality. Focus on non-obvious details: unique constraints, domain rules, and project specifics.

Absolutely. It feels like we spent decades talking about 'deep work' and 'flow state' only to abandon those concepts the moment AI companions showed up.

haha nice one :)