Skip to content

Add AGENTS.md for Cursor Cloud development environment setup#74

Open
Arhan13 wants to merge 1 commit into
mainfrom
cursor/development-environment-setup-f948
Open

Add AGENTS.md for Cursor Cloud development environment setup#74
Arhan13 wants to merge 1 commit into
mainfrom
cursor/development-environment-setup-f948

Conversation

@Arhan13

@Arhan13 Arhan13 commented Mar 14, 2026

Copy link
Copy Markdown

Adds AGENTS.md with Cursor Cloud specific development instructions for future cloud agents.

What's included

  • Quick reference table for common tasks (deps, analyze, test, build, publish dry-run)
  • Gotchas: Dart workspaces, .env file requirement, no iOS on Linux, Android SDK auto-downloads, no backend services needed

Environment verification

All the following were verified successfully during setup:

Check Result
flutter analyze (helium_flutter) No issues
flutter analyze (helium_revenuecat) No issues
flutter analyze (helium_stripe) No issues
flutter test (helium_flutter) 22/22 passed
flutter test (helium_revenuecat) 1/1 passed
flutter test (helium_stripe) 12/12 passed
flutter pub publish --dry-run 0 warnings
flutter build apk --debug (example) Built successfully (147M)
Open in Web Open in Cursor 

Summary by CodeRabbit

Documentation

  • Added comprehensive guide for Helium Flutter SDK integration including prerequisites, environment setup, common development tasks with examples, platform-specific limitations, and testing information.

Co-authored-by: Arhan Choudhury <Arhan13@users.noreply.github.com>
@coderabbitai

coderabbitai Bot commented Mar 14, 2026

Copy link
Copy Markdown
📝 Walkthrough

Walkthrough

A new documentation file AGENTS.md is added, describing the Helium Flutter SDK integration for Cursor Cloud. It covers prerequisites, quick reference tasks with Flutter commands, working directories, and important gotchas including root workspace behavior, environment file requirements, iOS build limitations, and Android SDK handling.

Changes

Cohort / File(s) Summary
Documentation
AGENTS.md
New documentation file (28 lines) outlining Helium Flutter SDK integration prerequisites, Flutter command reference with working directories, and notable implementation gotchas.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Poem

🐰 A guide has sprouted from the dev's keen pen,
With Flutter tasks and gotchas explained—
No code was changed, just wisdom on the page,
For Cursor Cloud's new stage!
hop hop 📚✨

🚥 Pre-merge checks | ✅ 3
✅ Passed checks (3 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title accurately describes the main change: adding AGENTS.md documentation for Cursor Cloud development environment setup, which aligns with the file addition and PR objectives.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch cursor/development-environment-setup-f948
📝 Coding Plan
  • Generate coding plan for human review comments

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@salami salami marked this pull request as ready for review March 14, 2026 01:18

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 3

🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@AGENTS.md`:
- Line 18: The table row for "Analyze all" is missing the third column and
breaks the 3-column table; update the row in AGENTS.md (the line containing
"Analyze all | Run `flutter analyze` in each package directory") to include a
third cell for the "Working directory" column (for example "each package
directory" or "repo root"), ensuring the row has three pipe-separated cells to
match the table header.
- Line 5: The heading "Cursor Cloud specific instructions" should use a hyphen
for the compound adjective; update the text to read "Cursor Cloud-specific
instructions" wherever the heading or this phrase appears (e.g., the AGENTS.md
heading string) to correct grammar and maintain consistency.
- Line 26: Update the sentence that currently reads "**No iOS builds on Linux**:
iOS plugin builds and `helium_stripe` (iOS-only) cannot compile on Linux VMs.
Analysis and Dart unit tests still work." to accurately describe `helium_stripe`
as a mobile-only SDK supporting both iOS and Android: state that iOS plugin
builds cannot be performed on Linux VMs while clarifying that `helium_stripe`
supports Android as well (i.e., is not iOS-only) and keep the note that analysis
and Dart unit tests still work; reference the occurrence of the phrase "No iOS
builds on Linux" and the `helium_stripe` mention when making the edit.

ℹ️ Review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro

Run ID: d7bcd513-f2d7-4f74-8544-9754a80b6107

📥 Commits

Reviewing files that changed from the base of the PR and between 236b519 and 7b6c9ff.

📒 Files selected for processing (1)
  • AGENTS.md

Comment thread AGENTS.md

Flutter plugin wrapping native iOS (Swift) and Android (Kotlin) Helium SDKs. See `CLAUDE.md` for architecture and key principles, `CONTRIBUTING.md` for release/CI workflows.

## Cursor Cloud specific instructions

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟡 Minor

Add hyphen to compound adjective.

The phrase "Cursor Cloud specific instructions" should be "Cursor Cloud-specific instructions" when used as a compound adjective modifying a noun.

📝 Proposed fix
-## Cursor Cloud specific instructions
+## Cursor Cloud-specific instructions
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
## Cursor Cloud specific instructions
## Cursor Cloud-specific instructions
🧰 Tools
🪛 LanguageTool

[grammar] ~5-~5: Use a hyphen to join words.
Context: ...r release/CI workflows. ## Cursor Cloud specific instructions ### Prerequisites...

(QB_NEW_EN_HYPHEN)

🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@AGENTS.md` at line 5, The heading "Cursor Cloud specific instructions" should
use a hyphen for the compound adjective; update the text to read "Cursor
Cloud-specific instructions" wherever the heading or this phrase appears (e.g.,
the AGENTS.md heading string) to correct grammar and maintain consistency.

Comment thread AGENTS.md
| Install deps | `flutter pub get` | `/workspace` (root) |
| Analyze a package | `flutter analyze` | `packages/helium_flutter`, `packages/helium_revenuecat`, or `packages/helium_stripe` |
| Run tests | `flutter test` | Same as above |
| Analyze all | Run `flutter analyze` in each package directory |

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟡 Minor

Fix table column count.

This table row has only 2 cells but the table defines 3 columns (Task, Command, Working directory). The third column is missing, which breaks the table structure.

📋 Proposed fix
-| Analyze all | Run `flutter analyze` in each package directory |
+| Analyze all | Run `flutter analyze` in each package directory | N/A |

Or, if you want to be more specific:

-| Analyze all | Run `flutter analyze` in each package directory |
+| Analyze all | `flutter analyze` | Each package directory |
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
| Analyze all | Run `flutter analyze` in each package directory |
| Analyze all | `flutter analyze` | Each package directory |
🧰 Tools
🪛 markdownlint-cli2 (0.21.0)

[warning] 18-18: Table column count
Expected: 3; Actual: 2; Too few cells, row will be missing data

(MD056, table-column-count)

🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@AGENTS.md` at line 18, The table row for "Analyze all" is missing the third
column and breaks the 3-column table; update the row in AGENTS.md (the line
containing "Analyze all | Run `flutter analyze` in each package directory") to
include a third cell for the "Working directory" column (for example "each
package directory" or "repo root"), ensuring the row has three pipe-separated
cells to match the table header.

Comment thread AGENTS.md

- **Dart workspaces**: The root `pubspec.yaml` defines a workspace with all packages + example. A single `flutter pub get` at root resolves deps for everything — no need to run it per-package.
- **`.env` file required**: The example app expects `example/.env` (gitignored). Copy from `example/.env.example`. For CI/test purposes, empty string values are fine.
- **No iOS builds on Linux**: iOS plugin builds and `helium_stripe` (iOS-only) cannot compile on Linux VMs. Analysis and Dart unit tests still work.

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟡 Minor

Correct the platform support description for helium_stripe.

The description incorrectly states that helium_stripe is "iOS-only." The package actually supports both iOS and Android platforms. While iOS-specific components cannot build on Linux, the package itself is not limited to iOS.

Based on learnings, the helium_stripe package is strictly a mobile-only SDK supporting both iOS and Android.

📱 Proposed fix
-- **No iOS builds on Linux**: iOS plugin builds and `helium_stripe` (iOS-only) cannot compile on Linux VMs. Analysis and Dart unit tests still work.
+- **No iOS builds on Linux**: iOS plugin builds and the iOS components of `helium_stripe` cannot compile on Linux VMs. Analysis and Dart unit tests still work.
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
- **No iOS builds on Linux**: iOS plugin builds and `helium_stripe` (iOS-only) cannot compile on Linux VMs. Analysis and Dart unit tests still work.
- **No iOS builds on Linux**: iOS plugin builds and the iOS components of `helium_stripe` cannot compile on Linux VMs. Analysis and Dart unit tests still work.
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@AGENTS.md` at line 26, Update the sentence that currently reads "**No iOS
builds on Linux**: iOS plugin builds and `helium_stripe` (iOS-only) cannot
compile on Linux VMs. Analysis and Dart unit tests still work." to accurately
describe `helium_stripe` as a mobile-only SDK supporting both iOS and Android:
state that iOS plugin builds cannot be performed on Linux VMs while clarifying
that `helium_stripe` supports Android as well (i.e., is not iOS-only) and keep
the note that analysis and Dart unit tests still work; reference the occurrence
of the phrase "No iOS builds on Linux" and the `helium_stripe` mention when
making the edit.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants