key-conventions
193paulpham157/paul-s-cursor-rules
Cursor rule Cursor
Key coding conventions for Astro projects including style guide and typescript.
paulpham157/paul-s-cursor-rules
Cursor rule Cursor
Key coding conventions for Astro projects including style guide and typescript.
paulpham157/paul-s-cursor-rules
Cursor rule Cursor
Performance metrics rules including Core Web Vitals, Lighthouse and WebPageTest.
paulpham157/paul-s-cursor-rules
Cursor rule Cursor
Best practices for using Tailwind CSS within Astro components.
paulpham157/paul-s-cursor-rules
Cursor rule Cursor
Rules for integrating Tailwind CSS with Astro using @astrojs/tailwind.
paulpham157/paul-s-cursor-rules
Cursor rule Cursor
Rules for testing Astro projects, including unit tests and end-to-end testing.
paulpham157/paul-s-cursor-rules
Cursor rule Cursor
description: Rules for proper API usage within Chrome extensions, ensuring compatibility and best practices. globs: /.js.
paulpham157/paul-s-cursor-rules
Cursor rule Cursor
Specific rules related to the Chrome extension manifest file, ensuring proper structure and content.
paulpham157/paul-s-cursor-rules
Cursor rule Cursor
description: Guidelines for structuring the architecture of a Chrome extension, focusing on modularity and maintainability. globs: /.{js,html}.
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: