feat(ai-autopilot): compose vike-crud/vike-admin for CRUD+admin UI#191
Merged
Conversation
) Add a vike-crud-composer persona to vikeExtensionPersonas so the composed build derives list/record/form screens and the admin panel from the schema instead of hand-writing them. Teaches crud()/crudBlocks() in a definePage, vike-admin resources for /admin/*, named crudActions for mutations, and the config -> slot -> eject ladder. No runtime change. Closes #189.
suleimansh
added
enhancement
This was referenced Jul 4, 2026
Closed
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
1 participant
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.
Teaches the composed build to derive the CRUD/admin UI from the schema instead of hand-writing it. Same lever as the auth/data composers (#187/#188): a persona, no runtime change, the agent stays a black box.
What changed
vike-crud-composerpersona inai-autopilot, wired intovikeExtensionPersonas(after data + auth, before the ui-intent guardrail).crud({ table })/crudBlocks({ table })inside adefinePage(screens derived from the schema, refined only where needed withcolumn()/display()/field()); render viavike-crud/react(or/vue);vike-adminfor a whole-DB/admin/*panel through the cumulativeadminResourcesseam; mutations via namedcrudActions(posts.delete, referenced by name, no inline closures); and the config -> slot -> eject ladder so eject is last resort.crud({ table })/ vike-admin / named actions / eject and forbids hand-rolled screens;vikeExtensionPersonasorder updated.API verification
Cross-checked every snippet against the real
vike-crud/vike-adminpublic API in the vike-data repo (README + exports):crud/crudBlocks/definePage/column/display/field,crudActions,vike-crud/reactPage,registerFieldWidgetfromvike-crud/react/widgets,ejectViewfromvike-crud/eject, anddefineResourcefromvike-admin/define.Notes
framework-live-blogworkspace CLAUDE.md named in the issue was untracked local scratch and no longer exists, so there is nothing to mirror there. The persona is the durable artifact that composes at runtime.Part of #186. Closes #189.