Results for “console”

Expert blueprint for console platforms (PlayStation, Xbox, Nintendo Switch) covering controller-first UI, certification requirements (TRCs/TCRs), platform services (achievements, cloud saves), and performance compliance. Use when targeting console releases or implementing gamepad-only interfaces. Keywords console, PlayStation, Xbox, Switch, TRC, TCR, certification, controller, gamepad, achievements.

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

Initialize an Adobe App Builder project end-to-end without Developer Console UI clicks. Creates the Console project and workspace, subscribes APIs (including those needing a product profile), maps user intent to the right template, runs non-interactive `aio app init`, and guides post-init customization. Use whenever the user mentions creating an App Builder app, scaffolding a project, `aio app init`, setting up an Experience Cloud extension, adding actions or web assets, creating a Console project or workspace, adding APIs, or bootstrapping App Builder — even if they don't say "App Builder". Also for SPA templates, AEM extensions, API Mesh, Asset Compute workers, and MCP server projects. Also handles debugging init failures — template not found, `aio app init` hangs or times out, Node version mismatches, npm install failures, post-init build errors, `aio login` issues, `aio app run` showing nothing, or `aio console project create` / `workspace create` / `workspace api add` errors.

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

Initialize an Adobe App Builder project end-to-end without Developer Console UI clicks. Creates the Console project and workspace, subscribes APIs (including those needing a product profile), maps user intent to the right template, runs non-interactive `aio app init`, and guides post-init customization. Use whenever the user mentions creating an App Builder app, scaffolding a project, `aio app init`, setting up an Experience Cloud extension, adding actions or web assets, creating a Console project or workspace, adding APIs, or bootstrapping App Builder — even if they don't say "App Builder". Also for SPA templates, AEM extensions, API Mesh, Asset Compute workers, and MCP server projects. Also handles debugging init failures — template not found, `aio app init` hangs or times out, Node version mismatches, npm install failures, post-init build errors, `aio login` issues, `aio app run` showing nothing, or `aio console project create` / `workspace create` / `workspace api add` errors.

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

Open web pages, follow navigation, and check form flows in a browser. Capture screenshots at different screen sizes, compare pages before and after actions, and collect console errors, the technical messages that can reveal page problems.

• Checking navigation and form flows
• Capturing mobile, tablet, and desktop views
• Recording screenshots and console errors

Guide browser tasks in the person's own Chrome using existing sign-ins. Covers tab management, site permissions, form entry, GIF recordings, and console inspection, with clear steps for handling connection failures and unresponsive pages.

• Work on websites using existing Chrome sign-ins
• Record a sequence of browser actions as a GIF
• Inspect console logs while debugging a page

Automate Chrome tasks such as navigating pages, clicking buttons, and filling forms. Capture screenshots or GIF recordings, and inspect console logs, the messages a website produces, to review interactions and investigate problems.

• Automating form entry and page navigation
• Capturing screenshots of web pages
• Recording browser steps as a GIF

Test a local web app in a real browser, checking the page structure, console messages, and network activity. Follow controls observed on the page and record evidence showing whether the tested flow passes or fails.

• Verify a web app flow in a real browser
• Check page state, console messages, and network activity
• Record evidence of test results

Use external APIs and GitHub's gh command through Iron Proxy while keeping real credentials out of the client. The skill guides account setup through the operator console and helps investigate blocked requests using observed errors.

• Connect an external API account through the operator console
• Use gh with credentials managed by Iron Proxy
• Investigate requests returning 401 or 403 errors

Install or update Iron Proxy and its official Iron Control console for NanoClaw. Configure stored credentials, access grants, allowed destinations, and human approval checks for outbound requests through a local Docker installation.

• Install Iron Proxy and its management console
• Configure credentials and access grants
• Set allowed destinations and human approvals

Turn topics, products, or audience problems into a prioritized keyword list. Compare search volume, ranking difficulty, search intent, and search results to recommend target terms and pages, with optional saving and tagging after confirmation.

• Finding target keywords for a new topic
• Prioritizing queries already close to strong rankings
• Researching keyword demand in a specific region

Investigate slow or failing requests in Google Cloud using Cloud Trace. Filter traces by duration or error status, inspect spans representing individual operations, and retrieve related Cloud Logging entries to investigate bottlenecks and exceptions.

• Find requests exceeding a latency threshold
• Inspect operation hierarchies within a trace
• Investigate failures using related application logs

Use persistent virtual terminal sessions to keep directories and environment variables across commands, interact with Python or database consoles, and answer prompts. The skill explains sending input, reading responses, detecting prompts, and closing sessions when finished.

• Keep directories and environment variables across commands
• Run a sequence of commands in an interactive Python console
• Interact with mysql or psql consoles

Test and debug rendered web apps by reproducing interaction bugs, checking layouts and console errors, making focused fixes, and validating again. Results include screenshots, observed state changes, and a QA report explaining coverage and remaining gaps.

• Reproducing and fixing broken UI interactions
• Checking desktop and mobile layouts
• Investigating blank pages and console errors

Create an article brief using live search results and your site's search data. It brings together keywords, headings, reader questions, and internal links so a writer knows what to cover and how to distinguish the article.

• Planning an article around a target keyword
• Finding topics competing articles leave uncovered
• Choosing internal links from existing pages

Coordinate SEO work from Google Search Console analysis and keyword research to title improvements, article creation, translation, internal linking, and technical audits. Follow a workflow that connects search performance diagnosis with content updates, validation, and deployment.

• Reviewing search impressions and click-through rates
• Researching keywords and improving article titles
• Creating blog content and translating articles

Manage AI agent Workers by creating roles, selecting runtimes, starting or stopping Workers, and updating their skills. It also covers runtime migration, direct mentions between Workers, and access to the QwenPaw console.

• Create a Worker with a defined role and skills
• Start, stop, or reset a Worker
• Add or remove Worker skills

Make C# code testable when it directly uses static services such as time, files, or processes. It introduces existing abstractions or minimal wrappers, supplies dependency registration, and demonstrates tests with controlled substitutes for real resources.

• Introducing TimeProvider for time-dependent tests
• Testing file operations with MockFileSystem
• Wrapping Environment, Console, or Process calls

Compare two or more dotnet new templates using their installed options, features, and supported frameworks. Get a focused comparison table and a recommendation that explains which template best fits the project you want to build.

• Choosing between webapi and webapp
• Comparing blazor and blazorwasm
• Selecting console or worker for background processing

Diagnose MSBuild failures from an existing binary build log. Inspect errors, settings, project references, and execution details to explain failures that console output alone does not clarify, including failures across multiple projects.

• Investigating build errors with unclear console output
• Tracing cascading failures across multiple projects
• Checking MSBuild target execution order

Format gh-aw terminal output using Go struct tags, annotations attached to data fields. Set labels and section titles, format numbers and dollar amounts, omit empty fields, and render lists of records as tables.

• Display workflow details as aligned fields
• Show job lists as terminal tables
• Format token counts and estimated costs

Full SEO audit combining Google Search Console, URL Inspection API, PageSpeed Insights, a technical crawl, keyword research, and metadata, schema, search intent and Core Web Vitals checks. Surfaces quick wins, diagnoses traffic drops and content gaps, and produces an actionable 30-day plan. Use whenever the user asks about SEO, search rankings, organic traffic, Google Search Console, keyword performance, search visibility, technical SEO, URL indexing, or 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.

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

Query and operate connected Google Search Console properties through NotFair MCP. Use for live GSC query or page performance, clicks, impressions, CTR, position, traffic changes, indexing status, URL inspection, sitemap reads or approved sitemap submission/removal, and Search Console MCP setup. Route full-site SEO audits to seo-analysis.

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

Classify a console screen (list/record/form), build it on @temps-sdk/ds templates and the shared shadcn primitives in @temps-sdk/ui, and follow the console's status vocabulary and status colour rules. Use for any new or changed console UI in web/src, and when building or extending web/packages/ds itself.

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

Pull Google Search Console data and perform search performance analysis. Use when asked about search rankings, clicks, impressions, CTR, index coverage, Core Web Vitals, or sitemap status. Trigger phrases: "search console", "GSC", "search performance", "clicks and impressions", "CTR analysis", "index coverage", "core web vitals", "URL inspection", "sitemap status", "ranking data", "search queries", "keyword positions".

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