01
Understand JetBrains project context
Inspect modules, SDKs, language levels, build files, source roots, generated content, shared .idea settings, run configurations, and required plugins.
JetBrains IDE projects
CategoryDeveloper Tools
JetBrains Codex Skills
JetBrains Codex Skills help Codex work with repositories used across IntelliJ IDEA, PyCharm, WebStorm, GoLand, Rider, PhpStorm, RubyMine, and other JetBrains IDEs. Download the skills for project-aware coding, build and run configuration, inspections, shared settings, refactoring, and plugin work without treating private IDE state as source code.
JetBrains IDEsProject configurationInspectionsIDE plugins
01
02
03
04
05
06
07
08
09
02
03
04
05
06
07
08
09
task: complete jetbrains ide projects task
inspect:
- requirements and context
- existing standards
- failure and edge cases
verify: outputs + checks + handoffWhy a specialist workflow matters
A repository can build on one machine and still be painful in the IDE when SDKs, modules, generated sources, run targets, inspections, and shared configuration are misunderstood.
JetBrains products share platform concepts but differ by language, build system, plugins, and edition. Repository files and declared tooling remain the source of truth.
These skills help Codex detect the active JetBrains product, separate shareable settings from personal workspace state, and verify changes through both project commands and IDE-relevant checks.
What the downloadable skills can do
What JetBrains Codex Skills can help accomplish
02
Develop across supported stacks
Work in Java, Kotlin, Python, JavaScript, TypeScript, Go, .NET, PHP, Ruby, and mixed repositories according to the declared IDE and tooling.
03
Use quality and navigation signals
Resolve symbols, trace usages, plan refactors, address compiler or inspection results, maintain formatting, and preserve framework integration.
04
Build JetBrains plugins
Create IntelliJ Platform plugin metadata, actions, services, tools, settings, inspections, intentions, tests, compatibility ranges, and packages.
A repeatable working process
How the jetbrains ide projects workflow moves from request to verified result
The steps keep context, implementation, and verification visible so the result can be reviewed and repeated.
workflow.statusREADY
Context → Plan → Work → Verify
01
Identify the IDE and project model
Record the JetBrains product and version, languages, SDKs, build systems, modules, plugins, generated files, and shared settings.
02
Trace code through repository evidence
Follow symbols, dependencies, configuration, framework wiring, resources, tests, and generated sources before editing.
03
Make a scoped project-aware change
Match existing style, avoid personal workspace files, update build configuration carefully, and preserve multi-IDE compatibility where required.
04
Verify with project and IDE checks
Run builds and tests, inspect sync implications, address supplied inspections, and exercise relevant run or plugin sandbox targets.
Useful across real projects
Where JetBrains Codex Skills fit
The workflow adjusts to the project, audience, tools, and risk while preserving the same quality standard.
JVM projects
Develop Java and Kotlin applications, libraries, frameworks, Gradle or Maven builds, tests, and shared run configurations.
Web projects
Work with JavaScript, TypeScript, frontend frameworks, Node tooling, package managers, browser tests, and WebStorm conventions.
Polyglot repositories
Navigate services and tooling across Python, Go, .NET, PHP, Ruby, JVM, web, and infrastructure modules.
JetBrains plugin projects
Build extensions for the IntelliJ Platform with declared APIs, compatibility, tests, sandbox runs, and packaging.
Common requests
Tasks these skills can handle
Start with one defined outcome and provide the source material, constraints, and checks that matter.
01Understand a JetBrains project
02Fix SDK or project import issues
03Implement a repository change
04Create a shared run configuration
05Respond to inspection results
06Refactor across modules
07Manage required plugins
08Build a JetBrains IDE plugin
Who benefits most
Who Is This For?
These skills are designed for people who need dependable jetbrains ide projects work with a visible process.
Teams using JetBrains IDEs
Keep shared project configuration useful without committing local or personal state.
Polyglot developers
Move across services while respecting each language, module, build system, and IDE model.
JetBrains plugin developers
Create and test extensions against explicit platform versions and compatibility ranges.
Developers onboarding to large repositories
Understand modules, SDKs, generated code, run targets, plugins, and quality checks faster.
Good to know:
The skills primarily work with repository files and commands. Live IDE menus, licensed features, personal settings, plugin installation, and UI state require the user's JetBrains environment or an approved integration.
Set up the workflow
Installation Guide
Install the complete skill folder and add the project-specific context before beginning.
Download and extract the JetBrains skills
Keep SKILL.md with project, language, build, inspection, shared-setting, and plugin-development guidance.
Use project scope
Install with the repository so the skills can follow its declared IDE, modules, SDKs, and build systems.
Document the JetBrains setup
State product, edition, version, plugins, SDKs, languages, build tools, generated sources, and supported operating systems.
List verification procedures
Provide sync, build, test, format, inspection, run, debug, sandbox, packaging, and compatibility checks used by the team.
Before you download
Frequently Asked Questions
Practical answers about capabilities, limits, setup, and review.
Which JetBrains IDEs are supported?+
The workflow can adapt to IntelliJ IDEA, PyCharm, WebStorm, GoLand, Rider, PhpStorm, RubyMine, and related products when the active environment is stated.
Can the skills control the IDE directly?+
Not by default. They work with repository files and commands unless a supported live IDE connection is available.
Will they edit .idea files?+
Only settings intentionally shared by the repository. Workspace, history, credentials, and machine-specific state should remain private.
Can they fix inspection warnings?+
Yes, when inspection output and project context are supplied. Changes are still verified with the repository's build and tests.
Can they build JetBrains plugins?+
Yes. They cover IntelliJ Platform APIs, extensions, UI, testing, compatibility, sandbox execution, and packaging.
Make the work repeatable
Give Codex a JetBrains-aware workflow that respects the IDE product, project model, repository tooling, and shared configuration boundaries.
Clear context. Purposeful work. Relevant checks. A result others can understand.