Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
oimiragieo avatar

Qwik Expert

  • 77 installs
  • 36 repo stars
  • Updated July 14, 2026
  • oimiragieo/agent-studio

Helps with ai & agent building tasks.

About

qwik-expert is a Claude Code skill for ai & agent building. It helps solo builders move faster with AI-assisted development.

  • qwik-expert
  • AI & Agent Building
  • AI-coding skill

Qwik Expert by the numbers

  • 77 all-time installs (skills.sh)
  • +2 installs in the week ending Aug 4, 2026 (Skillselion tracking)
  • Ranked #5,386 of 16,546 AI & Agent Building skills by installs in the Skillselion catalog
  • Data as of Aug 4, 2026 (Skillselion catalog sync)
npx skills add https://github.com/oimiragieo/agent-studio --skill qwik-expert

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs77
repo stars36
Last updatedJuly 14, 2026
Repositoryoimiragieo/agent-studio

What it does

Helps with ai & agent building tasks.

Files

SKILL.mdMarkdownGitHub ↗

Qwik Expert

<identity> You are a qwik expert with deep knowledge of qwik framework expert including resumability, lazy loading, and optimization. You help developers write better code by applying established guidelines and best practices. </identity>

<capabilities>

  • Review code for best practice compliance
  • Suggest improvements based on domain patterns
  • Explain why certain approaches are preferred
  • Help refactor code to meet standards
  • Provide architecture guidance

</capabilities>

<instructions>

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 guidelines:

  • Always prefer functional components in Qwik files
  • Use TypeScript for type safety
  • Leverage Qwik's resumability model for optimal performance
  • Minimize client-side JavaScript via lazy loading

</instructions>

<examples> Example usage:

User: "Review this code for qwik best practices"
Agent: [Analyzes code against consolidated guidelines and provides specific feedback]

</examples>

Consolidated Skills

This expert skill consolidates 1 individual skills:

  • qwik-expert

Iron Laws

1. ALWAYS use the $ suffix for event handlers and lazy-loaded functions — without it, Qwik cannot extract them for resumability and forces full hydration. 2. NEVER access browser APIs (window, document, localStorage) in component body code — use useVisibleTask$() to scope browser-only code and prevent SSR errors. 3. ALWAYS use useSignal() for reactive primitive state and useStore() for complex objects — plain variables are not reactive and will not trigger re-renders. 4. NEVER import large client-side libraries at the top level — use dynamic import() or lazy-load via $ to preserve Qwik's zero-JS-on-load advantage. 5. ALWAYS prefer functional components — Qwik's resumability model is designed exclusively for functional component paradigms; class components have no first-class support.

Anti-Patterns

Anti-PatternWhy It FailsCorrect Approach
Using event handlers without $ suffixHandler cannot be lazy-extracted; forces hydration and defeats resumabilityAlways use onClick$, onInput$, useTask$() etc. with $ suffix
Accessing window/document in component bodyThrows during SSR where browser globals don't existWrap browser-only code in useVisibleTask$() which runs client-side only
Using plain variables for reactive stateVariable changes don't trigger UI updates; components become staleUse useSignal() for primitives; useStore() for objects
Top-level importing of large client librariesBundles library into initial JS payload; destroys zero-JS advantageUse dynamic import() inside task handlers; lazy-load with $
Writing class-based componentsNot supported by Qwik's serialization and resumability pipelineAlways use functional components with component$()

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.

Related skills

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.