# AI-Powered Features
Source: https://docs.kintsu.ai/features/ai-powered
Leverage advanced AI capabilities for intelligent WordPress editing, intent understanding, and autonomous site improvements.
Kintsu.ai's AI features enable you to think, plan, and make changes autonomously. They're designed to make Kintsu.ai more capable, reliable, and independent when handling complex WordPress development tasks.
## Builder Chat
Use natural language to tell Kintsu.ai what you want changed on your WordPress site — and get the update implemented without touching code.
Builder chat enables you to:
* **Express intent naturally** — Describe changes the way you'd explain them to a colleague
* **Make complex edits** — Update multiple sections, components, or pages in one request
* **Iterate quickly** — Refine changes through conversation rather than manual edits
* **Skip technical details** — Focus on what you want, not how to implement it
* **Work across your site** — Make changes to any page, post, or component
* **Maintain context** — The AI remembers what you're working on throughout the conversation
Without manual intervention, Builder chat interprets your request, explores your codebase for necessary context, reads files on demand, fixes and refactors code as needed, and delivers working implementations with fewer errors and cleaner results.
***
## Discussion Mode
Brainstorm and plan edits with the AI without changing your live site. Use it to clarify requirements, compare options, and refine instructions before applying anything.
Discussion mode helps you:
* **Explore options** — Consider different approaches before committing
* **Clarify requirements** — Work through ambiguity in a safe space
* **Plan complex changes** — Break down large projects into manageable steps
* **Get expert input** — Receive suggestions based on WordPress best practices
* **Avoid mistakes** — Think through potential issues before implementation
* **Document decisions** — Keep a record of why choices were made
This reduces friction during development by allowing you to think through problems and validate approaches before making actual changes to your site.
***
## Intent-to-Change Understanding
Kintsu.ai turns vague requests ("make this section feel more premium") into concrete WordPress edits: layout adjustments, copy updates, styling changes, and component tweaks.
The AI can interpret:
* **Subjective goals** — "More professional," "friendlier," "less cluttered"
* **Directional requests** — "Improve the hierarchy," "emphasize the CTA"
* **Context-dependent changes** — "Make it work better on mobile"
* **Brand alignment** — "Match the tone of our other pages"
* **User experience improvements** — "Make this easier to understand"
* **Performance goals** — "Speed up the checkout process"
All without manual intervention. With deeper codebase understanding and real-time debugging, the AI delivers better results with fewer errors and cleaner, more maintainable code.
***
## Page-Aware Editing
Target exactly what you mean: "On the homepage hero," "On the pricing page FAQ," "On mobile only," or "Only in the footer."
Page-aware editing enables you to:
* **Target specific pages** — Homepage, pricing page, blog posts, or custom templates
* **Focus on sections** — Hero, features, testimonials, footer, sidebar
* **Device-specific changes** — Desktop only, mobile only, or tablet layouts
* **Component-level precision** — Individual buttons, forms, or navigation elements
* **Template-aware edits** — Changes to page templates vs. individual pages
* **Conditional updates** — Different content for different user segments
This precision ensures changes land exactly where intended without unintended side effects.
***
## Smart Guardrails for Risky Requests
When an edit could break layout, conflict with theme structure, or affect conversions, Kintsu.ai pushes back with safer alternatives instead of blindly applying changes.
Smart guardrails protect you from:
* **Layout-breaking changes** — Edits that would cause overlapping or misaligned elements
* **Theme conflicts** — Modifications that clash with your active theme
* **Plugin incompatibilities** — Changes that interfere with plugin functionality
* **Performance regressions** — Updates that significantly slow your site
* **SEO damage** — Edits that hurt search visibility or rankings
* **Accessibility issues** — Changes that reduce site accessibility
When Kintsu.ai detects potential problems, it suggests safer alternatives and explains the risks — giving you informed control over your site's evolution.
***
## Multi-Language Content Editing **(New)**
Edit and manage content across different languages seamlessly. Kintsu.ai understands context and maintains consistency across your multilingual WordPress site.
Multi-language support includes:
* **Context-aware translation** — Maintain tone and intent across languages
* **Consistency checking** — Ensure terminology stays aligned
* **Layout preservation** — Handle text length variations gracefully
* **RTL support** — Proper handling of right-to-left languages
* **Locale-specific content** — Regional variations and cultural adaptations
* **WPML & Polylang integration** — Works with popular translation plugins
Make changes in one language and get intelligent suggestions for how to adapt them across your other language versions.
***
## Block Pattern Suggestions **(New)**
Get intelligent Gutenberg block pattern recommendations based on your content and design goals. Kintsu.ai suggests layouts that match your site's style.
Block pattern suggestions help you:
* **Discover patterns** — Find relevant Gutenberg patterns from your theme and plugins
* **Match your style** — Get patterns that align with your existing design
* **Speed up layouts** — Build complex sections faster with proven patterns
* **Maintain consistency** — Use patterns that fit your site's visual language
* **Learn best practices** — See examples of effective WordPress layouts
* **Customize intelligently** — Get suggestions for pattern modifications
Instead of starting from scratch or browsing endless pattern libraries, get contextual recommendations that fit your current task.
***
## Accessibility Improvements **(New)**
AI suggests accessibility fixes like missing alt tags, contrast issues, and heading hierarchy problems — making your site more inclusive without manual audits.
Accessibility features include:
* **Alt text generation** — Intelligent descriptions for images missing alt attributes
* **Contrast checking** — Identify and fix color contrast issues
* **Heading hierarchy** — Ensure proper H1-H6 structure throughout your site
* **Keyboard navigation** — Verify and improve keyboard accessibility
* **Screen reader optimization** — Test and enhance screen reader compatibility
* **ARIA attributes** — Add appropriate ARIA labels and descriptions
* **Form accessibility** — Improve label associations and error messages
* **Focus indicators** — Ensure visible focus states for interactive elements
Kintsu.ai proactively identifies accessibility issues and suggests fixes that improve usability for all visitors.
***
## Pricing
AI-Powered features use usage-based pricing, which you can read more about in our [plans and credits documentation](/plans-and-credits). The cost of a message depends on its complexity to ensure you only pay for what you actually use. Many messages cost less than 1 credit, while more complex operations may cost more.
Looking for specific AI capabilities not listed here? [Contact our team](mailto:support@kintsu.ai) to discuss custom solutions.
# Design & Visual Edits
Source: https://docs.kintsu.ai/features/design-visual
Polish your WordPress site's appearance with responsive design, styling updates, brand consistency, and layout improvements — no rebuilds required.
Make your WordPress site look intentional, modern, and professional without rebuilding templates or hiring designers for every tweak. Kintsu.ai handles the common visual improvements that take hours manually but should take minutes.
***
## Responsive Design Edits
Make changes that hold up across desktop, tablet, and mobile — without breaking layouts on smaller screens.
Responsive design capabilities:
* **Device-specific adjustments** — Different layouts for desktop, tablet, and mobile
* **Breakpoint awareness** — Changes respect your theme's breakpoints
* **Mobile-first optimization** — Prioritize mobile experience automatically
* **Touch-friendly interfaces** — Ensure buttons and links work well on touchscreens
* **Responsive typography** — Text sizing that scales appropriately
* **Image handling** — Proper responsive image implementations
* **Layout preservation** — Prevent content overlap and misalignment
* **Navigation adaptation** — Mobile-friendly menus and navigation patterns
Describe what you want and Kintsu.ai ensures it works across all devices. No more "looks great on desktop but breaks on mobile" surprises.
When making design changes, Kintsu.ai automatically tests layouts at common viewport sizes and warns you about potential responsive issues.
***
## Instant Styling & Visual Tweaks
Update fonts, spacing, colors, button styles, and section layout — and get a cleaner, more modern look without redesigning the whole site.
Visual editing includes:
* **Typography updates** — Font families, sizes, weights, and line heights
* **Color adjustments** — Update brand colors, backgrounds, and text colors
* **Spacing improvements** — Padding, margins, and element spacing
* **Button styling** — Colors, shapes, sizes, and hover states
* **Section layouts** — Column arrangements and content organization
* **Border and shadows** — Subtle depth and visual hierarchy
* **Icon styles** — Consistent icon sizing and coloring
* **Animation and transitions** — Subtle motion for improved UX
Make the common visual tweaks that polish a site's appearance without touching template files or writing custom CSS.
### Example Improvements
* "Make the buttons more prominent and modern"
* "Increase spacing between sections for breathing room"
* "Update the hero area to feel less cramped"
* "Make the typography more readable"
* "Polish the footer to match the header style"
Kintsu.ai interprets these requests and implements appropriate visual changes that align with modern design standards.
***
## Consistent Brand Styling
Make site-wide styling consistent (buttons, headings, section spacing, icon styles) so the site looks intentional instead of patched together.
Brand consistency features:
* **Style standardization** — Unify inconsistent design elements
* **Button normalization** — Consistent button styles site-wide
* **Heading hierarchy** — Uniform heading styles across pages
* **Color palette enforcement** — Stick to defined brand colors
* **Typography consistency** — Standard font usage throughout
* **Spacing systems** — Consistent spacing scale across sections
* **Component alignment** — Unified styling for similar elements
Many WordPress sites evolve over time with different people making changes, resulting in visual inconsistency. Kintsu.ai identifies these inconsistencies and helps standardize styling without manual audits.
Brand consistency improvements can be applied gradually. You don't need to standardize everything at once — focus on the most visible areas first.
***
## Layout Polish (Without Rebuilds)
Fix common "legacy site" problems: misaligned sections, inconsistent padding, cramped typography, overly large hero areas, and messy mobile stacking.
Layout improvements include:
* **Alignment fixes** — Correct misaligned text, images, and sections
* **Padding adjustments** — Fix inconsistent or inadequate spacing
* **Typography spacing** — Improve line-height and paragraph spacing
* **Hero proportions** — Right-size overly tall or short hero sections
* **Content width** — Optimize text column widths for readability
* **Visual hierarchy** — Improve information hierarchy through spacing and sizing
* **Mobile stacking** — Fix awkward mobile layouts and column collapse
* **Footer layouts** — Organize cluttered footer content
These are the polish issues that make a site feel dated or unprofessional but don't justify a complete redesign.
### Common Fixes
1. **Misaligned sections** — Content that doesn't line up properly
2. **Inconsistent padding** — Some sections feel cramped, others too spacious
3. **Cramped typography** — Text that's hard to read due to tight spacing
4. **Oversized heroes** — Hero sections that push content too far down
5. **Poor mobile stacking** — Desktop layouts that break awkwardly on mobile
6. **Cluttered footers** — Footer content that needs organization
Describe the issue and Kintsu.ai implements appropriate fixes that respect your theme structure.
***
## Design System Integration
For sites with established design systems or brand guidelines, Kintsu.ai can work within those constraints.
Design system features:
* **Token awareness** — Work with design tokens for colors, spacing, and typography
* **Component libraries** — Respect existing component implementations
* **Style guide adherence** — Follow documented brand guidelines
* **Pattern library integration** — Use pre-approved design patterns
* **Constraint validation** — Ensure changes comply with design rules
This is particularly valuable for enterprise sites, agencies managing multiple brand properties, or teams with strict brand governance.
***
## Visual QA and Testing
Before publishing visual changes, Kintsu.ai performs automated visual testing to catch layout issues.
Visual testing includes:
* **Breakpoint validation** — Test layouts at common screen sizes
* **Browser compatibility** — Ensure changes work across browsers
* **Contrast checking** — Verify text remains readable after color changes
* **Layout integrity** — Detect overlapping or misaligned elements
* **Performance impact** — Check if visual changes affect load times
* **Accessibility validation** — Ensure visual changes maintain accessibility
Visual regressions are caught before they reach your visitors.
***
## Best Practices
### Start with High-Impact Areas
Focus visual improvements on the areas visitors see first: homepage hero, navigation, and key conversion pages.
### Maintain Visual Hierarchy
When making styling changes, preserve (or improve) the visual hierarchy that guides visitors through your content.
### Test Across Devices
Always preview visual changes on desktop, tablet, and mobile before publishing — even when Kintsu.ai's automated testing passes.
### Document Brand Standards
If you have specific brand requirements (colors, fonts, spacing), document them so Kintsu.ai can work within those constraints.
### Iterate Gradually
Make incremental visual improvements rather than sweeping redesigns. This reduces risk and makes it easier to A/B test changes.
***
## Pricing
Design and visual editing features are included in all Kintsu.ai plans. Visual changes follow our standard [credit system](/plans-and-credits), with most styling updates costing less than 1 credit.
Learn about pricing and how credits work.
Start making visual improvements to your site.
# Features
Source: https://docs.kintsu.ai/features/index
Explore Kintsu.ai's comprehensive suite of AI-powered WordPress editing and management tools.
Kintsu.ai provides a powerful set of features designed to help you safely evolve and maintain your WordPress sites. Switch between different capabilities that are optimized for specific tasks — from AI-powered content generation to precise design adjustments.
When working with Kintsu.ai, you have access to features across four main categories:
Intelligent editing, intent understanding, and autonomous improvements powered by advanced AI.
Essential WordPress editing capabilities that respect your existing theme, plugins, and structure.
Version control, collaboration, staging workflows, and audit trails for safe site evolution.
Responsive design, styling, brand consistency, and layout polish without rebuilds.
***
## Quick Feature Overview
### AI-Powered Features
Kintsu.ai's AI capabilities enable you to describe what you want in natural language and get intelligent, context-aware changes:
* **Builder chat** — Natural language editing without touching code
* **Discussion mode** — Brainstorm and plan before making changes
* **Intent understanding** — Turn vague requests into concrete WordPress edits
* **Page-aware editing** — Target specific pages, sections, or devices
* **Smart guardrails** — Get safer alternatives for risky requests
* **Multi-language support** **(New)** — Manage content across languages seamlessly
* **Block pattern suggestions** **(New)** — Get intelligent Gutenberg pattern recommendations
* **Accessibility improvements** **(New)** — AI-powered accessibility fixes and suggestions
[Explore AI-Powered Features →](/features/ai-powered)
***
### WordPress Editing Core
Make changes that work with your existing WordPress setup — themes, builders, plugins, and all:
* **Theme & builder compatibility** — Respects your existing structure
* **Safe edit pipeline** — Preview changes before publishing
* **Content updates** — Update copy, structure, and navigation
* **SEO-ready edits** — Optimize on-page SEO while editing
* **Performance-conscious** — Avoid changes that slow your site down
* **Plugin conflict detection** **(New)** — Prevent compatibility issues before they happen
[Explore WordPress Core Features →](/features/wordpress-core)
***
### Site Management & Extensibility
Track, control, and collaborate on WordPress changes with enterprise-grade tools:
* **Version control** — Track what changed and when
* **Rollback and undo** — Revert individual changes safely
* **Staging workflows** — Validate changes before production
* **Collaboration** **(Beta)** — Team review and approval workflows
* **Audit trail** — Complete change history for accountability
[Explore Site Management Features →](/features/site-management)
***
### Design & Visual Edits
Polish your site's appearance across all devices without starting from scratch:
* **Responsive design edits** — Changes that work on all screen sizes
* **Instant styling** — Update fonts, colors, spacing, and more
* **Brand consistency** — Site-wide styling improvements
* **Layout polish** — Fix common legacy site problems
[Explore Design & Visual Features →](/features/design-visual)
***
## Feature Updates
We continuously improve and expand Kintsu.ai's capabilities. Features marked with **(New)** are recently added, and those marked with **(Beta)** are in active development.
Have a feature request? Join our [Discord community](https://discord.gg/H6KHwqcfRX) and share your ideas.
# Site Management & Extensibility
Source: https://docs.kintsu.ai/features/site-management
Track, control, and collaborate on WordPress changes with version control, rollback, staging, and team workflows.
Enterprise-grade tools for managing WordPress site evolution safely and collaboratively. Track changes, control deployments, and coordinate with teams without losing the agility that makes Kintsu.ai powerful.
***
## Version Control for Site Changes
Track what changed and when, so you can restore a previous version if an edit doesn't land the way you expected.
Version control features:
* **Complete change history** — Every edit is tracked with timestamps and descriptions
* **Detailed diff views** — See exactly what changed in each edit
* **Change metadata** — Who made the change, when, and why
* **Branch support** — Work on multiple change sets simultaneously
* **Commit-like workflow** — Familiar version control concepts for WordPress
* **Search and filter** — Find specific changes quickly
* **Export history** — Download change logs for external records
Unlike traditional backups that restore everything or nothing, version control gives you surgical precision: see exactly what changed and when.
Version control tracks changes at the content level, not just file backups. This means you can see "Changed CTA button text on homepage hero" rather than "Modified wp-content."
***
## Rollback and Undo
Revert individual changes (not just "restore everything") so you can iterate safely without losing other progress.
Rollback capabilities:
* **Selective undo** — Revert specific changes while keeping others
* **Granular rollback** — Undo changes to individual sections or pages
* **Preserve subsequent work** — Roll back without losing later changes
* **Rollback preview** — See what will change before reverting
* **Bulk operations** — Revert multiple related changes at once
* **Time-based rollback** — Restore to a specific point in time
Traditional WordPress backup-and-restore is all-or-nothing. Kintsu.ai's rollback lets you undo the change that didn't work while keeping everything else intact.
### Example Workflow
1. Make five changes to your homepage
2. Discover change #3 caused an issue
3. Roll back only change #3
4. Changes #1, #2, #4, and #5 remain intact
This surgical approach to rollback eliminates the fear of experimenting and iterating on your site.
***
## Staging-Friendly Workflows
Make and validate changes on staging before pushing them to production — ideal for business-critical sites where mistakes cost money.
Staging features include:
* **Staging environment sync** — Keep staging aligned with production
* **Change promotion** — Push validated changes from staging to production
* **Selective deployment** — Promote specific changes, not everything
* **Testing validation** — Ensure changes work before going live
* **Client approval** — Let stakeholders review on staging
* **Scheduled deployment** — Push changes at optimal times
Kintsu.ai treats staging as a first-class concept, not an afterthought. Changes flow smoothly from development to staging to production with full visibility.
Staging workflows work with your existing hosting setup. Kintsu.ai doesn't require a specific hosting provider or infrastructure.
***
## Collaboration and Approvals **(Beta)**
Let stakeholders review proposed changes (marketing, product, agency, founder) and approve before anything goes live.
Collaboration features include:
* **Review workflows** — Route changes to appropriate reviewers
* **Approval gates** — Require sign-off before publishing
* **Comment threads** — Discuss changes with context
* **Role-based permissions** — Control who can propose vs. publish changes
* **Notification system** — Alert reviewers when input is needed
* **Change annotations** — Add notes and context to proposed edits
This is essential for agencies managing client sites or teams where multiple stakeholders need visibility into changes.
### Use Cases
* **Agency workflows** — Get client approval before publishing changes
* **Marketing teams** — Review content changes before they go live
* **Enterprise sites** — Ensure compliance and brand consistency
* **Multi-site management** — Coordinate changes across multiple properties
Collaboration features are currently in beta. [Join our Discord](https://discord.gg/H6KHwqcfRX) to participate in the beta program and provide feedback.
***
## Audit Trail
A clear record of changes: what was edited, where, and why — so maintenance doesn't become guesswork later.
Audit trail captures:
* **Change descriptions** — Natural language summaries of what changed
* **User attribution** — Who made each change
* **Timestamps** — Precise timing of all modifications
* **Affected areas** — Which pages, sections, or components were edited
* **Reasoning** — Why the change was made (if documented)
* **Related changes** — See connections between related edits
* **External integrations** — Track changes made via API or CI/CD
Audit trails are invaluable for:
* **Compliance** — Demonstrate change control for regulated industries
* **Troubleshooting** — Identify what changed before an issue appeared
* **Team handoffs** — New team members can understand site history
* **Client reporting** — Show clients what work was completed
* **Long-term maintenance** — Document the evolution of the site
Audit trail data is available via API for integration with external tools and workflows.
***
## Multi-Site Management
For agencies and teams managing multiple WordPress sites, Kintsu.ai provides centralized visibility and control.
Multi-site features:
* **Unified dashboard** — See all your sites in one place
* **Cross-site patterns** — Identify common changes across sites
* **Shared components** — Reuse successful changes across properties
* **Bulk operations** — Apply similar changes to multiple sites
* **Aggregate reporting** — Understand activity across your portfolio
* **Client segmentation** — Organize sites by client or project
Manage five sites or five hundred with the same level of control and visibility.
***
## Best Practices
### Document Your Changes
Add context when making changes: why you're making the edit, what problem it solves, and what outcome you expect. Your future self (and your team) will thank you.
### Use Staging for Important Changes
Production changes should be routine and low-risk. Save experiments and significant updates for staging environments.
### Review Audit Trails Regularly
Periodic review of the audit trail helps identify patterns, recurring issues, and opportunities for process improvement.
### Set Up Approval Workflows Early
Don't wait until after a mistake to implement review processes. Set up appropriate approval gates from the beginning.
***
## Pricing
Site management features are included in Professional and Enterprise plans. Collaboration and multi-site features require an Enterprise plan. See our [plans and pricing page](/plans-and-credits) for details.
Compare plans and understand pricing.
Integrate with external tools and workflows.
# WordPress Editing Core
Source: https://docs.kintsu.ai/features/wordpress-core
Essential WordPress editing capabilities that respect your existing theme, plugins, and site structure.
Kintsu.ai operates in the reality of WordPress sites: themes, page builders, plugins, and years of accumulated decisions — and focuses on edits that respect that structure.
These core features ensure changes work with your existing setup rather than forcing you to rebuild or migrate.
***
## Theme & Builder Compatibility
Kintsu.ai respects the structure of your WordPress site: themes, page builders, plugins, and the accumulated decisions that make your site unique.
Compatibility includes:
* **Popular page builders** — Elementor, Divi, WPBakery, Beaver Builder, and more
* **Block themes** — Full Site Editing (FSE) and block-based themes
* **Classic themes** — Traditional PHP-based themes with template files
* **Hybrid approaches** — Sites using both classic and block editors
* **Custom implementations** — Unique theme structures and custom post types
* **Plugin-generated content** — Respect content created by plugins
Rather than requiring a specific setup, Kintsu.ai adapts to what you already have. This means no forced migrations, no template rebuilds, and no starting over.
Kintsu.ai works with your site as it exists today — even if it's been patched, customized, and evolved over years.
***
## Safe Edit Pipeline (Preview-First)
Apply changes in a controlled way: generate the change, preview the impact, then publish — rather than "edit and pray."
The safe edit pipeline ensures:
* **Visual previews** — See exactly what will change before it goes live
* **Impact analysis** — Understand which pages and sections are affected
* **Validation checks** — Automated testing for layout breaks and conflicts
* **Selective application** — Choose which parts of a change to apply
* **Instant rollback** — Undo changes if they don't work as expected
* **Change summaries** — Clear explanations of what was modified
This approach eliminates the anxiety of making changes to production sites. You get confidence that updates will work before visitors see them.
***
## Content Updates (Copy + Structure)
Update headings, paragraphs, CTA buttons, navigation labels, and page sections — including reorganizing sections for clarity and flow.
Content editing includes:
* **Text updates** — Headlines, body copy, button labels, captions
* **Navigation changes** — Menu labels, links, and structure
* **Section reorganization** — Reorder content blocks for better flow
* **CTA optimization** — Update calls-to-action for clarity and conversion
* **Content hierarchy** — Improve information architecture
* **Micro-copy refinement** — Polish form labels, tooltips, and helper text
Make content improvements without touching template files or dealing with complex theme editors. Just describe what needs to change and where.
***
## SEO-Ready Page Edits
Make on-page SEO adjustments while editing: title tags, meta descriptions, headings hierarchy, internal links, and content clarity (without turning the site into keyword spam).
SEO capabilities include:
* **Meta optimization** — Update title tags and meta descriptions
* **Heading structure** — Ensure proper H1-H6 hierarchy for SEO
* **Internal linking** — Add contextual internal links
* **Content clarity** — Improve readability for users and search engines
* **Schema markup** — Add structured data where appropriate
* **Image optimization** — Update alt text and file names for SEO
* **URL structure** — Improve permalinks and slug readability
Kintsu.ai focuses on genuine SEO improvements that help both users and search engines — not keyword stuffing or manipulative tactics.
SEO changes are made with natural language and readability as priorities. Kintsu.ai avoids over-optimization that hurts user experience.
***
## Performance-Conscious Changes
Avoid common "quick fixes" that slow WordPress down. Prefer lightweight edits over piling on heavy scripts or bloated widgets.
Performance considerations:
* **Lightweight implementations** — Prefer CSS over JavaScript when possible
* **Asset optimization** — Avoid adding unnecessary scripts or stylesheets
* **Database efficiency** — Minimize query complexity
* **Caching compatibility** — Ensure changes work well with caching plugins
* **Mobile performance** — Optimize for mobile devices and slower connections
* **Core Web Vitals** — Consider impact on Largest Contentful Paint, First Input Delay, and Cumulative Layout Shift
Before applying performance-impacting changes, Kintsu.ai warns you and suggests lighter alternatives.
***
## Plugin Conflict Detection **(New)**
Kintsu.ai warns you before making changes that might conflict with active plugins, preventing broken functionality and compatibility issues.
Conflict detection covers:
* **Script conflicts** — Identify JavaScript library collisions
* **CSS conflicts** — Detect styling that might break plugin layouts
* **Functionality overlap** — Warn when changes duplicate plugin features
* **Hook interference** — Identify potential WordPress hook conflicts
* **Database compatibility** — Ensure changes work with plugin data structures
* **Version-specific issues** — Check for known compatibility problems
When Kintsu.ai detects a potential conflict, it explains the risk and suggests alternative approaches that work safely with your plugin stack.
Plugin conflict detection improves as you use Kintsu.ai. The system learns the behavior of popular plugins and your specific site configuration.
***
## Best Practices
### Start Small
Make incremental changes rather than sweeping updates. This reduces risk and makes it easier to identify what worked and what didn't.
### Use Staging
For business-critical sites, validate changes on staging before pushing to production. See [Staging-Friendly Workflows](/features/site-management#staging-friendly-workflows) for details.
### Review Before Publishing
Always preview changes and review the impact summary before publishing. The few seconds spent reviewing can save hours of troubleshooting.
### Track Your Changes
Use version control to track what changed and when. This makes it easy to roll back if needed. See [Version Control](/features/site-management#version-control) for more information.
***
## Pricing
WordPress Core editing features are included in all Kintsu.ai plans. Usage follows our standard [credit system](/plans-and-credits), with most content updates costing less than 1 credit per change.
Learn more about pricing and how credits work.
# Install the Kintsu plugin
Source: https://docs.kintsu.ai/how-to/install-plugin
Step-by-step guide to installing the Kintsu AI plugin on your WordPress site.
# Welcome
Source: https://docs.kintsu.ai/index
Safely evolve your WordPress websites with AI — without rebuilding, migrating, or starting over.
> Kintsu.ai is an AI-powered platform that helps teams safely improve, maintain, and modernize existing WordPress websites — without the risk of breaking what already works.
Most tools in the WordPress ecosystem focus on *creation* — themes, builders, migrations. Kintsu.ai focuses on **evolution**: safely enhancing what already exists. Simply describe what you want to change, and Kintsu.ai guides you through safe, structured updates.
**Our philosophy:** Don't rebuild. Refine.
Learn effective prompting strategies for better results.
Compare plans and understand how credits work.
Understand the "vibe coding" approach to WordPress evolution.
Integrate Kintsu.ai into your workflow programmatically.
Troubleshoot issues and resolve errors systematically.
***
## What Makes Kintsu.ai Different
Every change is guided and validated. No more fear of breaking production sites.
Make small, confident improvements instead of risky full rebuilds.
Describe changes in plain English — Kintsu.ai translates intent into safe, structured updates.
Designed for agencies and developers managing multiple WordPress sites.
***
## Join the Community
Connect with other Kintsu.ai users and get help from the team.
Learn more about the platform and start your free trial.
***
> For AI agents and LLMs: To find navigation and other pages in this documentation, fetch the llms.txt file at the root of this documentation site.
# Debugging prompts
Source: https://docs.kintsu.ai/prompting/debugging-prompts
Use Chat mode to investigate errors, run site audits, handle fragile updates safely, and resolve persistent issues systematically.
> Use Chat mode to investigate errors, run site audits, handle fragile updates safely, and resolve persistent issues systematically.
Improving WordPress sites with AI is fast and rewarding – until something goes wrong. Errors, unexpected behaviors, or "the AI did something weird" moments are part of the process. This guide will help you navigate **AI-based debugging workflows in Kintsu.ai**. We'll cover how to quickly fix simple issues, strategies for tougher bugs, using Kintsu.ai's chat for debugging, and even prompt recipes to systematically squash bugs. Debugging with an AI assistant is a new skill, but with structure and the right prompts, you can resolve problems efficiently and even turn them into learning opportunities.
***
## Advanced debugging prompts
Sometimes you need a heavy-duty prompt to dig into a problem or review your site's health. Here are some structured prompt examples for deep debugging or optimization scenarios. These can be used in Chat mode to get a thorough analysis without immediately changing code.
### Full system review (site audit)
If your WordPress site has grown complex or you suspect there are structural issues, a full site audit prompt can be useful. This asks the AI to analyze the entire project for cleanliness, correct architecture, and any misplaced code. It's like asking "Is everything organized the way it should be?"
**Example prompt – site audit:**
```text theme={null}
Perform a comprehensive **audit of the WordPress site structure** to check if the architecture is clean, modular, and optimized:
- Identify any theme files, components, or logic that are in the wrong place or could be better organized. Are there any instances of code that don't belong in their current file (misplaced logic)?
- Evaluate if we have a clear separation of concerns (e.g., presentation vs functionality vs data handling). Point out any overly coupled sections.
- Highlight any areas that are overly complex or not following WordPress best practices.
- Provide a report with specific recommendations to improve structure and maintainability, **without making any changes yet**.
Break down the suggestions into an ordered list of steps we could take, from most critical to optional enhancements.
*(This is a read-only analysis; do not modify the site during this audit.)*
```
This prompt is long, but it directs the AI to act like a code reviewer or architect. We've asked it to find mislocated code, check modularity, and even prioritize the fixes. The AI might respond with something like:
* *"1. **Separate custom functions from theme templates:** The `header.php` is directly making database queries. Suggestion: move data fetching to `functions.php` or a dedicated include to keep templates focused on presentation.*
* *2. **Reduce coupling in navigation logic:** The mobile menu toggle is updating both DOM and inline styles directly. This should be refactored to use proper CSS classes for better maintainability.*
* *3. **Organize utility functions:** There are helper functions scattered across multiple template files that would be better placed in a dedicated `inc/helpers.php` file.*
* *..."*
Each point might come with explanation and maybe references to specific files. Such a report helps you see the forest for the trees. It's especially useful if you've been focusing on one section at a time and haven't looked at the overall structure in a while.
Avoid generic and broad prompts
```text theme={null}
Nothing works, fix it!
```
Make your prompts more detailed and specific
```text theme={null}
The homepage hero section has gone blank after the last edit.
Can you check what happened and identify the cause?
```
After getting this output, you can decide which refactoring tasks to tackle (maybe even prompt the AI to implement some of those recommendations one by one).
### Safe approach for fragile updates
When you know the area you're changing is delicate (maybe a complex WooCommerce checkout flow or a core navigation system), it's wise to prepend a *cautionary guideline* in your prompt. This doesn't find bugs per se, but it helps prevent them by telling the AI to be extra careful.
**Example prompt – fragile update guidance:**
```text theme={null}
The next change is in a **critical part of the site**, so proceed with **utmost caution**.
- Carefully examine all related code and dependencies *before* making changes.
- **Avoid any modifications** to unrelated components or files.
- If there's any uncertainty, pause and explain your thought process before continuing.
- Ensure thorough testing after the change to confirm nothing else is affected.
**Task:** Update the WooCommerce checkout flow to add a gift message field without breaking the existing payment or shipping functionality.
*(Be extremely careful and double-check each step during implementation.)*
```
By including these guidelines and warnings, you're basically setting the AI's "mindset" to be cautious. The AI might then take a more measured approach, e.g., first explaining what it will do, or implementing the addition while explicitly noting that it left existing functionality intact.
This strategy is useful for **fragile sections**: checkout flows, payment processing, user authentication, membership areas – anything where a small mistake can break a lot. It's a preemptive debugging measure.
### Performance optimization check
If your WordPress site works correctly but is **slow** or resource-heavy, you can use a prompt to have the AI analyze performance. This might involve reviewing database queries, looking at rendering inefficiencies, or suggesting optimizations (caching, asset optimization, etc.).
**Example prompt – performance audit:**
```text theme={null}
Our WordPress site is functional but seems **sluggish**. Please **analyze the site for performance bottlenecks** and suggest optimizations:
- Check for any unnecessary database queries (e.g., duplicate queries or N+1 query patterns in loops).
- Identify any JavaScript or CSS that might be blocking rendering or loading unnecessarily.
- Look at our use of images and assets: are there any unoptimized images or large files affecting load time?
- Suggest improvements like caching frequently used data, lazy loading images, deferring non-critical scripts, and any other ways to speed up the site.
Provide the analysis and recommendations in a list. Do not make changes yet – just tell us what to improve for better performance.
```
Running this in Chat mode will give you a diagnostic report. The AI might say for example:
* *"Database queries: The blog archive is running a separate query for author data on each post. This could be improved by eager loading author data in the main query.*
* *Render blocking: There are 3 CSS files and 5 JS files loading in the header. Consider combining and deferring non-critical assets.*
* *Images: Noticed several hero images over 1MB. Compress these or use WebP format for faster loading.*
* *Caching: No object caching detected. Consider implementing Redis or Memcached for database query caching.*
* *..."*
Each suggestion comes from common WordPress performance best practices. You can then decide which ones to implement.
### Handling persistent errors
What about errors that just won't go away or keep coming back in slight variations? This can happen if the root cause isn't addressed. Here's a strategy:
* **Ask the AI what it has tried already.** Use: *"What solutions have we tried so far for this error?"* The AI can list the attempts, which helps you avoid repeating the same fixes.
* **Have the AI explain the error in simple terms.** *"Explain in simple terms why this error occurs."* This can reveal if the AI (and you) truly understand it.
* **Consider an alternate approach.** Ask: *"Given this error keeps happening, can we try a different approach to achieve the goal?"* The AI might suggest a different implementation strategy that bypasses the problematic area.
* **Revert and replay.** In worst-case scenarios, you might roll back a few steps. Then proceed with smaller changes.
Finally, if a specific component is "dead" (not working at all, no matter what), isolate it. Create a fresh minimal version of that component via prompt to see if it works, then slowly integrate it back. This is akin to turning things off and on again, but with code.
Throughout all this, maintain a dialogue with the AI. Treat it like a collaborator: *"We fixed X but now Y is acting up. What's the relationship between X and Y? Could the fix have caused Y's issue?"*
***
## Sample debugging flows
To cement these ideas, let's walk through common debugging scenarios with example flows:
### The "stuck in error loop"
You prompted something complex, and now the site won't load properly, and the fix failed twice.
*Flow:*
Throughout, you specifically described the error and had the AI confirm its understanding, rather than just blindly hitting fix repeatedly.
### The "feature not working right"
You added a contact form, but submissions aren't being received.
*Flow:*
By describing what you expect (an email) and what happened (nothing, with a log snippet), the AI was able to guide the investigation.
### The "UI element disappeared"
You refactored something and now a whole section of the page is just gone.
*Flow:*
Perhaps it realizes the refactor removed an include statement or changed a conditional that hides the section.
Prompt: *"Restore the services section by fixing the conditional or removing the wrapper that's hiding it."* Problem solved.
In this flow, the key was to notice the component was completely gone and communicate that.
Using browser dev tools and console logs
```text theme={null}
The site is showing a white screen.
Here's the error from the browser console:
Uncaught TypeError: Cannot read property 'querySelector' of null
at main.js:42:15
```
In all these cases, *communication and incremental steps* are your friends. Use the AI's strength in recalling details and analyzing errors. Use your strength in steering the process.
***
## Root cause analysis, rollback, and progressive enhancement
A few final pieces of advice:
### Root cause vs. symptom
Always ask "why did this happen?" not just "what to do now?". The AI can help find the root cause so that when you fix something, it stays fixed.
*I see you fixed the null error by adding a check, but why was it null in the first place? Can we address that cause?*
This leads to more robust solutions.
### Rollback wisely
Don't hesitate to roll back if the site has become too tangled by a series of bad fixes. It's often faster to rewind and try a different approach. If you do rollback, let the AI know:
*I reverted the site to before the navigation changes. Let's implement it again, but more carefully this time.*
This way, the AI has context that changes were undone.
### Progressive enhancement
When adding new features (especially complex ones), build them in small, testable increments. This isn't just a prompting tip – it's a development philosophy that pairs well with AI. If something breaks, you know exactly which small step caused it.
1. Add failing test cases.
2. Isolate the problem and analyze dependencies.
3. Document findings before applying fixes.
```text theme={null}
Here's the failing console log. Analyze the error, investigate the dependencies, and suggest a solution after understanding what's connected.
```
### Document as you go
It's helpful to keep notes (or even ask the AI to summarize what was done after a session). After resolving a tough bug, you might prompt:
*Summarize what the issue was and how we fixed it.*
The AI's summary can be saved for future reference. This is great for future you, or anyone else working on the site.
### Know when to ask for human help
Sometimes, despite all efforts, you might hit a wall. The Kintsu.ai community and support are there for you. Use the AI to gather as much info as possible first (so you can provide details), and then reach out if needed.
***
## Community debugging guidebook
These debugging principles apply to WordPress site improvements:
When fixing errors, focus exclusively on the relevant code sections without modifying unrelated functioning parts. Analyze the error message and trace it to its source. Implement targeted fixes that address the specific issue while maintaining compatibility with the existing site. Before confirming any solution, validate that it resolves the original problem without introducing new bugs. Always preserve working functionality.
When modifying existing code, use a surgical approach that changes only what's necessary. Preserve coding patterns and architectural decisions present in the theme or plugin. Before suggesting changes, analyze dependencies to ensure modifications won't break existing functionality. Present changes as minimal diffs rather than complete rewrites.
Before suggesting new database structures, thoroughly examine the existing schema to identify tables already present. Leverage existing tables whenever possible rather than duplicating data models. When modifications to the database are necessary, ensure they're compatible with existing queries. Consider migration strategies for schema changes that preserve existing data.
Approach every issue with a comprehensive diagnostic process. Begin by gathering all relevant information through careful examination of error messages, logs, and site behavior. Form multiple hypotheses about potential causes rather than jumping to conclusions. Test each hypothesis methodically until the root cause is identified.
Before confirming any solution, implement a rigorous verification process. Test the solution against the original issue to confirm it resolves the problem. Check for unintended side effects in related functionality. Ensure performance isn't negatively impacted. Verify compatibility with different browsers and devices.
Maintain consistency with the existing theme or plugin in terms of style, patterns, and approaches. Analyze the code to identify naming conventions, formatting preferences, and architectural patterns. Follow these established patterns when implementing new features or fixes.
When adding new features, build upon the existing architecture rather than introducing completely new paradigms. Identify extension points in the current design and leverage them for new functionality. Focus on backward compatibility to ensure existing features continue to work as expected.
Provide clear, concise explanations for all changes and recommendations. Explain not just what changes are being made, but why they're necessary and how they work. Document any assumptions or dependencies involved in the solution. Include comments in code when introducing complex logic.
Recognize when solutions might introduce technical debt and be transparent about these trade-offs. When time constraints necessitate less-than-ideal solutions, clearly identify what aspects would benefit from future refactoring. Distinguish between quick fixes and proper solutions.
Before creating new elements, conduct a thorough inventory of existing elements. Search for similar functionality. Identify opportunities to reuse or extend existing components rather than creating duplicates. Consider creating abstracted components that can be reused with different data or configurations.
Actively identify and remove unused code rather than letting it accumulate. When replacing functionality, cleanly remove the old implementation instead of simply commenting it out. Verify code is truly unused before deletion by checking for references throughout the site.
Treat working features as locked systems that require explicit permission to modify. Never remove or substantially alter features that are currently operational without explicit direction. When errors occur in one area, avoid making "just in case" changes to unrelated working components.
When encountering complex errors, resist the temptation to apply immediate fixes without deeper understanding. Take a deliberate step back to examine the problem from multiple perspectives. Consider fundamentally different approaches rather than minor variations of the same strategy.
Maintain strict adherence to the established design system and color palette. Before creating new UI components, study existing ones to understand the visual language. When implementing new interfaces, reuse existing patterns rather than creating visual variations.
Monitor site performance proactively. Review query caching strategies to minimize unnecessary database calls. Analyze asset loading patterns for potential bottlenecks. Implement virtualization for long lists and paginate large data sets. Focus on metrics that directly impact user experience.
Implement a comprehensive error handling strategy that maintains site stability while providing meaningful feedback. Design graceful degradation patterns where sections can continue functioning with limited data. Provide clear, user-friendly error messages.
# Prompt better in Kintsu.ai
Source: https://docs.kintsu.ai/prompting/prompt-better
Plan before you prompt, improve by component, use real content, and apply design buzzwords to get consistent, high-quality WordPress improvements.
> Plan before you prompt, improve by component, use real content, and apply design buzzwords to get consistent, high-quality results.
### Make Kintsu.ai ask clarifying questions
One of the most effective ways to get better results from Kintsu.ai is to let it fill in the gaps before making changes. After stating what improvement or change you want, add a line at the end of your prompt like:
> "Ask me any questions you need in order to fully understand what I want from this improvement and how I envision it."
Kintsu.ai will respond with focused, often insightful follow-up questions—sometimes ones you wouldn't have thought to specify. This process helps clarify your requirements up front and prevents misunderstanding or wasted effort later.
If you haven't tried prompting this way, give it a shot: you'll likely notice that site improvements land closer to your true intent, with less back-and-forth.
***
## Further Prompting Knowledge: Your Practical Playbook for Consistent, High-Quality Results in Kintsu.ai
Welcome to your comprehensive guide for high-impact prompting in Kintsu.ai!
This playbook brings together the most effective techniques, strategies, and principles for getting the best possible results when improving your WordPress sites. Whether you're new to prompting or ready to refine your skills, you'll find actionable advice and clear examples to help you evolve your sites quickly and consistently.
***
## Phase 1: Lay the Foundation
### 1. Plan before you prompt
Before using Kintsu.ai, define what you're improving. Skipping this step is like starting a renovation without knowing what room you're working on. Use a quick planning session—pen and paper, voice notes, ChatGPT, whatever works—to answer these four questions:
* What part of the site are you improving?
* Who visits this section?
* Why will this improvement matter to them?
* What is the one key action visitors should take?
You're not writing a spec doc. You're setting direction. The more aligned your thinking, the sharper your prompts. Vague ideas produce vague outputs. Clear thinking leads to clear results.
**Prompt example**
```text theme={null}
Improve the homepage hero section for a wellness clinic WordPress site. The main CTA should be "Book Your First Session." Focus on a calm, professional aesthetic with soft colors and clear typography.
```
### 2. Map the user journey visually
Design isn't about individual sections—it's about what happens between them. The best outputs in Kintsu.ai come from clear, logical flow. Map the journey your visitor takes from landing on the page to completing a key action.
Think in transitions:
* What does the visitor see first?
* What builds trust?
* What gives them confidence to act?
* Where does that action lead?
Even a simple three-step sketch — Hero → Services → CTA — can make your prompts 10× more effective.
> "You're not stacking blocks. You're guiding behavior. Every section should have a reason to exist—and a reason to lead to the next one."
### 3. Get the design right first
Your visual language is a foundation, not a polish layer. Kintsu.ai needs to know the look and feel you want—early. Otherwise, your improvements might function but feel totally wrong. Do not fix design problems later. Decide them up front.
Choose a direction, for example:
* Calm and elegant
* Bold and modern
* Premium and sleek
Then feed that style directly into your prompt using buzzwords, tone descriptors, and UI patterns. You can even create a "starter style prompt" and reuse it across all sections for consistency.
> "You don't prompt your way into good design. You prompt from it."
**Prompt example**
```text theme={null}
Use a calm, wellness-inspired design. Soft gradients, muted earth tones, round corners, and generous padding. Keep the existing brand fonts. Overall tone should feel gentle and reassuring.
```
***
## Phase 2: Think in Systems
### 4. Prompt by component, not page
Kintsu.ai works best when you improve your site in modular parts—not full pages at once. Asking it to redesign an entire homepage is like dumping a recipe into a blender. You'll get something, but it won't be usable.
Instead, approach your prompts like building with Lego bricks. Each block should have one clear purpose: a hero section, a services grid, a testimonial slider, a contact form. Improve one, review it, refine it, then move to the next.
When you prompt by component, you gain clarity, control, and flexibility. If something doesn't look right, you can fix just that block instead of re-prompting an entire page. This also helps you maintain consistency across your site—components can be refined and adapted without starting over.
> "A full-page prompt gets you noise. A section-based prompt gets you signal."
**Prompt example**
```text theme={null}
Update the sticky header with modern styling. Add smooth scroll behavior, a subtle shadow on scroll, and ensure the mobile menu is clean and accessible.
```
### 5. Design with real content
Kintsu.ai does not work well with placeholder content like "lorem ipsum" or "service 1 / service 2." The AI responds to structure and intent—and the fastest way to show intent is to use real words.
Even if your final copy isn't ready, use copy that reflects your message. If you're improving a page for a dental practice, write what a patient would actually read. Don't fake it.
This doesn't just help Kintsu.ai generate better layouts and spacing—it helps you make smarter design decisions. A real headline might need two lines instead of one. A CTA might work better if it's a verb instead of a noun. Placeholder text hides those issues. Real content reveals them early.
> "Design loves constraints. Real content creates the right ones."
**Prompt example**
```text theme={null}
Hero section with headline: "Your Smile, Our Priority." Subtext: "Compassionate dental care for the whole family." CTA: "Schedule Your Visit." Use a clean, trust-building layout with generous white space.
```
### 6. Speak atomic: buttons, cards, modals
Kintsu.ai thinks in atoms. The smaller and more specific your UI language, the better it performs. Instead of asking for a "section with a contact form," say, "Add a form with input fields for name, email, and message, plus a rounded submit button." These atomic instructions get interpreted as native patterns.
Think like a system. Describe cards, badges, toggles, form fields, dropdowns, etc. Don't say "a user interface" when you can say "a modal with a success message after form submission."
This atomic vocabulary also lets you layer complexity gradually. Start with a card. Then add an icon. Then add hover states. Each layer builds naturally on the last.
> "The smaller the part, the smarter the response."
**Prompt example**
```text theme={null}
Create a team member card with a profile photo, name, role title, and a brief bio. Add a subtle hover effect that lifts the card and shows social media links.
```
### 7. Use buzzwords to dial in aesthetic
Visual style is one of the most important—and most misunderstood—parts of prompting in Kintsu.ai. It's not enough to describe layout. You need to guide the tool on vibe. Buzzwords are the fastest way to do that.
Kintsu.ai understands terms like "minimal," "expressive," "professional," "playful," "premium," and "enterprise-grade." These aren't fluff—they're promptable parameters that influence typography, spacing, shadow, border radius, and color palette.
Use these words early in your prompts. Better yet, include them in every section. You'll get cohesive improvements across the board and avoid the dreaded "generic WordPress" look.
You can also mix and match buzzwords to evolve your tone. A page can start "bold and confident" in the hero and become "calm and reassuring" in the testimonials section.
> "Design isn't just structure. It's tone. Buzzwords define it."
**Prompt example**
```text theme={null}
Improve the pricing section to feel premium and trustworthy. Use clean card layouts, subtle shadows, strategic use of brand accent color, and clear visual hierarchy between plan tiers.
```
***
## Phase 3: Build with Precision
### 8. Use prompt patterns for layouts
Prompts are easier to write—and far more effective—when you use structured, repeatable patterns. Think of them as layout recipes. Rather than trying to explain your layout from scratch every time, describe it using a consistent rhythm.
A good layout prompt breaks the section into visual parts, clarifies their order, and defines how they're styled. Most patterns follow a "header → content → action" structure, but you can customize that flow depending on what you're improving.
Start building a personal prompt library. For example, write a go-to structure for a feature grid, a testimonial slider, or a pricing table. Reuse and remix these patterns with slight modifications to match different pages.
> "Kintsu.ai responds best to prompt language that is structured, scoped, and predictable. Prompt patterns make you faster and your output more consistent."
**Prompt example**
```text theme={null}
Create a services section with a centered headline, followed by three horizontally aligned cards. Each card includes an icon on top, a service name, and a short description. Cards should have soft shadows and lift on hover.
```
### 9. Add visuals via URL
Want your improvements to feel real? Reference existing images, product demos, or videos using URLs. Kintsu.ai supports visual embeds when prompted clearly.
Prompt for placement (e.g., below hero or inside a feature card), style (e.g., rounded corners, full-width), and context (why it's there).
**Prompt example**
```text theme={null}
Add a video testimonial section below the services. Embed the YouTube video at [URL]. Display it in a rounded container with a subtle shadow, centered on the page.
```
### 10. Layer context with the Edit feature
The Edit feature is one of the most powerful capabilities in Kintsu.ai—but only if you use it properly. Instead of rewriting full prompts when something needs to change, use edits to focus on specific layers or elements. This lets you iterate quickly without disturbing what's already working.
Think of edits like design overrides. They're not replacements—they're adjustments. For example, you can select a CTA button and change just the copy, or tweak a card layout without affecting the typography of the entire section.
This keeps your project clean and modular. You avoid prompt bloat, you move faster, and you reduce the risk of breaking something that was already working.
When editing, be precise in your language. Say exactly what you want to change and what should stay the same.
**Prompt example (within edit)**
```text theme={null}
Change the CTA button text to "Get Started Today" and increase the padding. Keep the existing background color and font styling.
```
***
## Phase 4: Iterate and Ship
### 11. Build with WordPress structure in mind
Improving a layout is just one part of evolving a WordPress site. If you want your Kintsu.ai improvements to work seamlessly, you need to think about how they'll integrate with your existing WordPress setup.
WordPress has its own patterns—themes, plugins, page builders, custom post types. Kintsu.ai understands this ecosystem and can help you work within it rather than against it.
When you're designing with WordPress in mind, start by anticipating:
* **Theme compatibility** — Will this improvement work with the existing theme structure?
* **Plugin interactions** — Are there contact forms, sliders, or other plugins that need to be preserved?
* **Responsive behavior** — How should this look on mobile vs desktop?
* **Content management** — Will the client be able to update this content easily?
This early thinking helps you prompt smarter sections and makes the improvement process smoother.
**Prompt example**
```text theme={null}
Improve the blog archive page layout. Keep the existing category filtering functionality. Display posts in a clean grid with featured images, titles, dates, and excerpt previews. Ensure it works with the current theme's pagination.
```
You don't need to rebuild everything—but thinking about how improvements integrate with existing WordPress structures is how you avoid breaking what already works.
### 12. Version control is your friend
Kintsu.ai helps you track changes, but that doesn't mean you should move fast without thinking. If you're not keeping track of what you changed and why, you'll lose control quickly.
Good versioning isn't about naming files. It's about thinking in iterations. Make one meaningful change at a time. Update the hero section. Improve the navigation. Adjust the footer. Check the result. Then move forward.
This is how professional site evolution works—layer by layer, with intention.
Adopt your own system:
* Think in milestones (e.g., "homepage complete", "services section improved", "mobile responsive")
* Document your prompts and what they achieved
* Preview before major changes, and create backups before risky improvements
> "Safe iteration doesn't mean slow. It means confident. Build intentionally. Iterate with awareness."
**Prompt habit**
```text theme={null}
Before making a major change to a production section, review the current state and ensure you can roll back if needed. Small cost, big safety net.
```
***
## Summary
Effective prompting in Kintsu.ai comes down to a few core principles:
1. **Plan before you prompt** — Know what you're improving and why
2. **Work in components** — Small, focused improvements beat sweeping changes
3. **Use real content** — Placeholder text leads to placeholder results
4. **Speak specifically** — Atomic UI language gets atomic precision
5. **Set the vibe early** — Buzzwords shape the aesthetic from the start
6. **Iterate safely** — Layer improvements, track changes, stay in control
Master these, and you'll transform how you evolve WordPress sites with Kintsu.ai.
# Could not reach the Kintsu API
Source: https://docs.kintsu.ai/troubleshooting/could-not-reach-api
Fix the 'Could not reach the Kintsu API' error when connecting your WordPress site to Kintsu AI.
If you see this error when connecting your WordPress site to Kintsu AI, your site's permalink settings may need to be updated.
## How to fix
In your WordPress admin, go to **Settings → Permalinks**.
Select any option **other than "Plain"** (we recommend **Post name**).
Click **Save Changes**.
Go back to Kintsu AI and try connecting again.
## Why this happens
Kintsu AI communicates with your WordPress site through its REST API. This API requires "pretty permalinks" to be enabled — which is any permalink setting other than "Plain."
Most WordPress sites have this enabled by default, but some hosting environments or fresh installations may use the "Plain" option.
## Still not working?
If you've changed your permalinks and are still seeing this error, it could be caused by:
* A **security plugin** (like Wordfence or Sucuri) blocking API requests
* A **firewall** (like Cloudflare) challenging bot traffic
* Your **hosting provider** blocking external API access
Contact us at [support@kintsu.ai](mailto:support@kintsu.ai) and we'll help you get connected.
# WordPress REST API (wp-json) returning 404
Source: https://docs.kintsu.ai/troubleshooting/wp-json-404
Fix the wp-json 404 error that prevents your WordPress site from connecting to Kintsu AI.
## Symptoms
* Can't connect your site to Kintsu
* Visiting `yoursite.com/wp-json/` shows "Not Found"
* WordPress Site Health shows: "The REST API encountered an unexpected result"
* Your homepage works but other pages may not
## Cause
Your server's Apache configuration is ignoring WordPress's `.htaccess` rewrite rules. This is common on unmanaged hosting providers like Hetzner, DigitalOcean, and AWS EC2, where Ubuntu ships with `AllowOverride None` by default.
## Quick check
Visit `yoursite.com/wp-json/` in your browser. If you see an Apache "Not Found" page instead of JSON data, this guide applies to you.
## Fix (if you have SSH access)
```bash theme={null}
sudo nano /etc/apache2/apache2.conf
```
Look for this block:
```apacheconf theme={null}
Options Indexes FollowSymLinks
AllowOverride None
```
Change `None` to `All`:
```apacheconf theme={null}
Options Indexes FollowSymLinks
AllowOverride All
```
```bash theme={null}
sudo systemctl restart apache2
```
In WordPress, go to **Settings → Permalinks** and click **Save Changes**.
## Fix (if you don't have SSH access)
Send this to your hosting provider's support:
"WordPress REST API URLs (`/wp-json/`) are returning 404. Please change `AllowOverride None` to `AllowOverride All` for the `/var/www/` directory in the Apache configuration and restart Apache."
## After fixing
Visit `yoursite.com/wp-json/` again — you should see JSON data instead of a 404. Then reconnect your site in Kintsu.