[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M77X7MNK49BYVD8DA997S8T7":3,"skill-same:01M77X7MNK49BYVD8DA997S8T7":56},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":30,"ownerDescription":6,"updatedAt":31,"install":32,"resources":45},"01M77X7MNK49BYVD8DA997S8T7","web-design-reviewer",null,"This skill enables visual inspection of websites running locally or remotely to identify and fix design issues. Triggers on requests like \"review website design\", \"check the UI\", \"fix the layout\", \"find design problems\". Detects issues with responsive design, accessibility, visual consistency, and layout breakage, then performs fixes at the source code level.","Reihantt6\u002Fsns-myagent","Reihantt6","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F219822095?v=4","01M77KK94PV8B7C2D9XWXNS8DJ","Mohamad Reihan tegar prasetya","01M77KK958QFMTHYXGXFV7KZ79",2,"MIT","https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fweb-design-reviewer\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\ndescription: \"This skill enables visual inspection of websites running locally or remotely to identify and fix design issues. Triggers on requests like \\\"review website design\\\", \\\"check the UI\\\", \\\"fix the layout\\\", \\\"find design problems\\\". Detects issues with responsive design, accessibility, visual consistency, and layout breakage, then performs fixes at the source code level.\"\n---\n# Web Design Reviewer\n\nThis skill enables visual inspection and validation of website design quality, identifying and fixing issues at the source code level.\n\n## Scope of Application\n\n- Static sites (HTML\u002FCSS\u002FJS)\n- SPA frameworks such as React \u002F Vue \u002F Angular \u002F Svelte\n- Full-stack frameworks such as Next.js \u002F Nuxt \u002F SvelteKit\n- CMS platforms such as WordPress \u002F Drupal\n- Any other web application\n\n## Prerequisites\n\n### Required\n\n1. **Target website must be running**\n   - Local development server (e.g., `http:\u002F\u002Flocalhost:3000`)\n   - Staging environment\n   - Production environment (for read-only reviews)\n\n2. **Browser automation must be available**\n   - Screenshot capture\n   - Page navigation\n   - DOM information retrieval\n\n3. **Access to source code (when making fixes)**\n   - Project must exist within the workspace\n\n## Workflow Overview\n\n```mermaid\nflowchart TD\n    A[Step 1: Information Gathering] --> B[Step 2: Visual Inspection]\n    B --> C[Step 3: Issue Fixing]\n    C --> D[Step 4: Re-verification]\n    D --> E{Issues Remaining?}\n    E -->|Yes| B\n    E -->|No| F[Completion Report]\n```\n\n---\n\n## Step 1: Information Gathering Phase\n\n### 1.1 URL Confirmation\n\nIf the URL is not provided, ask the user:\n\n> Please provide the URL of the website to review (e.g., `http:\u002F\u002Flocalhost:3000`)\n\n### 1.2 Understanding Project Structure\n\nWhen making fixes, gather the following information:\n\n| Item | Example Question |\n|------|------------------|\n| Framework | Are you using React \u002F Vue \u002F Next.js, etc.? |\n| Styling Method | CSS \u002F SCSS \u002F Tailwind \u002F CSS-in-JS, etc. |\n| Source Location | Where are style files and components located? |\n| Review Scope | Specific pages only or entire site? |\n\n### 1.3 Automatic Project Detection\n\nAttempt automatic detection from files in the workspace:\n\n```\nDetection targets:\n├── package.json     → Framework and dependencies\n├── tsconfig.json    → TypeScript usage\n├── tailwind.config  → Tailwind CSS\n├── next.config      → Next.js\n├── vite.config      → Vite\n├── nuxt.config      → Nuxt\n└── src\u002F or app\u002F     → Source directory\n```\n\n### 1.4 Identifying Styling Method\n\n| Method | Detection | Edit Target |\n|--------|-----------|-------------|\n| Pure CSS | `*.css` files | Global CSS or component CSS |\n| SCSS\u002FSass | `*.scss`, `*.sass` | SCSS files |\n| CSS Modules | `*.module.css` | Module CSS files |\n| Tailwind CSS | `tailwind.config.*` | className in components |\n| styled-components | `styled.` in code | JS\u002FTS files |\n| Emotion | `@emotion\u002F` imports | JS\u002FTS files |\n| CSS-in-JS (other) | Inline styles | JS\u002FTS files |\n\n---\n\n## Step 2: Visual Inspection Phase\n\n### 2.1 Page Traversal\n\n1. Navigate to the specified URL\n2. Capture screenshots\n3. Retrieve DOM structure\u002Fsnapshot (if possible)\n4. If additional pages exist, traverse through navigation\n\n### 2.2 Inspection Items\n\nWork through [references\u002Fvisual-checklist.md](references\u002Fvisual-checklist.md) during inspection and again during post-fix verification.\n\n#### Layout Issues\n\n| Issue | Description | Severity |\n|-------|-------------|----------|\n| Element Overflow | Content overflows from parent element or viewport | High |\n| Element Overlap | Unintended overlapping of elements | High |\n| Alignment Issues | Grid or flex alignment problems | Medium |\n| Inconsistent Spacing | Padding\u002Fmargin inconsistencies | Medium |\n| Text Clipping | Long text not handled properly | Medium |\n\n#### Responsive Issues\n\n| Issue | Description | Severity |\n|-------|-------------|----------|\n| Non-mobile Friendly | Layout breaks on small screens | High |\n| Breakpoint Issues | Unnatural transitions when screen size changes | Medium |\n| Touch Targets | Buttons too small on mobile | Medium |\n\n#### Accessibility Issues\n\n| Issue | Description | Severity |\n|-------|-------------|----------|\n| Insufficient Contrast | Low contrast ratio between text and background | High |\n| No Focus State | Cannot determine state during keyboard navigation | High |\n| Missing alt Text | No alternative text for images | Medium |\n\n#### Visual Consistency\n\n| Issue | Description | Severity |\n|-------|-------------|----------|\n| Font Inconsistency | Mixed font families | Medium |\n| Color Inconsistency | Non-unified brand colors | Medium |\n| Spacing Inconsistency | Non-uniform spacing between similar elements | Low |\n\n### 2.3 Viewport Testing (Responsive)\n\nTest at the following viewports:\n\n| Name | Width | Representative Device |\n|------|-------|----------------------|\n| Mobile | 375px | iPhone SE\u002F12 mini |\n| Tablet | 768px | iPad |\n| Desktop | 1280px | Standard PC |\n| Wide | 1920px | Large display |\n\n---\n\n## Step 3: Issue Fixing Phase\n\n### 3.1 Issue Prioritization\n\n```mermaid\nblock-beta\n    columns 1\n    block:priority[\"Priority Matrix\"]\n        P1[\"P1: Fix Immediately\\n(Layout issues affecting functionality)\"]\n        P2[\"P2: Fix Next\\n(Visual issues degrading UX)\"]\n        P3[\"P3: Fix If Possible\\n(Minor visual inconsistencies)\"]\n    end\n```\n\n### 3.2 Identifying Source Files\n\nIdentify source files from problematic elements:\n\n1. **Selector-based Search**\n   - Search codebase by class name or ID\n   - Explore style definitions with `grep_search`\n\n2. **Component-based Search**\n   - Identify components from element text or structure\n   - Explore related files with `semantic_search`\n\n3. **File Pattern Filtering**\n   ```\n   Style files: src\u002F**\u002F*.css, styles\u002F**\u002F*\n   Components: src\u002Fcomponents\u002F**\u002F*\n   Pages: src\u002Fpages\u002F**, app\u002F**\n   ```\n\n### 3.3 Applying Fixes\n\n#### Framework-specific Fix Guidelines\n\nSee [references\u002Fframework-fixes.md](references\u002Fframework-fixes.md) for details.\n\n#### Fix Principles\n\n1. **Minimal Changes**: Only make the minimum changes necessary to resolve the issue\n2. **Respect Existing Patterns**: Follow existing code style in the project\n3. **Avoid Breaking Changes**: Be careful not to affect other areas\n4. **Add Comments**: Add comments to explain the reason for fixes where appropriate\n\n---\n\n## Step 4: Re-verification Phase\n\n### 4.1 Post-fix Confirmation\n\n1. Reload browser (or wait for development server HMR)\n2. Capture screenshots of fixed areas\n3. Compare before and after\n\n### 4.2 Regression Testing\n\n- Verify that fixes haven't affected other areas\n- Confirm responsive display is not broken\n\n### 4.3 Iteration Decision\n\n```mermaid\nflowchart TD\n    A{Issues Remaining?}\n    A -->|Yes| B[Return to Step 2]\n    A -->|No| C[Proceed to Completion Report]\n```\n\n**Iteration Limit**: If more than 3 fix attempts are needed for a specific issue, consult the user\n\n---\n\n## Output Format\n\n### Review Results Report\n\n```markdown\n# Web Design Review Results\n\n## Summary\n\n| Item | Value |\n|------|-------|\n| Target URL | {URL} |\n| Framework | {Detected framework} |\n| Styling | {CSS \u002F Tailwind \u002F etc.} |\n| Tested Viewports | Desktop, Mobile |\n| Issues Detected | {N} |\n| Issues Fixed | {M} |\n\n## Detected Issues\n\n### [P1] {Issue Title}\n\n- **Page**: {Page path}\n- **Element**: {Selector or description}\n- **Issue**: {Detailed description of the issue}\n- **Fixed File**: `{File path}`\n- **Fix Details**: {Description of changes}\n- **Screenshot**: Before\u002FAfter\n\n### [P2] {Issue Title}\n...\n\n## Unfixed Issues (if any)\n\n### {Issue Title}\n- **Reason**: {Why it was not fixed\u002Fcould not be fixed}\n- **Recommended Action**: {Recommendations for user}\n\n## Recommendations\n\n- {Suggestions for future improvements}\n```\n\n---\n\n## Required Capabilities\n\n| Capability | Description | Required |\n|------------|-------------|----------|\n| Web Page Navigation | Access URLs, page transitions | ✅ |\n| Screenshot Capture | Page image capture | ✅ |\n| Image Analysis | Visual issue detection | ✅ |\n| DOM Retrieval | Page structure retrieval | Recommended |\n| File Read\u002FWrite | Source code reading and editing | Required for fixes |\n| Code Search | Code search within project | Required for fixes |\n\n---\n\n## Reference Implementation\n\n### Implementation with Playwright MCP\n\n[Playwright MCP](https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fplaywright-mcp) is recommended as the reference implementation for this skill.\n\n| Capability | Playwright MCP Tool | Purpose |\n|------------|---------------------|---------|\n| Navigation | `browser_navigate` | Access URLs |\n| Snapshot | `browser_snapshot` | Retrieve DOM structure |\n| Screenshot | `browser_take_screenshot` | Images for visual inspection |\n| Click | `browser_click` | Interact with interactive elements |\n| Resize | `browser_resize` | Responsive testing |\n| Console | `browser_console_messages` | Detect JS errors |\n\n#### Configuration Example (MCP Server)\n\n```json\n{\n  \"mcpServers\": {\n    \"playwright\": {\n      \"command\": \"npx\",\n      \"args\": [\"-y\", \"@playwright\u002Fmcp@latest\", \"--caps=vision\"]\n    }\n  }\n}\n```\n\n### Other Compatible Browser Automation Tools\n\n| Tool | Features |\n|------|----------|\n| Selenium | Broad browser support, multi-language support |\n| Puppeteer | Chrome\u002FChromium focused, Node.js |\n| Cypress | Easy integration with E2E testing |\n| WebDriver BiDi | Standardized next-generation protocol |\n\nThe same workflow can be implemented with these tools. As long as they provide the necessary capabilities (navigation, screenshot, DOM retrieval), the choice of tool is flexible.\n\n---\n\n## Best Practices\n\n### DO (Recommended)\n\n- ✅ Always save screenshots before making fixes\n- ✅ Fix one issue at a time and verify each\n- ✅ Follow the project's existing code style\n- ✅ Confirm with user before major changes\n- ✅ Document fix details thoroughly\n\n### DON'T (Not Recommended)\n\n- ❌ Large-scale refactoring without confirmation\n- ❌ Ignoring design systems or brand guidelines\n- ❌ Fixes that ignore performance\n- ❌ Fixing multiple issues at once (difficult to verify)\n\n---\n\n## Troubleshooting\n\n### Problem: Style files not found\n\n1. Check dependencies in `package.json`\n2. Consider the possibility of CSS-in-JS\n3. Consider CSS generated at build time\n4. Ask user about styling method\n\n### Problem: Fixes not reflected\n\n1. Check if development server HMR is working\n2. Clear browser cache\n3. Rebuild if project requires build\n4. Check CSS specificity issues\n\n### Problem: Fixes affecting other areas\n\n1. Rollback changes\n2. Use more specific selectors\n3. Consider using CSS Modules or scoped styles\n4. Consult user to confirm impact scope\n","# Web Design Reviewer\n\nThis skill enables visual inspection and validation of website design quality, identifying and fixing issues at the source code level.\n\n## Scope of Application\n\n- Static sites (HTML\u002FCSS\u002FJS)\n- SPA frameworks such as React \u002F Vue \u002F Angular \u002F Svelte\n- Full-stack frameworks such as Next.js \u002F Nuxt \u002F SvelteKit\n- CMS platforms such as WordPress \u002F Drupal\n- Any other web application\n\n## Prerequisites\n\n### Required\n\n1. **Target website must be running**\n   - Local development server (e.g., `http:\u002F\u002Flocalhost:3000`)\n   - Staging environment\n   - Production environment (for read-only reviews)\n\n2. **Browser automation must be available**\n   - Screenshot capture\n   - Page navigation\n   - DOM information retrieval\n\n3. **Access to source code (when making fixes)**\n   - Project must exist within the workspace\n\n## Workflow Overview\n\n```mermaid\nflowchart TD\n    A[Step 1: Information Gathering] --> B[Step 2: Visual Inspection]\n    B --> C[Step 3: Issue Fixing]\n    C --> D[Step 4: Re-verification]\n    D --> E{Issues Remaining?}\n    E -->|Yes| B\n    E -->|No| F[Completion Report]\n```\n\n---\n\n## Step 1: Information Gathering Phase\n\n### 1.1 URL Confirmation\n\nIf the URL is not provided, ask the user:\n\n> Please provide the URL of the website to review (e.g., `http:\u002F\u002Flocalhost:3000`)\n\n### 1.2 Understanding Project Structure\n\nWhen making fixes, gather the following information:\n\n| Item | Example Question |\n|------|------------------|\n| Framework | Are you using React \u002F Vue \u002F Next.js, etc.? |\n| Styling Method | CSS \u002F SCSS \u002F Tailwind \u002F CSS-in-JS, etc. |\n| Source Location | Where are style files and components located? |\n| Review Scope | Specific pages only or entire site? |\n\n### 1.3 Automatic Project Detection\n\nAttempt automatic detection from files in the workspace:\n\n```\nDetection targets:\n├── package.json     → Framework and dependencies\n├── tsconfig.json    → TypeScript usage\n├── tailwind.config  → Tailwind CSS\n├── next.config      → Next.js\n├── vite.config      → Vite\n├── nuxt.config      → Nuxt\n└── src\u002F or app\u002F     → Source directory\n```\n\n### 1.4 Identifying Styling Method\n\n| Method | Detection | Edit Target |\n|--------|-----------|-------------|\n| Pure CSS | `*.css` files | Global CSS or component CSS |\n| SCSS\u002FSass | `*.scss`, `*.sass` | SCSS files |\n| CSS Modules | `*.module.css` | Module CSS files |\n| Tailwind CSS | `tailwind.config.*` | className in components |\n| styled-components | `styled.` in code | JS\u002FTS files |\n| Emotion | `@emotion\u002F` imports | JS\u002FTS files |\n| CSS-in-JS (other) | Inline styles | JS\u002FTS files |\n\n---\n\n## Step 2: Visual Inspection Phase\n\n### 2.1 Page Traversal\n\n1. Navigate to the specified URL\n2. Capture screenshots\n3. Retrieve DOM structure\u002Fsnapshot (if possible)\n4. If additional pages exist, traverse through navigation\n\n### 2.2 Inspection Items\n\nWork through [references\u002Fvisual-checklist.md](references\u002Fvisual-checklist.md) during inspection and again during post-fix verification.\n\n#### Layout Issues\n\n| Issue | Description | Severity |\n|-------|-------------|----------|\n| Element Overflow | Content overflows from parent element or viewport | High |\n| Element Overlap | Unintended overlapping of elements | High |\n| Alignment Issues | Grid or flex alignment problems | Medium |\n| Inconsistent Spacing | Padding\u002Fmargin inconsistencies | Medium |\n| Text Clipping | Long text not handled properly | Medium |\n\n#### Responsive Issues\n\n| Issue | Description | Severity |\n|-------|-------------|----------|\n| Non-mobile Friendly | Layout breaks on small screens | High |\n| Breakpoint Issues | Unnatural transitions when screen size changes | Medium |\n| Touch Targets | Buttons too small on mobile | Medium |\n\n#### Accessibility Issues\n\n| Issue | Description | Severity |\n|-------|-------------|----------|\n| Insufficient Contrast | Low contrast ratio between text and background | High |\n| No Focus State | Cannot determine state during keyboard navigation | High |\n| Missing alt Text | No alternative text for images | Medium |\n\n#### Visual Consistency\n\n| Issue | Description | Severity |\n|-------|-------------|----------|\n| Font Inconsistency | Mixed font families | Medium |\n| Color Inconsistency | Non-unified brand colors | Medium |\n| Spacing Inconsistency | Non-uniform spacing between similar elements | Low |\n\n### 2.3 Viewport Testing (Responsive)\n\nTest at the following viewports:\n\n| Name | Width | Representative Device |\n|------|-------|----------------------|\n| Mobile | 375px | iPhone SE\u002F12 mini |\n| Tablet | 768px | iPad |\n| Desktop | 1280px | Standard PC |\n| Wide | 1920px | Large display |\n\n---\n\n## Step 3: Issue Fixing Phase\n\n### 3.1 Issue Prioritization\n\n```mermaid\nblock-beta\n    columns 1\n    block:priority[\"Priority Matrix\"]\n        P1[\"P1: Fix Immediately\\n(Layout issues affecting functionality)\"]\n        P2[\"P2: Fix Next\\n(Visual issues degrading UX)\"]\n        P3[\"P3: Fix If Possible\\n(Minor visual inconsistencies)\"]\n    end\n```\n\n### 3.2 Identifying Source Files\n\nIdentify source files from problematic elements:\n\n1. **Selector-based Search**\n   - Search codebase by class name or ID\n   - Explore style definitions with `grep_search`\n\n2. **Component-based Search**\n   - Identify components from element text or structure\n   - Explore related files with `semantic_search`\n\n3. **File Pattern Filtering**\n   ```\n   Style files: src\u002F**\u002F*.css, styles\u002F**\u002F*\n   Components: src\u002Fcomponents\u002F**\u002F*\n   Pages: src\u002Fpages\u002F**, app\u002F**\n   ```\n\n### 3.3 Applying Fixes\n\n#### Framework-specific Fix Guidelines\n\nSee [references\u002Fframework-fixes.md](references\u002Fframework-fixes.md) for details.\n\n#### Fix Principles\n\n1. **Minimal Changes**: Only make the minimum changes necessary to resolve the issue\n2. **Respect Existing Patterns**: Follow existing code style in the project\n3. **Avoid Breaking Changes**: Be careful not to affect other areas\n4. **Add Comments**: Add comments to explain the reason for fixes where appropriate\n\n---\n\n## Step 4: Re-verification Phase\n\n### 4.1 Post-fix Confirmation\n\n1. Reload browser (or wait for development server HMR)\n2. Capture screenshots of fixed areas\n3. Compare before and after\n\n### 4.2 Regression Testing\n\n- Verify that fixes haven't affected other areas\n- Confirm responsive display is not broken\n\n### 4.3 Iteration Decision\n\n```mermaid\nflowchart TD\n    A{Issues Remaining?}\n    A -->|Yes| B[Return to Step 2]\n    A -->|No| C[Proceed to Completion Report]\n```\n\n**Iteration Limit**: If more than 3 fix attempts are needed for a specific issue, consult the user\n\n---\n\n## Output Format\n\n### Review Results Report\n\n```markdown\n# Web Design Review Results\n\n## Summary\n\n| Item | Value |\n|------|-------|\n| Target URL | {URL} |\n| Framework | {Detected framework} |\n| Styling | {CSS \u002F Tailwind \u002F etc.} |\n| Tested Viewports | Desktop, Mobile |\n| Issues Detected | {N} |\n| Issues Fixed | {M} |\n\n## Detected Issues\n\n### [P1] {Issue Title}\n\n- **Page**: {Page path}\n- **Element**: {Selector or description}\n- **Issue**: {Detailed description of the issue}\n- **Fixed File**: `{File path}`\n- **Fix Details**: {Description of changes}\n- **Screenshot**: Before\u002FAfter\n\n### [P2] {Issue Title}\n...\n\n## Unfixed Issues (if any)\n\n### {Issue Title}\n- **Reason**: {Why it was not fixed\u002Fcould not be fixed}\n- **Recommended Action**: {Recommendations for user}\n\n## Recommendations\n\n- {Suggestions for future improvements}\n```\n\n---\n\n## Required Capabilities\n\n| Capability | Description | Required |\n|------------|-------------|----------|\n| Web Page Navigation | Access URLs, page transitions | ✅ |\n| Screenshot Capture | Page image capture | ✅ |\n| Image Analysis | Visual issue detection | ✅ |\n| DOM Retrieval | Page structure retrieval | Recommended |\n| File Read\u002FWrite | Source code reading and editing | Required for fixes |\n| Code Search | Code search within project | Required for fixes |\n\n---\n\n## Reference Implementation\n\n### Implementation with Playwright MCP\n\n[Playwright MCP](https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fplaywright-mcp) is recommended as the reference implementation for this skill.\n\n| Capability | Playwright MCP Tool | Purpose |\n|------------|---------------------|---------|\n| Navigation | `browser_navigate` | Access URLs |\n| Snapshot | `browser_snapshot` | Retrieve DOM structure |\n| Screenshot | `browser_take_screenshot` | Images for visual inspection |\n| Click | `browser_click` | Interact with interactive elements |\n| Resize | `browser_resize` | Responsive testing |\n| Console | `browser_console_messages` | Detect JS errors |\n\n#### Configuration Example (MCP Server)\n\n```json\n{\n  \"mcpServers\": {\n    \"playwright\": {\n      \"command\": \"npx\",\n      \"args\": [\"-y\", \"@playwright\u002Fmcp@latest\", \"--caps=vision\"]\n    }\n  }\n}\n```\n\n### Other Compatible Browser Automation Tools\n\n| Tool | Features |\n|------|----------|\n| Selenium | Broad browser support, multi-language support |\n| Puppeteer | Chrome\u002FChromium focused, Node.js |\n| Cypress | Easy integration with E2E testing |\n| WebDriver BiDi | Standardized next-generation protocol |\n\nThe same workflow can be implemented with these tools. As long as they provide the necessary capabilities (navigation, screenshot, DOM retrieval), the choice of tool is flexible.\n\n---\n\n## Best Practices\n\n### DO (Recommended)\n\n- ✅ Always save screenshots before making fixes\n- ✅ Fix one issue at a time and verify each\n- ✅ Follow the project's existing code style\n- ✅ Confirm with user before major changes\n- ✅ Document fix details thoroughly\n\n### DON'T (Not Recommended)\n\n- ❌ Large-scale refactoring without confirmation\n- ❌ Ignoring design systems or brand guidelines\n- ❌ Fixes that ignore performance\n- ❌ Fixing multiple issues at once (difficult to verify)\n\n---\n\n## Troubleshooting\n\n### Problem: Style files not found\n\n1. Check dependencies in `package.json`\n2. Consider the possibility of CSS-in-JS\n3. Consider CSS generated at build time\n4. Ask user about styling method\n\n### Problem: Fixes not reflected\n\n1. Check if development server HMR is working\n2. Clear browser cache\n3. Rebuild if project requires build\n4. Check CSS specificity issues\n\n### Problem: Fixes affecting other areas\n\n1. Rollback changes\n2. Use more specific selectors\n3. Consider using CSS Modules or scoped styles\n4. Consult user to confirm impact scope\n",{"description":7},"main","58843b159d7a4050d6b785a98b908cce505c0b92","agent\u002Fskills\u002Fweb-design-reviewer",0,"https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent","https:\u002F\u002Fgithub.com\u002FReihantt6","reihsns.web.id","2026-08-19 20:08:18",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add Reihantt6\u002Fsns-myagent --skill web-design-reviewer",{"tool":38,"command":39},"bunx","bunx skills add Reihantt6\u002Fsns-myagent --skill web-design-reviewer",{"tool":41,"command":42},"pnpm","pnpm dlx skills add Reihantt6\u002Fsns-myagent --skill web-design-reviewer","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fweb-design-reviewer\u002FSKILL.md",true,[46,52],{"path":47,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":50,"sourceHtmlUrl":51},"references\u002Fframework-fixes.md","REFERENCE","参考文档",7437,"https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fweb-design-reviewer\u002Freferences\u002Fframework-fixes.md",{"path":53,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":54,"sourceHtmlUrl":55},"references\u002Fvisual-checklist.md",5989,"https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fweb-design-reviewer\u002Freferences\u002Fvisual-checklist.md",[57,64,71,78,85,92],{"skillNo":58,"name":59,"nameZh":6,"description":60,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":61,"categories":62,"keywords":63,"publishedAt":19},"01M77XDCYZ407XYMF2T4P6F7VT","youtube-transcript","Extract transcripts from YouTube videos. Use when the user asks for a transcript, subtitles, or captions of a YouTube video and provides a YouTube URL (youtube.com\u002Fwatch?v=, youtu.be\u002F, or similar). Supports output with or without timestamps.","https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fyoutube-transcript\u002FSKILL.md",[],[],{"skillNo":65,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":68,"categories":69,"keywords":70,"publishedAt":19},"01M77XD7PBC98J6MXGJJ2TJ8DX","youtube-thumbnail-design","YouTube thumbnail design with specific dimensions, contrast rules, and mobile preview optimization. Covers safe zones, text placement, face expression psychology, and A\u002FB testing. Use for: YouTube thumbnails, video cover images, click-through optimization. Triggers: youtube thumbnail, thumbnail design, video thumbnail, click through rate, ctr optimization, youtube cover, video cover image, thumbnail maker, thumbnail tips, youtube design, video preview image","https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fyoutube-thumbnail-design\u002FSKILL.md",[],[],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"publishedAt":19},"01M77XD2541C8HXJ6RHYZP4NGJ","youtube-short-maker","Make YouTube Shorts that hold attention with Pexo — vertical 9:16, fast-paced, hook in the first 3 seconds. Describe your topic and Pexo writes the script, generates the shots, picks the models, and assembles a finished Short with music and captions. Use for YouTube Shorts: \"youtube short\", \"make a youtube short\", \"shorts video\", \"short-form video\". NOT for long-form or landscape video.","https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fyoutube-short-maker\u002FSKILL.md",[],[],{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":19},"01M77XCXKVSYK7KTZ3PQBVVGFD","xcode-project-setup","Safely modifies Xcode projects (.pbxproj) to add Swift Packages and link files. Use this skill whenever an iOS project needs dependencies installed (e.g. Firebase, Alamofire).","https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fxcode-project-setup\u002FSKILL.md",[],[],{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":19},"01M77XCR1DV8ZQK2NHWKVY4EWX","x402","Set up Browser Use Cloud payments with x402 — pay per request from a crypto wallet (USDC on Base mainnet), no signup or API key. Two setups it works out up front — \"just use it\" (set up a wallet so you or Claude Code can run cloud browser tasks paid from the wallet — Claude writes and runs throwaway scripts, nothing touches your codebase) or \"build it in\" (install the SDK and write the key + code into your project). Walks through wallet setup, funding, .env, and a ~$1 test run. Use when the user asks about x402, pay-per-use, USDC payments, or wants Browser Use Cloud without an API key. For the free-tier signup (reverse-CAPTCHA → API key), use `browser-use cloud signup` or the `cloud` skill instead.","https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fx402\u002FSKILL.md",[],[],{"skillNo":93,"name":94,"nameZh":6,"description":95,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":96,"categories":97,"keywords":98,"publishedAt":19},"01M77XCMD3R3ZBZQQSW6E0793B","x-twitter-scraper","Build GitHub Copilot workflows with Xquik X API SDKs, REST endpoints, hosted Apify Actor runs, MCP tools, TweetClaw OpenClaw plugin installs, signed webhooks, tweet search, user lookup, follower exports, media actions, and agent automation.","https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fx-twitter-scraper\u002FSKILL.md",[],[]]