wp-phpstan-stubslisted

# PHPStan Stubs Scaffold > **Model note:** File scaffolding from a fixed template — `haiku` handles end-to-end. Only reach for `sonnet` if the source plugin has complex namespace hierarchies needing stub organization decisions. Scaffold a complete PHPStan stubs package from scratch, following the `my-org/phpstan-freemius-stubs` standard structure. ## When to use - "Create stubs for X", "new stubs package", "scaffold phpstan stubs", "add stubs for plugin/composer package". **Not for:** Configuring `phpstan.neon` or generating baselines — use the official `wp-phpstan` skill. Adding PHPStan to a plugin that already has stubs installed. ## References - `references/wp-org-api.md` — WP.org plugin API, version listing, download URLs, cleanup patterns - `references/packagist-api.md` — Packagist API, version filtering, source/composer.json update pattern - `references/common-errors.md` — Known errors and fixes (jq `\d`, unzip prompt, find+set-e, git reset, missing source/composer.json) - `references/github-setup.md` — Repo creation, branch rename trunk→main, topics, secrets, all 11 current repos ## Gather Required Info Before writing any files, collect (ask user if missing): 1. **Plugin/package name** — human-readable (e.g. "SureCart", "Action Scheduler") 2. **Source type** — one of: - `wp-plugin` — downloadable from WordPress.org (slug known) - `composer` — Composer package on Packagist (e.g. `woocommerce/action-scheduler`) - `paid` — paid plugin, user places sourc