Qwik Expert qwik and tailwind best practices
When reviewing or writing code, apply these guidelines:
Use $ suffix for lazy-loaded functions Utilize useSignal() for reactive state Implement Tailwind CSS classes for styling Use @apply directive in CSS files for reusable styles Implement responsive design using Tailwind's responsive classes Utilize Tailwind's configuration file for customization Leverage TypeScript for type safety Use Vite's fast HMR for development qwik city routing
When reviewing or writing code, apply these guidelines:
Utilize Qwik City for routing when applicable qwik folder structure
When reviewing or writing code, apply these guidelines:
Recommended folder structure:
src/ components/ routes/ global.css root.tsx entry.ssr.tsx public/ tailwind.config.js postcss.config.js vite.config.ts tsconfig.json
qwik functional components preference
When reviewing or writing code, apply these guidelines:
Always prefer functional components in Qwik files. qwik js best practices
When reviewing or writing code, apply these guidelines:
Use $ suffix for lazy-loaded functions Utilize useSignal() for reactive state Implement useStore() for complex state objects Use useResource$() for data fetching Implement useTask$() for side effects Utilize useVisibleTask$() for browser-only code qwik js error handling optimization
When reviewing or writing code, apply these guidelines:
Implement proper error boundaries Utilize Qwik City for routing when applicable Use Qwik's built-in optimization features Implement lazy-loading for improved performance qwik js folder structure
When reviewing or writing code, apply these guidelines:
Use the following folder structure:
src/ components/ routes/ global.css root.tsx entry.ssr.tsx public/ vite.config.ts tsconfig.json
qwik js general preferences
When reviewing or writing code, apply these
Consolidated Skills
This expert skill consolidates 1 individual skills:
qwik-expert Memory Protocol (MANDATORY)
Before starting:
cat .claude/context/memory/learnings.md
After completing: Record any new patterns or exceptions discovered.
ASSUME INTERRUPTION: Your context may reset. If it's not in memory, it didn't happen.