phpstan-stubs-scaffoldlisted

Use when asked to create a new PHPStan stubs package (phrases like "create stubs for X", "new stubs package", "scaffold phpstan stubs", "add stubs for plugin/composer package"). Scaffolds the full standard structure matching the mralaminahamed freemius pattern.
mralaminahamed/wp-dev-skills · ★ 3 · Data & Documents · score 76

Install: claude install-skill mralaminahamed/wp-dev-skills

# PHPStan Stubs Scaffold Scaffold a complete PHPStan stubs package from scratch, following the `mralaminahamed/phpstan-freemius-stubs` standard structure. ## 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 source manually 3. **WP.org slug** (if `wp-plugin`) — e.g. `surecart`, `forminator` 4. **Packagist package** (if `composer`) — e.g. `woocommerce/action-scheduler` 5. **Source dir path inside package** — where the plugin/package files land: - `wp-plugin`: `source/<slug>/` - `composer`: `source/vendor/<vendor>/<package>/` - `paid`: `source/<slug>/` 6. **Packagist name** — `mralaminahamed/phpstan-<slug>-stubs` 7. **GitHub repo name** — `phpstan-<slug>-stubs` 8. **Versions to release**