「cat」の検索結果

SDK installation and setup patterns for Agent-to-Agent Protocol across Python, TypeScript, Java, C#, and Go. Use when implementing A2A protocol, setting up SDKs, configuring authentication, or when user mentions SDK installation, language-specific setup, or A2A integration.

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

Protect your SaaS app from common vulnerabilities. Use when building auth, handling user data, or deploying features. Covers authentication, data protection, API security, and OWASP Top 10 for non-technical founders using AI tools.

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

MANDATORY deploy after every code change. Typecheck → deploy → purge CDN → E2E on production → visual verify → fix-forward loop. Workers Builds native CI/CD, D1 Time Travel PIT recovery, D1→R2 long-term backups, wrangler rollback, wrangler secrets management, structured observability, cross-browser smoke tests, rollback procedures, and GitHub auto-configuration.

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

Soc2 Compliance Checker - Auto-activating skill for Security Advanced. Triggers on: soc2 compliance checker, soc2 compliance checker Part of the Security Advanced skill category.

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

Raccourcir des URLs via is.gd ou v.gd. Use when: l'utilisateur demande de raccourcir une URL, créer un lien court, ou simplifier une URL longue. NOT for: URLs nécessitant une authentification, liens personnalisés avec domaine propre, analytics avancés.

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

Use when you need to design, review, or improve security in Spring Boot applications — including SecurityFilterChain, OAuth2/JWT resource server patterns, form login basics, method security (@PreAuthorize), CSRF and CORS for APIs, session fixation, security headers, exception handling, password encoding, and sensitive-data-safe logging. This should trigger for requests such as Add Spring Boot security support; Review Spring Boot security configuration; Improve API authorization in Spring Boot; Add JWT resource server security in Spring Boot; Harden Spring Boot security headers and CSRF settings. 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

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

Scaffolds a complete .NET solution following Clean Architecture principles with proper layer separation (API, Application, Domain, Infrastructure). Creates project structure, dependency injection setup, and cross-cutting concerns configuration.

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

Technical SEO for AI search engines. Checks AI crawler accessibility, llms.txt compliance, robots.txt configuration, server-side rendering. Outputs problems + fixes (generates llms.txt, robots.txt modifications). Use when user says "AI crawlers", "llms.txt", "GPTBot", "GEO technical".

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

Technical SEO audit across 8 categories: crawlability, indexability, security, URL structure, mobile, Core Web Vitals, structured data, JS rendering. Schema deep validation → seo-schema. AI crawlers → seo-geo-technical. Use when user says "technical SEO", "crawl issues", "robots.txt", "Core Web Vitals".

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

Write, review, or audit this repository's technical documentation, including README.md, CONTRIBUTING.md, root and scoped AGENTS.md files, docs pages, and documentation drift. Use for source-backed documentation authoring, behavior verification, and cross-surface consistency. Do not use for code review, deslop diff cleanup, or whole-page rewrites, splits, or reorganizations handled by docs-refactor.

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

Run Unity Test Runner and report detailed results. Use for EditMode/PlayMode tests, change verification, or failure diagnosis.

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

Build kokoro-js-jp and run its real-browser e2e suite (Worker + WASM openjtalkjs g2p + ONNX kokoro-js synthesis, English and Japanese). Use when asked to verify this package actually works in a browser, to check whether a change broke synthesis, or to add browser-level regression coverage for a bug in the g2p/synthesis pipeline that vitest's pure-function tests can't catch. Not for typecheck/lint/unit-test requests — use npm run typecheck / npm test for those.

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

Inventory a person's work history as facts before any document is written, listing each period of employment and what they actually did, splitting every experience into situation, their own actions, outcome, and stated role, and recording what each claim rests on (public record, their own records, someone who was there, or memory alone). Use when a user is starting a job search, needs material for a rirekisho, shokumu-keirekisho, or entry sheet, or wants to find which periods of their history they have never written down; do not use to judge their strengths, aptitude, or market value, to name a job they are suited for, or to write finished application copy.

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

Assemble a Japanese shokumu-keirekisho (career history document) from an experience inventory, choosing between reverse-chronological, chronological, and skills-based layouts, mapping the target posting's requirements to the experiences that can support them, and drafting the summary, work history, skills, and self-PR so that each sentence stays within what its evidence supports and confidential details are abstracted. Use when a user wants to write or rebuild a whole shokumu-keirekisho for a specific posting or as a general version, or wants to decide which experiences to include and in what order; do not use to invent experience, numbers, titles, or qualifications, to predict whether it will pass screening, to fill in a rirekisho form, or to submit it anywhere.

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

Work out the order and the loose ends before turning down an offer or withdrawing from a selection process: whether the offer being kept is actually settled in writing, whether each decline is mid-selection, post-offer, or after acceptance, who besides the employer has to be told when the application came through an agent, a school recommendation, or a referral, which reply deadlines have passed, and what documents, expenses, or borrowed items are still outstanding. Use when a user holds more than one offer and needs to decline the rest, wants to withdraw from a process they are no longer pursuing, or has been asked to turn down other employers as a condition; do not use to decide whether to decline, to rule on what declining after acceptance means legally, or to send any message.

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

Sort incoming scout messages and agent-forwarded openings by what they actually disclose: whether the employer is named at all, which of pay, location, employment type, and duties are stated, whether the message refers to the applicant's own history or reads as a mass send, whether a stated salary is an offer or a "up to" figure, and whether the same employer has arrived through more than one route. Use when a user has a backlog of scout messages and wants to know which ones can be researched, what to ask before replying, and what to settle before handing over a resume; do not use to rate how promising an opening is, to judge an employer or an agent, or to reply on the user's behalf.

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

Keep GPT-5.6 and other coding-agent work proportional to the request by locking scope, choosing the smallest sufficient implementation, matching verification to risk, and stopping when success is proven. Use for implementations, bug fixes, refactors, reviews, or maintenance where scope creep, speculative abstractions, unrelated cleanup, repeated test runs, unnecessary dependencies, or polishing beyond the request are risks.

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

Read market data from the HoneyComb job position exchange. Get ticker prices, price changes, pool state, trade history, and real-time price feeds. Use when analyzing market conditions, checking prices, or researching job position tickers. No authentication required.

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

Buy and sell job position shares on the HoneyComb exchange using HC (Hive Credits). Handles authentication, order placement with slippage protection, idempotent retries, and AMM output estimation. Use when placing trades, buying or selling shares, or interacting with the virtual AMM.

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

DON'T USE THAT SKILL. IT'S JUST AN EXAMPLE. Summarize today's Gmail inbox by category with anonymized senders and subjects, then surface the top 3 emails to focus on next. Run only when the user types /email-summary.

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

Gate a build on browser fingerprint regressions with liarjs - save a baseline scan as JSON, diff later runs against it, and fail the job when the consistency score falls below a floor. Use when asked to add a fingerprint or headless-detection check to GitHub Actions, GitLab CI or another pipeline, to catch a regression in a Chromium build or scraping harness before it ships, or to track how a fingerprint score changes across commits.

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

Rank and prioritize neoantigen/epitope candidates by likely T-cell response using NeoFox feature annotation, PRIME2.0, BigMHC-IM, the Łuksza/Balachandran fitness model (agretopicity + foreignness), and pVACtools tiering. Encodes the field's hard truths that immunogenicity is the least-solved layer (dedicated scores ~AUROC 0.6-0.7, modest PPV), that scores are valid only for RANKING within one patient (never absolute go/no-go or cross-patient), that DAI has anchor-inflation and WT-denominator traps, and that stacking weak correlated scores into one number is a red flag. Use when ordering a candidate list for a vaccine. Binding lives in mhc-binding-prediction; calling in neoantigen-prediction.

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

Assign cell types from marker expression in IMC/MIBI data using clustering (PhenoGraph/FlowSOM/Leiden/Pixie), marker-based probabilistic classifiers (Astir), or image-context CNNs (CellSighter), covering the double-positive segmentation artifact, lineage-vs-state markers, the two spillover types, and why a "cell type" in imaging is conditioned on a segmentation guess. Use when phenotyping segmented IMC cells, choosing clustering vs classification, diagnosing implausible double-positive populations, separating lineage from functional markers, or transferring labels across a cohort.

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