diff --git a/guides/20260531_ide_your_rules.md b/guides/20260531_ide_your_rules.md
new file mode 100644
index 00000000..4ca22923
--- /dev/null
+++ b/guides/20260531_ide_your_rules.md
@@ -0,0 +1,130 @@
+# Your IDE, Your Rules: Universal Access for AI Development
+
+AI development should not force you into a browser-only workflow.
+
+Developers already have preferred editors, existing tooling, and established habits. The best AI infrastructure should fit into that reality instead of making everyone rebuild their workflow from scratch.
+
+This guide explains why native IDE integration matters, how remote development helps, and where the future is heading.
+
+## Breaking free from browser-only limitations
+
+Browser-only tools can be convenient, but they also create friction:
+
+- slower context switching
+- harder access to local repo tools
+- less control over extensions and config
+- awkward copy/paste workflows
+- weaker integration with test and build systems
+
+If the developer already lives in an IDE, forcing them into a browser can slow them down.
+
+## Native integration with popular IDEs
+
+The strongest AI tools usually meet developers where they already work.
+
+### Why this matters
+
+- faster adoption
+- less workflow disruption
+- easier access to local files and terminals
+- better support for existing shortcuts and habits
+
+A good AI workflow should work with:
+
+- VS Code
+- JetBrains IDEs
+- Cursor
+- Neovim/Vim
+- remote code environments
+
+## Supporting AI-enhanced IDEs
+
+Modern AI development is not just about text generation. It’s about using the IDE as the center of the workflow.
+
+That means supporting:
+
+- inline suggestions
+- code chat
+- repo-aware edits
+- test execution from the editor
+- jump-to-definition and reference navigation
+- remote environment sync
+
+The more the tool respects the IDE, the less it feels like an add-on.
+
+## Remote development best practices
+
+Remote development becomes important when teams need:
+
+- reproducible environments
+- access to heavyweight dependencies
+- shared team templates
+- consistent setup across contributors
+- secure access to private systems
+
+### Good remote dev habits
+
+- keep the environment reproducible
+- use a standard startup script
+- expose only required ports and services
+- automate dependency installation
+- document the common commands
+- keep secrets out of the image
+
+Remote development should feel like a local workflow, just with better consistency.
+
+## Feature comparison table
+
+| Capability | Browser-only tools | IDE-native tools |
+|---|---:|---:|
+| Inline editing | Limited | Strong |
+| Local repo access | Awkward | Strong |
+| Terminal integration | Weak | Strong |
+| Workflow speed | Medium | Strong |
+| Customization | Limited | Strong |
+| Remote dev support | Medium | Strong |
+| Multi-file editing | Medium | Strong |
+| Validation loop | Medium | Strong |
+
+## Future trends
+
+A few trends are likely to shape the next phase of AI development tools.
+
+### 1. More hybrid environments
+
+Users will expect tools to work both in the IDE and in remote environments.
+
+### 2. More context-aware workflows
+
+Tools will need to understand repo structure, tests, and environment state, not just the prompt text.
+
+### 3. More collaboration between humans and agents
+
+Developers will increasingly split work into:
+
+- human planning
+- agent execution
+- human review
+
+### 4. More enterprise control
+
+Teams will want better access controls, compliance, and environment standardization.
+
+## Why Daytona fits this future
+
+Tools like Daytona fit the future of AI development because they support:
+
+- reproducible environments
+- remote workspace access
+- IDE-friendly workflows
+- developer control over where work runs
+
+That means teams can keep their preferred IDEs while still getting the benefits of isolated, standardized AI dev environments.
+
+## Final takeaway
+
+The future of AI development is not browser-only.
+
+Developers want to keep their IDEs, their shortcuts, and their existing habits. The winning tools will be the ones that support that reality instead of fighting it.
+
+Native IDE integration, remote development, and reproducible environments are the path forward.