You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/next-steps.md
+16Lines changed: 16 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -45,3 +45,19 @@ Focused follow-up work for `@knighted/develop`.
45
45
- Ensure assistant/editor integration remains compatible with this model (edits should target one of the fixed tabs) without expanding to dynamic tab metadata yet.
46
46
- Suggested implementation prompt:
47
47
- "Implement Phase 2 UX/UI tab support in @knighted/develop with a fixed first-pass tab model: Component, Styles, and App only (no arbitrary tab names yet). Add a clear tab UI for switching editor panes, preserve existing editor behavior/content wiring, and keep render/lint/typecheck/diagnostics flows working with the selected tab context where relevant. Keep AI/BYOT feature-flag behavior unchanged, maintain CDN-first runtime constraints, and do not add dependencies. Add targeted Playwright coverage for tab switching, default/active tab behavior, and interactions with existing render/style-mode flows. Validate with npm run lint and targeted Playwright tests."
- Add a short behavior matrix in docs that explains when implicit App wrapping is allowed versus when users must define `App` explicitly.
51
+
- Include concrete Component editor examples for each case so reviewer/user expectations are clear.
52
+
- Suggested example cases to document:
53
+
- Allowed implicit wrap (standalone top-level JSX, no imports/declarations), for example:
54
+
-`(<button type="button">Standalone</button>) as any`
55
+
- Requires explicit `App` (top-level JSX with declarations/imports), for example:
56
+
-`const label = 'Hello'`
57
+
-`const Button = () => <button>{label}</button>`
58
+
-`(<Button />) as any`
59
+
- Recommended explicit pattern, for example:
60
+
-`const Button = () => <button>Hello</button>`
61
+
-`const App = () => <Button />`
62
+
- Suggested implementation prompt:
63
+
- "Document the current implicit App behavior in @knighted/develop for auto-render mode using a compact behavior matrix and concrete component-editor snippets. Clearly distinguish supported implicit wrapping from cases that intentionally require an explicit App (such as top-level JSX mixed with imports/declarations). Keep docs concise, aligned with current runtime behavior, and include at least one positive and one explicit-error example."
0 commit comments