Results for “console”

Set up or recover MTP hot reload for a long-lived console-host edit/re-run loop in a Microsoft Testing Platform project. Use for explicit MTP console requests such as "enable hot reload", "dotnet run to rerun on edit", or unsupported/rude edits. Covers setup, run/watch, restarts, filters, and the VSTest no-mutation fallback. For one-time runs, exact commands, filter errors, TRX/dumps, or merely a failing test, use run-tests. Do not use when Test Explorer or an IDE should rerun tests without an MTP console host. Excludes editor integration, CI, and writing/debugging tests.

The English summary is being prepared. Showing the original description.

Remote JavaScript console and debugging on mobile. Use for phone/tablet console errors, responsive testing, Eruda, and vConsole.

The English summary is being prepared. Showing the original description.

A three-surface marketing system organized around alternating black, white, and PlayStation Blue chapters that scroll past the viewer like a console launch trailer. Each section has a single editorial purpose — hero photography, console product render, PS Plus tier callout, news strip — and each owns one of three full-bleed canvas modes. The chrome is unusually quiet for a gaming brand: bright PlayStation Blue (`#0070d1`) carries every primary CTA as a fully-rounded pill, the proprietary SST face renders display copy at a signature weight 300 (light) for an airy, premium feel, and a crisp 8px-radius secondary card system carries product info on either canvas mode. The system never decorates — no gradient backgrounds on chrome, no atmospheric mesh, no drop shadows beyond a faint section-divide. Imagery does all the heavy lifting: console glamour shots, game key art, and PS Plus tier illustrations occupy 60-90% of every section, with copy compressed into a small editorial slot.

The English summary is being prepared. Showing the original description.

Structured diagnostic code library for JavaScript/TypeScript. Turns errors and other conditions into typed, machine-readable `Diagnostic` instances with stable codes, docs URLs, and actionable fields. Use this skill whenever the project imports `nostics`, or works with `defineDiagnostics`/`defineProdDiagnostics`, the `Diagnostic` class, diagnostic code registries, or structured error handling. Also covers reporters (`createConsoleReporter`, `createFetchReporter` from nostics/reporters/fetch, `createFileReporter` from nostics/reporters/node, `createDevReporter` from nostics/reporters/dev), formatters (`formatDiagnostic`, `ansiFormatter`, `jsonFormatter`), and Vite plugins (`nosticsStrip` from @nostics/unplugin/strip-transform, `nosticsCollector` from @nostics/unplugin/dev-server-collector). Also use when migrating a library's existing `console.warn`/`console.error`/`warn()` helpers or thrown `Error`s to diagnostics: follow `references/migration.md`.

The English summary is being prepared. Showing the original description.

Run, diagnose, or manually test the private Stacktape Console locally, especially when local API/UI behavior must use the shared dev RDS data, Cognito users, AWS services, OAuth callbacks, or provider webhooks. Use for Console dev-mode setup, deciding between UI-only and full mode, shared-dev migrations, and GitHub/GitLab/Bitbucket end-to-end testing.

The English summary is being prepared. Showing the original description.

Stop black console windows (cmd, PowerShell, Windows Terminal) from flashing and stealing focus on a Windows machine. Use when scheduled tasks, hooks or background scripts pop up consoles: finds all three sources with evidence, silences them reversibly and proves the before and after count. Triggers: /windowless, black windows, console windows popping, windows steal focus.

The English summary is being prepared. Showing the original description.

Full SEO audit: Google Search Console data + URL Inspection API + PageSpeed Insights API + technical crawl + keyword research + metadata audit + schema markup audit + search intent analysis + Core Web Vitals monitoring. Feeds real GSC data and PageSpeed metrics into AI to surface quick wins, diagnose traffic drops, find content gaps, identify metadata mismatches, detect schema gaps, monitor page performance, and produce an actionable 30-day plan. Use this skill whenever the user asks about SEO, search rankings, organic traffic, Google Search Console, keyword performance, traffic drops, content gaps, search visibility, technical SEO, meta tags, schema markup, structured data, URL indexing, keyword research, indexing issues, page speed, performance, Core Web Vitals, LCP, INP, CLS, or Lighthouse scores. Also trigger on: "why is my traffic down", "what keywords am I ranking for", "improve my rankings", "check my search console", "SEO audit", "analyze my SEO", "technical SEO", "meta tags", "indexing issues", "crawl errors", "content strategy", "keyword cannibalization", "search intent", "schema markup", "structured data", "URL inspection", "page speed", "performance score", "core web vitals", "lighthouse", or any organic search question. If in doubt, trigger. This skill handles everything from quick GSC checks to deep technical audits with performance monitoring.

The English summary is being prepared. Showing the original description.

Renders rich console output. Spectre.Console tables, trees, progress, prompts, live displays.

The English summary is being prepared. Showing the original description.

Google Analytics 4, Search Console, and Indexing API toolkit. Analyze website traffic, page performance, user demographics, real-time visitors, search queries, and SEO metrics. Use when the user asks to: check site traffic, analyze page views, see traffic sources, view user demographics, get real-time visitor data, check search console queries, analyze SEO performance, request URL re-indexing, inspect index status, compare date ranges, check bounce rates, view conversion data, or get e-commerce revenue. Requires a Google Cloud service account with GA4 and Search Console access.

The English summary is being prepared. Showing the original description.

Inspect the running Hermes desktop app through CDP, Chrome's debugging connection. Read rendered elements, computed styles, layout measurements, and console output to verify interface changes and investigate why a style takes effect.

• Verify interface changes in the running app
• Find which CSS rule determines a style
• Check computed design token values

Monitor a live app after deployment for console errors, slower performance, and page failures. Periodic screenshots and comparisons with pre-deployment baselines help identify anomalies and check whether the release is behaving as expected.

• Monitoring a live app after deployment
• Checking for performance regressions after a release
• Comparing screenshots before and after deployment

Choose an agent and model tier using the task description and learned patterns. The skill can explain its recommendation, use compiler-based edits for supported simple changes, and record task outcomes to inform future routing decisions.

• Choose an agent and model before starting a task
• Review the reasoning behind a routing recommendation
• Apply supported code changes through the TypeScript compiler

Create and audit JSON-LD, structured data that describes page content to search engines. Check JSON syntax, schema types, and required fields for articles, products, FAQs, and breadcrumbs, then guide validation for enhanced search results.

• Creating structured data for articles and products
• Checking FAQ and breadcrumb structured data
• Finding JSON syntax errors and missing required fields

Audit and set up favicons, the small site icons used in browser tabs and search results. Check HTML links, image formats and dimensions, HTTPS access, and crawler restrictions, with guidance for ICO, SVG, and iOS icons.

• Checking a site's existing favicon configuration
• Setting up favicons for a new project
• Investigating missing icons in search results

Finds and rewrites code by its syntax structure across 25 languages. Use it to locate matching calls or declarations, preview bulk changes, and run reusable YAML rules that check code or apply fixes.

• Finding calls or functions with a specific structure
• Previewing and applying bulk code changes
• Checking code with reusable YAML rules

Audit a website for problems affecting search visibility, from search engine access and indexing to speed, page titles, content, and links. Receive evidence-based findings and a prioritized action plan, including checks for multilingual and local business sites.

• Investigating a drop in search traffic or rankings
• Reviewing page titles and internal links
• Checking multilingual search settings

Control interactive command-line programs through tmux by sending keystrokes, reading terminal output, and waiting for prompts. Use separate sessions to operate Python consoles or run multiple coding agents while checking their progress and results.

• Operate an interactive Python console
• Run multiple coding agents in parallel
• Wait for prompts and inspect terminal output

Automate page interactions and screenshots with agent-browser running in AWS Bedrock AgentCore cloud browsers. Use standard browser commands, preserve login state across sessions with persistent profiles, and watch active sessions through an AWS Console link.

• Run browser automation on AWS
• Reuse login state across browser sessions
• Watch a cloud browser session live

Develop HTML and JavaScript web games through small changes and repeated Playwright tests, which automate browser actions. Inspect gameplay screenshots, text representations of game state, and console errors to check controls, outcomes, and newly added features.

• Adding features to a browser game
• Testing movement, jumping, and attacks
• Checking score changes and win or lose transitions

Audit a website for search visibility problems across indexing, technical performance, page content, and links. Produce findings with supporting evidence, estimated impact, and specific fixes organized into a prioritized action plan.

• Investigate why important pages are missing from search
• Review page titles, descriptions, and headings
• Check technical SEO after a site migration

Retrieve Google Workspace audit logs, which record account activity, and usage reports through gws. Review activity in applications such as the Admin console and Google Drive, or inspect statistics for the organization, users, and entities.

• Reviewing Admin console and Google Drive activity
• Checking organization usage statistics
• Retrieving usage reports for users

Control interactive command-line programs through tmux by sending keystrokes, reading terminal output, and waiting for prompts. Use separate sessions to operate Python consoles or run multiple coding agents while checking their progress and results.

• Operate an interactive Python console
• Run multiple coding agents in parallel
• Wait for prompts and inspect terminal output

Audit a website’s technical setup, page elements, and content for search visibility issues. Produce page and site health scores, evidence-backed findings, and a prioritized action plan covering urgent fixes, practical improvements, and longer-term work.

• Investigating falling search traffic or rankings
• Reviewing page titles, headings, and internal links
• Checking SEO before or after a site migration

Group keywords by what searchers want and assign each group to an existing or proposed page. Produce a page map, priorities, and content briefs, while checking whether multiple pages compete for the same searches.

• Mapping keyword lists to pages
• Planning new pages and updates
• Checking competition between pages on the same site