update skill to say dont make up Tabler icons - #2703
Conversation
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
Visual recap — skipped (diff too small)The change in this pull request is too small to be worth a visual recap. This is informational only and does not block the PR. |
|
@builderio-bot why is the Chat template E2E test failing? |
|
I looked into PR #2703 and the CI run for the failing job. What's failing: The The element exists (it's already marked Why it's not related to this PR: This PR only touches Confirmation it's not a broken/consistently-failing test: The same workflow has been passing reliably on Recommendation: Re-run the failed job — this should be safe to retry since the PR content is docs-only. Want me to trigger a re-run via ⠀ |
There was a problem hiding this comment.
Builder reviewed your changes — looks good ✅
Review Details
Incremental Code Review Summary
The latest PR head remains a documentation-only addition to .agents/skills/frontend-design/SKILL.md. The Tabler icon verification guidance is unchanged and remains technically correct: the declaration path is node_modules/@tabler/icons-react/dist/tabler-icons-react.d.ts, the package layout supports it, and the previously corrected dist/esm/ path has not regressed.
Independent reviews found no new or unresolved actionable issues. The guidance is consistent with the surrounding frontend-design rules and should help prevent invalid named imports that fail Vite builds. This remains low risk with no user-facing runtime impact. 🧪 Browser testing: Skipped — PR only modifies backend/config/docs, no UI impact.
silly agent