PHPStan configuration, error fixing, and baseline management for WordPress projects.
Works with
Handles WordPress-specific typing patterns: REST endpoints with WP_REST_Request , hook callbacks with accurate @param types, database results, and Action Scheduler job arguments
Manages third-party plugin/theme class resolution via stubs ( php-stubs/woocommerce-stubs , php-stubs/acf-pro-stubs ) and targeted ignore patterns
Provides deterministic PHPStan discovery, configuration validation, baseline g
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionwp-phpstanExecute the skills CLI command in your project's root directory to begin installation:
Fetches wp-phpstan from wordpress/agent-skills and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate wp-phpstan. Access via /wp-phpstan in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
0
total installs
0
this week
1.1K
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
1.1K
stars
Use this skill when working on PHPStan in a WordPress codebase, for example:
phpstan.neon / phpstan.neon.distphpstan-baseline.neonwp-project-triage output (run first if you haven't)node skills/wp-phpstan/scripts/phpstan_inspect.mjsPrefer the repo’s existing composer script (e.g. composer run phpstan) when present.
szepeviktor/phpstan-wordpress or php-stubs/wordpress-stubs are effectively required for most WordPress plugin/theme repos. Without it, expect a high volume of errors about unknown WordPress core functions.
composer.dependencies in the inspect report).references/third-party-classes.md).phpstan.neon for WordPress projectspaths focused on first-party code (plugin/theme directories).vendor/, node_modules/, build artifacts, tests unless explicitly analyzed).ignoreErrors entries narrow and documented.See:
references/configuration.mdPrefer correcting types over ignoring errors. Common WP patterns that need help:
WP_REST_Request<...>@param types for callback args$args array shapes for job callbacksSee:
references/wordpress-annotations.mdWhen integrating with plugins/themes not present in the analysis environment:
php-stubs/woocommerce-stubs, php-stubs/acf-pro-stubs).ignoreErrors patterns for the specific vendor prefix.See:
references/third-party-classes.mdSee:
references/configuration.mdcomposer run ... or vendor/bin/phpstan analyse).ignoreErrors to ensure patterns are not masking unrelated issues.paths, add excludePaths, start at a lower level, then ratchet upMake data-driven prioritization decisions faster
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Prerequisites
Time Estimate
30-60 minutes to see productivity improvements
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid when
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
mattpocock/skills
parcadei/continuous-claude-v3
cursor/plugins
ailabs-393/ai-labs-claude-skills
ailabs-393/ai-labs-claude-skills
pproenca/dot-skills
wp-phpstan is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
Registry listing for wp-phpstan matched our evaluation — installs cleanly and behaves as described in the markdown.
wp-phpstan reduced setup friction for our internal harness; good balance of opinion and flexibility.
wp-phpstan fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
wp-phpstan reduced setup friction for our internal harness; good balance of opinion and flexibility.
We added wp-phpstan from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
Keeps context tight: wp-phpstan is the kind of skill you can hand to a new teammate without a long onboarding doc.
Registry listing for wp-phpstan matched our evaluation — installs cleanly and behaves as described in the markdown.
wp-phpstan is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
wp-phpstan is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
showing 1-10 of 53