Investigate migrating our `general-wasp-knowledge` doc to be a set of custom `rules.md` files

[vincanger]

Instead of adding an import the the user's CLAUDE.md file, we could instead just copy a set of rules.md files to the the local project's .claude/rules directory. Rules can be path-specific, easier to maintain, and also can be used in Cursor projects (a nice win-win).

https://code.claude.com/docs/en/memory#modular-rules-with-claude/rules/

[Martinsos]

Note: these can be a symlink. So this rule could just be a symlink to the rules file we have in our plugin, therefore ensuring it gets updated together with the plugin, and making it clear it is not "user owned", but "plugin owned".