feat: skill updates

[brandonjpierce]

• Add skill-creator to repo
• Update existing 3rd party skills and lockfile
• Add two new references to two skills
• Run skill-creator eval loop twice against accelint-react-best-practices

[belsrc]

Obviously fine with the .agents/.claude stuff. And the React addition. Slight concerned with the addition is best-practice. When auditkit is released, the versions in this code base will:

• Need to be deprecated as the skills are a part of it now (preferred)
• Will need to keep both in sync (more maintenance)

Also slightly torn on placement given the direct call outs to Next, Webpack and similar. And the likely need to have some sort of auditing specifically for bundling in general that doesn't exactly fit in with strict coding rules.

Thoughts?

[brandonjpierce]

Obviously fine with the .agents/.claude stuff. And the React addition. Slight concerned with the addition is best-practice. When auditkit is released, the versions in this code base will:

• Need to be deprecated as the skills are a part of it now (preferred)
• Will need to keep both in sync (more maintenance)

Also slightly torn on placement given the direct call outs to Next, Webpack and similar. And the likely need to have some sort of auditing specifically for bundling in general that doesn't exactly fit in with strict coding rules.

Thoughts?

I think the hard part here is that with essentially any modern js setup you have some bundler in play no matter what. So this is meant to be sort of a catch all since all bundlers currently behave the same way with regards to this example.