Results for “setup”

Set up an LLM-judge evaluation that extracts canonical use cases for a PostHog feature at scale and streams the results to a Slack channel as a live feed. Use when someone wants to understand how users are actually using a specific AI/LLM-powered feature in production — what they're investigating, what questions they're trying to answer, and what patterns surface — without manually reading hundreds of traces. Assumes the feature emits `$ai_generation` and `$ai_evaluation` events with `$session_id` linkage to the trigger user's recording (the standard setup post the session-summary linkage PRs).

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

Guides agents through the 3-step experiment creation flow: defining the hypothesis, configuring rollout, and setting up analytics. Delegates rollout decisions to configuring-experiment-rollout and metric setup to configuring-experiment-analytics. TRIGGER when: user asks to create a new experiment or A/B test, OR when you are about to call experiment-create. DO NOT TRIGGER when: user is updating an existing experiment, managing lifecycle, or only browsing experiments.

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

Design database schemas — tables, relationships, indexes, constraints, and ORM setup. Covers relational design, normalization, and common patterns.

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

How to author, edit, and adapt PostHog Signals scouts — the scheduled agents that scan a project and emit findings into the Signals inbox. Use when a user wants to customize a canonical scout for their own setup (narrow its scope, retune its thresholds, add disqualifiers), tweak a scout's schedule or dry-run posture, or write a brand-new scout from scratch for a specific use case (a custom event, a product surface no canonical scout covers). Covers the scout SKILL.md anatomy, the emit contract, the dedupe + scratchpad-memory conventions, the per-team skills-store path vs the canonical in-repo path, and the emit-and-inspect test loop (with dry-run as an optional safety net). Trigger on "write/edit/customize a signals scout", "new scout for X", "tune my scout schedule", "make a scout that watches <event>".

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

Audit PostHog experiments and feature flags for configuration issues, staleness, and best-practice violations. Read when the user asks to audit, health-check, or review experiments or feature flags, check flag hygiene, or verify experiment setup.

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

Dockerize an application with a production-ready Dockerfile, docker-compose setup, and .dockerignore.

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

TOP PRIORITY skill — find and immediately fix or remove every piece of wrong, outdated, or redundant information in ToolUniverse docs. Wrong code, broken links, incorrect counts, and overlapping instructions must be fixed or removed — never left in place. Runs five phases: (D) static method scan, (C) live code execution, (A) automated validation, (B) ToolUniverse audit, (E) less-is-more simplification. Core philosophy: each concept appears exactly once; remove don't add; no emojis; single setup entry point. Use when reviewing docs, before releases, after API changes, or when asked to audit, fix, or simplify documentation.

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

Build-system setup for GNOME apps per language: Python/PyGObject, Rust/gtk-rs, C, Vala, JavaScript/GJS — meson files, blueprint-compiler wiring, Flatpak manifests. Use when choosing a language for a GNOME app or setting up its build.

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

Build or improve UI test coverage for visual regression, interactions, and accessibility. Use when the user asks for a test strategy, automated tests, testing setup, or fixes to flaky UI tests. A one-time browser inspection or visual review does not require a new test suite.

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

Configure and debug MCP servers for Claude Code, OpenCode, and Codex CLI, including auth headers, scope, and validation checks. Use when MCP tools fail to connect, when an MCP server returns 401/404/HTML, or when adding a new MCP server to this repo.

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

Configure and debug MCP servers for OpenCode, Codex CLI, and Claude Code, including auth headers, scope, and validation checks. Use when MCP tools fail to connect or when adding a new MCP server.

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

Stellar smart contract development (Rust, soroban-sdk). Entry point with project setup, contract anatomy, and build/deploy workflow, routing to three companion files in this directory — development.md (storage/TTL, authorization, cross-contract calls, tokens, events, errors, upgrades, fees, troubleshooting), testing.md (unit, fuzz, property, fork, mutation, integration), and security.md (vulnerability classes, checklists, tooling, audits). Use when writing, testing, reviewing, securing, debugging, or shipping Stellar smart contracts, including anything the user calls "Soroban" — Soroban contracts, soroban-sdk, Soroban auth/storage/TTL errors, SEP-41 tokens, or SAC integration from contract code.

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

Guide agency management system setup and optimization. TRIGGERS - Use when user needs help with agency-management-system related tasks.

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

Writes an autonomous agent for the CARLA Leaderboard — an AutonomousAgent subclass with setup/sensors/run_step/destroy, a sensor suite inside the track's budget, and the right constructor signature for the leaderboard version (1.0 and 2.x differ). Generates a working skeleton, validates the sensor configuration against the real per-track limits offline, and covers the ROS1/ROS2 agent base classes. Use when the user asks to "write a leaderboard agent", "make my agent work with the leaderboard", "add sensors to my agent", "port my agent to 2.1", or hits SensorConfigurationInvalid.

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

ZMK Firmware (オープンソースキーボードファームウェア) リファレンス。 Getting Started (hardware, user-setup, customization, zmk-cli)、 Features (bluetooth, split keyboards, encoders, displays, lighting, pointing, studio, low-power)、 Keymaps (keycodes, modifiers, combos, conditional layers)、 Behaviors (タップ・ホールド、レイヤー、マクロ、tap-dance, sticky-key)、 Input Processors、Hardware Integration、Troubleshooting (building, flashing, connection, hardware issues)。

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

TanStack Start (TanStack Router ベースのフルスタック React フレームワーク、 @tanstack/react-start) の API リファレンス。Next.js とは別フレームワーク。 createServerFn (validator / handler), createMiddleware, server routes, createServerOnlyFn / createIsomorphicFn、SSR / selective SSR / SPA mode / static prerendering / ISR、streaming、hydration、server entry / client entry、 TanStack Query 連携 (setupRouterSsrQueryIntegration)、RC → stable 移行、 hosting (Cloudflare Workers / Netlify / Vercel / Node / Bun / Docker)、 production checklist、authentication / session、Tailwind、SEO、 environment variables。ルーティングは tanstack-router スキルを参照。

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

Claude Code (code.claude.com) の権限・セキュリティ・企業管理リファレンス。 permissions (allow / ask / deny), permission modes, auto mode (classifier billing), sandboxing, sandbox environments, sandboxed Bash, zero data retention, data usage, HIPAA, managed settings (MDM / plist / registry), server-managed settings, managedMcpServers, allowedProviders, admin setup, authentication (SSO), network config, corporate launcher, OpenTelemetry monitoring, analytics, costs, large codebases, communications kit / champion kit。

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

Check whether a Playwright, Puppeteer, Selenium or CDP-driven browser presents a coherent fingerprint, using liarjs as a library against a Page you already have - navigator.webdriver, HeadlessChrome tokens, worker versus main-thread identity, patched-API integrity, WebGL versus WebGPU GPU identity. Use when asked whether an automated browser looks like a normal one, when a headless setup or a stealth plugin's effect needs measuring rather than assuming, or when an assertion on fingerprint quality belongs in a test suite.

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

The shared Codex web-work inbox. Use when a coding agent needs browser work, provider account setup, OAuth or ecommerce portal work, npm publishing, or recovery of an incomplete Vault/account handoff delegated to Codex.

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

Secures Spring Security filters, JWT validations, OAuth2 setups, and CORS/CSRF headers.

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

Configure a Rails project to work with Conductor (parallel coding agents)

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

Enforces Pydantic v2 strict models, asynchronous dependency generators, and uv environment setup.

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

Write or fix a test in the Lyrion Dashboard's suite. Use this whenever a task adds a test, changes one, or asks why the suite fails — anything touching `tests/`. Covers the standalone-per-file scaffolding, the env-before-import rule, where to patch (the route/service the code under test imports), the cache-and-clock testing pattern, and how to run one test vs the whole suite. Reach for it any time you touch `tests/` so new tests match the existing shape instead of re-inventing setup.

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

Use when writing tests of any kind — unit, slice, or integration. Covers test structure, naming conventions, Mockito patterns, @WebMvcTest, @DataJpaTest, and Testcontainers setup.

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