「quest」の検索結果

Expert en revue de code (PR reviews, patterns, anti-patterns, security, performance, readability)

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

Activate this skill when BenchmarkDotNet (BDN) is involved in the task — creating, running, configuring, or reviewing BDN benchmarks. Also activate when microbenchmarking .NET code would be useful and BenchmarkDotNet is the likely tool. Consider activating when answering a .NET performance question requires measurement and BenchmarkDotNet may be needed. Covers microbenchmark design, BDN configuration and project setup, how to run BDN microbenchmarks efficiently and effectively, and using BDN for side-by-side performance comparisons. Do NOT use for profiling/tracing .NET code (dotnet-trace, PerfView), production telemetry, or load/stress testing (Crank, k6).

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

Every product will be AI-powered. The question is whether you'll build it right or ship a demo that falls apart in production.

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

Autonomous coding agent. Delegate any task that involves understanding, writing, or running code — from a GitHub issue, a bug report, or a user request. It explores, implements, and verifies on its own.

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

Helps an AI assistant work with the Miraheze wiki farm — writing wiki requests that get approved, navigating ManageWiki, doing common how-to tasks (templates, skins, permissions, custom domains, backups), writing regex for MediaWiki search-and-replace, AND writing actual article and page content for Miraheze-hosted wikis. Miraheze does NOT ban generative AI; AI-written content is permitted (subject to per-wiki rules). MADE BY SQERSTERS

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

Use when the user is unsure which skill to use or where to start. Interviews the user with targeted questions and recommends the best skill(s) from the installed library for their goal.

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

Universal deep research agent team. 13-agent pipeline for rigorous academic research on any topic. 7 modes: full research, quick brief, paper review, lit-review, fact-check, Socratic guided research dialogue, and systematic review with optional meta-analysis. Covers research question formulation, Socratic mentoring, methodology design, systematic literature search, source verification, cross-source synthesis, risk of bias assessment, meta-analysis, APA 7.0 report compilation, editorial review, devil's advocate challenges, ethics review, and post-research literature monitoring. Triggers on: research, deep research, literature review, systematic review, meta-analysis, PRISMA, evidence synthesis, fact-check, guide my research, help me think through, 研究, 深度研究, 文獻回顧, 文獻探討, 系統性回顧, 後設分析, 事實查核, 引導我的研究, 幫我釐清, 幫我想想, 我不確定要研究什麼, 研究方向, 研究主題.

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

Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill.

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

Create or update a pull request from current branch to origin main with auto-generated title and description

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

Defend a design decision to skeptical stakeholders with structure and evidence. Use when presenting design work, writing design documentation, or pushing back on requests to change something.

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

Run taste-informed design reviews using Observation > Principle > Question. Use when facilitating design critiques, improving feedback quality on a team, or building a shared vocabulary for quality.

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

Write a structured design review that someone can act on without follow-up questions. Use when giving async design feedback, writing portfolio case studies, or documenting design decisions.

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

Investigate a question against high-trust primary sources and capture the findings as a Markdown file in the repo. Use when the user wants a topic researched, docs or API facts gathered, or reading legwork delegated to a background agent.

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

Develops an implementation plan ready for wave-orchestration to execute. Takes the user's goal or rough plan as input, mines the codebase for facts, grills the user one question at a time for the decisions, drafts the planning/ artifacts (task DAG, wave table, worker prompt template, state file), then reviews its own plan on two axes before seeking approval. Use when the user wants to turn a feature idea, master plan, or backlog into a wave-orchestration execution plan.

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

Supervise other Claude Code sessions on this machine: roster, status requests, GO board, idle notices. Generated from plugin-commands.json; invoke as $bdb-aos:mastersession.

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

Adds new visual examples to the tdmcp prompt cookbook documentation — both the English and Portuguese versions. Use when asked to: add more cookbook examples, create visual examples for the docs, show more surprising things you can do, add entries to the prompt cookbook, expand the cookbook, or any request to extend the cookbook with new prompts and results. Runs a 3-phase pipeline: curate candidates → write EN → write PT.

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

Build a throwaway prototype to answer a design question, as UI variations or a state-model walkthrough. Use when the user types /prototype, wants to sanity-check whether a state model or logic feels right, wants to explore what a UI should look like, or as the prototype step of the web design flow with brainstorm or grill before the final plan goes to plan-canvas (annotate the running prototype with the plan-canvas annotation tool).

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

Create 3D scenes, interactive experiences, and visual effects using Three.js. Use when user requests 3D graphics, WebGL experiences, 3D visualizations, animations, or interactive 3D elements.

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

Use when completing tasks, implementing major features, or before merging to verify work meets requirements

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

Use when the user just says "plan", "planen" or "roadmap": offer a template via aos-plan-canvas templates. Open plans and HTML artifacts in a local browser canvas where the human annotates elements, chats, and approves or requests changes without leaving the page. Use for planning, whenever a user says "plan", "roadmap", "visualize the plan", "review the plan" or /plan-canvas, right after a brainstorm or grill interview has produced a plan, and whenever any skill's artifact (plan, design, comparison, report, diagram) can be reviewed visually instead of with typed feedback.

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

Write JavaScript code in n8n Code nodes. Use when writing JavaScript in n8n, using $input/$json/$node syntax, making HTTP requests with $helpers, working with dates using DateTime, troubleshooting Code node errors, or choosing between Code node modes.

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

Use the `gh` CLI for issues, pull requests, Actions runs, and GitHub API queries.

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

Experimental workflow for auditing recurring feedback, telemetry, errors, and brittle delivery paths to find systemic fixes. Use for periodic or requested cross-source lookbacks, not routine single-item intake.

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

Experimental workflow for summarizing work that still needs human judgment across configured pull requests, issues, feedback, errors, and delivery signals. Use for a human decision queue or bounded review.

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