Home / Cursor rules / Qwik Basic
Qwik Basic
Cursor rules for Qwik development with TypeScript and Vite integration.
Cursor rules (.mdc)Public domain (CC0)
–unranked
Install
mkdir -p .cursor/rules && curl -sL https://raw.githubusercontent.com/PatrickJS/awesome-cursorrules/b044f956f021b6e8877f16781bcfc466a6a120e9/rules/qwik-basic-cursorrules-prompt-file.mdc -o .cursor/rules/qwik-basic.mdcDownloads the file at commit b044f956f021 into .cursor/rules/.
To remove it later:
rm .cursor/rules/qwik-basic.mdcContext cost: ≈320 tokens when used.
Rules file
--- description: "Cursor rules for Qwik development with TypeScript and Vite integration." globs: **/* alwaysApply: false --- // Qwik.js Basic Setup (with TypeScript and Vite) .cursorrules // Prefer functional components const preferFunctionalComponents = true; // Qwik.js best practices const qwikBestPractices = [ "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", "Leverage TypeScript for type safety", "Use Vite's fast HMR for development", ]; // Folder structure const folderStructure = ` src/ components/ routes/ global.css root.tsx entry.ssr.tsx public/ vite.config.ts tsconfig.json `; // Additional instructions const additionalInstructions = ` 1. Use TypeScript for all .ts and .tsx files 2. Implement proper error boundaries 3. Utilize Qwik City for routing when applicable 4. Use Qwik's built-in optimization features 5. Implement lazy-loading for improved performance 6. Follow Qwik's naming conventions and best practices 7. Use server$ for server-side code execution 8. Leverage Vite plugins for optimized builds `;
Security
Scanned Nov 4, 2026 at commit b044f956f021, with Cisco's open-source skill-scanner.
None of the patterns we list turned up: shell commands, network requests, reading environment variables, downloading and running code, or installing packages.
A scan lists patterns in the code. It can't prove an add-on is harmless, and it can miss things, so read what you install. How we scan