idea-debug-tools-dev-guidelines

Document development guidelines for Maven multi-module and IntelliJ IDEA plugin projects.

Updated Feb 11, 2026
One-click install
npx skills add https://github.com/ayuayue/skills --skill idea-debug-tools-dev-guidelines
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: idea-debug-tools-dev-guidelines
Source: https://github.com/ayuayue/skills/tree/main/idea-debug-tools-dev-guidelines
Command: npx skills add https://github.com/ayuayue/skills --skill idea-debug-tools-dev-guidelines

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This guide consolidates development standards, architecture decisions, and workflow practices to streamline work on the Debug Tools project, reducing onboarding time and inconsistencies.

Core Features & Use Cases

  • Covers project structure, module dependencies, coding standards, build and test workflows, and contribution expectations across Maven, Gradle, and IntelliJ IDEA plugin contexts.
  • Helps new contributors quickly align with project conventions and ensures consistent PR reviews.

Quick Start

Read this guide to align your development workflow with the project standards.

Frequently Asked Questions about idea-debug-tools-dev-guidelines

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

FAQPage Schema
What development guidelines are required for contributing to an IntelliJ IDEA plugin?

Development guidelines for IntelliJ IDEA plugins require standardized project structure, specific coding conventions, and defined build workflows. This guide codifies expectations for module organization, naming conventions, and formatting rules to ensure consistent PR reviews.

How do I set up a Maven multi-module project for IntelliJ plugin development?

Setting up a Maven multi-module project for IntelliJ plugin development involves configuring module dependencies and structuring the project according to specific architecture decisions. The guide outlines build workflows and testing requirements to streamline this setup.

Does this guide cover coding standards and architecture decisions for Java plugin development?

Yes, this guide covers Java coding standards and architecture decisions for plugin development. It provides comprehensive documentation on formatting rules, naming conventions, and common development patterns to align contributors with project expectations.

What is the best way to align my workflow with project conventions for a debug tools plugin?

The best way to align your workflow with project conventions is to follow the consolidated development standards and testing requirements documented in the guide. This reduces onboarding time, minimizes inconsistencies, and ensures your contributions meet PR review criteria.

Can I use Gradle workflows alongside Maven for IntelliJ plugin builds?

The guide covers build and test workflows across Maven, Gradle, and IntelliJ IDEA plugin contexts. It defines how to manage project structure and module dependencies within these build systems to maintain consistent contribution processes.

Why do we need standardized project structure and naming conventions for IntelliJ plugins?

Standardized project structure and naming conventions are needed for IntelliJ plugins to reduce onboarding time and prevent inconsistencies. Codifying these development patterns ensures that new contributors quickly align with project expectations and architecture decisions.