5,365 件 ・ 関連度順
概要と使いどころ
Generates professional infographics with 21 layout types and 20 visual styles. Analyzes content, recommends layout×style combinations, and generates publication-ready infographics. Use when user asks to create "infographic", "信息图", "visual summary", "可视化", or "高密度信息大图".
日本語の概要は準備中です。原文の説明を表示しています。
Take a markdown file of raw material and shape it into an article through a conversational session — drafting candidate openings, growing the piece paragraph by paragraph, arguing about format (lists, tables, callouts, quotes) at each step. Use when the user has a pile of notes, fragments, or a rough draft and wants help turning it into something publishable.
日本語の概要は準備中です。原文の説明を表示しています。
Turn the current conversation context into a PRD and publish it to the project issue tracker. Use when user wants to create a PRD from the current context.
日本語の概要は準備中です。原文の説明を表示しています。
Keeps README badge + inline counts in sync with the real number of skills, agents, graph nodes/edges, communities, converted pipelines, and test inventory. Runs automatically on every commit via a git pre-commit hook. Use when the README drifts from reality or before publishing a release.
日本語の概要は準備中です。原文の説明を表示しています。
Establishes configuration ownership, validation, secret boundaries and environment isolation; not credential identity policy or live deployment.
日本語の概要は準備中です。原文の説明を表示しています。
Commits, pushes and remotely verifies authorized repository changes; does not create releases.
日本語の概要は準備中です。原文の説明を表示しています。
Implements one scoped product feature or fix using existing contracts; not upgrades, performance tuning or establishing cross-cutting technical foundations.
日本語の概要は準備中です。原文の説明を表示しています。
Drafts or publishes authorized, fact-checked GitHub Discussions announcements; does not create releases.
日本語の概要は準備中です。原文の説明を表示しています。
Formulate coherent product strategy, synthesize opportunity frames and falsifiable hypotheses, establish non-goals and trade-offs, and bind decisions to verified strategic authority. (triggers: `product strategy decision`, `product opportunity framing`)
日本語の概要は準備中です。原文の説明を表示しています。
Posts sanitized batches of PR review comments or replies through configured review tooling. Use after review-ticket when findings are approved for publication.
日本語の概要は準備中です。原文の説明を表示しています。
Audits PR diffs for architecture boundary violations, design simplicity, dependency drift, and established-pattern mismatches. Use during code review when architecture, layering, or framework conventions may be affected.
日本語の概要は準備中です。原文の説明を表示しています。
Select and implement SSG, SSR, ISR, Streaming, or Partial Prerendering strategies in Next.js App Router. Use when choosing a rendering mode for a page, configuring generateStaticParams, or enabling PPR.
日本語の概要は準備中です。原文の説明を表示しています。
Automate Swagger/OpenAPI documentation and standardize API response schemas in NestJS. Use when generating OpenAPI specs, documenting paginated or generic responses, configuring the Nest CLI Swagger plugin, or publishing versioned API docs.
日本語の概要は準備中です。原文の説明を表示しています。
Infer the requesting operator's technical fluency from message content (never ask directly) and adapt register — business, hybrid, or technical — across SDLC workflow output. Use when starting sdlc, brainstorm-feature, plan-feature, verify-work, publish-notes, or session-report, or whenever a request's phrasing signals a non-technical or cross-stack operator.
日本語の概要は準備中です。原文の説明を表示しています。
Migrate a Jetpack Compose app to edge-to-edge display and fix system bar inset issues. Use when UI components are obscured by navigation/status bars, fixing IME insets, or enabling edge-to-edge for SDK 35+.
日本語の概要は準備中です。原文の説明を表示しています。
Verify a rewrite slice against its obligations: preflight, capture fresh test evidence, audit translationese and parity, update the ledger. Use after /phx:work finishes a rewrite slice, or before claiming parity.
日本語の概要は準備中です。原文の説明を表示しています。
End-to-end academic paper writing workflow. Takes a research repository and produces a publication-ready LaTeX manuscript for top ML/AI conferences (NeurIPS, ICML, ICLR, ACL, AAAI, COLM). Covers repo understanding, structure planning, section drafting, citation management, anti-AI polishing, and conference formatting. Triggers on "write paper", "draft paper", "scholar writing", "paper writing workflow".
日本語の概要は準備中です。原文の説明を表示しています。
Systematic experimental results analysis workflow for ML/AI research papers. Connects experimental data to publication-ready Results sections with statistical validation, visualizations, and quality checks. Triggers on "analyze experimental results", "generate results section", "statistical analysis of experiments", "compare model performance", "create results visualization".
日本語の概要は準備中です。原文の説明を表示しています。
Converts mastered audio to sheet music and creates printable songbooks. Use after mastering when the user wants sheet music or a songbook for their album.
日本語の概要は準備中です。原文の説明を表示しています。
Use when someone asks "does this sound AI?", "check if this is AI-written", "what gives this away as AI", "run ai-check on this", or "score this text". Also use when reviewing a draft for AI tells before publishing, or when a piece of text reads as suspiciously polished, generic, or pattern-y and the user wants a forensic breakdown of why.
日本語の概要は準備中です。原文の説明を表示しています。
Turn one confirmed security finding into a disclosure-ready GitHub advisory with root cause, proof of concept, impact, and source evidence. Use for reporting an established vulnerability, not discovering or validating one.
日本語の概要は準備中です。原文の説明を表示しています。
Build and publish a Gradio Hugging Face Space for a user-provided image or video LoRA, including pipeline selection and model-card settings. Use for LoRA demos; use huggingface-spaces for general Space work.
日本語の概要は準備中です。原文の説明を表示しています。
Run evaluations for Hugging Face Hub models using inspect-ai and lighteval on local hardware. Use for backend selection, local GPU evals, and choosing between vLLM / Transformers / accelerate. Not for HF Jobs orchestration, model-card PRs, .eval_results publication, or community-evals automation.
日本語の概要は準備中です。原文の説明を表示しています。
Synthesises the current conversation context into a Product Requirements Document and publishes it to GitHub (as a comment on a referenced issue, or a new issue). Synthesises from context; does not interview. TRIGGER when: the conversation has produced enough understanding of a feature and the user wants it captured as a PRD. DO NOT TRIGGER when: a single small issue is enough → creating-issues; the idea has not been stress-tested yet → grilling-ideas first; bug reports.
日本語の概要は準備中です。原文の説明を表示しています。