{"owner":"image-rs","repo":"image","hasSkills":true,"totalSkillsCount":1,"totalTokensCount":353,"categories":["cursor-rule"],"hasMcp":false,"mcpConfig":null,"found":[".cursorrules (landing-page-image-quality-cursorrules-prompt-file.mdc)"],"skills":{".cursorrules (landing-page-image-quality-cursorrules-prompt-file.mdc)":"---\ndescription: \"Cursor rules for avoiding placeholder or broken image URLs, using stable visual assets, and checking alt text, dimensions, licensing, and responsive behavior.\"\nglobs: **/*\nalwaysApply: false\n---\n# Landing Page Image Quality\n\nWhen generating or editing user-facing pages, use real, relevant visual assets instead of placeholder image services.\n\n## Image Sources\n\n- Do not commit `placehold.co`, `via.placeholder.com`, `dummyimage.com`, `picsum.photos`, random image URLs, or broken/deprecated image services.\n- Prefer committed project assets, product screenshots, generated assets approved by the user, or stable URLs from an approved image provider.\n- Before using a third-party image, confirm the license and attribution requirements are compatible with the project.\n- Avoid hotlinking images from arbitrary websites.\n\n## Asset Quality\n\n- Match images to the actual content, product, place, object, or user state they represent.\n- Do not use vague atmospheric images when the user needs to inspect a product, feature, workflow, or interface.\n- Use consistent aspect ratios for repeated cards or gallery items.\n- Provide explicit `width` and `height` attributes or CSS aspect-ratio constraints to prevent layout shift.\n- Use optimized formats and sizes appropriate for the target framework.\n\n## Accessibility\n\n- Every informative image must have specific `alt` text that describes the image's purpose in context.\n- Decorative images must use empty alt text and should not be announced to assistive technology.\n- Do not put essential text only inside an image.\n\n## Implementation Checks\n\n- Ensure image paths resolve in the built application.\n- Check responsive behavior at mobile and desktop widths.\n- Verify that loading, error, and empty states do not leave broken image icons in production UI.\n"},"files":{".cursorrules (landing-page-image-quality-cursorrules-prompt-file.mdc)":"---\ndescription: \"Cursor rules for avoiding placeholder or broken image URLs, using stable visual assets, and checking alt text, dimensions, licensing, and responsive behavior.\"\nglobs: **/*\nalwaysApply: false\n---\n# Landing Page Image Quality\n\nWhen generating or editing user-facing pages, use real, relevant visual assets instead of placeholder image services.\n\n## Image Sources\n\n- Do not commit `placehold.co`, `via.placeholder.com`, `dummyimage.com`, `picsum.photos`, random image URLs, or broken/deprecated image services.\n- Prefer committed project assets, product screenshots, generated assets approved by the user, or stable URLs from an approved image provider.\n- Before using a third-party image, confirm the license and attribution requirements are compatible with the project.\n- Avoid hotlinking images from arbitrary websites.\n\n## Asset Quality\n\n- Match images to the actual content, product, place, object, or user state they represent.\n- Do not use vague atmospheric images when the user needs to inspect a product, feature, workflow, or interface.\n- Use consistent aspect ratios for repeated cards or gallery items.\n- Provide explicit `width` and `height` attributes or CSS aspect-ratio constraints to prevent layout shift.\n- Use optimized formats and sizes appropriate for the target framework.\n\n## Accessibility\n\n- Every informative image must have specific `alt` text that describes the image's purpose in context.\n- Decorative images must use empty alt text and should not be announced to assistive technology.\n- Do not put essential text only inside an image.\n\n## Implementation Checks\n\n- Ensure image paths resolve in the built application.\n- Check responsive behavior at mobile and desktop widths.\n- Verify that loading, error, and empty states do not leave broken image icons in production UI.\n"},"items":[{"name":".cursorrules","path":".cursorrules (landing-page-image-quality-cursorrules-prompt-file.mdc)","rawUrl":"https://raw.githubusercontent.com/PatrickJS/awesome-cursorrules/main/rules/landing-page-image-quality-cursorrules-prompt-file.mdc","title":"Awesome Cursorrules: landing page image quality","category":"cursor-rule","format":"markdown","content":"---\ndescription: \"Cursor rules for avoiding placeholder or broken image URLs, using stable visual assets, and checking alt text, dimensions, licensing, and responsive behavior.\"\nglobs: **/*\nalwaysApply: false\n---\n# Landing Page Image Quality\n\nWhen generating or editing user-facing pages, use real, relevant visual assets instead of placeholder image services.\n\n## Image Sources\n\n- Do not commit `placehold.co`, `via.placeholder.com`, `dummyimage.com`, `picsum.photos`, random image URLs, or broken/deprecated image services.\n- Prefer committed project assets, product screenshots, generated assets approved by the user, or stable URLs from an approved image provider.\n- Before using a third-party image, confirm the license and attribution requirements are compatible with the project.\n- Avoid hotlinking images from arbitrary websites.\n\n## Asset Quality\n\n- Match images to the actual content, product, place, object, or user state they represent.\n- Do not use vague atmospheric images when the user needs to inspect a product, feature, workflow, or interface.\n- Use consistent aspect ratios for repeated cards or gallery items.\n- Provide explicit `width` and `height` attributes or CSS aspect-ratio constraints to prevent layout shift.\n- Use optimized formats and sizes appropriate for the target framework.\n\n## Accessibility\n\n- Every informative image must have specific `alt` text that describes the image's purpose in context.\n- Decorative images must use empty alt text and should not be announced to assistive technology.\n- Do not put essential text only inside an image.\n\n## Implementation Checks\n\n- Ensure image paths resolve in the built application.\n- Check responsive behavior at mobile and desktop widths.\n- Verify that loading, error, and empty states do not leave broken image icons in production UI.\n","tokens":353,"sizeBytes":1816}],"systemPromptSnippet":"<yakaai_skills repo=\"image-rs/image\">\n<!-- File: .cursorrules (landing-page-image-quality-cursorrules-prompt-file.mdc) (Tokens: ~353 | Category: cursor-rule) -->\n---\ndescription: \"Cursor rules for avoiding placeholder or broken image URLs, using stable visual assets, and checking alt text, dimensions, licensing, and responsive behavior.\"\nglobs: **/*\nalwaysApply: false\n---\n# Landing Page Image Quality\n\nWhen generating or editing user-facing pages, use real, relevant visual assets instead of placeholder image services.\n\n## Image Sources\n\n- Do not commit `placehold.co`, `via.placeholder.com`, `dummyimage.com`, `picsum.photos`, random image URLs, or broken/deprecated image services.\n- Prefer committed project assets, product screenshots, generated assets approved by the user, or stable URLs from an approved image provider.\n- Before using a third-party image, confirm the license and attribution requirements are compatible with the project.\n- Avoid hotlinking images from arbitrary websites.\n\n## Asset Quality\n\n- Match images to the actual content, product, place, object, or user state they represent.\n- Do not use vague atmospheric images when the user needs to inspect a product, feature, workflow, or interface.\n- Use consistent aspect ratios for repeated cards or gallery items.\n- Provide explicit `width` and `height` attributes or CSS aspect-ratio constraints to prevent layout shift.\n- Use optimized formats and sizes appropriate for the target framework.\n\n## Accessibility\n\n- Every informative image must have specific `alt` text that describes the image's purpose in context.\n- Decorative images must use empty alt text and should not be announced to assistive technology.\n- Do not put essential text only inside an image.\n\n## Implementation Checks\n\n- Ensure image paths resolve in the built application.\n- Check responsive behavior at mobile and desktop widths.\n- Verify that loading, error, and empty states do not leave broken image icons in production UI.\n</yakaai_skills>"}