'commands' 검색 결과

Route a task through SIPS commands, agents, scripts, MCP tools, or bounded delegation. Use when asked to route, split, fan out, escalate, or choose the right SIPS path.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

End-to-end playbook for creating a new NV oOS Pro toolkit under addons/pro/includes/tools/<toolkit> — folder layout, service layer, tool class conventions (canonical envelope, two-gate sanitisation, capability flags), ALL eleven registration surfaces (Pro module registry loader, central registry, admin Tools section + Features subtab, admin settings page/side menu, settings status map, both WP-CLI commands, schedule presets, workflow presets, SA Toolkit Manager, coverage manifests), fixture/oracle testing with a standalone smoke harness, and the phpcs gotcha checklist. Use when asked to build a new Pro toolkit, add a toolkit to the plugin, scaffold toolkit tools, register toolkit presets/toggles, or debug why a new toolkit's tools, toggle, or admin menu don't appear. First case study: food-beverage (F&B Management, 21 tools, 2026-10-08, 20/20 Check-totals oracle verified). Complements mcp-ai-wpoos-toolkit-audit (hardening existing toolkits) and mcp-ai-wpoos-test-suite (repair).

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Automate recruiting and hiring workflows in Ashby -- manage candidates, jobs, applications, interviews, and notes through natural language commands.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Create, revise, or audit AGENTS.md files from repository evidence, verified commands, and correctly scoped instructions without overwriting maintainer intent.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Generate MSBuild binary logs (binlogs) for build diagnostics and analysis. Only activate in MSBuild/.NET build context. USE FOR: adding /bl:{} to any dotnet build, test, pack, publish, or restore command to capture a full build execution trace, prerequisite for binlog-failure-analysis and build-perf-diagnostics skills, enabling post-build investigation of errors or performance. Requires MSBuild 17.8+ / .NET 8 SDK+ for {} placeholder; PowerShell needs -bl:{{}}. DO NOT USE FOR: non-MSBuild build systems (npm, Maven, CMake), analyzing an existing binlog (use binlog-failure-analysis instead). INVOKES: shell commands (dotnet build /bl:{}).

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Validates custom dotnet new templates for correctness before publishing. Catches missing fields, parameter bugs, shortName conflicts, constraint issues, and common authoring mistakes that cause templates to fail silently. USE FOR: checking template.json files for errors before publishing or testing, diagnosing why a template doesn't appear after installation, reviewing template parameter definitions for type mismatches and missing defaults, finding shortName conflicts with dotnet CLI commands, validating post-action and constraint configuration. DO NOT USE FOR: finding or using existing templates (use template-discovery), creating projects from templates (use template-instantiation), creating templates from existing projects (use template-authoring).

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Code formatting and linting context for the Megahub project. Use when writing or reviewing code in C++ or JavaScript, or when running format/lint checks. Describes tool commands, style conventions, and when to apply them.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Trace BIRD routing-daemon behavior through the actual C source tree. Use for implementation questions, suspected upstream bugs, parser/keyword origins, filter instructions, protocol state machines, route attributes, birdc commands, stack traces, or BIRD 2 versus BIRD 3 source comparisons. Prefer a local checkout or exact upstream tag/commit and cite concrete files, functions, and revisions. Route config linting to bird-agent and active incidents to bird-troubleshooting.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when performing security audits, vulnerability assessments, penetration testing, or when asked to find security issues. Use when encountering code that handles user input, executes commands, reads files, or makes network requests.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Inspect, debug, and inject custom code into a running Steam client — desktop (macOS, Linux, Windows) or Steam Deck over the network — through its Chromium Embedded Framework (CEF) Chrome DevTools Protocol endpoint. Use when developing Steam UI plugins, mods, themes, or integrations — injecting CSS/JS to try a change, locating webpack modules and obfuscated class names, reading React or SteamUIStore state, inspecting Big Picture / Quick Access Menu windows, screenshotting what actually rendered, streaming console logs, or diagnosing runtime errors in Steam's UI. The same commands run against either device, or both at once. Injection is per-session and for development only. Not for building a plugin loader or making changes persist across restarts, Steamworks game SDK work, game development, or scraping the public Steam web store.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

TidyFactor Design track — code-native UI design lifecycle engine (Figma alternative). Supports all 7 stages of UI design (Discovery, Foundation, Architecture, Components, Motion, Quality, Delivery) with zero per-page CSS/JS and zero build step. Pluggable CSS foundations (Native, Tailwind utility-first, daisyUI, Hybrid, shadcn, Pico, Bootstrap, Alpine) and full Arabic/RTL support (El Messiri/Tajawal, never Amiri above 24px). Trigger on commands "study", "brief", "init", "brand", "typography", "school", "tokens", "palette", "assets", "layout", "nav-footer", "components", "page", "dashboard", "motion", "states", "flow", "i18n", "perf", "audit", "clone", "retrofit", "handoff", "deploy", or requests like "build a design system", "UI design lifecycle", "prototype this website", "Figma alternative", "نموذج أولي تفاعلي", "صمّم لوحة تحكم".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Code-native UI design lifecycle engine (Figma alternative) with Contextual Decision Layer (CDL). Supports all 7 design stages with zero per-page CSS/JS and pluggable CSS foundations (Native, Tailwind, daisyUI, Pico, Hybrid). Trigger on commands 'brief', 'study', 'init', 'brand', 'tokens', 'palette', 'layout', 'components', 'page', 'dashboard', 'motion', 'i18n', 'audit', 'deploy', or design system requests.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Generate a professional git commit message from the repo's current diff. Analyzes all staged, unstaged, and untracked changes, categorizes them, and creates the commit directly once the user approves it, then asks before pushing it (paste-safe commands are a fallback). Trigger on: "commit", "write a commit", "commit message", "what changed", "summarize changes", "draft commit", "changelog", or any request to commit, stage, or describe the current diff.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Vite build systems: production-level ESM, assets, chunk strategies and commands. Use when implementing, reviewing or testing vite build systems for React, Vite, Next.js or Perfect_AI projects.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Open the AOS Hub on 127.0.0.1:7900 (services, plan kits, store) or stop/status it. Generated from plugin-commands.json; invoke as $bdb-aos:hub.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Install, verify, and operate mdoctor on macOS and Debian/Arch-based Linux. Use when users ask to set up mdoctor, install dependencies, test branch builds on the current machine, run first health checks, troubleshoot install/runtime issues, or perform safe cleanup/fix workflows with mdoctor commands.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Bash/Linux terminal patterns. Critical commands, piping, error handling, scripting. Use when working on macOS or Linux systems.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when about to claim work is complete, fixed, or passing — requires running verification commands and confirming output before making any success claims. Evidence before claims, always.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Utility — fill the surface stack map in tech-stack.md and provision skills using intelligent resolution. Called by pipeline commands when tech stack info changes.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

REQUIRED --repo flag for all commands, helper functions for code review comments, suggestion block syntax rules

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when working with Ansible — ansible automation and configuration management. Covers playbook execution, inventory management, role management, vault secrets, ad-hoc commands, fact gathering, and task debugging. Use when running playbooks, managing inventories, debugging task failures, or auditing Ansible configurations.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Train and fine-tune transformer language models using TRL (Transformers Reinforcement Learning). Supports SFT, DPO, GRPO, KTO, RLOO and Reward Model training via CLI commands.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Run verification commands and confirm output before claiming success

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Zero-config Postgres for Netlify apps via @netlify/database — querying data from Functions/Edge Functions, writing schema migrations, setting up Drizzle ORM, local dev with netlify dev, database branches for deploy previews, and migrating an existing Postgres project onto Netlify. Use when adding a database, building a contact form or CRUD API, writing SQL migrations, wiring up Drizzle, running netlify database commands, testing with a local Postgres, or switching from Neon/Supabase/RDS to Netlify Database.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.