Build and verify Adaptive navbar for Marketing landing with Bootstrap v5.3 using a working semantic implementation, responsive RTL/LTR behavior, theme tokens, test plan and design verification.
日本語の概要は準備中です。原文の説明を表示しています。
3,437 件 ・ 関連度順
概要と使いどころ
Build and verify Adaptive navbar for Marketing landing with Bootstrap v5.3 using a working semantic implementation, responsive RTL/LTR behavior, theme tokens, test plan and design verification.
日本語の概要は準備中です。原文の説明を表示しています。
Build and verify Adaptive navbar for Mobile-first interface with Bootstrap v5.3 using a working semantic implementation, responsive RTL/LTR behavior, theme tokens, test plan and design verification.
日本語の概要は準備中です。原文の説明を表示しています。
Build and verify Adaptive navbar for Data-heavy application with Bootstrap v5.3 using a working semantic implementation, responsive RTL/LTR behavior, theme tokens, test plan and design verification.
日本語の概要は準備中です。原文の説明を表示しています。
Build and verify Adaptive navbar for Commerce and checkout with Bootstrap v5.3 using a working semantic implementation, responsive RTL/LTR behavior, theme tokens, test plan and design verification.
日本語の概要は準備中です。原文の説明を表示しています。
Build and verify Adaptive navbar for Documentation and knowledge with Bootstrap v5.3 using a working semantic implementation, responsive RTL/LTR behavior, theme tokens, test plan and design verification.
日本語の概要は準備中です。原文の説明を表示しています。
Conducts authorized wireless network penetration tests to assess the security of WiFi infrastructure by testing for weak encryption protocols, captive portal bypasses, evil twin attacks, WPA2/WPA3 handshake capture, rogue access point detection, and client-side attacks. The tester evaluates wireless authentication, network segmentation, and the effectiveness of wireless intrusion detection systems. Activates for requests involving wireless pentest, WiFi security assessment, WPA2/WPA3 testing, or rogue access point detection.
日本語の概要は準備中です。原文の説明を表示しています。
Analyzes network traffic captures and flow data to identify adversary activity during security incidents, including command-and-control communications, lateral movement, data exfiltration, and exploitation attempts. Uses Wireshark, Zeek, and NetFlow analysis techniques. Activates for requests involving network traffic analysis, packet capture investigation, PCAP analysis, network forensics, C2 traffic detection, or exfiltration detection.
日本語の概要は準備中です。原文の説明を表示しています。
Transforms conversations and discussions into structured documentation pages in Notion. Captures insights, decisions, and knowledge from chat context, formats appropriately, and saves to wikis or databases with proper organization and linking for easy discovery.
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user explicitly asks for a desktop or system screenshot (full screen, specific app or window, or a pixel region), or when tool-specific capture capabilities are unavailable and an OS-level capture is needed.
日本語の概要は準備中です。原文の説明を表示しています。
Add PostHog log capture to track application logs. Use after implementing features or reviewing PRs to ensure meaningful log events are captured with structured properties. Also handles initial OTLP exporter setup if not yet configured.
日本語の概要は準備中です。原文の説明を表示しています。
Diagnoses why a session recording is missing or was not captured. Use when a user asks why a session has no replay, why recordings aren't appearing, or wants to troubleshoot session replay capture issues for a specific session ID or across their project. Covers SDK diagnostic signals, project settings, sampling, triggers, ad blockers, and quota/billing scenarios.
日本語の概要は準備中です。原文の説明を表示しています。
Debugs why session recordings aren't appearing in the local dev environment. Use when a developer reports that local replay ingestion isn't working, recordings aren't showing up despite /s calls, or the replay pipeline seems broken after hogli start. Covers the full local pipeline: SDK capture, Caddy proxy, capture-replay (Rust), Kafka, ingestion-sessionreplay (Node), recording-api (Node), SeaweedFS, and common failure modes like orphaned processes, stuck phrocs workers, and trigger misconfiguration.
日本語の概要は準備中です。原文の説明を表示しています。
Kubb (OpenAPI / Swagger コードジェネレーター) リファレンス。 kubb.config.ts、OpenAPI から TypeScript 型・TanStack Query フックを生成するコード生成プラグイン・ Zod スキーマ・MSW モック・Faker・Axios / SWR / React Query クライアント生成。 プラグインベース、モノレポ対応。 parser-ts / parser-md パーサー、adapter-oas アダプター、Kit API・diagnostics。 TanStack Query 本体の API は tanstack-query スキル。
NVIDIA DGX Spark User Guide リファレンス。GB10 Grace Blackwell Superchip ハードウェア仕様、first-boot / UEFI 設定、Spark Stacking クラスタ、 DGX OS / NGC / container runtime ソフトウェアスタック、 PXE / cloud-init プロビジョニング、fleet lifecycle 運用、 apt / fwupdmgr 更新、system recovery、PSIRT サポート、 vLLM / TensorRT-LLM / Ollama / ComfyUI / NIM / NeMo fine-tune / NCCL 等の build.nvidia.com/spark playbook、複数 Spark 接続・Tailscale・VS Code、 NVIDIA Developer Forums 由来の known issues / troubleshooting。
Claude API (platform.claude.com) の Messages API リファレンス。 streaming (SSE), thinking (adaptive) / effort, prompt caching, context editing, compaction, structured outputs, Message Batches, token counting, vision / PDF, Files API, citations, embeddings (Voyage AI)。 errors, rate limits, beta headers, Amazon Bedrock / Vertex AI / Foundry 経由アクセスを含む。
The perception-by-culture lens for psycho-logic — establish HOW a specific region, country, or subculture reads a signal before you send it, because perception is culturally coded and the same move can mean the opposite elsewhere. Use when adapting a product, price, message, or campaign to a new market; when the user asks 'will this work in [country/region]', 'why does this land in X but flop in Y', 'how do people here perceive Z', 'how do we localise/differentiate by region', or is about to copy a US/global playbook into another market. Covers the cultural dimensions that move Sutherland's levers — uncertainty avoidance, individualism/collectivism, status/power distance, high- vs low-context communication, mental-accounting norms, trust locus, and taboo/sacredness — and how each rewires reframing, costly-signaling, and experience-design. Inspired by Rory Sutherland's *Alchemy*. Routed to from psycho-logic; pair with market-recon for live local data. 日本語・中文の相談(「この地域で通用する?」「适合本地市场吗?」)にも使う。
The live fieldwork layer for psycho-logic — go look at the actual target market NOW instead of reasoning from your training-data stereotype of it. Use when a psycho-logic move needs grounding in a specific place: the user asks 'what do competitors in [region/country] actually do', 'what's the real price band / norm here', 'how do local leaders position themselves', 'research this market before we localise', 'what signals trust to buyers in X', or is about to launch/adapt in a market you haven't studied. Runs structured web research in the local language — local competitors and their signals, price bands, category conventions, review/trust sources, local terminology, taboos and regulations — and synthesises a compact perception profile the four moves consume. Inspired by Rory Sutherland's *Alchemy*. Routed to from psycho-logic; pair with cultural-context (the lens that tells you what to look for). 日本語・中文の相談(「現地の実態を調べて」「调研当地市场」)にも使う。
Analyzes single-cell pooled CRISPR screens (Perturb-seq, CROP-seq, Perturb-CITE-seq, ECCITE-seq, multiome) where each cell carries an sgRNA and a scRNA-seq / surface-protein / chromatin readout. Covers experimental design (direct-capture Perturb-seq Dixit 2016 vs CROP-seq 3'UTR-barcoded Datlinger 2017 vs ECCITE-seq vs Multiome), MOI for sgRNA assignment, escaper-cell filtering (Mixscape, Papalexi 2021), SCEPTRE NB GLM + permutation for low-MOI (Barry 2024 Genome Biol 25:124), the Pertpy framework, factor decomposition, genome-scale Perturb-seq (Replogle 2022 Cell, 2.5M cells), and per-perturbation single-cell DE. Use when running a single-cell CRISPR screen, choosing direct-capture vs CROP-seq architecture, filtering escaper cells, performing single-cell DE, integrating Perturb-seq with pathway analysis, scaling to GW CRISPRi via Replogle protocol, or analyzing multi-omics screens.
日本語の概要は準備中です。原文の説明を表示しています。
Preprocess CLIP-seq reads (eCLIP, iCLIP, iCLIP2, iCLIP3, irCLIP, PAR-CLIP, FLASH) with protocol-specific UMI extraction, adapter trimming, length filtering, and post-alignment PCR-duplicate collapse. Use when raw CLIP FASTQ must be turned into deduplicated, crosslink-preserving BAM input for peak calling; choosing between two-pass and single-pass adapter trimming; deciding minimum read length; or mapping UMI patterns to specific eCLIP/iCLIP/iCLIP2/iCLIP3 library preps.
日本語の概要は準備中です。原文の説明を表示しています。
Use when the project follows hexagonal (ports & adapters) architecture. Prevents domain code from depending on Spring or JPA. Use when you see packages like domain/, application/, infrastructure/, or adapters/ in the project structure.
日本語の概要は準備中です。原文の説明を表示しています。
When the user wants to optimize any form that is NOT signup/registration — including lead capture forms, contact forms, demo request forms, application forms, survey forms, or checkout forms. Also use when the user mentions "form optimization," "lead form conversions," "form friction," "form fields," "form completion rate," "contact form," "nobody fills out our form," "form abandonment," "too many fields," "demo request form," or "lead form isn't converting." Use this for any non-signup form that captures information. For signup/registration forms, see signup-flow-cro. For popups containing forms, see popup-cro.
日本語の概要は準備中です。原文の説明を表示しています。
BROWSER REVIEW QA SKILL — Use the built-in browser/headless browser (puppeteer-core) to open a browser-runnable Cocos preview, switch preview targets, capture screenshots, and compare them with reference images. USE FOR: screen-driven QA only when the user has already prepared a Browser Review environment that can run in the browser (`http://localhost:7456`, LoadingScene/preview host/preview target wiring ready). DO NOT USE FOR: current Cocos Editor window screenshots, Editor Preview capture, compile errors, or pure log analysis. If the Browser Review environment is not ready, stop and remind the user to prepare it first.
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user asks to switch AI role/mode/persona or uses role-trigger words such as Captain, Coordinator, 寫文章, 寫文章模式, 文章模式, 技術文章, 部落格, 出版, 預覽. Routes the request to Project Captain, Publishing Director, or Article Writing Mode, loads the matching keep memory when available, and applies the role's workflow without excessive roleplay.
日本語の概要は準備中です。原文の説明を表示しています。
Captain 派工規範與決策手冊。當 AI 進入隊長模式或進行派工/派任務語境時,遵照這套標準,產出可供人類直接轉貼、高度結構化、符合 token 經濟且能動態適應可用 Roster 的派工單。
日本語の概要は準備中です。原文の説明を表示しています。