「status」の検索結果

Self-review, audit, or verify CS/AI/ML paper drafts as a critical peer reviewer. Three-round review (evidence→argument→style) with Verification Status and debt tracking. Use when: reviewing a paper draft before submission, checking evidence compliance of claims, simulating peer reviewer feedback, verifying citation closure and evidence debts, performing cross-section consistency checks. Triggers on: 审修, self review, 自查, verification, revise, 修订, check draft, 审稿, evidence compliance, peer review, 论文审查, draft audit, 验证论文, 检查引用, cross-section review.

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

Use when you need to design, review, or improve REST APIs with Micronaut — including @Controller routes, HTTP status codes, DTOs, Bean Validation, exception handlers, pagination, idempotency, ETag/If-Match, caching headers, versioning, contract-first OpenAPI (OpenAPI Generator), optional runtime OpenAPI via micronaut-openapi, and security annotations. This should trigger for requests such as Review or improve Micronaut @Controller REST APIs; Add validation, error handling, or align controllers with the OpenAPI contract on Micronaut HTTP layer. Part of cursor-rules-java project

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

Use when you need to design, review, or improve REST APIs with Quarkus REST (Jakarta REST) — including resource classes, HTTP methods, status codes, request/response DTOs, Bean Validation, exception mappers, optional runtime OpenAPI exposure (SmallRye), contract-first generation from OpenAPI, content negotiation, pagination, sorting and filtering, API versioning, idempotency (Idempotency-Key), optimistic concurrency (ETag / If-Match), HTTP caching (Cache-Control), API deprecation (Sunset / Deprecation headers), RFC 7807 Problem Details, ISO-8601 for time in contracts, and security-aware boundaries. This should trigger for requests such as Review or improve JAX-RS resources in a Quarkus project; Design HTTP APIs with validation and error handling on Quarkus; Add API versioning, idempotency, ETag concurrency, or deprecation headers; Implement pagination, sorting, or RFC 7807 Problem Details error responses. Part of cursor-rules-java project

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

Use when you need to design, review, or improve REST APIs with Spring Boot — including HTTP methods, resource URIs, status codes, DTOs, versioning, deprecation and sunset headers, content negotiation (JSON and vendor media types), ISO-8601 instants in DTOs, pagination/sorting/filtering, Bean Validation at the boundary, idempotency, ETag concurrency, HTTP caching, error handling, security, contract-first OpenAPI (OpenAPI Generator), controller advice, and problem details for errors. This should trigger for requests such as Review Java code for Spring Boot REST API; Apply best practices for Spring Boot REST API in Java code. Part of cursor-rules-java project

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

プロジェクトの進捗をステータス別・優先度別・サイズ別に集計してレポートを生成する。完了率と未完了の優先度内訳を表形式で出力する読み取り専用スキル。「進捗を見せて」「プロジェクトレポート」「完了率は？」「ステータス別の件数」などで使用。

Generate Skills from HTTP MCP servers with async job patterns (submit/status/result). Use when converting MCP specifications (.mcp.json) into reusable Skills using mcp_tool_catalog.yaml. Supports --lazy mode for context-saving generation. Also use for calling async MCP tools via JSON-RPC 2.0 with session-based polling.

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

Track and report progress of a request to create and run an EcoSIM case for a site ("create an ecosim run for site US-UMB", "set up and run EcoSIM at <site>"). Records four stages — data preparation, namelist creation, model simulation, and output evaluation — in result/<SITE_ID>/progress.json and PROGRESS.md, derives step status from files and quality reports on disk, and records manual results such as the executable, test run, and evaluation verdicts. Use at the start of such a request, after each stage, and whenever the user asks where a site run stands.

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

Use when generating REST controllers, response wrappers, DTOs, error handlers, or any HTTP-facing code. Defines response envelope, HTTP status mapping, pagination, and versioning.

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

Drill-down on the shared MatrxDataTable, local or server, with per-Dimension levels. Use when adding group-by, breakdown or 'by X' analytics to a table, replacing hand-built totals or rollup tables, or when people want counts or sums by status, owner, model or day.

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

Space/aerospace mission monitoring: dark command center, amber telemetry on navy, monospace precision. Functional clarity above all. For ops dashboards, build/deploy status, and real-time monitoring.

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

Pro-camera HUD mockup template — full-viewport black canvas wrapping a real video with monospace overlays (corner brackets, top status bar, side AF/exposure columns, bottom timecode + aperture/shutter/ISO row, vertical 8-filter wheel, animated reticle). For cinematographer portfolios, camera-app demos, LUT pack previews, filter-look auditions. NOT a TikTok/Reels mockup, NOT a storyboard, NOT a shot list, NOT a script document. The chrome wraps real footage — never a div placeholder.

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

Launch, inspect, or tear down an isolated fleet of ready SDD Composy tasks: one branch and Git worktree per member, a bound LOOP, cmux/tmux/headless presentation, no automatic merge. Use to run several ready tasks in parallel — 'rodar várias tarefas em paralelo', 'lançar o fleet', 'fleet status', 'tear down member X'. Do NOT use for a single task (sdd-execute, sdd-loop) or for merging without the explicit teardown token.

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

Summarize existing QA criteria, cases, evidence, defects, limitations, authorization, and verdict without mutation.

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

Use when a user asks for QA planning, execution, review, release assessment, reporting, status, or test-tool recommendations and the correct PWDEV QA workflow must be selected safely.

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

Design deterministic CI quality gates that read the normalized manifest verdict independently from report-export process status.

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

Use when the user asks which PRDs exist — 'listar PRDs', 'quais PRDs temos', 'list PRDs' — with status, version, roadmap state and GitHub Project. Read-only.

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

Cria, atualiza, comenta, fecha e reabre issues do GitHub e gerencia as tarefas de um GitHub Project — mover Status, editar campos, sub-issues e dependências "blocked by", inclusive em lote. Use quando o usuário disser "criar issue", "abrir uma issue", "fechar a issue #12", "reabrir", "comentar na issue", "atribuir para", "mover para Em andamento", "marcar como concluída", "bloqueada por", "sub-issue", "o que está bloqueando", "tarefas do project", "fechar as tasks da feature", ou citar #123 num repo GitHub. Não use para criar um Project novo (skill github-project) nem para publicar um roadmap inteiro (skill github-publish).

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

Use when approved phases should run in parallel — visually in a cmux panel or unattended — when fleet status is requested, or when a fleet member must be stopped or merged

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

Launch, inspect, and tear down autonomous phase fleets in isolated Git worktrees, on the Codex or the Claude runtime. Use when approved Flow phase slugs should run in parallel, when fleet status is requested, or when a fleet member must be stopped or explicitly merged.

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

Loading, empty, and error states with AdwStatusPage and AdwSpinner — placeholder icons, titles, action buttons. Use when an app view can be empty, loading, or failed.

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

Create GitHub releases for this project or similar GitHub repositories. Use when the user asks to release the current master/main branch, create a version tag, publish a GitHub Release, write release notes, check release workflow status, or follow the repository's release process.

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

Organize, categorize, track, and manage invoices systematically with automated extraction of invoice data, payment tracking, and financial organization. Use when processing invoice uploads, extracting invoice details (date, amount, vendor), categorizing expenses, tracking payment status, organizing receipts, generating financial reports, or building accounting and bookkeeping systems.

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

YC Office Hours — two modes. Startup mode: six forcing questions that expose demand reality, status quo, desperate specificity, narrowest wedge, observation, and future-fit. Builder mode: design thinking brainstorming for side projects, hackathons, learning, and open source. Saves a design doc. Use when asked to "brainstorm this", "I have an idea", "help me think through this", "office hours", or "is this worth building". Proactively invoke this skill (do NOT answer directly) when the user describes a new product idea, asks whether something is worth building, wants to think through design decisions for something that doesn't exist yet, or is exploring a concept before any code is written. Use before /plan-ceo-review or /plan-eng-review. (gstack)

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

Configure deployment settings for /land-and-deploy. Detects your deploy platform (Fly.io, Render, Vercel, Netlify, Heroku, GitHub Actions, custom), production URL, health check endpoints, and deploy status commands. Writes the configuration to CLAUDE.md so all future deploys are automatic. Use when: "setup deploy", "configure deployment", "set up land-and-deploy", "how do I deploy with gstack", "add deploy config".

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