3-minute install

Install a pack in under three minutes.

Every Aevrix Studio pack installs by copying two folders into your repo. No build step, no plugin marketplace, no config server. Below: install steps for Cursor, Claude Code, Cline, and Continue, plus a verification step so you know it worked.

Step 01 — Unzip

After purchase, Lemon Squeezy emails you a download link. Save the .zip and unzip it next to your project (not inside it — you only need two folders from it).

$ cd ~/Downloads
$ unzip aevrix-studio-flutter-riverpod-mastery-v1.0.0.zip
$ cd aevrix-studio-flutter-riverpod-mastery
$ ls
.cursor/    CLAUDE.md    LICENSE    README.md    reference/

Step 02 — Drop the rules in

Copy the .cursor/rules/ folder and append the pack's CLAUDE.md to yours. From your project root:

$ PACK=~/Downloads/aevrix-studio-flutter-riverpod-mastery
$ mkdir -p .cursor/rules
$ cp -r "$PACK"/.cursor/rules/* .cursor/rules/
$ cat "$PACK"/CLAUDE.md >> CLAUDE.md
$ ls .cursor/rules/*.mdc | wc -l
10

If you don't yet have a CLAUDE.md, just cp the pack's. If you already have one, append. The packs are written to compose with existing rules — they don't fight existing constraints, they tighten them.

Step 03 — Reload your editor

Each editor picks up the new rules differently. None of them require an extension install.

Step 04 — Verify

Open a fresh chat with your agent and ask for a feature the pack covers. With Pack 01 (Flutter + Riverpod), try:

"Add a simple async counter feature using Riverpod 2.4 — show
loading, error, and data states correctly. Include a widget test."

If the pack is active, the output will:

If none of that happens, the pack didn't load. Most common cause: the rules are in ~/.cursor/rules/ instead of <project>/.cursor/rules/. Project-local always wins.

Troubleshooting

Agent ignores the rules — what now?

Confirm rules are project-local at .cursor/rules/*.mdc (not in your home directory). Check the file frontmatter — at least one of alwaysApply: true or a globs: entry matching the file you're editing must be present. Cursor 0.45+ shows active rules in the bottom-right indicator.

Multiple packs at once — any conflict?

None expected — every pack scopes its rules with globs:. Pack 01 only triggers on **/*.dart; Pack 02 only on **/*.py; Pack 05 only on MCP server files. The flagship Pack 03 and Pack 04 are framework-agnostic and apply more broadly.

My team uses Cline only — can I skip Cursor?

Yes. Cline reads both .cursor/rules and CLAUDE.md. Either works on its own. The Cursor folder is just the canonical location.

How do I uninstall?

Delete .cursor/rules/<rule>.mdc files you added and remove the appended section from CLAUDE.md. Reload. Done.

Stuck?

Email [email protected] with the editor name and a screenshot of .cursor/rules/. Best-effort same business day.

See the packs Read a sample rule Compare packs