Reviews Rust macro code for hygiene issues, fragment misuse, compile-time impact, and procedural macro patterns. Use when reviewing macro_rules! definitions, procedural macros, derive macros, or attribute macros.
日本語の概要は準備中です。原文の説明を表示しています。
525 件 ・ 関連度順
概要と使いどころ
Reviews Rust macro code for hygiene issues, fragment misuse, compile-time impact, and procedural macro patterns. Use when reviewing macro_rules! definitions, procedural macros, derive macros, or attribute macros.
日本語の概要は準備中です。原文の説明を表示しています。
RIPDPI Compose performance: stability annotations, compiler metrics, LazyColumn key/contentType, per-screen recomposition notes. Use when diagnosing recomposition, stability, or list performance here.
日本語の概要は準備中です。原文の説明を表示しています。
Use only when the user explicitly invokes /loop-graph or names this skill. Compiles a custom loop-graph run. Do not use unless named. Existing runtime nodes are self-contained.
日本語の概要は準備中です。原文の説明を表示しています。
Build and maintain a persistent, LLM-maintained markdown wiki following Andrej Karpathy's LLM Wiki pattern — the agent incrementally compiles raw sources into an interlinked knowledge base instead of re-deriving answers from scratch. Use this whenever the user wants to ingest a source (an article, paper, transcript, chapter, meeting notes), file knowledge or conversation findings into the wiki, query the accumulated knowledge base, lint or health-check the wiki, or mentions "the wiki", "knowledge base", "ingest this", "file this", "what do we know about X", or accumulating notes on a topic over time — even if they don't say "LLM Wiki" explicitly.
日本語の概要は準備中です。原文の説明を表示しています。
This skill should be used when the user asks to "validate Perl script", "check Perl syntax", "verify Perl code", "/perl-validate", or mentions script validation, compile check, security review, or best practice compliance for Perl code.
日本語の概要は準備中です。原文の説明を表示しています。
Build responsive email templates using MJML markup language. Compiles to cross-client HTML that works in Outlook, Gmail, and Apple Mail. Includes template renderer, layout patterns, and variable substitution.
日本語の概要は準備中です。原文の説明を表示しています。
Plans a research project as a decision map that persists across sessions, resolving one ticket per session until the design is defensible and pre-registerable. The map lives as Markdown in the repository, literature sweeps run as parallel research tickets, and the resolved map compiles into a pre-analysis plan. Use at project start, when a design has more open decisions than one conversation can hold, or when planning restarts each session. Not for executing analyses or writing the paper.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a repository has a valuable agentic workflow, prompt chain, playbook, command, or runbook that should become a portable ChatGPT/Codex Skill without losing its real decision logic.
日本語の概要は準備中です。原文の説明を表示しています。
Extract visual identity from screenshots (primary) or website URL (fallback) and compile into a DESIGN.md-format brand kit — YAML token frontmatter (colors, typography, rounded, spacing, components) + 8 ordered prose sections. The YAML tokens are machine-authoritative; downstream visual skills consume them directly. Writes to marketing/brand/brand-kit.md. Triggers - "brand kit", "brand identity", "visual identity", "design tokens", "extract brand", "DESIGN.md"
日本語の概要は準備中です。原文の説明を表示しています。
Super-skill for developing Haskell projects with cabal nix-style builds. Orchestrates HLS diagnostics, Haddock, Hoogle, source formatting, and cabal-gild into one workflow. Use when writing, editing, refactoring, building, typechecking, fixing compiler errors, renaming symbols, looking up APIs, or changing dependencies in Haskell projects. Treat cabal.project as the source of truth, prefer HLS before full builds, and prefer local docs over remote lookup.
日本語の概要は準備中です。原文の説明を表示しています。
Review touched subsystems for layering, crate boundaries, single-source-of-truth rules, registry-driven behavior, and compiler/runtime separation. Use when a broad review needs a dedicated architecture pass or when the user asks for architectural review specifically.
日本語の概要は準備中です。原文の説明を表示しています。
Run and write tests for the Incan compiler. Use when the user asks to test changes, add tests, run the test suite, verify a feature, or says /test. Guides test selection, provides correct patterns, and runs the right commands.
日本語の概要は準備中です。原文の説明を表示しています。
Use whenever creating, renaming, or editing any file under docs/ in this repo, or when asked to compile/build the book PDF. Enforces the exact .mdx frontmatter, ID scheme, and heading-depth rules required by the go-pretty-pdf tool (https://github.com/sazardev/go-pretty-pdf) so the whole book keeps compiling.
日本語の概要は準備中です。原文の説明を表示しています。
Author low-poly WoW-style 3D characters — mesh, skeleton, and animations — in the WAM text language, compiled to glTF plus multi-view PNG renders. Use when the user wants to create or edit a stylized/low-poly 3D character, creature, or prop with a rig and animations, supplies one or more reference images or views, mentions WAM or .wam files, or asks for "WoW-style" / game-ready models.
日本語の概要は準備中です。原文の説明を表示しています。
Author, compile, inspect, and revise WAM low-poly 3D characters, creatures, props, rigs, and animations with ChatGPT Codex. Use for WAM or .wam requests, WoW-style or game-ready models, and one or more reference images or requested render views.
日本語の概要は準備中です。原文の説明を表示しています。
Provides reverse engineering techniques. Use when the main job is to understand how a compiled, obfuscated, packed, or virtualized target works before exploiting or solving it, including binaries, APKs, WASM, firmware, custom VMs, bytecode, game clients, malware-like loaders, and anti-debug or anti-analysis logic. Do not use it when the vulnerability is already understood and the remaining task is exploitation; use pwn instead. Do not use it for pure web workflows, log or disk forensics, or standalone crypto problems unless reversing the implementation is the real blocker.
日本語の概要は準備中です。原文の説明を表示しています。
Benchmark clean and incremental Xcode builds, surface compile and configuration hotspots, and produce an approval-first optimization plan before changing project files.
日本語の概要は準備中です。原文の説明を表示しています。
Build a tdmcp TouchDesigner-bridge vertical slice the house way — promote an op from /api/exec to a first-class REST endpoint (e.g. POST /api/connect, GET /api/logs, node_detail flags), add its typed method in src/td-client/touchDesignerClient.ts, its Zod envelope in src/td-client/validators.ts, rewire the tool(s) to prefer the endpoint with an exec fallback, and write py_compile + td/tests unittest + offline msw client tests. Use when adding/changing a bridge REST endpoint, editing td/, extending node_detail/get_bridge_logs, promoting connect/disconnect/param-modes/DAT-text off exec, or doing any exec→REST work — especially the td-depth bridge-robustness backlog. Honors probe-live discipline when TouchDesigner is offline.
日本語の概要は準備中です。原文の説明を表示しています。
Build Cadmus on Linux and macOS hosts using xtask. Use when asked how to compile, test, lint, or run the project locally.
日本語の概要は準備中です。原文の説明を表示しています。
Compiler-level code intelligence via native LSP — definitions, references, types, call hierarchies, and diagnostics.
日本語の概要は準備中です。原文の説明を表示しています。
Master binary analysis patterns including disassembly, decompilation, control flow analysis, and code pattern recognition. Use when analyzing executables, understanding compiled code, or performing static analysis on binaries.
日本語の概要は準備中です。原文の説明を表示しています。
Phase 5 of 5 — triage-first review orchestrator; dispatches up to 17 domain checks in parallel and compiles one report. Use only when the user asks to run Phase 5 or review a PR, branch, or set of changes — never trigger automatically after writing code.
日本語の概要は準備中です。原文の説明を表示しています。
Mobile (Android) app recon and analysis — decompile APK, extract secrets, find hardcoded endpoints, exposed Firebase / AWS / API keys, deeplink abuse, intent vulnerabilities, exported components, WebView XSS, MobSF static analysis. Use when target's scope includes Android apps (.apk).
日本語の概要は準備中です。原文の説明を表示しています。
Orchestrate the full PaperOrchestra (Song et al., 2026, arXiv:2604.05018) five-agent pipeline to turn unstructured research materials (idea, experimental log, LaTeX template, conference guidelines, optional figures) into a submission-ready LaTeX manuscript and compiled PDF. TRIGGER when the user asks to "write a paper from my experiments", "turn this idea and these results into a paper", "generate a conference submission", "run paper-orchestra on X", or otherwise wants the end-to-end paper-writing pipeline. Coordinates the outline-agent, plotting-agent, literature-review-agent, section-writing-agent, and content-refinement-agent skills.
日本語の概要は準備中です。原文の説明を表示しています。