3,792 件 ・ 関連度順
概要と使いどころ
Analyzes provided content for quality, E-E-A-T signals, and SEO best practices. Scores content and provides improvement recommendations based on established guidelines. Use PROACTIVELY for content review.
日本語の概要は準備中です。原文の説明を表示しています。
Develop native iOS applications with Swift/SwiftUI. Masters iOS 18, SwiftUI, UIKit integration, Core Data, networking, and App Store optimization. Use PROACTIVELY for iOS-specific features, App Store optimization, or native iOS development.
日本語の概要は準備中です。原文の説明を表示しています。
Master C#/.NET backend development patterns for building robust APIs, MCP servers, and enterprise applications. Covers async/await, dependency injection, Entity Framework Core, Dapper, configuration, caching, and testing with xUnit. Use when developing .NET backends, reviewing C# code, or designing API architectures.
日本語の概要は準備中です。原文の説明を表示しています。
Expert .NET backend architect specializing in C#, ASP.NET Core, Entity Framework, Dapper, and enterprise application patterns. Masters async/await, dependency injection, caching strategies, and performance optimization. Use PROACTIVELY for .NET API development, code review, or architecture decisions.
日本語の概要は準備中です。原文の説明を表示しています。
郑希观点库——基于易方达基金经理郑希 2012–2026 年全部公开观点原文语料，外加从语料蒸馏、有本人原话佐证的郑希投资方法的可溯源 research skill。能做： (1) 溯源问答——他怎么看 AI算力/光通信/新能源/半导体/ROE 等，引用其原话作答； (2) 讲解他的投资方法/框架/选股逻辑；(3) 前瞻应用——用他的方法分析当下任意主题/行业/个股，语料没谈过也能据框架推演； (4) 风格化点评——用他季报/手记的口吻写市场点评、季度展望； (5) 言行对照——用他全部基金真实数据（季度持仓/净值/业绩/规模/任职回报）核对"说的"与"买的"，或答他的业绩/重仓/规模； (6) 全市场查询对比——内置约 2.7 万只基金列表，按需抓任意基金真实数据做查询或与郑希对比； (7) 郑希框架评分——给一只基金按他的方法打分（多像郑希会买的）。 When the user mentions 郑希/易方达郑希/zhengxi, asks his view on a sector/stock/theme, his 投资方法/框架/选股/风格/持仓/业绩/净值/规模, wants to apply his approach, a commentary 用郑希口吻, to check words vs holdings, or to look up/compare/score ANY China mutual fund (任意基金/某基金经理/同类对比/给基金打分)——use this skill, even if they don't say "skill", even if the topic isn't in his corpus (fall back to his method). 引用忠于原文、不杜撰；推演与原话区分。研究学习辅助，非投资建议。
日本語の概要は準備中です。原文の説明を表示しています。
Write an Instagram Reel from a raw idea - hook options off 26 formulas, the spoken script, the on-screen text, and a timed beat sheet - in the user's own voice and scored before they shoot it. Use whenever the user wants a Reel, a short-form video script, a hook, a voiceover, "make a reel about X", "what should I say in this video", or is about to record and does not have the first line yet.
日本語の概要は準備中です。原文の説明を表示しています。
Strip the machine fingerprint out of any draft - em dashes, AI slop words, invisible watermark characters - and score it against a five-check detection panel before it goes out. Use whenever text needs to sound human, when the user says humanize, "does this sound like AI", "remove the em dashes", "de-slop this", "this sounds like ChatGPT", or before any caption, script, comment, reply or DM is shown to the user.
日本語の概要は準備中です。原文の説明を表示しています。
Writing a Succession-style ensemble series (继承之战群像剧写法) — distilled from Jesse Armstrong's complete shooting scripts for all four seasons, 39 episodes (Faber 2023), with his introductions and footnotes, plus Frank Rich's and Lucy Prebble's essays on the writers' room. Covers the invisible-act three-test for scripts with no ACT marks, container episodes built on a ceremony's running order, pressure chambers, one core question per episode, finales with fewer and longer scenes, the absent protagonist at the climax, humiliation passed downward, stage directions carrying subtext and "maybe", reversals turned on one word, writing long, alts, the mega-chart, and engineering an ending once the plot engine loses pressure. Use when the user wants a dynastic family drama, a media-power ensemble, a wedding/funeral/summit set piece, a streaming hour with no act breaks, a finale that redraws alliances, or asks how to "Succession-ize" a script or kill a lead mid-season.
日本語の概要は準備中です。原文の説明を表示しています。
Use when someone asks to audit their AIOS, score the Four Cs, find stale paths or unlinked projects, compare AGENTS.md and CLAUDE.md, check Claude/Codex skill compatibility, or assess migration readiness. Automatically saves dated reports and tracks evidence-backed improvements across runs.
日本語の概要は準備中です。原文の説明を表示しています。
传播心理解码。给定一段内容，用 5 个经典传播学理论解码它为什么能引起受众共鸣，分析受众情绪底层和有效立场，输出聊天室的讨论方向。 触发方式：/dbs-spread、「传播心理解码」、「为什么这个能火」、「受众想听什么」、「这个内容打中了什么情绪」 Transmission psychology decoder. Given a piece of content, analyze the psychological mechanism that makes it resonate, identify the emotional core and effective stance, and output direction for chatroom discussion. Trigger: /dbs-spread, "why does this resonate", "what emotion does this hit", "decode this content"
日本語の概要は準備中です。原文の説明を表示しています。
Use when creating Codex, Claude Code, Gemini CLI, Cursor, or AGENTS.md runtime adapters from one canonical agent core. Use whenever a generated repo needs multiple AI runtimes without duplicating instructions.
日本語の概要は準備中です。原文の説明を表示しています。
Use when designing how one canonical agent core runs across Codex, Claude Code, Gemini CLI, Cursor, and AGENTS.md-compatible tools.
日本語の概要は準備中です。原文の説明を表示しています。
Use when creating Codex, Claude Code, Antigravity, Cursor, or AGENTS.md runtime adapters from one canonical agent core. Use whenever a generated repo needs multiple AI runtimes without duplicating instructions.
日本語の概要は準備中です。原文の説明を表示しています。
Use when creating a single Agentlas agent, creating a multi-agent team, or packaging an existing local/external agent into Agentlas architecture. Make sure to use this for /meta-agent requests.
日本語の概要は準備中です。原文の説明を表示しています。
Use when designing how one canonical agent core runs across Codex, Claude Code, Antigravity, Cursor, and AGENTS.md-compatible tools.
日本語の概要は準備中です。原文の説明を表示しています。
Debug Azure production issues on Azure using AppLens, Azure Monitor, resource health, and safe triage. WHEN: debug production issues, troubleshoot app service, app service high CPU, app service deployment failure, troubleshoot container apps, container app 503 or target port mismatch, troubleshoot functions, function telemetry missing or stopped after a config/connection-string change, troubleshoot AKS, VM RDP, Linux SSH, VM black screen, can't connect to VM, reset VM password, NSG or firewall blocking, kubectl cannot connect, kube-system/CoreDNS failures, pod pending, crashloop, node not ready, upgrade failures, analyze logs, KQL, insights, image pull failures, cold start issues, health probe failures, resource health, root cause of errors, troubleshoot event hubs, troubleshoot service bus, messaging SDK error, AMQP connection failure, message lock lost, lock renewal during long-running processing, service bus dead letter.
日本語の概要は準備中です。原文の説明を表示しています。
Write a YouTube video script from a raw idea - hook options off 21 formulas, scored, then the full spoken script with the retention beats marked. Use whenever the user wants a video script, a hook, an opening line, "what should I say", "write my next video", or is about to record and does not have the first fifteen seconds yet.
日本語の概要は準備中です。原文の説明を表示しています。
Use Phaser 4 Arcade Physics: enable the world, give sprites bodies, set velocity/acceleration/gravity, and resolve collisions with colliders, overlaps, groups, and world bounds. Use when a Phaser game needs movement or collisions — when the user mentions Arcade Physics, this.physics, setVelocity, collider, overlap, gravity, onFloor, or a platformer/top-down controller. For game config, scenes, and the loader use phaser-core.
日本語の概要は準備中です。原文の説明を表示しています。
Set up and debug a Phaser 4 game: the Game config, the Scene lifecycle (init/preload/create/update), the asset loader, cameras, and cross-scene communication. Use when building or debugging a Phaser game — when the user mentions Phaser, Phaser.Game, Phaser.Scene, preload/create/update, this.load, this.add, or scene transitions. For Arcade Physics movement/collisions use phaser-arcade-physics.
日本語の概要は準備中です。原文の説明を表示しています。
Structure and debug a LÖVE (Love2D) game in Lua: the love.load/update/draw loop, delta-time movement, input, and screen states. Use when building a LÖVE 11.x game (main.lua, conf.lua, .love).
日本語の概要は準備中です。原文の説明を表示しています。
Structure a pygame (pygame-ce) game in Python: the init/event/update/draw loop, delta-time movement, Surface/Rect blitting, keyboard/mouse input, and Sprite/Group management with collision. Use when building or debugging a pygame game — when the user mentions pygame, pygame-ce, the game loop, blit, Surface, Rect, sprite groups, or clock.tick. Targets pygame-ce.
日本語の概要は準備中です。原文の説明を表示しています。
Score whether a news event is worth newsjacking, or whether a user's pitch idea is actually newsworthy to journalists. Uses calibrated anchors, hard anti-inflation rules, standing checks, timing windows, and brand-safety kill switches.
日本語の概要は準備中です。原文の説明を表示しています。
Run a structured Azure incident response workflow for triage, diagnosis, mitigation, and root cause analysis. Use when operations or security teams need guided incident handling for Azure service symptoms.
日本語の概要は準備中です。原文の説明を表示しています。
Create a qualitative risk register and mitigation plan using a Probability x Impact matrix. Use when a project needs structured risk identification, scoring, ownership, and response planning.
日本語の概要は準備中です。原文の説明を表示しています。