「window」の検索結果

Use when bypassing a Windows exploit/platform mitigation — ASLR/DEP/CFG/XFG/CET, ACG/CIG, WDAC/App Control, ASR/AMSI/ETW, PPL/LSA Protection, BYOVD/VBS/HVCI

日本語の概要は準備中です。原文の説明を表示しています。

Local Windows privilege escalation on a STANDALONE / workgroup host, or a local shell on a domain member - foothold to SYSTEM. Token privileges (SeImpersonate/Potato), service misconfig (weak perms / unquoted path / writable binary), registry autologon creds, scheduled-task + writable-script abuse, DLL hijack, AlwaysInstallElevated, UAC bypass, credential loot. For DOMAIN escalation (kerberoast/DCSync/ADCS/BloodHound) use hunt-ad instead. Wiki-first, FIND schema output.

日本語の概要は準備中です。原文の説明を表示しています。

Create original short videos using the 手势边界换媒｜局部窗口、多形态验真与回归 Creative DNA for MiniMax H3 or Seedance 2.0. Use when the user wants a hand-defined local medium window, repeated geometry proof, strict clipping, and a controlled return with new subjects and surfaces.

日本語の概要は準備中です。原文の説明を表示しています。

Identify differentially bound regions across CLIP-seq conditions (knockdown vs control, treatment vs vehicle, disease vs healthy) using DEWSeq (sliding-window DESeq2), Flipper (Skipper-downstream), ASpeak, edgeR, or limma-voom. Use when computing condition-level changes in RBP binding intensity, choosing peak-level vs window-level vs crosslink-level testing, designing replicate experiments, or distinguishing biological binding shifts from technical confounders.

日本語の概要は準備中です。原文の説明を表示しています。

Symfony UX Map for interactive maps with Leaflet or Google Maps in Symfony. Covers markers, polygons, polylines, circles, info windows, and LiveComponent integration. Use when displaying maps, placing markers, drawing shapes or routes, handling map events, building store locators, using custom tile layers, or making maps reactive with LiveComponent. Code triggers: <twig:ux:map />, Map(), Point(), Marker(), Polygon(), Polyline(), Circle(), InfoWindow(), MapOptionsInterface, ComponentWithMapTrait, fitBoundsToMarkers, ux:map:marker:before-create, ux:map:connect, SYMFONY_UX_MAP_DSN. Also trigger when the user asks "how to display a map", "how to add markers", "how to draw a polygon on a map", "how to handle map click events", "how to make a reactive map", "how to use Leaflet in Symfony", "how to use Google Maps in Symfony", "map not showing", "map has zero height". Do NOT trigger for SVG icons (use ux-icons) or general frontend interactivity (use stimulus).

日本語の概要は準備中です。原文の説明を表示しています。

Assists with building cross-platform desktop applications using Electron. Use when architecting main/renderer process communication, configuring secure contexts, implementing auto-updates, or packaging apps for Windows, macOS, and Linux. Trigger words: electron, desktop app, browserwindow, ipc, auto-update, electron-builder.

日本語の概要は準備中です。原文の説明を表示しています。

Use when designing space missions, computing launch windows, optimizing trajectories, analyzing payload constraints, or planning mission phases and contingencies. Use when "mission design, launch window, trajectory optimization, mission timeline, mass budget, propellant budget, mission phases, porkchop plot, C3, gravity assist, low thrust, mission architecture, LEO, GEO, interplanetary, " mentioned.

日本語の概要は準備中です。原文の説明を表示しています。

Show whether each skill is earning its context-window cost — combined tokens-used view sorted by waste. Use when the user asks 'are my skills worth it', 'what's my context budget', 'which skills are dead weight', or wants to audit skill value, token cost, or usage. Trigger with '/janitor-value'.

日本語の概要は準備中です。原文の説明を表示しています。

Use Nexscope data to reverse-lookup traffic keywords for any Amazon ASIN, including organic ranking, ad ranking, search volume, traffic share, organic/paid scores, ABA TOP3 click concentration, click conversion rate, year-over-year search volume changes, and weekly/monthly time windows. Trigger when the user mentions ASIN keyword analysis, ASIN reverse lookup, traffic keyword research, organic ranking query, ad ranking query, keyword position tracking, Nexscope keyword data, competitor keyword peeking, viewing which keywords drive traffic to a product, analyzing keyword performance for a specific ASIN, time windows by week/month/recent N days, ASIN reverse keyword lookup, traffic keywords, organic ranking, ad ranking, search volume, Nexscope keywords, competitor keyword reverse lookup, click concentration, click-to-purchase conversion, week-over-week search volume. Even if the user does not explicitly mention "Nexscope", if their need involves finding keywords associated with a specific Amazon product (ASIN), this skill should also be triggered.

日本語の概要は準備中です。原文の説明を表示しています。

Win #1 Product of the Day on Product Hunt. Completely reverse-engineered from 30x daily winner and 3x weekly winner campaigns — ranking algorithm decoded, launch timing optimized, hunter selection guide, community engagement approach, and post-launch momentum playbook. Use this if you're: (1) already read PH launch guides but still can't break into Top 5 and need algorithm-level deep optimization, (2) targeting Daily #1 and 5,000+ sign-ups with a proven 30+ case validated approach, or (3) an investor/accelerator coaching portfolio companies on PH launches. What's inside: PH ranking algorithm decoded: weighted factors for first 3 hours, 24 hours, and weekly ranking · Pre-launch preparation: gallery optimization, product URL selection, tagline refinement (≤60 chars) · Launch timing optimization: exact PST launch windows + scheduling guide · Community engagement KPIs: upvote targets, comment response time, maker comment strategy · Platform compliance guide: understanding PH's quality signals and organic growth · Post-launch 72-hour plan: maintaining momentum, conditions for Weekly #1 · Case studies: 3 different categories (AI Tool, App, SaaS) dissected Expected outcomes: Product Hunt Daily #1 ranking · strong community engagement on launch day · 3,000–10,000+ sign-ups (depending on product-market fit) 🇨🇳 Product Hunt 打榜完整攻略 | 🇯🇵 Product Hunt ローンチガイド | 🇰🇷 Product Hunt 런칭 가이드 Keywords: Product Hunt #1, Product Hunt launch strategy, PH ranking algorithm, PH #1 daily winner, Product Hunt tips, product launch, startup launch, ranking optimization, PH gallery optimization, Community engagement strategy, maker community engagement, product strategy, launch tactics, how to win Product Hunt, product hunt best practices

Implements ASP.NET Core rate limiting middleware for API protection. Covers fixed window, sliding window, token bucket, and concurrency limiters with custom policies.

日本語の概要は準備中です。原文の説明を表示しています。

Orchestrator context window discipline enforcement. Prevents the orchestrator from reading source files it will not edit, running diagnostic commands that waste context, and rationalizing delegation bypasses. Use when setting up orchestrator guardrails, reviewing delegation discipline, or diagnosing context window waste in multi-agent workflows. Activates PreToolUse hooks that surface decision points before source file reads and diagnostic command execution.

日本語の概要は準備中です。原文の説明を表示しています。

Quantitative cost measurement for technical research — token injection costs, payload sizes, context window consumption, and file-level counts from actual repo files. Use when a technical-researcher orchestrator needs the cost dimension of adding or changing something: how many tokens will it inject, how big are the artifacts, what is the context window impact? This is NOT blast-radius analysis (which files break) — it covers size, tokens, and performance cost only.

日本語の概要は準備中です。原文の説明を表示しています。

Use when validating windows paths

日本語の概要は準備中です。原文の説明を表示しています。

Run the oncall handoff for a rotation window — the whole handoff, not just a document: build the summary (what the incoming oncall needs first, what's still open, incidents with impact numbers, alert and page counts, hygiene suggestions, every number traceable to a source), post it for the outgoing oncall to correct, walk the incoming oncall through the open items in the thread, update the list as they respond, and note when they acknowledge. Runs mainly in the team's standing oncall / monitoring channel, normally as a scheduled routine firing at rotation change so the report is waiting when the shift turns over; can also be run by hand and works from an incident channel. Use when a handoff routine fires, or on "handoff", "hand over", "oncall summary", "weekly oncall report", "what happened this shift / this week". Re-running for the same window updates the report rather than duplicating it. Unattended runs carry a run-summary block and at least one chart.

日本語の概要は準備中です。原文の説明を表示しています。

REQUIRED for end-user customization of Linux desktop, window manager, or system config. Use when editing ~/.config/hypr/, ~/.config/omarchy/, ~/.config/alacritty/, ~/.config/foot/, ~/.config/kitty/, or ~/.config/ghostty/. Triggers: Hyprland, window rules, animations, keybindings, monitors, gaps, borders, blur, opacity, omarchy-shell, bar, terminal config, themes, background, night light, idle, lock screen, screenshots, reminders, layer rules, workspace settings, display config, and user-facing omarchy commands. Excludes Omarchy source development through `omarchy dev link` workflows.

日本語の概要は準備中です。原文の説明を表示しています。

What this project has already learned the hard way, and where any new such fact belongs. Two jobs. (1) Routing: this project keeps NO per-project Claude memories — read this before writing anything down, and pick a durable home from the list here. (2) An index, by area, of non-obvious facts worth knowing before you guess: debugging rigs and measurements that lie, iOS/WebKit and the tethered iPhone, the Windows app, production and deployment, and general codebase traps. Use before setting up a browser- or server-driven debugging session, when a bug reproduces only on iPhone, in Safari or in the Windows app, before changing deployment configuration or reading store/crash data, when something behaves unexpectedly and you are about to guess why, and whenever you are tempted to record a fact for later.

日本語の概要は準備中です。原文の説明を表示しています。

Windows local privilege escalation from a low-privilege shell to Administrator or SYSTEM. Covers quiet vs loud enumeration, SeImpersonate/Potato family including LocalPotato, token privileges (SeBackup/SeRestore/SeManageVolume/SeLoadDriver/SeDebug), service/DLL/COM/scheduled-task abuse, AlwaysInstallElevated and UAC boundary, KrbRelayUp-style domain-joined local admin, and version-gated kernel LPE. Use when the operator already has a Windows foothold and needs local SYSTEM. Endpoint blocks hand off to /edr-bypass then return here.

日本語の概要は準備中です。原文の説明を表示しています。

Rules and patterns for creating Avalonia UI visual elements (controls, dialogs, panels, windows). Use when creating or modifying XAML controls, dialogs, panels, or windows in this project.

日本語の概要は準備中です。原文の説明を表示しています。

Assesses market receptivity for equity issuance with sector sentiment, volatility, and comparable recent offering performance. Use when timing equity offerings, analyzing market windows, or evaluating issuance conditions.

日本語の概要は準備中です。原文の説明を表示しています。

Living catalogue of 7 known hazard entries (SE-01 through SE-07) specific to agent-studio: Windows backslash paths, prototype pollution, hook exit codes, async swallowing, ReDoS in glob-to-regex, DST arithmetic, array mutation during iteration. Each entry: symptom, root cause, fix, test assertion.

日本語の概要は準備中です。原文の説明を表示しています。

PowerShell 7+ scripting and Windows system administration -- cross-platform automation, secure credential handling, Pester testing, DSC, and JEA patterns.

日本語の概要は準備中です。原文の説明を表示しています。

Specialized agentic and context engineering prompt methodology for Claude. Use when designing AI agents — system prompts, tool definitions, context window architectures, failure mode planning, multi-agent coordination, agent evaluation. Trigger on: "design an agent," "build a system prompt for an agent," "architect an agent's context," "design tool definitions," "agent system prompt," "context window architecture," "tool interface design," "evaluate agent behavior," "multi-agent coordination," "context engineering for agents," "ACI design." Provides 12 tested approaches for agent architecture (designing agents, not using them). Do NOT use for evaluating or scoring individual non-agent prompts (use rootnode-prompt-validation if available). Do NOT use for general software architecture that hosts agents (use standard technical reasoning for that).

日本語の概要は準備中です。原文の説明を表示しています。

Use when the user wants to run SQL - especially analytical SQL - on local files (parquet/csv/json), URLs, S3 paths, or remote databases (Postgres, MySQL, MongoDB, ClickHouse Cloud, Iceberg, Delta Lake) without setting up a server. Provides chDB - embedded ClickHouse SQL in Python with 1000+ functions, Session for stateful multi-step pipelines, parametrized queries, and cross-source joins via `s3()`, `mysql()`, `postgresql()`, `iceberg()`, `deltaLake()`, `remoteSecure()` table functions. TRIGGER when: user wants SQL on parquet/csv/files or across remote analytical sources; uses ClickHouse SQL features (window functions, windowFunnel, geoToH3, JSON path ops, Session, parametrized queries); imports `chdb` or calls `chdb.query()`. SKIP this skill for pandas-style DataFrame method-chaining (use chdb-datastore instead) or ClickHouse server administration.

日本語の概要は準備中です。原文の説明を表示しています。