skills.rest
JetBrains
JetBrainsOFFICIAL
Explore all skills by this author →
Website𝕏@jetbrainsGitHub

remote-dev

Structure IntelliJ remote development modules into shared, rpc, backend, and frontend.

20.4k|6.0k|Updated Sep 30, 2011
Search Tags:#development#platform#frontend-backend#remote#rpc#module-architecture#intellij
One-click install
npx skills add https://github.com/JetBrains/intellij-community --skill remote-dev
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: remote-dev
Source: https://github.com/JetBrains/intellij-community/tree/main/.agents/skills/remote-dev
Command: npx skills add https://github.com/JetBrains/intellij-community --skill remote-dev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Guidelines for structuring and developing IntelliJ remote development modules to help teams organize frontend, backend, and shared code when building Remote Development features.

Core Features & Use Cases

  • Module suffix conventions: frontend (.frontend), backend (.backend), shared (.shared), rpc (.rpc) modules.
  • RPC and reactive patterns guidance: interfaces, DTOs, and state-flow patterns for frontend-backend communication.
  • Module splitting and documentation: recommended structure for remote development projects and best practices.

Quick Start

Create a new remote development feature by establishing shared, rpc, backend, and frontend modules following the naming conventions.

Frequently Asked Questions about remote-dev

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I structure IntelliJ remote development modules for frontend and backend code?▼

You structure remote development modules by splitting code into shared, rpc, backend, and frontend components with corresponding suffix conventions. This enforces clear separation of concerns across frontend, backend, and shared layers.

What naming conventions should I use for IntelliJ remote development module splitting?▼

Module splitting uses .frontend, .backend, .shared, and .rpc suffixes to categorize code. These naming conventions ensure clear boundaries between frontend, backend, shared, and RPC layers in remote development projects.

How do RPC patterns work for frontend-backend communication in IntelliJ remote development?▼

RPC patterns define interfaces and DTOs to establish frontend-backend communication in remote development. Reactive state-flow patterns are applied to manage data synchronization across the separated modules.

When do I need a dedicated rpc module for IntelliJ remote development features?▼

A dedicated rpc module is needed when building remote development features that require frontend-backend communication. It isolates interfaces and DTOs, ensuring both frontend and backend modules depend on a shared communication contract.

Can I use this remote development module structure for non-IntelliJ platform projects?▼

This module structure targets IntelliJ platform teams building remote development features. While the module splitting principles are generally applicable, the naming conventions and patterns are specifically tailored for IntelliJ platform architecture.

Related Skills

Explore More Software Engineering Skills→
LAF-USLAF-US

spring-boot-scaffolding

Generate a multi-module Spring Boot project scaffold with Maven and Java 21.

Official
Intermediate
Sheon-SSheon-S

ignition-rpc-and-endpoints

Codify gateway endpoints, RPC contracts, and DTO structures for Ignition SDK modules.

Community
Intermediate
asitawayukiasitawayuki

frontend-patterns

Provide standardized React and Next.js frontend development patterns for component composition and state management.

Community
Advanced
willyu1007willyu1007

organize-frontend-codebase

Organize frontend codebases into feature or module directories with public exports.

Community
Intermediate