Agentic development

[albx]

With PR #96 I added a first version of skills, instructions and agent which (ideally) will help with the development of bitblazor.
In the main branch now there are:

• two instructions files: one related to blazor development and one to accessibility aspects (which must be first-citizen in this library)
• a set of skills related to the end-to-end development of the components (including tests, stories and documentation) and two skills which allows to write and read issues from gitrhub via GitHub CLI.
• a set of agents which defines some roles that I think could be useful to help with the full development lifecycicle.

Important

Since this is a first release of the feature all the instructions, skills and agent may change in the future.
If you notice some changes of behaviors which will break existing workloads, feel free to contact me or open issues and PRs.

Agents

I defined the following agents:

• Project manager: this agent is responsible to build the backlog on github, open issues and check for existing issues to avoid duplicate.
• Software architect: help with the design of a specific feature in term of defining the structure of the components related to the feature and how they will communicate and interact. It does not write any code, it just produces a markdown report
• Developer: this is the agent which writes code. It should read the requirements and implement the feature. It writes also tests, stories and documentation
• Code reviewer: this agent is the one who reviews components and features and produces a report with the result of this review. It's not allow to write any code.

What's next?

After this first release, the idea is to make some experiments, collect feedback and try to improve the quality of this aspect.

So, if you want to give it a try, feel free to write your feedbacks, open issues or PRs in order to improve the developer experience of BitBlazor.