Results for “dev server”

Scaffold a one-command `dev-local` launcher for ANY codebase. Investigates the repo to find its services, ports, and infra dependencies, then generates a single `scripts/dev-local.sh` (up/down/status/logs/restart) that runs every dev server in one tmux session, plus a short skill doc describing it. Use when someone says "set up dev-local", "make a one-command dev launcher", "I want one script to start this repo", "scaffold dev-local for this project".

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

Search Google Cloud (GKE) server logs of the DEV environment (dev.voxt.ai). Use when troubleshooting anything that needs the server side of the story — stream stalls, RPC peer changes / reconnects, watchdog closures, mesh/node churn, pod restarts — or when the user says "check GCP logs", "check server logs on dev", or gives a dev.voxt.ai timeline from a client console log.

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

Scaffold a one-command `dev-local` launcher for ANY codebase. Investigates the repo to find its services, ports, and infra dependencies, then generates a single `scripts/dev-local.sh` (up/down/status/logs/restart) that runs every dev server in one tmux session, plus a short skill doc describing it. Use when someone says "set up dev-local", "make a one-command dev launcher", "I want one script to start this repo", "scaffold dev-local for this project".

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

Test SwiftUI apps on a real iPhone or iPad by repeatedly capturing screens, analyzing them, taking actions, and verifying results. An embedded HTTP server enables interaction, with optional remote access through Tailscale.

• Find bugs in an iPhone app on a real device
• Check an iPad app on a real device
• Test screen behavior using Swift source and screenshots

Test browser interfaces through Chrome DevTools MCP, a connection that lets an agent inspect a live browser. Check screenshots, errors, network traffic, accessibility, and performance to diagnose problems and verify fixes.

• Diagnosing layout and styling problems
• Investigating browser errors and failed API requests
• Comparing screenshots before and after a fix

Measure how Google Tag Manager affects page loading and rendering. Identify costly tags, triggers, and requests, then guide cleanup, asynchronous loading, or a move to server-side processing based on observed performance problems.

• Investigate slow pages using GTM
• Review unused tags and triggers
• Check asynchronous script loading

Launch the local Remotion Convert app and open it in the Codex in-app browser to inspect its interface. The workflow prepares dependencies, builds the project, starts the development server, and reports the actual local URL.

• Launch convert.remotion.dev locally
• Inspect the Convert interface in the Codex browser
• Check the local server URL and startup status

Build MCP servers, which expose tools and data to AI agents, with mcp-use. The material covers server functions, reusable prompts, and interactive React widgets, but this skill is deprecated and points to mcp-app-builder as its replacement.

• Planning an MCP server's tools and data resources
• Implementing reusable prompts and response formats
• Adding interactive React widgets to an MCP server

Guide changes to SGLang runtime configuration and shared process state. Identify where resolved settings, runtime flags, resources, and per-forward state belong, and use the documented access patterns and checks when developing or testing.

• Review how server settings are read and updated
• Choose where shared and per-forward state should live
• Check configuration publication order in worker processes

Audit MCP servers, which provide external tools to AI agents, for hidden instructions, changes after approval, unsafe internal requests, and missing authentication. Use mcp-scan and manual checks to document risks and recommended fixes.

• Reviewing an MCP server before adding it to an agent
• Auditing an internally developed MCP server
• Checking approved tools for unexpected changes

Develop and debug LangBot's backend and web frontend. The skill guides environment setup, API additions, authentication, database migrations, and testing, including updates to matching MCP tools so agents can use changed API features.

• Set up the LangBot backend and frontend for development
• Add an API endpoint and its matching MCP tool
• Update the database schema with Alembic

Build remote MCP servers, which let AI agents call external tools, on Cloudflare Workers. This skill covers server code, tool definitions, OAuth authentication, local testing, deployment, and connecting a Codex client.

• Building a remote MCP server
• Adding OAuth authentication to MCP tools
• Exposing external APIs as tools for AI agents

Verify device legitimacy and app integrity using DeviceCheck (DCDevice per-device bits) and App Attest (DCAppAttestService key generation, attestation, and assertion flows). Use when implementing fraud prevention, detecting compromised devices, validating app authenticity with Apple's servers, protecting sensitive API endpoints with attested requests, or adding device verification to a backend architecture.

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

Expert knowledge for Azure DevOps development including troubleshooting, best practices, decision making, architecture & design patterns, limits & quotas, security, configuration, integrations & coding patterns, and deployment. Use when managing org/projects, repos, pipelines, work items, dashboards/analytics, or Azure DevOps Server deployments, and other Azure DevOps related development tasks. Not for Azure Boards (use azure-boards), Azure Pipelines (use azure-pipelines), Azure Repos (use azure-repos), Azure Test Plans (use azure-test-plans).

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

Bootstrap Trigger.dev into an existing project from scratch: authenticate the CLI, install @trigger.dev/sdk and @trigger.dev/build, write trigger.config.ts with the project ref and task dirs, scaffold a /trigger directory with a first task, wire tsconfig and .gitignore, set TRIGGER_SECRET_KEY, and run the dev server. Load this when a project has no trigger.config.ts yet and the user asks to "add Trigger.dev", "set up Trigger.dev", "initialize Trigger.dev", or get a first task running, including in a monorepo. Once the project is set up and you are writing task code, switch to the trigger-authoring-tasks skill.

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

DDEV local development environment for Craft CMS projects. ALWAYS load this skill when running any ddev command, configuring .ddev/config.yaml, or troubleshooting local container issues. Covers config.yaml (project type, PHP/Node versions, database, docroot), shorthand commands, add-ons and built-in Mailpit, custom commands, Vite dev server exposure, database import/export, Xdebug toggling, sharing local sites, and troubleshooting (port conflicts, container restarts, ddev-injected env vars silently overriding your .env or config/general.php).

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

Containerize an R-based MCP (Model Context Protocol) server using Docker. Covers mcptools integration, port exposure, stdio vs HTTP transport, and connecting Claude Code to the containerized server. Use when deploying an R MCP server without requiring a local R installation, creating a reproducible MCP server environment, running MCP servers alongside other containerized services, or distributing an MCP server to other developers.

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

Create a SQL Server CDC capture using flowctl. Use when setting up real-time streaming from SQL Server, Azure SQL, Amazon RDS SQL Server, or Google Cloud SQL. Use when user says "capture SQL Server", "stream from MSSQL", "SQL Server CDC", or "connect SQL Server to Estuary".

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

Verify device legitimacy and app integrity using DeviceCheck (DCDevice per-device bits) and App Attest (DCAppAttestService key generation, attestation, and assertion flows). Use when implementing fraud prevention, detecting compromised devices, validating app authenticity with Apple's servers, protecting sensitive API endpoints with attested requests, or adding device verification to a backend architecture.

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

Split a home network into VLANs, separate logical networks for trusted devices, IoT, servers, and guests. Plan switch ports, Wi-Fi network mapping, and firewall rules using UniFi, pfSense/OPNsense, or MikroTik.

• Isolate smart home devices from PCs and servers
• Create guest Wi-Fi with internet-only access
• Assign switch ports and Wi-Fi networks to VLANs

Review a Homecore server operation plan before startup. Check authentication, restoration order, feature tests, speech provider configuration, and handling of pairing secrets. The skill reviews the plan without starting the server.

• Review a Homecore server startup plan
• Check restoration order and bounded limits
• Verify feature tests before enabling Wasmtime or HAP

Start, stop, and restart the OmniRoute server from the command line. Configure its port, background operation, automatic recovery, and system tray integration, or open the dashboard to manage the running server.

• Starting the server on a chosen port
• Running the server in the background with automatic recovery
• Stopping or restarting the server

Plan and build an MCP server, a connection that lets Claude use external tools. Choose hosting, tool structure, authentication, and a framework, then scaffold a server or hand off to specialized packaging and interface skills.

• Connect a cloud API to Claude
• Choose how to run and distribute an MCP server
• Organize tools for an API with many actions

Set up and maintain an OpenViking server, from configuration and installation to startup, shutdown, and health checks. Includes troubleshooting through logs and a data cleanup procedure with backups and explicit deletion confirmation.

• Setting up an OpenViking server
• Checking server health and investigating startup failures
• Resetting stored data after creating a backup