AI Conversation Builder
AI conversation is Linkraft's core interaction method. Using it well can greatly improve efficiency; using it poorly can easily waste Credits without reaching expectations. This article explains the conversation mechanism and practical tips.
What Conversation Can Do
| Stage | Role of Conversation |
|---|---|
| Before building | Describe needs and let AI generate the requirements document and website |
| After building | Modify the website: change style, add/remove sections, add pages, fix issues |
Conversation entry: the input box at the bottom of the site page, available anytime.
How Conversation Executes
AI Does More Than Answer — It Executes Tasks
Unlike ordinary chatbots, Linkraft's AI actually modifies your website files. After you issue an instruction, the interface displays the execution process in real time:
| Display | Meaning |
|---|---|
| Task executing… | Processing |
| N tasks executed | Cumulative completed tasks |
| New content / Edited content | Creating or modifying files |
| Wrote N lines / +N lines / -N lines | Code change volume |
| Current task progress | Overall progress |
Specific Actions You Will See
AI invokes various capabilities while working. The interface may show:
| Action | Description |
|---|---|
| Analyzing website… / Website analysis completed | Reads current website structure and understands context |
| Generating requirements document | Produces PRD |
| Viewing directory | Browses project file structure |
| Reading content | Reads existing file content |
| Fuzzy code search | Locates positions that need modification |
| Retrieving relevant materials | Finds reference information |
| Executing command line | Runs build commands, etc. |
| Configuring backend services | Builds server-side capabilities |
| Executing SQL statements / Getting table info / Getting table data | Operates database |
| Calling plugin skills | Calls specialized function plugins |
| Information collection form | Requires you to fill in information |
| Enabling email verification / Enabling SMS verification | Configures visitor login capabilities |
| Preview page / Go to preview | Results can be previewed |
The value of this transparency is that you can judge whether AI understood correctly. If you notice it is modifying irrelevant places, you can interrupt and re-explain in time.
Conversation Is Continuous
AI remembers the context of the current session. You can make requests continuously like this:
You: Change the homepage primary color to dark blue
AI: (completes modification)
You: Make the font larger too
AI: (understands "font" refers to the homepage font)
You do not need to repeat the background every time.
How to Write Good Instructions
This is the most important part of this article. Instruction quality directly determines result quality and Credits consumption.
Principle 1: Say Clearly "Where to Change"
AI needs to know the modification location.
| ❌ Poor | ✅ Better |
|---|---|
| Change the title | Change the homepage hero title to "Focused on Handmade Leather Goods for 8 Years" |
| The color looks bad | Change the navbar background from white to dark gray |
| Add a module | Add a customer testimonials module below the homepage product showcase |
Principle 2: Say Clearly "What to Change To"
Give a clear target state, not just dissatisfaction.
| ❌ Poor | ✅ Better |
|---|---|
| This section is ugly | Change this section to a three-column card layout, each card with an icon and title |
| The layout has issues | The product list displays in one column on mobile; currently two columns are squeezed together |
| Not professional enough | Switch to business style: dark blue with gray-white, right-angle borders, sans-serif fonts |
Principle 3: One Thing at a Time
Multiple unrelated requests at once are easy for AI to miss or misunderstand.
| ❌ Poor | ✅ Better |
|---|---|
| Change the homepage color, then add a contact form, also adjust the product page, and change the nav order | Say it in four separate messages, one thing each |
Exception: Related modifications to the same location can be said together, e.g., "Change the homepage hero title to XXX, subtitle to YYY, and button text to 'Contact Us Now'."
Principle 4: Use the Editor If You Can
This saves the most money. The following operations are faster in the visual editor and consume no Credits:
- Changing text content
- Replacing images
- Adjusting font size, color, alignment
Conversation is suitable for: structural changes, style system adjustments, adding features, adding pages.
Principle 5: Use Screenshots
If something displays abnormally, you can upload a screenshot, which is more accurate than text description.
If "Screenshot parsing failed, please retry" or "Screenshot upload failed, please retry" appears, just upload again.
Common Instruction Templates
Use directly.
Visual Style
Change the whole site's primary color to #1E3A8A (dark blue), with light gray as the auxiliary color
Change the overall style to minimal: more white space, remove shadows, use sans-serif fonts
Make all buttons rounded, and darken the color on hover
Make the navbar fixed at the top and not disappear when scrolling
Section Add/Remove
Add a customer testimonials module below the homepage "Product Introduction" section, three-column cards, each with avatar, name, and testimonial content
Delete the "Team Introduction" section on the homepage
Swap the positions of the "About Us" and "Service Items" sections on the homepage
Add a contact bar at the bottom of the page, including address, phone, email, and WeChat QR code
Content Structure
Change the navbar order to: Home, Product Center, Solutions, About Us, Contact Us
Change the product list to three per row, with pagination, 9 per page
Add category filtering to the article list
Features
Add a contact form collecting name, company, phone, and requirement description; save to database after submission
Add an online booking feature, can select date and time slot, need to fill in phone number
Add visitor login with phone number verification code
Add an "Inquiry" button to the product page, click to pop up a form
Responsive Adaptation
Change mobile navigation to a hamburger menu
Change product list to single column on mobile
Halve the height of the homepage hero image on mobile, and keep text from overlaying the image
Fixes
Fix: the bottom button on the mobile homepage is blocked
The product detail page images are not scaled proportionally and are distorted
Add a success prompt after form submission
The interface also provides a "Fix Issue" shortcut to trigger the fix flow directly.
Interaction Forms in Conversation
AI will proactively ask when it needs more information. Forms include:
| Form | Interface Display | Operation |
|---|---|---|
| Single choice | Option list | Select one. If not selected, prompts "Please select an option" |
| Multiple choice | Marked "(multiple choice)" | Select at least one. If not selected, prompts "Please select at least one option" |
| Fill in the blank | Input box | Enter content. If empty, prompts "Please fill in content" |
| Custom input | Options + input box | Prompts "Please enter custom content" |
| Upload file | Upload control | Prompts "Upload relevant materials for supplementation, supporting company logo, company address, company phone, and company introduction" |
After filling in, click "Submit."
Two Key Decision Points
Decision 1: Continue Refining vs Generate Directly
After the first requirement description, AI will ask follow-up questions. At this point there are two buttons:
| Button | Effect | Applicable Scenario |
|---|---|---|
| Continue to refine requirements | AI continues asking questions | Description is brief; you want AI to help you think it through |
| Generate requirements document directly | Skip follow-up questions and produce PRD immediately | Description is already detailed; you do not want to answer more questions |
Suggestion: When the description is complete, choose "Generate directly" to save time and Credits.
Decision 2: Upgrade vs Skip
When needs exceed current plan capabilities, a popup asks you to choose:
| Scenario | Choose "Upgrade" | Choose "Skip" |
|---|---|---|
| Database capability limited | Get full data storage capability | Website can be generated, but data cannot be saved |
| Premium plugin limited | Implemented by dedicated plugin, stable and reliable | AI implements autonomously, function availability cannot be guaranteed |
Reminder: If the feature is core to the business (e.g., booking records for a booking system), do not choose skip — the feature will be useless. If it is only an auxiliary feature, skip is acceptable.
Abnormal Situation Handling
| Prompt | Meaning | Handling |
|---|---|---|
| Conversation in progress | Previous round not finished | Wait for the current task to complete before sending a new instruction |
| System exception, please try again later | Temporary service exception | Retry later |
| Request failed, please retry. | Network or service fluctuation | Resend the instruction |
| Task N execution failed | A subtask failed | Rephrase the description; or break into smaller steps |
| Input contains sensitive words | Triggered content security check | Adjust wording and retry |
| Credits quota used up | Balance exhausted | Recharge, then click "Payment completed"; task continues |
| Card not found | Interface rendering exception | Refresh the page |
Dealing with Repeated Task Failures
If the same requirement fails multiple times, try these methods:
- Break it down: Split "build a complete membership system" into "add login first," "then add member center page," and "finally add benefits display."
- Rephrase: Describe it in more specific, technology-independent language.
- Switch methods: If it is just a style issue, use the visual editor to manually adjust.
- Preview first to confirm: Sometimes the task actually succeeded but the interface did not refresh. Refresh the page to see the actual effect.
Efficiency and Cost Suggestions
Reducing Credits Consumption
| Practice | Effect |
|---|---|
| Make the first description as complete as possible | Reduce follow-up rounds and get it right the first time |
| Use the visual editor for small changes | Consumes no Credits at all |
| One thing at a time | Avoid rework due to misunderstanding |
| Carefully review at the PRD stage | Structural issues resolved before generation cost the least |
| Upload reference materials | Reduce AI guessing and trial-and-error |