Split combined "VS Code & Cursor" links to reflect separate integration pages

[Copilot]

The quickstart documentation referenced "VS Code & Cursor" as a single link, but the repository maintains separate integration pages for VS Code and Cursor/VSCodium-based IDEs.

Changes

• Tip section (line 68): Split combined link into three separate links pointing to their respective integration pages:

  • VS Code → /docs/arkenv/integrations/vscode
  • Cursor → /docs/arkenv/integrations/open-vsx
  • JetBrains IDEs → /docs/arkenv/integrations/jetbrains

• Next steps cards (lines 149-158): Separated single card into two distinct cards with correct links

Screenshots

Updated tip section with separate links:

Separated integration cards:

Warning

Firewall rules blocked me from connecting to one or more addresses (expand for details)

I tried to connect to the following addresses, but was blocked by firewall rules:

• fonts.googleapis.com
  • Triggering command: /usr/local/bin/node /usr/local/bin/node /home/REDACTED/work/arkenv/arkenv/node_modules/.pnpm/next@16.1.1_@babel+core@7.28.5_@opentelemetry+api@1.9.0_@playwright+test@1.57.0_react-d_f42438f6717e44ec3de5d0c1806f5fb0/node_modules/next/dist/server/lib/start-server.js (dns block)

If you need me to access, download, or install something from one of these locations, you can either:

• Configure Actions setup steps to set up my environment, which run before the firewall is enabled
• Add the appropriate URLs or hosts to the custom allowlist in this repository's Copilot coding agent settings (admins only)

Original prompt

---

This section details on the original issue you should resolve

<issue_title>Fix "Integrate with VS Code & Cursor" links</issue_title>
<issue_description>They should be broken down to separate "Integrate with VS Code" and "Integrate with Cursor" links or one of them should be removed. We separated the integrations to 2.</issue_description>

Comments on the Issue (you are @copilot in this section)

• Fixes Fix "Integrate with VS Code & Cursor" links #651

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

Summary by CodeRabbit

• Documentation
  • Reorganized IDE integration guidance in the quickstart to list VS Code, Cursor, and JetBrains as separate options.
  • Separated combined integration cards into distinct items for improved clarity and navigation across integration sections.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[changeset-bot]

⚠️ No Changeset found

Latest commit: 6f6a7df

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[coderabbitai]

Walkthrough

Updated the quickstart documentation to separate combined "Integrate with VS Code & Cursor" card references into two distinct cards: "Integrate with VS Code" and "Integrate with Cursor" throughout the "Integrate with" and "Next steps" sections.

Changes

Cohort / File(s)	Summary
Documentation/Integration Restructuring apps/www/content/docs/arkenv/quickstart.mdx	Split combined VS Code & Cursor integration cards into separate entries with individual hrefs and descriptions; updated references in both primary "Integrate with" section and "Next steps" section.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Possibly related PRs

• yamcodes/arkenv#534: Separates arkenv integrations documentation to split VS Code and Cursor into distinct integration options.
• yamcodes/arkenv#223: Modifies the Quickstart docs' integration section with similar restructuring of integration card presentations.
• yamcodes/arkenv#155: Directly addresses splitting VS Code & Cursor integration cards in the quickstart documentation.

Poem

🐰 Two cards now dance where once was one,
VS Code and Cursor, each shining in the sun!
No longer bound together tight,
Each integration shines just right! ✨

Pre-merge checks and finishing touches

✅ Passed checks (5 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: splitting combined VS Code & Cursor links into separate ones, which aligns with the primary objective of the pull request.
Linked Issues check	✅ Passed	The pull request successfully implements issue #651 requirements by separating the combined 'VS Code & Cursor' link into distinct cards for VS Code and Cursor with correct separate links.
Out of Scope Changes check	✅ Passed	All changes in the pull request are directly related to separating the combined VS Code & Cursor links as specified in issue #651; no out-of-scope modifications detected.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch copilot/fix-integrate-links

---

📜 Recent review details

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 87c3929 and 6f6a7df.

📒 Files selected for processing (1)

• apps/www/content/docs/arkenv/quickstart.mdx

🧰 Additional context used

🧠 Learnings (10)

📚 Learning: 2025-12-23T07:09:57.130Z

Learnt from: CR
Repo: yamcodes/arkenv PR: 0
File: .github/copilot-instructions.md:0-0
Timestamp: 2025-12-23T07:09:57.130Z
Learning: Applies to **/*.{ts,tsx} : Use built-in validators (host, port, url, email) from ArkEnv when available instead of custom ArkType schemas

Applied to files:

• apps/www/content/docs/arkenv/quickstart.mdx

📚 Learning: 2025-11-24T16:03:45.295Z

Learnt from: CR
Repo: yamcodes/arkenv PR: 0
File: .cursor/rules/arktype.mdc:0-0
Timestamp: 2025-11-24T16:03:45.295Z
Learning: Applies to packages/arkenv/**/*.ts : Use ArkType's `type()` function to define schemas in environment variable definitions

Applied to files:

• apps/www/content/docs/arkenv/quickstart.mdx

📚 Learning: 2025-12-23T07:09:57.130Z

Learnt from: CR
Repo: yamcodes/arkenv PR: 0
File: .github/copilot-instructions.md:0-0
Timestamp: 2025-12-23T07:09:57.130Z
Learning: Applies to **/*.{ts,tsx} : For environment schema definition, use ArkType string literal syntax for enumerated values (e.g., "'development' | 'production' | 'test'")

Applied to files:

• apps/www/content/docs/arkenv/quickstart.mdx

📚 Learning: 2025-11-24T16:04:00.957Z

Learnt from: CR
Repo: yamcodes/arkenv PR: 0
File: .cursor/rules/coding-guidelines.mdc:0-0
Timestamp: 2025-11-24T16:04:00.957Z
Learning: Applies to **/*.{ts,tsx} : Use `ArkEnvError` for environment variable validation errors

Applied to files:

• apps/www/content/docs/arkenv/quickstart.mdx

📚 Learning: 2025-11-24T16:03:45.295Z

Learnt from: CR
Repo: yamcodes/arkenv PR: 0
File: .cursor/rules/arktype.mdc:0-0
Timestamp: 2025-11-24T16:03:45.295Z
Learning: Applies to packages/arkenv/**/*.ts : Keep environment variable schemas readable and TypeScript-like using ArkType syntax

Applied to files:

• apps/www/content/docs/arkenv/quickstart.mdx

📚 Learning: 2025-11-24T16:03:45.295Z

Learnt from: CR
Repo: yamcodes/arkenv PR: 0
File: .cursor/rules/arktype.mdc:0-0
Timestamp: 2025-11-24T16:03:45.295Z
Learning: Applies to packages/arkenv/**/*.ts : Leverage ArkType's built-in types (e.g., `string.host`, `number.port`) where possible in environment schemas

Applied to files:

• apps/www/content/docs/arkenv/quickstart.mdx

📚 Learning: 2025-12-23T07:09:57.130Z

Learnt from: CR
Repo: yamcodes/arkenv PR: 0
File: .github/copilot-instructions.md:0-0
Timestamp: 2025-12-23T07:09:57.130Z
Learning: Applies to **/*.{ts,tsx} : Use `createEnv(schema)` function (or default import as `arkenv`) to create validated environment objects in TypeScript

Applied to files:

• apps/www/content/docs/arkenv/quickstart.mdx

📚 Learning: 2025-11-24T16:03:45.295Z

Learnt from: CR
Repo: yamcodes/arkenv PR: 0
File: .cursor/rules/arktype.mdc:0-0
Timestamp: 2025-11-24T16:03:45.295Z
Learning: ArkType validates environment variables at runtime and TypeScript types are inferred from the schema definition

Applied to files:

• apps/www/content/docs/arkenv/quickstart.mdx

📚 Learning: 2025-12-05T20:33:10.676Z

Learnt from: yamcodes
Repo: yamcodes/arkenv PR: 498
File: apps/playgrounds/node/index.ts:2-2
Timestamp: 2025-12-05T20:33:10.676Z
Learning: ArkType 2.1.28+ supports Standard Schema specification, allowing interoperability with other Standard Schema-compliant validation libraries (e.g., Zod, Valibot) within the same schema definition

Applied to files:

• apps/www/content/docs/arkenv/quickstart.mdx

📚 Learning: 2025-11-24T16:03:45.295Z

Learnt from: CR
Repo: yamcodes/arkenv PR: 0
File: .cursor/rules/arktype.mdc:0-0
Timestamp: 2025-11-24T16:03:45.295Z
Learning: Applies to packages/arkenv/**/*.ts : Convert ArkType validation errors to `ArkEnvError` for user-friendly error messages that include variable name and expected type

Applied to files:

• apps/www/content/docs/arkenv/quickstart.mdx

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (2)

• GitHub Check: test-e2e (a11y)
• GitHub Check: test-e2e (e2e)

🔇 Additional comments (2)

apps/www/content/docs/arkenv/quickstart.mdx (2)

150-158: LGTM! Cards properly separated.

The split from a single combined card to two distinct cards correctly addresses issue #651. The card structure is consistent with other cards in the "Next steps" section, and the descriptions are clear.

---

68-68: All integration links are valid and correctly configured.

The Cursor link to /docs/arkenv/integrations/open-vsx is correct—this is the only Cursor integration page available in the repository. The VS Code and JetBrains links also resolve to their respective existing pages. No changes needed.

---

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

• X
• Mastodon
• Reddit
• LinkedIn

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

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Review	Updated (UTC)
arkenv	Ready	Preview, Comment	Dec 27, 2025 3:07pm

[yamcodes]

@coderabbitai review

[coderabbitai]

✅ Actions performed

Review triggered.

Note: CodeRabbit is an incremental review system and does not re-review already reviewed commits. This command is applicable only when automatic reviews are paused.