745건 · 관련도순
Audits and realigns UI to match design system standards, spacing, tokens, and patterns. Use when the user mentions consistency, design drift, mismatched styles, tokens, or wants to bring a feature back in line with the system.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Audits and realigns UI to match design system standards, spacing, tokens, and patterns. Use when the user mentions consistency, design drift, mismatched styles, tokens, or wants to bring a feature back in line with the system.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Autonomous DevSecOps & FinOps Guardrails. Orchestrates Gemini 3 Flash to audit Linux Kernel patches, Terraform cost drifts, and K8s compliance.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Audit the project's documentation (CLAUDE.md, .claude/rules, skills, README, CONTRIBUTING, SECURITY, .env.example, app/data/*.md, learn articles) against the actual code and config, and fix drift. Use after refactors, dependency or workflow changes, or on a schedule.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Periodic repository health check — install, full validation, unused-code scan, outdated/vulnerable dependencies, and docs drift — ending in a concise report and, when there are safe fixes, a single PR. Designed to run unattended from a scheduled routine; also usable on demand.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Terraform / OpenTofu / Nix / k8s manifest misconfiguration detection — open security groups, missing encryption, public S3/GCS, IAM wildcards, plaintext secrets, missing tags. Use when reviewing an IaC PR, gating `terraform apply` / `tofu apply`, auditing existing state for drift, or building a compliance report for cloud configuration.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Review changes for bugs, regressions, missing tests, safety gaps, public/private leaks, and architecture drift before stylistic comments.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Refresh `memory/SPEC.md` and `memory/PLAN.md` in mature mode — restore canonical truth, archive retired plan history, delete stale derivative artifacts, and flag drift against code.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Design verification strategy: diagnose observability, select oracle families, map to loop tiers, surface blind spots. Use after ln-plan when frontier items or scoped slices need oracle design — especially for LLM, visual, or compositional work — or when verification coverage has drifted.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Universeller Skill für LLM-Navigation, Orientierung und Ausfallsicherheit. Stellt aktives Wayfinding, Selbstorientierung und Wiederherstellungsheuristiken bereit, wenn Agenten mit Kontextdrift, fehlschlagenden Werkzeugen, Schleifen oder Sackgassen konfrontiert sind. Enthält die synonymen Strategien survival-routing, dead-reckoning, pathfinder-routing und celestial-routing.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Baut aus einem Chatverlauf oder aus bestehenden Automatisierungs-Prompts (z. B. eines anderen Agenten-Systems) eine selbstlaufende, user-neutrale Workflow-Automatisierung: einen wiederkehrenden Prompt bzw. Automations-Skill für Cron/Schedule/Loop. Alias: automations-extractor. Nutze diesen Skill bei „mach daraus eine Automatisierung", „das soll regelmäßig/nächtlich laufen", „extrahiere Workflows aus diesen Chatverläufen/Automationen", „Automation aus dieser Session bauen", oder bei `/workflow-extract`. Ergänzt fehlende Automations-Bausteine (Rotations-Auswahl, Check-Registry, Idempotenz, Log-Hygiene, Freigabe-Gate, Eskalations-Handoff, Monitor-Meldedisziplin) systematisch. Enthält auch den Fleet-Audit-Modus: bestehende Automations-Flotten auf Silent-Failures, Redundanz, Drift und Lücken prüfen („prüfe meine Automatisierungen/Scheduled Tasks/Cron-Jobs"). Soll stattdessen ein abrufbarer Skill (Fähigkeit auf Zuruf) entstehen, den Schwester-Skill skill-extractor nutzen.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Übersetzt zwischen Benutzeroberfläche und Text — in beide Richtungen. Aus einer beschriebenen Oberfläche wird ein Skill; aus einem Skill wird eine Oberfläche. Nutzen, wenn eine Anwendung entworfen wird und der Ablauf noch unklar ist, wenn ein bestehendes Werkzeug als Skill verfügbar gemacht werden soll, wenn Oberfläche und Agentenzugang auseinanderdriften, oder wenn ein Skill zu lang wird und niemand weiß warum.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Rework an existing NV oOS Pro toolkit from a single-tenant demo into a universal product — currency-neutral schema with legacy aliases, a Tenant Profile + token renderer shared across the two assistant-delivery surfaces (packs via Portability vs blueprints via Blueprint Installer), demo-mode inversion, a universal single-folder ingestor (header-alias dictionary + dry_run + JSON), report export to CSV/PDF (DomPDF vs html_to_pdf choice), the add-a-tool drift checklist (TOOLS_LIST, coverage manifest, admin tool list, presets), and the re-seed-on-settings-save gotcha. Use when asked to 'universalise', 'de-demo', 'multi-tenant', 're-tenant', 'remove LKR/Surf Club', 'point the toolkit at a single Drive folder', 'export reports as CSV/PDF', or 'avoid re-installing assistants on save'. First case study: food-beverage (F&B Management, 2026-10-16). Complements mcp-ai-wpoos-toolkit-creation (build new) and mcp-ai-wpoos-toolkit-audit (harden existing).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Per-toolkit hardening audit loop for NV oOS Pro tools. Systematically scans each addons/pro/includes/tools/<toolkit> (and its plugins/nvoos-content-graph-pro mirror) for the recurring production failure classes — unguarded shell calls that fatal on exec-disabled hosts, calls to nonexistent client methods, string-assuming parsing of provider responses that may be arrays, provider enum/service mismatches, metric/source column drift that silently returns 0, secondary-table denominator gaps, the Chart.js fixed-height loop, misleading native-source errors, and silent import truncation that reports partial writes as success — then fixes, tests (Docker PHPUnit), and validates (phpcs both standards) before moving to the next toolkit. Use when asked to audit a toolkit, review the X tools for similar issues, do the same for the other toolkits, or continue the toolkit audit loop. The first case study (document-generation) found 3 fatal bugs + 1 broken regex; the food-beverage pass added classes 5–9.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Review a change for architectural drift, guardrail weakening, and ADR impact before shipping.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Ensure designs define data flow, state ownership, consistency boundaries, and cross-boundary writes to prevent drift and incidents.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Ensure ADRs capture context, decision, alternatives, tradeoffs, and follow-ups in a way that prevents future drift.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Ensure design changes stay consistent across ADRs, diagrams, and specs; decisions are traceable; and drift is explicitly managed.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Ensure architecture docs define bounded contexts, ownership, and a consistent ubiquitous language to prevent domain drift and coupling.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Detects domain terms drifting between code identifiers and the established ubiquitous language (same concept under different names, or different concepts sharing a name).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
モジュール/スキルの構造変更で当該ファイルは更新したが、caller 側が古い構造（旧参照・旧シグネチャ・旧採番）を参照したまま残るパターンを検出する
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Audit OpenClaw frontend code and rendered interfaces for Carapace drift, token misuse, primitive reimplementation, accessibility problems, responsive defects, and off-brand copy. Use for design reviews, compliance checks, or scheduled audit-and-fix workflows.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when the user wants a wall of album covers, an image wall, a covers grid, or any square art drifting slowly in the background of a site. Includes collecting their saved albums from Spotify and building the wall from them. The wall goes behind whatever front the site already has; a frosted panel is the default when the site has none.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Local database and persistence selection for Flutter including SharedPreferences, SecureStorage, Hive, and Drift. Use when implementing offline storage, encrypted data persistence, or choosing between key-value and relational local databases.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.