Add Intent-Driven JSDoc to splitter.MainContainer Example

Hi, I have recently known and started writing JSDoc based comments with docdash theme for my personal projects and would be great If I could know more about the intent-driven JSDoc style from the existing comments from src/core/Base.mjs file and would love to contribute to write similar intent-driven JSDoc style comment to examples/component/splitter/MainContainer.mjs file.

Could you please assign this documentation issue to me? I’d be happy to submit a PR with the updated comments.

Sure, and thanks for your interest! Hint: do not submit PRs before October 1, to ensure they count for the Hacktoberfest event.

I just finished: https://github.com/neomjs/neo/blob/dev/.github/WORKING_WITH_AGENTS.md

Which relates to: https://github.com/neomjs/neo/blob/dev/.github/AI_QUICK_START.md

While the task can be easily done manually, I encourage you to try out the new "AI Native" workflows.

Thank you for the advice, I will surely go through the both readme's and try to use the AI Native workflows.

You are welcome. Let me explain my own rationale a bit: It has definitely taken me longer to craft the intro ticket and subs, than it would have taken to just tell Gemini to resolve the tasks.

So, my goal is not to just delegate work, but to enable others to learn something new on the way. Since you mentioned that that you looked at core.Base: You will most likely agree, that it takes a lot of cognitive load to even understand parts of it. And yet, the class config system (combined with the Neo.mjs file) enables us to do great things.

Bigger picture: my goal is to enable others to get the most out of multi-threaded frontend development, without the need to fully understand the internal mechanics => making the platform/framework more accessible and approachable.

That makes a lot of sense, and I really appreciate your approach! I can see how the goal is not just to get things done, but to make the learning journey meaningful for everyone involved. I agree that understanding core.Base and the class config system takes a lot of mental load, but it’s amazing how it enables so much flexibility and power.

Also as you advised I was trying out the "AI Native" worflow, I stumbled upon the installation of google gemini cli and found out the package name was bit off in https://github.com/neomjs/neo/blob/dev/.github/AI_QUICK_START.md

Currently it is: npm i -g @google/generative-ai/cli

It should have been: npm i -g @google/gemini-cli

Would it be okay if I update this in my next PR?

Thanks for the heads up! Normally I would recommend to open a ticket (please do in the future!), but since this item affects to hacktoberfest onboarding experience for others, I will change & push it right away.

There is a Slack & a Discord Channel posted inside the parent ticket, in case you prefer a more direct communication (e.g. for asking questions).