feat: add Cursor plugin support

[alvaroarmijos]

Description

Adds Cursor IDE support to the VGV AI Flutter Plugin. This includes:

• .cursor-plugin/plugin.json — Cursor plugin manifest that maps skills, hooks, and MCP server configuration so Cursor can discover and load the plugin
• README.md — adds a dedicated Cursor installation section with the /add-plugin vgv-ai-flutter-plugin chat command and a link to the Cursor Marketplace
• CLAUDE.md — updates the project overview and repository structure to reflect that this plugin supports both Claude Code and Cursor

Closes #48

Type of Change

• New feature (feat)
• Bug fix (fix)
• Code refactor (refactor)
• Documentation (docs)
• CI change (ci)
• Chore (chore)

[ryzizub]

We have couple of important stuff like hooks that are not addressed here and those might not be supported by cursor. But good start @alvaroarmijos ! ❤️

[alvaroarmijos]

@ryzizub Correct! This initial PR focuses on enabling skills and MCP server support for Cursor as a first step. Hooks compatibility will be addressed in a follow-up PR. Cursor uses a different hook event format and payload structure than Claude Code, so those scripts will need adaptation before we can wire them up.

[ryzizub]

Moving this to draft as there are some extra steps we are discussing internally

[RuiMiguel]

@ryzizub Correct! This initial PR focuses on enabling skills and MCP server support for Cursor as a first step. Hooks compatibility will be addressed in a follow-up PR. Cursor uses a different hook event format and payload structure than Claude Code, so those scripts will need adaptation before we can wire them up.

I'm curious to see the difference between hooks. I wouldn't like to do them twice and maintain nearly similar scripts, but if they use different payload we would need to adapt it

[RuiMiguel]

Also linked to this other issue #66 we must document Cursor hooks at its own md document. That's a good example of what Claude and Cursor should include into their owns md files

[ryzizub]

We would need to add cursor marketplace setup into https://github.com/VeryGoodOpenSource/very-good-claude-code-marketplace am i wrong?

[ryzizub]

Closing in favor of the open-standard approach (epic #51).

We've decided not to maintain per-harness plugin manifests. Instead we publish skills to the open agent-skills standard (.agents/skills/ + skills.sh, #50). Cursor reads .agents/skills/ directly, so it picks up the skills for free once we publish — no dedicated .cursor-plugin/ manifest to maintain. Cursor is now tracked as an experimental-tier consumer in #48.

Thanks for the work here — the manifest-mapping done in this PR was useful for understanding the tradeoffs that led to this decision. Reopen or reference it if we ever promote Cursor to a dedicated tier.