docs(intent): sync AI assistant guide with the parser implementation#6295
Merged
Conversation
Reconcile intent-assistant-guide.md (the Intent Editor AI assistant's system prompt) with what IntentParser actually accepts: - Fix Calendar: it is fully implemented (view: calendar|range|slots, calendar:/slots: blocks, function: Calendar), not "reserved/not yet available". The reserved-and-rejected entity functions are Board / Gantt / Timeline. - Add a "views - calendar, range, and slots" capability section documenting the calendar:/slots: blocks and their keys. - Document assignee: personal on user tasks (routes to the record owner's Inbox; requires a personal: relation). - Document field aggregate: true (document totals footer). - Document scheduled generate.children (per-matched-row fan-out). - Extend the Allowed values table with entity/field/relation function, entity view, report kind/chart/widget, custom widget kind, rollup op and expansion unit enums. Source of truth: IntentParser.java + the model POJOs. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Reconciles
components/engine/engine-intent/src/main/resources/intent-assistant-guide.md— the system prompt that powers the Intent Editor's AI assistant — with whatIntentParseractually accepts. The parser + model POJOs are the single source of truth.Why
The guide had drifted from the implementation in a few places, most notably claiming the calendar family was "reserved / not yet available" when it ships and is accepted by
validateViews. Since this file is the assistant's system prompt, drift here directly degrades the suggestions users get in the editor.Changes
view: calendar | range | slots, thecalendar:/slots:config blocks, andfunction: Calendarare fully implemented (IntentParser.validateViews,CalendarIntent,SlotsIntent). Corrected the reserved-values note: the entity functions that are recognised-but-rejected areBoard/Gantt/Timeline.calendar:block (start/end/title/color/scope/initialView) and theslots:block (start/open/close/step/disabledDays), plus the embedded-calendar-in-detail-pane behaviour for composition children.assignee: personalon user tasks (routes the task to the record owner's Inbox; requires apersonal:relation — the parser rejects it otherwise).aggregate: true(document totals footer).generate.children(per-matched-row fan-out, e.g. a day row per working day).function, entityview, reportkind/chart/widget.kind, custom-widgetkind, rollupopand expansionunitenums.Verification
Every added/changed statement was checked against
IntentParser.javaand themodel/*.javaPOJOs (enum sets,validateViews,validateTaskFormActionsforassignee: personal,CalendarIntent/SlotsIntentfield names and defaults). Content-only change to a classpath Markdown resource; no code paths affected.🤖 Generated with Claude Code