Skip to content

update skill to say dont make up Tabler icons #2703

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
emmacramer wants to merge 3 commits into
base: main
Choose a base branch
from
+5 −0
Open

update skill to say dont make up Tabler icons #2703

Changes from 2 commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
4f2fb77
update skill to say dont make up Tabler icons
emmacramer Aug 6, 2026
b157950
Update SKILL.md
emmacramer Aug 6, 2026
388b79a
Merge branch 'main' into emmacramer-patch-1
emmacramer Aug 7, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 5 additions & 0 deletions .agents/skills/frontend-design/SKILL.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -130,6 +130,11 @@ passed this requirement yet.
- Do not build custom dropdowns, menus, popovers, modals, or confirmations with manual absolute positioning and click-outside effects.
- Never use browser dialogs (`window.alert`, `window.confirm`, `window.prompt`). Use `AlertDialog`, `Dialog`, or app-specific confirmation UI.
- Use Tabler icons for all first-party UI icons. Do not add Lucide, Heroicons, inline SVG icon sets, or emoji icons.
- Never guess a Tabler icon name. Names like `IconPartyPopper` or `IconConfettiCannon` feel
plausible but don't exist and crash Vite with a "Named export not found" error. Before importing
an icon you haven't used elsewhere in this app, confirm it exists by grepping
`node_modules/@tabler/icons-react/dist/tabler-icons-react.d.ts` (or the package's icon list)
for the exact name, and pick the closest real match if your first guess isn't there.
- Use `useActionQuery` and `useActionMutation` from `@agent-native/core/client` for action-backed UI. Standard CRUD should go through actions, not custom `/api/` routes.
- Keep UI optimistic where possible: update cache and navigation immediately, then reconcile or roll back on mutation result.
- Custom styles belong in Tailwind classes, component CSS, or the existing global CSS theme file; avoid inline styles.
Expand Down