Goal
Give the AI access to WordPress block schemas and hook documentation via an embedded WASM/SQLite database (@pluginslab/wp-devdocs-wasm), so it answers developer questions with verified data instead of hallucinating.
Status
Partially implemented on the feature/wasm-sqlite-devdocs branch (not yet merged). Four abilities built and tested (11 tests including multi-turn chains).
What's done
search-wp-blocks — search Gutenberg blocks by keyword
get-block-schema — retrieve full schema for a specific block (attributes, supports, variations)
search-wp-hooks — search WordPress hooks (actions and filters)
get-hook-context — retrieve details for a specific hook (type, file, parameters)
- Databases bundled inline via webpack browser entry point (no raw sql.js)
- 11 tests in
tests/abilities/devdocs-wasm.test.js (10 single-turn + 1 multi-turn chain)
- ReAct agent fix for partial tool ID suffix matching
What's remaining
Key Files (on feature/wasm-sqlite-devdocs branch)
src/extensions/abilities/search-wp-blocks.js
src/extensions/abilities/get-block-schema.js
src/extensions/abilities/search-wp-hooks.js
src/extensions/abilities/get-hook-context.js
src/extensions/abilities/index.js — registers all four
webpack.config.js — browser added to conditionNames for WASM package resolution
src/extensions/services/react-agent.js — partial tool ID suffix matching fix
tests/abilities/devdocs-wasm.test.js — 11 tests
Technical Notes
- Uses
@pluginslab/wp-devdocs-wasm package (dynamic import, graceful degradation if not installed)
- Database covers 121+ core Gutenberg blocks + WordPress hooks with verified schemas
- See CLOUDFEST_HACKATHON.md Goal 9 for full context
Skills needed
React/JS, WASM
Goal
Give the AI access to WordPress block schemas and hook documentation via an embedded WASM/SQLite database (
@pluginslab/wp-devdocs-wasm), so it answers developer questions with verified data instead of hallucinating.Status
Partially implemented on the
feature/wasm-sqlite-devdocsbranch (not yet merged). Four abilities built and tested (11 tests including multi-turn chains).What's done
search-wp-blocks— search Gutenberg blocks by keywordget-block-schema— retrieve full schema for a specific block (attributes, supports, variations)search-wp-hooks— search WordPress hooks (actions and filters)get-hook-context— retrieve details for a specific hook (type, file, parameters)tests/abilities/devdocs-wasm.test.js(10 single-turn + 1 multi-turn chain)What's remaining
feature/wasm-sqlite-devdocsbranch to mainKey Files (on
feature/wasm-sqlite-devdocsbranch)src/extensions/abilities/search-wp-blocks.jssrc/extensions/abilities/get-block-schema.jssrc/extensions/abilities/search-wp-hooks.jssrc/extensions/abilities/get-hook-context.jssrc/extensions/abilities/index.js— registers all fourwebpack.config.js—browseradded toconditionNamesfor WASM package resolutionsrc/extensions/services/react-agent.js— partial tool ID suffix matching fixtests/abilities/devdocs-wasm.test.js— 11 testsTechnical Notes
@pluginslab/wp-devdocs-wasmpackage (dynamic import, graceful degradation if not installed)Skills needed
React/JS, WASM