git-subtree-dir: aiui git-subtree-mainline:0c4826f8ccgit-subtree-split:e30ac1d106
1.5 KiB
name, description, allowed-tools
| name | description | allowed-tools |
|---|---|---|
| fix-tab | Diagnose and fix a broken content panel tab (extraction, routing, rendering) | Bash(*), Read, Edit, Glob, Grep, Agent |
Diagnose and fix a broken content panel tab. The user will specify which tab (e.g., "app", "code", "image", "nostr").
Diagnostic pipeline — check each layer:
-
System prompt: Does
useAI.tsSYSTEM_PROMPT tell the AI to use the tag format for this content type? If not, add instructions. -
Tag regex: Does
contentExtraction.tshave a regex for this content type's tags? If not, add one. -
Extraction function: Does
extractAll{Type}s()orextract{Type}s()exist and work correctly? Test with sample input. -
Query classifier: Do
is{Type}Query()and/oris{Type}LikeResponse()exist incontentFiltering.ts? -
Tab filtering: Is the tab included in
filterTabsByContext()andpreferredFirstTab()? Check the boolean flag is wired. -
useContentPanel.ts: Is the extraction called in
updatePanelFromText()? Is the panel ref populated? Is the tab added toavailableTabs? -
ContentPanel.vue: Is there a grid render block for
activeTab === '{tab}'? Are imports present? Is the tab in TAB_LABELS? -
ContentGridView.vue: Same checks for the wide desktop view.
-
ChatPage.vue: Are the panel data props passed to ContentGridView?
-
Grid component: Does the grid component exist and render correctly?
-
Detail component: Does the detail component exist?
Fix each broken layer. Run pnpm typecheck after all fixes.