2,030 件 ・ 関連度順
概要と使いどころ
Help users build functional product prototypes from natural language or visual mocks using AI coding tools. This skill enables product leaders to bypass engineering bottlenecks and validate ideas through hands-on building.
日本語の概要は準備中です。原文の説明を表示しています。
Behavioral guardrails for Codex coding work based on common user complaints. Use when Codex is asked to implement, modify, debug, review, test, or operate on a codebase and should avoid unsafe scope expansion, stale edits, fake completion, brittle edits, shallow debugging, superficial patch-on fixes, one-off special-case code, short-term design choices that hurt maintainability, blindly following incorrect user assumptions, poor dependency choices, generic product or UI output, over-mocked tests, noisy approvals, verbose status reports, or leaking internal reasoning into project artifacts or user-facing UI.
日本語の概要は準備中です。原文の説明を表示しています。
Pre-launch and pre-commit audit for vibe coding projects. Use when asked to check whether a project is ready to ship, deploy, merge, or commit, especially for common AI-built app mistakes: broken project structure, committed secrets or cache files, environment variable hygiene, database migrations, ORM/schema drift, unsafe raw SQL, unused legacy code, dead routes/components, weak auth, missing tests, build failures, and deployment footguns.
日本語の概要は準備中です。原文の説明を表示しています。
Write, edit, or review C (and C-compatible header) code according to C coding style rules, then check and run clang-format to enforce formatting. Trigger on "write C code", "edit a .c/.h file", "review C code style", "format C code", "run clang-format", "check clang-format", "apply the C style guide".
日本語の概要は準備中です。原文の説明を表示しています。
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still an open loop, and what was just started. Use when someone asks "what happened this week", "what is still open", "what did the team finish", "give me the weekly rollup", or wants a status report over a .specstory/history corpus.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a coding task needs a concurrent checkout, unrelated dirty state blocks safe branch switching, or the user or repository explicitly requires a worktree.
日本語の概要は準備中です。原文の説明を表示しています。
Conduct a retrospective on a coding session.
日本語の概要は準備中です。原文の説明を表示しています。
Orchestrate multi-agent coding tasks via Claude DevFleet — plan projects, dispatch parallel agents in isolated worktrees, monitor progress, and read structured reports.
日本語の概要は準備中です。原文の説明を表示しています。
Coordinate coding agents through AMQ. Use for agent messages, inboxes, receipts, sessions, wake delivery, cross-project routing, managed launches, or AMQ diagnostics. Use amq-spec for collaborative design; do not use this for general message queues or single-agent work.
日本語の概要は準備中です。原文の説明を表示しています。
Use when you need the latest stable JuliaLang version number (e.g., to fill `VERSION=` in an install script) instead of hard-coding a value
日本語の概要は準備中です。原文の説明を表示しています。
Use Waggle automatically as portable, local project memory during meaningful coding work; retrieve prior decisions and constraints, then store only durable outcomes.
日本語の概要は準備中です。原文の説明を表示しています。
Talk to other coding agents on this machine (Claude Code, Codex, Copilot, Cursor, Gemini, AGY, Grok, OpenCode) through the magents MCP. Use when the user asks what another agent was working on, wants to carry on that work, send them a message, start an independent agent session, or check the shared inbox. Prefer magents MCP tools over hunting session files on disk.
日本語の概要は準備中です。原文の説明を表示しています。
Pick the right way to represent a dataset so a reader gets the finding in three seconds — a catalog of 20+ chart and diagram forms with when-to-use and failure modes, plus the encoding decisions that make any of them readable (takeaway headline, direct labels, kill the axis, highlight-and-mute, show the caveat). Style-agnostic — use with whatever palette or design system the destination already has. Use when charting survey results, benchmark data, usage metrics, or research findings for a post, brief, deck, or report, and whenever the default bar chart feels like it's burying the point.
日本語の概要は準備中です。原文の説明を表示しています。
Review generated or changed production code before it ships, using Clean Code, SOLID, DRY, KISS, YAGNI, and LLM-specific failure-mode checks in any programming language. Best used reactively after an agent writes, edits, refactors, or fixes code, before presenting, committing, or merging the result. Use when the user asks "review this PR", "is this safe to merge?", "make this cleaner", "audit this code", "refactor this", "fix this bug", or after a coding agent produced implementation code. Can also guide writing when explicitly invoked before a risky edit. Invoke it on your own initiative the moment you finish writing, editing, or refactoring non-trivial production code, before presenting or committing — don't wait to be asked. DO NOT USE for factual/conceptual questions, CI/tooling config, git workflow, running/debugging tests, pure architecture discussion, prose writing, data analysis, or test-code review (use test-guard).
日本語の概要は準備中です。原文の説明を表示しています。
Use when planning or reporting the analysis for an American Educational Research Journal (AERJ) manuscript — multilevel/HLM and growth models, IRT/measurement, quasi-experimental estimation, or qualitative coding and thematic analysis. Analysis must meet the AERA reporting standards (warrant + transparency). Strengthens analysis reporting; it does not run models for you.
日本語の概要は準備中です。原文の説明を表示しています。
Use when executing and reporting the analysis for an Administrative Science Quarterly (ASQ) manuscript — qualitative coding and data-to-theory construction, or quantitative estimation and robustness. Makes the evidence-to-theory link transparent; it does not design the study (see asq-methods).
日本語の概要は準備中です。原文の説明を表示しています。
Use when analyzing the material of an Accounting, Organizations and Society (AOS) manuscript — coding and interpreting qualitative field data, estimating experimental and survey models, or running theory-laden archival analyses, with an audit trail appropriate to each tradition. Analyzes and reports; it does not design the study (aos-methods).
日本語の概要は準備中です。原文の説明を表示しています。
Use when strengthening reproducibility evidence for an ACL paper reviewed through ACL Rolling Review, covering the Responsible NLP checklist end to end, hyperparameter and compute reporting, prompt and decoding disclosure for LLM experiments, data contamination auditing, variance across runs, and checklist-to-paper consistency.
日本語の概要は準備中です。原文の説明を表示しています。
Use when designing the study for an Accounting, Organizations and Society (AOS) manuscript — qualitative field studies (access, case logic, interviews, observation), behavioral experiments, surveys, historical/archival inquiry, or theory-laden archival designs, each with the ethics and site-anonymity groundwork done early. Designs the inquiry; it does not run the coding or estimation (aos-data-analysis).
日本語の概要は準備中です。原文の説明を表示しています。
Use when an Accounting, Organizations and Society (AOS) revise-and-resubmit arrives — planning revisions that may include recoding field data, new experimental conditions, or deepened theorizing, and drafting the point-by-point response to an interdisciplinary reviewer panel. Drafts the response; it does not run new analysis (aos-data-analysis) or the final preflight (aos-submission).
日本語の概要は準備中です。原文の説明を表示しています。
Use when systematically gathering, coding, and synthesizing a management/organization literature for an Academy of Management Annals (Annals) review — the search-and-coverage methodology and the choice of narrative vs. systematic vs. bibliometric integration. Builds the corpus and synthesis notes; it does not impose the organizing spine (amann-organizing-framework) or write prose.
日本語の概要は準備中です。原文の説明を表示しています。
Creates and inspects Fabric Activator (Reflex) alerts: rules, their data sources, conditions, and the Teams or email action they fire, plus decoding an existing ReflexEntities definition. Choose it whenever someone wants to be told, or something done, when values cross a threshold. The pipeline delivering those values is eventstream-cli.
日本語の概要は準備中です。原文の説明を表示しています。
Governs Event Schema Sets, the Fabric registries of event types and message payload schemas. Covers create, rename, update and delete of a definition, and listing, property reads or base64 decoding. Every Event Schema Set task belongs here. Ingestion pipelines are eventstream-cli.
日本語の概要は準備中です。原文の説明を表示しています。
当用户询问 AgentDock 是什么、如何使用、配置在哪里、不同平台或安装方式怎样修改配置并生效、如何重启或验证配置、如何发现并配置 Codex/Claude/Grok 等 Coding Agent 的 ACP，以及常见运行问题时使用；覆盖 macOS Desktop、Windows Desktop、Linux 服务、Docker 和直接运行二进制，不用于源码开发与贡献流程。
日本語の概要は準備中です。原文の説明を表示しています。