714 件 ・ 関連度順
概要と使いどころ
PHP type juggling and weak comparison (`==`) bypass. Use when authentication, HMAC/signature checks, or token validation uses loose equality, numeric coercion, or hash comparisons without strict types — common in legacy PHP and CTF-style code paths.
日本語の概要は準備中です。原文の説明を表示しています。
Mobile SSL pinning bypass playbook. Use when intercepting HTTPS traffic from mobile applications that implement certificate pinning, public key pinning, or SPKI hash pinning on Android and iOS, including React Native, Flutter, and Xamarin frameworks.
日本語の概要は準備中です。原文の説明を表示しています。
Create engaging Xiaohongshu (RED/小红书) content including titles, body text, hashtags, and image style recommendations. Supports multiple content types such as product reviews, tutorials, lifestyle sharing, and shopping guides with platform-specific optimization.
日本語の概要は準備中です。原文の説明を表示しています。
使用SHA-256内容哈希缓存昂贵的文件处理结果——路径无关、自动失效、服务层分离。
日本語の概要は準備中です。原文の説明を表示しています。
使用 SHA-256 内容哈希缓存高昂的文件处理结果 —— 与路径无关、自动失效且服务层分离。
日本語の概要は準備中です。原文の説明を表示しています。
Replay an LLM inference request trace (Mooncake / vLLM / SGLang hash_ids format) against a block-level KV prefix cache and compute hit statistics. Use when given a request trace plus cache configuration and asked for hit rate, hit tokens, or final cache contents. Covers the longest-contiguous-prefix semantics that distinguishes KV prefix caching from full-prompt prompt caching, the policy-specific residency and eviction rules (LRU, LFU, S3FIFO), and the partial-last-block accounting rule.
日本語の概要は準備中です。原文の説明を表示しています。
Implements authentication, authorization, encryption, secrets management, and security hardening patterns. Use when designing auth flows, managing secrets, configuring CORS, implementing rate limiting, or when asked about JWT, OAuth, password hashing, API keys, RBAC, or security best practices.
日本語の概要は準備中です。原文の説明を表示しています。
Puts a built website live on a free HTTPS link, or your own .com with no DNS. Use when the user says "put it online", "go live", "make it live", "put this live", "publish my site", "share it with friends", "send my friends a link", "get a link", "make it public", "it only works on localhost" or "get a .com", or asks to deploy or host a site built with an AI tool (Claude Code, Cursor, Codex, Windsurf, Lovable, Bolt, v0, ChatGPT), or mentions DropTheHassle, and has not picked another host. Covers building first, CLI or MCP setup, deploying, the claim link, the live check, linking a server part the user hosts on AWS, Google Cloud, DigitalOcean or their own server with set_backend, and domain search. The agent never spends money. The human pays.
日本語の概要は準備中です。原文の説明を表示しています。
Record a decision, document existing code, or file a supplied research material. Modes: document decision (ADR, RFC, or rule), document code (spec, doc, guide, or scenario for existing behavior), document research (only when a finished report or one external material is already in hand). Use for 'we decided', 'record this decision', 'document why we chose X', 'make it our standard', 'draft an RFC', 'should we switch to Y' proposals, 'resolve the RFC', 'we accepted the proposal', 'document the auth module', 'capture how the payment system works', reference material, how-to instructions, or a user flow with examples over an existing spec. Name the type inside the subject to skip the type question. Planning a feature or an intended user journey → /archcore:plan. Checking docs against code or docs health → /archcore:review.
日本語の概要は準備中です。原文の説明を表示しています。
Translate PDF documents with BabelDOC while retaining layout, figures and formulas; supports bilingual output, custom glossaries, domain terminology and local processing with configurable translation providers. Use for translated PDFs, not merely summaries or plain text extraction.
日本語の概要は準備中です。原文の説明を表示しています。
Check that a web page you wrote or changed actually works, by opening it in a browser and driving every control on it. Use after creating or editing an HTML page, or the JavaScript or CSS that a page loads.
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user wants to pull data out of one or more PDFs (invoices, bank/credit-card statements, receipts, reports, tables) and put it into a spreadsheet. pdf_read is one of the most-used tools; this codifies the read-PDF → structure → write-Excel workflow. Powered by LMCP on macOS and Windows.
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user wants to read or search iMessage or Signal (macOS) or Microsoft Teams, Slack and WhatsApp (macOS and Windows) from the apps on their computer. Powered by LMCP.
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user wants to find, read or create files and Office documents (Word/Excel/PowerPoint/PDF) on macOS or Windows, or browse OneDrive / Google Drive. Powered by LMCP; the tools execute on the device.
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user wants to read or search Microsoft Teams or Slack on macOS or Windows, including channels and DMs. Powered by LMCP, reading the desktop apps' local data.
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user wants to read, search, summarize, draft or triage their Apple Mail / Gmail / Outlook / iCloud email in Apple Mail on macOS. Powered by LMCP's Mail tools, which are macOS-only.
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user wants to deal with their inbox — find what needs a response, draft replies, and turn emails into calendar events or reminders. Captures the common email→read→reply→schedule workflow on macOS (Apple Mail, Calendar, Reminders). Powered by LMCP.
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user wants to check their calendar, find availability, or create/update/delete events in Apple Calendar on macOS. Powered by LMCP's Calendar tools, which are macOS-only.
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user asks "what's on my plate today", "catch me up", "morning brief", or wants a summary of their day across calendar, reminders and email. The single most common multi-step automation. Powered by LMCP on macOS and Windows.
日本語の概要は準備中です。原文の説明を表示しています。
Coordinate multi-step work across services the user has authorized through Aident Loadout, using live action schemas, connection checks, cost preflight, and explicit approval for side effects.
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user asks what they are not seeing, what they forgot, what could go wrong, or what an expert would say about a plan, decision, document, code change, or setup they already have. Triggers: "what am I missing", "what don't I know", "poke holes in this", "what would an expert ask", "что я упускаю", "что я не вижу", or /clueless-blindspots. One-shot review; does not change the always-on level.
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user explicitly cannot review the output in the current domain, says they do not understand it or will copy-paste without checking, or requests clueless mode. Examples: "I know nothing about this", "не разбираюсь", "сделай за меня". Brevity, "make it nice", and delegation alone do not establish a knowledge gap.
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user asks how clueless works, what its commands or levels are, or types /clueless-help.
日本語の概要は準備中です。原文の説明を表示しています。
上下文生命周期管理总览：四层记忆架构（L0-L3）、任务阶段感知、 渐进压缩策略、按需召回与四分区预算模型。
日本語の概要は準備中です。原文の説明を表示しています。