docs: 📜 readme updates and description in deno.json

Author: erlendellefsen

README.md

@@ -1,9 +1,13 @@
+[![JSR](https://jsr.io/badges/@intility/no-inline-styles)](https://jsr.io/@intility/no-inline-styles)
+
 # @intility/no-inline-styles
 
 A Deno lint plugin that prevents inline styles in JSX/TSX components. This helps maintain a consistent styling approach by encouraging the use of CSS classes instead of inline styles.
 
 ## Installation
 
+Add the plugin to your `deno.json`:
+
 ```json
 {
   "lint": {
@@ -17,6 +21,8 @@ A Deno lint plugin that prevents inline styles in JSX/TSX components. This helps
 
 ## Usage
 
+Once configured, the plugin will flag any inline styles:
+
 ```tsx
 // ❌ Error
 <div style={{ color: 'red' }}>Content</div>
@@ -27,7 +33,9 @@ A Deno lint plugin that prevents inline styles in JSX/TSX components. This helps
 
 ## Ignoring Specific Cases
 
+If you have legitimate use cases for inline styles, you can ignore specific lines:
+
 ```tsx
 // deno-lint-ignore no-inline-styles/no-inline-styles
 <div style={{ backgroundColor: dynamicColor }}>Content</div>
-```
+```

deno.json

@@ -1,6 +1,7 @@
 {
   "name": "@intility/no-inline-styles",
-  "version": "1.0.0",
+  "version": "1.0.1",
+  "description": "Deno lint plugin to prevent inline styles in JSX/TSX. Enforces consistent styling through CSS classes instead of style props.",
   "license": "MIT",
   "exports": "./plugin.ts",
   "tasks": {

plugin.ts

@@ -38,8 +38,7 @@
  *
  * ## Ignoring Specific Cases
  *
- * If you have legitimate use cases for inline styles (e.g., dynamic colors from data),
- * you can ignore specific lines:
+ * If you have legitimate use cases for inline styles, you can ignore specific lines:
  *
  * ```tsx
  * // deno-lint-ignore no-inline-styles/no-inline-styles