「got」の検索結果

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; Design Spring Boot REST controllers and DTOs; Add Problem Details error responses in Spring Boot REST; Improve pagination validation or idempotency in Spring APIs. Part of Plinth Toolkit

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

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; Improve Quarkus REST resources and exception mappers. Part of Plinth Toolkit

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

Security-first SOP for multi-tenant RAG systems. Activate when a calling agent is building, reviewing, or debugging any retrieval pipeline whose vector store is shared across more than one user, organisation, workspace, customer, or permission scope. Encodes the single non-negotiable rule — **filter at the vector store query, never after retrieval / never after rerank** — together with the per-vendor query-time filter APIs (Pinecone namespaces + `$eq`/`$in`, Weaviate `multiTenancyConfig` + tenant handle, Qdrant `is_tenant` payload index + `Filter.must`, Chroma `where`, pgvector RLS), and the cross-framework adapters (LlamaIndex `MetadataFilters`, LangChain `filter=` dict). Frame the work as preventing CVE-2024-41892 / EchoLeak / Slack-AI-class cross-tenant leakage, not as "adding a filter for relevance".

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

Tool skill — the *first move* in any LM-debugging session: dump the actual rendered prompt the framework sent to the model, before changing anything else. Activate when an LM call produced an unexpected output (wrong answer, schema violation, refusal, truncation, cost spike, latency spike, infinite loop, "model got dumber after upgrade"). The skill enforces a 30-second inspect step BEFORE any prompt edit, model swap, retry, or temperature tweak. Cross-framework cheat sheet: DSPy `inspect_history`, LangGraph `get_state_history`, CrewAI `step_callback`, LangChain `set_debug`/`set_verbose`, Aider `/diff`+`--verbose`, raw OpenAI/Anthropic via `OPENAI_LOG=debug`/`ANTHROPIC_LOG=debug` or HTTPX event hooks. Do NOT activate for first-time prompt authoring, exploratory prompt design, or non-LM bugs.

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

Diagnoses why your product team ships slowly and produces a velocity plan with a baseline, a bottleneck map, the top 3 interventions and a stop-doing list. Use it when you say 'we're too slow', 'how do we ship faster', 'projects keep slipping', 'too many meetings', 'approvals take forever', 'our releases are scary', 'velocity', 'cycle time', 'we hired more people and nothing got faster' or 'AI made coding fast but we still ship slowly'. Draws on 226 Lenny's Podcast guests including Farhan Thawar, Nicole Forsgren and Melissa Perri.

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

当重要的故事元素（角色、情节线、伏笔）10章以上未出现时自动提醒 - 防止长篇小说中的'角色消失综合症'和遗漏的情节线

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

Use to manage pricing, packaging, and approval workflows for renewal negotiations.

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

Operate the Resend platform from the terminal — send emails (including React Email .tsx templates via --react-email), manage domains, contacts, broadcasts, templates, webhooks, API keys, logs, automations, and events via the `resend` CLI. Use when the user wants to run Resend commands in the shell, scripts, or CI/CD pipelines, or send/preview React Email templates. Always load this skill before running `resend` commands — it contains the non-interactive flag contract and gotchas that prevent silent failures.

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

Use when working with the Resend email API — sending transactional emails (single or batch), receiving inbound emails via webhooks, managing email templates, tracking delivery events, managing domains, contacts, broadcasts, webhooks, API keys, automations, events, viewing API request logs, or setting up the Resend SDK. Always use this skill when the user mentions Resend, even for simple tasks like "send an email with Resend" — the skill contains critical gotchas (idempotency keys, webhook verification, template variable syntax) that prevent common production issues.

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

Analyze and compare subcontractor bids against CWICR benchmarks. Evaluate pricing, identify outliers, and support negotiation.

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

Argues the strongest honest case against a decision, plan, belief, hire, pricing move, strategy, or piece of work the user is leaning toward. Steelmans the other side, ranks at most three objections by consequence, runs a short pre-mortem, credits what the user got right, and ends with what would have to be true for their choice to work. Calibrated and collegial, never combative; says plainly when the position is strong. Use whenever the user says "play devil's advocate", "argue the other side", "poke holes in this", "what am I missing", "am I making a mistake", "talk me out of it", "stress-test this idea", "tell me why this is a bad idea", or asks for pushback on something they have mostly decided. Supports gentle, standard, and hard intensity. Not for interrogating requirements before a build (grill-the-brief) or staging a multi-persona debate (debate-simulator).

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

Drop a folder of vendor quotes, proposals, and SOWs on Cowork -- normalizes them into one comparison matrix, computes true total cost of ownership, surfaces the terms each vendor buried, and arms you with negotiation leverage points and reference-check questions.

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

Uses Cowork-style multi-step analysis to process deal room documents -- contracts, financials, org charts. Outputs risk assessment, term comparison, key findings, and negotiation recommendations.

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

Decode a commercial lease before signing or renewing -- true all-in occupancy cost (base rent plus NNN/CAM plus escalations), the clauses that hurt small tenants (personal guarantees, relocation, restoration), and the negotiation asks landlords routinely grant. The lease is most SMBs' biggest fixed cost and least-read document.

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

Shared discipline for every hunt-* skill: scope and authorization gating, the two-account rule, the confirmation gate that separates a real finding from a false positive, enumeration limits, stop conditions, marker discipline, wiki-first query and self-heal, FIND output, Deadends, and wiki distillation. ALWAYS LOADED alongside any hunt skill. Also trigger directly on "is this in scope", "is this a real bug", "how do I confirm this", "should I keep going", "how many IDs should I test", "what severity", "how do I report this", "I got someone else's data". Every hunt-* skill assumes this file; without it they run without their safety and quality layer.

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

Builds a comprehensive breach response team playbook defining CSIRT and privacy team structure with named roles (incident commander, legal counsel, communications, IT forensics, DPO), escalation matrices, communication templates, pre-negotiated vendor contacts, and regulatory authority contacts organized by jurisdiction. Keywords: breach response playbook, CSIRT, incident response team, escalation matrix, communication templates, vendor contacts.

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

Give the owner one page when they come back from sleep, a meeting or a long run: what got done, what is stuck, what waits for their answer, and what it cost in quota. Use when the owner asks what happened while they were away, wants a status page, or when you finish a long stretch of work and must report it.

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

Recover assets (images, videos, data) that weren't directly archived by Wayback Machine by crawling archived pages that reference them. Use when: (1) Direct asset URL returns 404/503 from Wayback, (2) Asset was hosted on CDN that Wayback didn't crawl, (3) You have the page URL but not the asset URL, (4) Recovering avatars, thumbnails, or embedded media from defunct services. The key insight: pages often got archived even when their assets didn't - extract URLs from archived HTML, then try alternative fetch methods.

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

Set up Cloud Run Jobs with CloudSQL connection. Use when: (1) Deploying long-running batch jobs that need database access, (2) Errors like "Cloud SQL Proxy not found" in container, (3) "password authentication failed" despite correct credentials, (4) Job creation fails with permission errors. Covers socket path configuration, IAM permissions, and common gotchas.

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

Enforces strict modular code architecture: SRP, no monolithic index files, no catch-all utils, 200 LOC hard limit. This rule is NON-NEGOTIABLE. Violations BLOCK all further work until resolved.

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

Evaluate vendors with comparison matrices, TCO analysis, risk assessment, reference check templates, and negotiation strategies

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

Prepare structured briefings for meetings with legal relevance and track resulting action items. Use when preparing for contract negotiations, board meetings, compliance reviews, or any meeting where legal context, background research, or action tracking is needed.

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

Review contracts against your organization's negotiation playbook, flagging deviations and generating redline suggestions. Use when reviewing vendor contracts, customer agreements, or any commercial agreement where you need clause-by-clause analysis against standard positions.

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

Use whenever you need to understand how this theme works — adding pages, managing content, configuring the site, using partials/components/modules, project architecture, scripts, or styling/theming (Tailwind v4, Bootstrap 5, or a hybrid — verify which). Use for ANY question about the structure, usage, or customization of the template or theme.

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