What the Data for This Category Looks Like
Daily documents for this category typically include interaction prototypes, page flowcharts, component descriptions, and design review records. Teams source data primarily from Figma or Axure files, internal team design systems, user feedback, and usability test records. Most updates happen weekly or align with product version iterations. The most time-consuming steps focus on sorting state transitions, supplementing abnormal scenarios, and revising review comments. This category centers on page structure and operation path definition. It differs from requirements analysis documents by not emphasizing business rules or function descriptions.
What Constraints These Characteristics Impose on Knowledge Base Retrieval and Recall
Interaction prototypes and review records mostly use structured page node descriptions and operation logic. Fields typically include page ID, interaction actions, trigger conditions, and more. Data volume grows gradually with version iterations. The high update frequency requires the knowledge base to support frequent incremental synchronization. This prevents retrieval results from lagging behind the latest design versions. Supplementary modifications to abnormal scenarios trigger partial data adjustments. Retrieval and recall must accurately match current version design details, while avoiding interference from redundant old data. Component description documents have strong reusability. Retrieval rules must support matching cross-page component call logic, while filtering out obsolete historical version content.
Configuration Settings
The following configuration items apply to FastGPT v4.17.0 knowledge base retrieval and recall logic:
| Configuration Item | Recommended Value | Rationale |
|---|---|---|
similarity | 0.72–0.80 | Matches operation path descriptions in interaction prototypes, filters low-relevance non-design documents, and prevents irrelevant business requirement content from appearing in retrieval results |
limit | Top 6 | Limits the number of design document entries returned per round to fit review and Q&A scenarios for front-end teams, preventing excessive entries from exceeding the context window |
searchMode | Semantic Retrieval | Adapts to unstructured text descriptions of interaction prototypes, accurately matching operation logic and page structure keywords |
usingReRank | Enabled | Re-ranks initial retrieval results to prioritize recalling component descriptions or review records with higher relevance to current pre-sales or support questions |
datasetSearchUsingExtensionQuery | Enabled | Expands relevant design terminology based on user questions, matching hidden component naming and interaction rules in Figma files |
Three Common Configuration Mistakes
- Phenomenon: Knowledge base results returned via API do not match those in the platform test interface. Cause: The
collectionIdsparameter was not specified in the API request to bind the corresponding design knowledge base. The default public dataset does not sync the latest Axure prototypes and review records. - Phenomenon: Obsolete old version prototype pages appear in retrieval results. Cause: No regular cleanup rule for expired design documents was configured, and low-priority historical version data was not filtered via the
similaritythreshold. - Phenomenon: Hidden interaction rules in component descriptions cannot be retrieved. Cause: The
datasetSearchUsingExtensionQueryparameter was not enabled, so matching design system professional term aliases is not supported.
How to Confirm Configuration Is Successfully Applied
- Upload a latest Axure prototype fragment to the test knowledge base. Enter a question corresponding to the operation path in the platform test interface, and verify whether the retrieval results include the fragment’s content.
- Call the API to initiate a retrieval request, compare the number of returned entries and their order with those in the platform test interface, and confirm that the
limitandusingReRankconfigurations are active. - Check the knowledge base’s document update log to confirm that design review records from the past week have completed synchronization, verifying that the high-frequency update configuration logic works properly.
- Try entering a question containing a design term alias, and confirm that enabling
datasetSearchUsingExtensionQueryallows recalling the corresponding component description document.
The values provided are common starting points and should be measured against the reader's own samples.
Question material comes from public community discussions. Configuration values are common starting points and should be measured against your own samples. Verified on 2026-10-19.