Best use case
phpstorm is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
PhpStorm PHP IDE with debugging. Use for PHP development.
Teams using phpstorm should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/phpstorm/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How phpstorm Compares
| Feature / Agent | phpstorm | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
PhpStorm PHP IDE with debugging. Use for PHP development.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# PhpStorm PhpStorm is essential for modern PHP. It understands **Laravel** Facades, **Symfony** Dependency Injection, and **Doctrine** queries. ## When to Use - **PHP**: It is practically mandatory for professional PHP dev. - **Blade / Twig**: Excellent support for template engines. - **Database**: Integrated SQL tools are fantastic. ## Core Concepts ### Composer Integration Manages dependencies and `composer.json` synced with the project model. ### Pest / PHPUnit Visual test runner integration. ### Remote Development (SSH) Edit files directly on the server (if you must) or use Deployment configurations. ## Best Practices (2025) **Do**: - **Install Laravel Idea**: A paid plugin but transforms the Laravel experience. - **Use Xdebug**: PhpStorm makes setting up Step Debugging easier than any other tool. - **Type Hinting**: Use the IDE to add return types and strict types to modernize legacy code. **Don't**: - **Don't disable inspections**: They find bugs (SQL injection risks, undefined variables) instantly. ## References - [PhpStorm Documentation](https://www.jetbrains.com/phpstorm/documentation/)
Related Skills
template
Expert [skill-name] assistance covering [feature 1], [feature 2], and [feature 3]. Use when [working with X], [debugging Y], or [implementing Z].
zsh
Zsh shell with oh-my-zsh. Use for terminal shell.
zed
Zed high-performance collaborative editor. Use for fast editing.
xcode
Xcode Apple development IDE with simulators. Use for iOS/macOS development.
webstorm
WebStorm JavaScript IDE with debugging. Use for web development.
webpack
Webpack module bundler with loaders and plugins. Use for bundling.
warp
Warp modern terminal with AI. Use for terminal work.
vscode
Visual Studio Code editor with extensions and debugging. Use for code editing.
vite
Vite fast build tool with HMR. Use for modern frontend builds.
visual-studio
Visual Studio IDE for Windows with debugging and profiling. Use for .NET development.
vim
Vim text editor with motions, macros, and plugins. Use for terminal editing.
turbopack
Turbopack Rust-powered bundler. Use for fast builds.