'firefox' 검색 결과

Develop and maintain the WXT browser extension that adds a Repomix button to GitHub repository pages. The skill covers Chrome, Firefox, and Edge compatibility, extension scripts, translation files, and commands for building, linting, and testing.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Maintaining the GitHub Repomix button extension
• Checking Chrome, Firefox, and Edge compatibility
• Updating translations or adding a language

Add browser WebCodecs bugs to the Remotion Mediabunny documentation. It checks the linked issue’s title, filing date, reporter, and resolution, then adds a table row while preserving the existing format.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Adding a Chromium bug to the documentation
• Recording WebKit or Firefox issues
• Checking reporter details and fix status before adding a row

Analyze authorized browser extensions for Chrome, Edge, and Firefox. Inspect permissions, background scripts, storage, and network activity to reconstruct key data flows and explain credential handling, signing, encryption, or proxy behavior.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Review extension permissions and entry scripts
• Trace credential handling and network data flows
• Investigate suspicious or compromised extensions

Handle website tasks in Dot’s Firefox browser, including logging in, reading pages, filling forms, and clicking through workflows. Separate browser profiles preserve each account’s cookies and login state between sessions.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Log in and read information on a website
• Fill out and submit website forms
• Keep browser profiles separate for different accounts

Default to Firefox for browser automation and decide when Chrome is truly required. Use before any task that needs a browser: fetching a page, grabbing cookies, headless runs, logging into a site. Includes a matrix of which tasks must stay on Chromium and why. Triggers: /firefox, /ff, via firefox, need a browser, headless browser, which browser to use, browser automation.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Check website behavior across Chrome, Firefox, Safari, and Edge, and fix browser-specific problems. Review desktop and mobile test coverage alongside CI, the automated checks run during development, to identify gaps that let regressions pass.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Checking layouts and features across major browsers
• Reviewing desktop and mobile browser test coverage
• Finding gaps in automated browser checks

Use when developing Firefox WebExtensions - Manifest V2/V3 configuration, WebExtension APIs, content security policy, web-ext CLI, cross-browser support with the polyfill, AMO submission, or debugging extensions

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Build cross-browser extensions with WXT — the modern framework for Chrome, Firefox, Safari, and Edge extensions. Use when someone asks to "build a browser extension", "Chrome extension with React", "WXT framework", "cross- browser extension", "manifest v3 extension", "build Firefox extension", or "browser extension with TypeScript". Covers content scripts, background workers, popup/options pages, storage, messaging, and publishing.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Manage separate browser profiles for website tasks, keeping each account’s cookies and logins between sessions. The skill guides profile selection, reuse, opening, and closing, and explains when a direct download is simpler than browser work.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Reuse a browser profile already signed in
• Keep different accounts in separate profiles
• Use a separate profile for signup verification

Control the user's Firefox browser with their logins and cookies intact. Use when you need to browse websites as the user, interact with authenticated pages, fill forms, click buttons, take screenshots, or get page content. (user)

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Expert in building browser extensions that solve real problems - Chrome, Firefox, and cross-browser extensions. Covers extension architecture, manifest v3, content scripts, popup UIs, monetization strategies, and Chrome Web Store publishing. Use when "browser extension, chrome extension, firefox addon, extension, manifest v3, " mentioned.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Expert in building browser extensions that solve real problems - Chrome, Firefox, and cross-browser extensions. Covers extension architecture, manifest v3, content scripts, popup UIs, monetization strategies, and Chrome Web Store publishing. Use when: browser extension, chrome extension, firefox addon, extension, manifest v3.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Expert in building browser extensions that solve real problems - Chrome, Firefox, and cross-browser extensions. Covers extension architecture, manifest v3, content scripts, popup UIs, monetization strategies, and Chrome Web Store publishing. Use when: browser extension, chrome extension, firefox addon, extension, manifest v3.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Turn product requirements, roadmaps, architecture reviews, and retrospectives into HTML slides for decision-making. Choose one of eight visual themes to create a consistent, horizontally navigable deck, using source evidence and real numbers to support review.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Building a business case for a proposed feature
• Preparing a roadmap for stakeholder review
• Presenting architecture choices for a decision

Review stylesheets for a CSS reset or normalization layer that reduces differences in browser defaults. Check import order, framework provisions, and rendered layouts across screen sizes and interaction states, then suggest changes for a consistent styling foundation.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Investigating layout differences between browsers
• Choosing a reset for a new site's styles
• Checking reset coverage in a CSS framework

Guide web app testing with screen readers such as VoiceOver, NVDA, and JAWS. Check forms, dialogs, keyboard navigation, and spoken update notifications to identify accessibility problems across desktop and mobile browser combinations.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Checking form labels and error announcements
• Testing dialog focus behavior
• Verifying announcements for changing content

Use ROADrecon and roadtx during authorized Microsoft Entra ID testing to inspect directory objects and authentication tokens, which represent access permissions. Explore collected configuration offline, test token exchanges, and assess conditional access and device controls.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Mapping tenant users, groups, roles, and applications
• Reviewing conditional access policies
• Testing token exchanges and device-based single sign-on

Run Playwright tests on BrowserStack to check behavior across browsers and devices. Configure cloud connections, compare results by browser, inspect session videos and logs, and set up a tunnel for testing local or restricted environments.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Checking browser compatibility with Playwright tests
• Configuring BrowserStack cloud test connections
• Investigating failures through session videos and logs

Build image export features for HTML elements with snapDOM. The skill covers SVG, PNG, JPG, and WebP output, preserving styles and fonts, adjusting dimensions, excluding elements, and troubleshooting missing resources.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Adding image downloads for HTML elements
• Exporting charts and graphics as SVG
• Creating images with specified dimensions

Control, debug, and test live All API Hub extension UI on desktop or Android Firefox, Edge, and Lemur, including installed release diagnostics and development hot updates via CDP/RDP.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use for authorized reverse engineering of browser extensions (Chrome/Firefox) including manifest analysis, background workers, and extension-based credential or traffic logic recovery.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Browser automation, web scraping, E2E testing, and visual regression with Playwright. Covers 30+ patterns: login flows, form testing, responsive design checks, broken link validation, API mocking, data extraction, PDF generation, accessibility audits (axe-core), performance budgets (Lighthouse), visual diffing, multi-browser testing (Chromium/Firefox/WebKit), mobile emulation, infinite scroll, shadow DOM, iframes, file downloads, auth state reuse, cookie consent handling, WebSocket monitoring, console error detection, HAR export, trace viewer, Docker CI, GitHub Actions, and parallel sharding. Use when user asks to test a website, take screenshots, check responsive design, automate a browser task, scrape data, validate forms, check broken links, test login, audit accessibility, or measure page performance. Do NOT use for unit testing, API-only testing, or static analysis. Requires Node.js 18+.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Browserless turns Chrome, Firefox, and WebKit into a remote browser service you can self-host or consume as a managed platform. It gives automation stacks a stable WebSocket and REST surface for screenshots, PDFs, scraping, persistent sessions, and debugging without hand-managing browser fleets.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Run tests on BrowserStack. Use when user mentions "browserstack", "cross-browser", "cloud testing", "browser matrix", "test on safari", "test on firefox", or "browser compatibility".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.