Building a website does not have to be expensive, slow, or overly technical. I tested Claude Haiku 4.5 to see whether this lower-cost model could build functional WordPress assets, including custom themes and directory sites, through a workflow often called vibe coding. In this test, Haiku 4.5 handled complex prompts, generated custom WordPress structures, created custom post types and taxonomies, and produced a working directory site for about $0.33.
Quick Answer
You can use Claude Haiku 4.5 to build WordPress themes and directory sites by running detailed natural-language prompts inside a supported code editor. In this test, the workflow generated theme files, custom post types, taxonomies, and directory structures for under one dollar.
Vibe coding means using natural language instructions to generate functional code instead of writing every file manually. For WordPress projects, that can include theme templates, custom post types, taxonomies, ACF field structures, import workflows, and starter layouts.
Key Takeaways
- Low build cost: The full directory build cost about $0.33 using Haiku 4.5 in this test.
- Good for structured prompts: The model followed a detailed WordPress prompt and generated theme files, custom post types, and taxonomies.
- Best with the right editor setup: You need a supported editor workflow such as VS Code with a compatible AI coding extension.
- Works well for directory sites: The process combined AI code generation, Local WP, ACF, and XLSX importing to populate listings.
- Manual review still matters: You should test templates, imports, maps, scripts, and mobile layouts before publishing.
At a Glance
| Best For | WordPress theme prototypes, local directory sites, custom post type builds, and fast development tests |
| Difficulty | Intermediate, because you still need to test WordPress files, plugins, fields, and imports |
| Tools Needed | Local WP, VS Code, a compatible AI coding extension, ACF, and an XLSX importer |
| Test Cost | About $0.33 for the directory build in this test, excluding hosting, plugins, or paid data tools |
What I built with Haiku 4.5
Using this workflow, I created several WordPress assets from structured prompts and local testing:
- A custom WordPress theme from a single vibe coding prompt.
- An instant directory site featuring travel agencies in the USA using 50 listings.
- Custom post type and taxonomy structures for directory-style publishing.
- Sample SEO articles generated and posted to the custom theme.
Why choose Haiku 4.5 for coding tasks?
Haiku 4.5 offers a more affordable alternative to larger AI coding models while still understanding structured developer prompts well enough for practical WordPress work. That makes it useful when you need high output volume, quick tests, and low operating cost.
For this kind of build, the main advantage is not just price. The model can follow a long prompt, understand naming conventions, create related files, and keep the structure consistent across templates, fields, and taxonomies.
Best use cases for this workflow
Haiku 4.5 is especially useful when the project has a clear structure and repeatable rules. Directory sites fit that pattern because they usually need custom fields, category systems, archive templates, single listing pages, and import logic.
- Local business directories: Agencies, contractors, clinics, restaurants, repair services, or niche professional listings.
- Template-heavy WordPress builds: Themes that need consistent archive pages, post templates, and custom sections.
- Prototype websites: Quick drafts you can review before investing in a more polished custom build.
- Bulk site experiments: Testing different niches, structures, and layouts while keeping AI usage cost low.
- Internal tools: Simple content dashboards, listing managers, or private database-style WordPress sites.
Note: Haiku 4.5 is best treated as a fast development assistant, not a complete replacement for review. Always inspect generated files before using them on a live site.
Prepare your prompts and basic configuration
I keep prompts in a plain text file so I can adjust variables quickly. For the WordPress theme prompt, I changed the folder name, site title, and team name. I also appended “Haiku 4.5” to the team name so I could track which model produced the theme.
For the directory prompt, I set the following variables before running the generation:
- Site folder name: travel-agency-team
- Site title: Travel Agencies in the US
- Custom post key: travel-agency
- Taxonomy: State as the parent and City as the child
- Country: USA
This step matters because the model uses these names across theme folders, template files, custom post types, taxonomy labels, and import instructions. Clear naming reduces cleanup later.
Pro Tip: Keep one reusable prompt template and change only the variables for each niche. This makes your tests faster and helps you compare results across different models.
What to include in your WordPress prompt
A strong WordPress vibe coding prompt should be specific. Do not only ask the model to “build a directory site.” Give it the exact post type, taxonomy structure, template requirements, field names, design style, and plugin assumptions.
- Project goal: Explain the type of site you want and who it serves.
- Theme folder name: Give the exact folder name the model should use.
- Custom post type: Define the singular name, plural name, slug, and purpose.
- Taxonomies: Explain parent and child relationships, such as State and City.
- ACF fields: List the fields each listing needs, such as address, phone, website, image URL, rating, and description.
- Templates: Request archive pages, single listing pages, taxonomy pages, and homepage sections.
- Design rules: Mention layout style, mobile behavior, spacing, cards, buttons, and navigation.
- Import logic: Tell the model how XLSX columns should map to post fields and taxonomies.
- Safety checks: Ask it to avoid placeholders, broken links, missing templates, or unsupported plugin assumptions.
The more structured the prompt is, the more consistent the generated WordPress files will be.
Run WordPress locally
If you test locally, install Local WP, create a new site, and open the WP admin. Click the VS Code button to open the project. I created two Local WP sites to run theme generation and directory generation in parallel.
Working locally is safer than testing directly on a live site. You can break the theme, reset files, change plugins, and rerun prompts without affecting visitors or search engines.
Configure your editor and select the model
I use vibe coding extensions in the editor, specifically Klein, Cloud Code, or Plot. In the settings, choose your API provider and select the Haiku 4.5 model. If Haiku 4.5 does not appear in your Cloud Code extension, run the widget update command from the terminal to make the model available.
Before running a large prompt, confirm that the extension can read and write project files. Also check that the selected workspace is the correct Local WP theme or plugin directory.
Execute the vibe code prompt
Paste the prepared prompt into the vibe code runner and execute it. For the directory, I used the directory prompt alongside a sample XLSX file containing 50 scraped travel agencies. The process generated the necessary site files, including theme files, custom post types, taxonomies, and starter content.
Troubleshooting editor errors
If you encounter errors, check your extension compatibility. I initially tried running the prompt in Klein and it threw errors. The fix was to use Cloud Code after updating the extension.
If the model stops early, rerun the prompt with a smaller scope. For example, ask it to create only the theme structure first, then ask for custom post types, then ask for archive templates, and then ask for import support.
Warning: Do not push generated code to a live WordPress site without testing it locally first. Check PHP errors, template loading, plugin dependencies, JavaScript behavior, and mobile layout issues.
Import directory listings
To populate the directory, I exported 50 listings into an XLSX file. I installed two essential WordPress plugins:
- Advanced Custom Fields (ACF): Sync this with the field groups generated by the theme.
- A custom XLSX Importer plugin: Use this to map columns to the custom post fields.
During the import process, map your taxonomies so “State” becomes the parent category and “City” becomes the child category. Map the image URL to the main image column and let the importer handle the ACF field data automatically.
After importing, review several listings manually. Check the listing title, address, phone number, website link, image, taxonomy assignment, and custom field output on the front end.
Quality checks before publishing
AI-generated WordPress builds can look complete while still having hidden issues. Before using the site publicly, run through a practical review process.
- Theme activation: Confirm the theme activates without PHP warnings or fatal errors.
- Template coverage: Check homepage, archive, taxonomy, single listing, search, and 404 pages.
- ACF output: Make sure all custom fields display in the correct places.
- Import accuracy: Compare a few XLSX rows against the imported WordPress listings.
- Mobile layout: Test listing cards, menus, maps, and buttons on small screens.
- Speed: Compress heavy images and avoid unnecessary scripts.
- Security: Escape output, sanitize inputs, and avoid exposing private keys or sensitive data.
- SEO basics: Check headings, internal links, clean URLs, indexable pages, and schema output.
A low-cost AI build is useful only when the final site is reviewed, tested, and cleaned up before publishing.
Generate sample SEO articles
I used an Article AI Generator to create SEO-friendly posts using keywords from Semrush. Because the generator supports Haiku 4.5, I created two sample posts with featured images. The output included proper formatting, related posts, and layout structures that looked professional right from the start.
For a real site, review AI-generated articles before publishing. Check facts, add first-hand details, remove generic wording, and make sure each article matches the site niche.
Costs and final results
The directory build cost roughly $0.33 using Haiku 4.5. This makes it a practical option for bulk creation when you need to minimize AI usage costs. The final result included the core WordPress structure, directory listing support, taxonomy setup, and sample content output.
Even with a strong result, you should expect small manual fixes. In my test, the types of areas worth checking included JavaScript behavior for maps or hero sections, imported data formatting, mobile spacing, and field output consistency.
This workflow is most valuable when you treat Haiku 4.5 as a low-cost builder for prototypes and structured WordPress assets. For a production site, the generated code still needs developer review, security checks, and final QA.
Limitations to keep in mind
Haiku 4.5 can generate useful WordPress code, but it is not perfect. The quality depends heavily on prompt clarity, editor support, file access, plugin setup, and the complexity of the build.
- Plugin assumptions can be wrong: The model may assume a plugin structure that differs from your actual setup.
- Imports need testing: XLSX column mapping can fail if field names or taxonomy relationships are inconsistent.
- Design polish varies: You may need to adjust spacing, typography, cards, and responsive layouts.
- Security review is required: Generated PHP should be checked for escaping, sanitization, and safe output.
- SEO still needs human judgment: AI can build templates, but content strategy and quality control remain your responsibility.
Frequently Asked Questions
What is Haiku 4.5 and why should I use it?
Haiku 4.5 is a cost-effective AI model that can follow structured developer prompts. It is useful for high-volume tasks such as generating WordPress themes, directory site structures, custom post types, and starter layouts when you want to keep costs low.
Can I use Haiku 4.5 in any code editor?
Compatibility depends on the editor extension and API provider. In my testing, Haiku 4.5 worked best with Cloud Code or Plot. If the model does not appear in your list, update your extension and check your provider settings.
How do I import listings into a WordPress directory?
Prepare your data in an XLSX file and use an importer plugin with ACF. Map your columns to the matching ACF fields, then set taxonomies so states act as parent categories and cities act as child categories.
How much manual work is needed after generation?
You will likely need to make small fixes, such as adjusting hero sections, checking imported field data, testing JavaScript, cleaning mobile spacing, and reviewing the generated PHP. The core structure may be usable, but QA is still required.
Is Haiku 4.5 good enough for production WordPress sites?
It can help create a strong starting point, especially for structured sites. However, production use should include code review, security checks, plugin testing, responsive design review, and content quality control before launch.
What type of WordPress site works best with this workflow?
Directory sites, niche databases, local business listings, and template-heavy WordPress projects work well because they have repeatable structures. The clearer your fields, taxonomies, and templates are, the better the output tends to be.
Sources
- Local WP — local WordPress development environment used for testing the generated site.
- Advanced Custom Fields — plugin used for custom field structures in the directory workflow.
- WordPress Documentation — general WordPress reference for themes, templates, and site management.
- Visual Studio Code — code editor used as part of the local development workflow.
Using Haiku 4.5 for web development offers a low-cost way to experiment with WordPress site building and automation. Start by testing your prompts on a small local project so you can see how the model structures your files, fields, and templates. With a clear prompt and careful review, this workflow can help you create directory sites and custom WordPress assets while keeping operating costs low.
Last Updated on June 28, 2026 by Logan Carter
