Repository navigation
Closed
Description
Outcome
Ensure generated projects contain the required development configuration, testing setup, documentation and folder structure. These requirements apply to generated output, not merely the scaffold repository.
Requirements and acceptance criteria
- Review the referenced
developbranches: shared.github/.claude, and ThisOneTimeOnAcidCom’s.agents,.claude,.specify,.githubandguidelinesfolders. Adapt relevant roles, skills and instructions for generated output. - Identify required Mustache placeholders and follow mustache.js conventions.
- Include
src/and build folders, using@wordpress/buildfor the plugin. - Use WordPress packages for Prettier, ESLint, Playwright and applicable tooling; configure Node.js 24.x.
- Adapt Playwright configuration and E2E coverage from the supplied reference, placing tests in
test/e2e/rather than roote2e/. - Copy or adapt
postcss.config.mjs,jest.config.js,.code-workspace,.coderabbit.yml,.gitignoreand.gitattributes. - Include initial PHPUnit configuration, PHPStan checks and a working, tested Composer setup.
- Follow Gutenberg coding guidelines, WordPress Coding Standards and BEM for CSS.
- Include all required root files:
LICENSE,README.md,SECURITY.md,CONTRIBUTING.md,changelog.txt,readme.txt. - Include lint configuration:
.editorconfig,eslint.config.mjs,.jshintignore,prettier.config.mjs,.stylelintignore,.stylelintrc.js,.markdownlintignore,.npmpackagejsonlintrc.json,phpcs.xml.dist. - Include build configuration:
.browserslistrc,jsconfig.json,tsconfig.json,tsconfig.build.json,webpack.config.js. - Include
.wp-env.json,composer.json,composer.lock,package.jsonandpackage-lock.json. - Include
phpunit/,test/unit/,test/e2e/,tools/eslint/,tools/webpack/and project-specificdocs/. - Review Gutenberg’s
tools/before optionally relocating additional tools there. The two explicitly required tools subfolders remain mandatory.
Scope and references
Use the supplied requirements and reference links. Check each repository’s own instructions before implementation; reference configurations are inputs to review, not verified compatibility evidence.
The source’s meeting-relative timing, Claude logger/Figma follow-up and skill-suggester instruction are excluded from these generated-output issues. No deadline is inferred.
Metadata
Metadata
Assignees
Labels
No labels
Type
Fields
Priority
Urgent
Activity
linear-code commentedon Oct 28, 2026
BPS-10
krugazul commentedon Oct 28, 2026
Done. Every criterion is in
develop, each proven first in lightspeedwp/ls-test and then moved intoplugin-template/.npm run check:generationgates the generated output in CI..claudeand ThisOneTimeOnAcidCom's.agents,.claude,.specifyandguidelinesadapted for generated pluginssrc/and build folders@wordpress/scriptsfor builds, because@wordpress/buildisn't stable yet. Moving to it is a separate piece of work for later.test/e2e/postcss.config.mjs,.code-workspace,.coderabbit.yml,.gitignore,.gitattributesjest.config.js. Unit tests run on Vitest throughwp-scripts test-unit-js, configured invitest.config.mjs.check:generationin #61guidelines/in #58.wp-env.json,composer.json,composer.lock,package.json,package-lock.jsonphpunit/,test/unit/,test/e2e/,tools/eslint/,tools/webpack/,docs/tools/reviewedNot in scope here: the same work for the theme scaffold (lightspeedwp/block-theme-scaffold#20).