update AI info (skills, AGENTS.md, etc.)

[vincanger]

Summary

• Add skills and mcp settings based on agent standards (Agent Skills & AGENTS.md -> CLAUDE.md)
• Decided on copying the plugin skills to .claude/skills and using AGENTS.md instead of installing plugin (this means we would have to copy the plugin folders over to open saas whenever we update the CC plugin until we come up with a better way)
• Update vibe coding guide documentation
• Adjust LP messaging slightly

Fixes #584 and #601

[Martinsos]

@vincanger Cool effort here!

I tihnk we should do something like this, the main thing though is that it feels incosistent.

So here, we offer an AGENTS.md (rules) and .claude/skills (skills), so that anybody using OpenSaas, has an easier time using AI with it. Ok, motivation is clear.

Those however are not OpenSaas-specific rules or skills, but Wasp-specific ones, and they are the same as in our CC Wasp plugin. This is the first problem -> if they are not OpenSaaS speciifc, why are we offering them only in OpenSaas, why not in other templates (e.g. those taht come with Wasp)?
It also means they are out of Wasp's "lifecycle", so I can imagine it will be easy to froget to update them as we update Wasp.

Second, we are duplicating them from CC plugin, as you said your self is a problem. That will be tricky to maintain.

My thinking is, if we want to do this, let's do it right, so we can maintain it properly.
First of all, if these are not OpenSaaS specific, I wouldn't have them in OpenSaas.
OK, let's say we want to make it easy for people to get these in any Wasp project. Solution I can think of is that they run a command and bam, these are added to their Wasp project. Maybe wasp ai:setup? wasp ai:init? Something. So it could be part of Wasp CLI -> wasp produces useful AI rules and stuff for you. Maybe also informs you about CC plugin -> asks if you want CC plugin, or just copy-pasted stuff.
If not part of wasp CLI, it could be a separate thing, maybe a small npm package that one can run with npx wasp-ai-setup. Then however it can't be versionsed together with the CLI, but that might be just fine.
There is still a problem that we duplicate knowledge between CC Wasp plugin, and these standalone rules and skills. But maybe we don't have to -> can't we just copy them from CC Wasp plugin?

[Martinsos]

Commendted above! Let's make this more maintainable.

[Martinsos]

We are mixing ai and vibe coding here. Vibe means you are not checking the code at all. We should udpate the title and make it about AI coding, not vibe coding, since this is useufl for all peopel using AI (which is eveyrbody hah), not just "vibe" coders.

[Martinsos]

what does it mean they can be used as-is after they've been properly referenced?

[Martinsos]

Maybe explain what is this about, I feel it is missing context.