Loading...
Loading...
Found 36 Skills
KIRIKAE ローカル開発プロキシの環境管理スキル。 curl経由でAdmin API (localhost:4000) を操作し、環境の一覧表示・追加・切り替え・リネーム・更新・削除を行う。 使用タイミング: (1) 開発環境のプロキシ先を切り替えたい (2) 新しいポートを登録したい (3) 環境のラベル名を変更したい (4) 登録済み環境を確認したい (5) 環境を削除したい トリガーキーワード: kirikae、切替、プロキシ切替、環境切替、ポート登録、ポート切替
Set up multi-container applications with Docker Compose including services, networks, and volumes
Validates .env files and environment variable configurations against project requirements. Checks for missing required variables, type mismatches, insecure defaults, unreferenced variables, and common configuration errors. Compares .env against .env.example, code references, and deployment manifests. Produces a structured validation report with severity-ranked findings. Triggers on: "validate env file", "check environment variables", "env file audit", "missing env vars", "env validation", "check .env", "environment config check", "validate configuration", "env file review", "dotenv validation". Use this skill when verifying environment configuration completeness and correctness before deployment or after onboarding. NOT for secret scanning (use repo-sentinel or secret-scanner). NOT for general config file editing (use filesystem skill).
Integrates GuaraCloud into local development workflows — project linking, remote shell access, port forwarding, log streaming, and environment management. Use when the user wants to connect their local environment to GuaraCloud, tail logs, exec into a container, or forward ports.
Comprehensive package and environment management using pixi - a fast, modern, cross-platform package manager. Use when working with pixi projects for (1) Project initialization and configuration, (2) Package management (adding, removing, updating conda/PyPI packages), (3) Environment management (creating, activating, managing multiple environments), (4) Feature management (defining and composing feature sets), (5) Task execution and management, (6) Global tool installation, (7) Dependency resolution and lock file management, or any other pixi-related operations. Supports Python, C++, R, Rust, Node.js and other languages via conda-forge ecosystem.
Use ryuu.js (domo.js) APIs for env, events, navigation, and data calls.
MUST USE for anything related to mise, development tool versions, or dev environment setup. Triggers: (1) User mentions mise, mise.toml, .tool-versions, or mise commands like 'mise use', 'mise install', 'mise run'. (2) User wants to install, switch, pin, upgrade, or check versions of dev tools — node, python, go, ruby, java, rust, etc. — at project or global level, even without mentioning mise (e.g. 'set up node 22', 'what python version', 'upgrade go', 'check for outdated tools', 'configure dev environment'). (3) User wants to manage per-project environment variables via config files (e.g. 'add DATABASE_URL env var', 'set up env vars for different environments'). (4) User wants to define or run project tasks via mise (e.g. 'create a build task', 'run tests with mise'). Do NOT trigger for: Dockerfiles, package.json scripts, Makefiles, nvm/pyenv/rbenv commands, pip/npm package installation, git tags, CI/CD config, or deployment.
Use when users need to prepare a NocoBase environment, install and start an app, bootstrap local nocobase-ctl runtime, manage app environments (add/use/current/list), upgrade a single instance, or diagnose environment-level failures.
Execute mcloud environments commands to list, get, create, delete, redeploy, or trigger builds for Cloud environments. Use when managing environment lifecycle, redeploying after variable changes, or starting new builds from source.
Shared Base for Aike Smart Parking Open Platform (openydt) CLI: First-time use of openydt, profile configuration, signature (v2/v3) and multi-environment (test/dev/prod) setup, response envelope and status code/business code handling, exit codes, rate limiting and retry, write operation security rules. Triggered when users first use openydt, configure/switch profiles, handle signature or environment issues, interpret status/resultCode, encounter rate limiting or authentication failures, or before performing any parking lot write operations. All openydt domain skills should read this base first.
Queries Tilt resource status, logs, and manages dev environments. Use when checking deployment health, investigating errors, reading logs, or working with Tiltfiles.
Configure environment via mise [env] SSoT. TRIGGERS - mise env, mise.toml, environment variables, centralize config, Python venv, mise templates, hub-spoke architecture, monorepo structure, subfolder mise.toml.