Repository navigation
Prompt Library
Gaurav Tiwari edited this page Sep 19, 2026
·
1 revision
Replace bracketed fields with real input. These prompts establish scope; they do not grant the assistant tools or website access it does not already have.
Use generateblocks-layouts to build [page/section] for [audience and purpose].
Use GenerateBlocks/Pro and core blocks only. Keep new styling local and preserve
existing shared references. My installed versions are [versions], theme [theme].
Use this copy and these assets: [content]. The post ID is [ID], or use a random
four-digit scope if no record exists. Save the markup to a file and validate it.
Work in a draft; do not publish.
Use html-to-generateblocks on [files]. Preserve copy, destinations, images and
responsive behavior. Put supported styles in the owning blocks and use native
components for interactions. Keep styling local. Identify any source behavior
that needs a native alternative before silently removing it. Verify the result
against the source and write the block markup to a file.
Use elementor-to-generateblocks for [export/page]. Preserve the working content,
queries and interactions. Remove only wrappers that own no necessary behavior.
Keep new styling local. Create a separate draft for review and check desktop,
mobile, open states, links and editor validity. Leave the published page intact.
Use figma-to-generateblocks for [accessible frame or export]. Follow the supplied
layout and typography, using [assets]. Preserve heading semantics and implement
[supplied mobile frame or stated responsive behavior]. Use native blocks and
local styles. State which design choices were inferred rather than specified.
Add these questions and answers to [section/page] with a native Pro accordion,
or core Details if Pro is unavailable. Give both questions and answers proper
padding, including mobile, and leave room for the toggle icon. Keep the styling
local. Test keyboard activation, expanded answers and theme spacing overrides.
Use the V2 Query/Looper/Loop-Item family to show the latest [count] published
[post type] records filtered by [taxonomy/field]. Include linked titles, images,
excerpts, an empty state and [pagination choice]. Use exact supported dynamic
tags, local styles and [column behavior]. Verify with actual records.
For this project, I explicitly want [Global Styles / Design Tokens / both].
Inspect the existing system first and preserve unrelated references. Propose
names for the reusable values and components, check collisions, and implement
the requested shared scope. Keep one-off changes local. Verify affected pages
and imports without overwriting an existing system by default.
Use generateblocks-layouts to fix [exact issue] in [page/section]. Read the current
raw content and inspect the native block type and compiled selector. Change only
the affected section/attributes. Preserve content and publication status. Run the
relevant preflight check, compare saved raw content and verify the failing state.
Audit this generated file/draft for native block validity, missing content,
CSS styles/cache parity, duplicate IDs, mobile overflow, keyboard behavior and
padded accordion states. Report what was checked and what remains unverified.
Do not introduce shared styles/tokens or publish as part of the audit.
For the next step, see WordPress Editing and Publishing.
Wiki home · Repository · Latest release · Report an issue
The wiki covers GenerateBlocks Skills; plugin features depend on the installed GenerateBlocks/Pro version. Detailed authoring rules are maintained in the repository's skill files.
GenerateBlocks Skills
Start
Build
- Styling and Responsive Design
- Global Styles and Design Tokens
- Conversion Workflows
- Dynamic Content
- Interactive Blocks and Forms
- Building a Website
- WordPress Editing and Publishing
Reference and Help