5,644 件 ・ 関連度順
概要と使いどころ
Integrate Iteration Layer APIs for document, website, image, and sheet processing. Composable APIs — Document Extraction, Website Extraction, Document to Markdown, Image Transformation, Image Generation, Document Generation, and Sheet Generation — share one credit pool and chain together into workflows.
日本語の概要は準備中です。原文の説明を表示しています。
Draws debug overlays in a running CARLA world via world.debug — points, lines, arrows, bounding boxes, and text strings, each with a colour and lifetime. Use when the user asks to "draw/mark/highlight a point or box in the world", "visualise a path/waypoints", "label a location", or "show something on the map for debugging". Shapes are an overlay, not actors.
日本語の概要は準備中です。原文の説明を表示しています。
Installs the CARLA Autonomous Driving Leaderboard (leaderboard.carla.org) at a chosen version — 1.0, 2.0 or 2.1 — together with the exact scenario_runner branch and CARLA build each one requires, then wires the four-root PYTHONPATH and verifies the whole stack imports. Detects which version an existing checkout is by reading its code, not its branch name. Use when the user asks to "install the leaderboard", "set up the CARLA challenge", "evaluate my driving agent", "reproduce my leaderboard score", or names a leaderboard version.
日本語の概要は準備中です。原文の説明を表示しています。
Expert security auditor specializing in comprehensive security assessments, compliance validation, and risk management. Masters security frameworks, audit methodologies, and compliance standards with focus on identifying vulnerabilities and ensuring regulatory adherence.
日本語の概要は準備中です。原文の説明を表示しています。
Expert penetration tester specializing in ethical hacking, vulnerability assessment, and security testing. Masters offensive security techniques, exploit development, and comprehensive security assessments with focus on identifying and validating security weaknesses.
日本語の概要は準備中です。原文の説明を表示しています。
Repository-specific AGENTS.md authoring and maintenance workflow. Use when creating, refreshing, or expanding AGENTS.md coverage for a codebase, including deciding whether nested AGENTS.md files are needed for subsystems with distinct rules, workflows, or AI-sensitive constraints.
日本語の概要は準備中です。原文の説明を表示しています。
Debate multi-agente: 2-4 perspectivas (PM, Arquiteto, QA, Security) debatem decisao tecnica. Output: decisao + rationale + dissenting opinions → ADR. Inspirado no Party Mode do BMAD-METHOD.
日本語の概要は準備中です。原文の説明を表示しています。
Automated compliance checking for affiliate marketing content. Verifies FTC disclosure requirements, link tracking, and ethical affiliate practices.
日本語の概要は準備中です。原文の説明を表示しています。
Evaluates and implements age estimation and verification technologies for online services. Covers facial age estimation, digital ID verification, self-declaration with risk assessment, AI-based age estimation, and the accuracy versus privacy tradeoff. Includes ICO guidance and euCONSENT framework. Keywords: age verification, age estimation, facial analysis, digital ID, children, online safety.
日本語の概要は準備中です。原文の説明を表示しています。
Perform 12-Factor Agents compliance analysis on any codebase. Use when evaluating agent architecture, reviewing LLM-powered systems, or auditing agentic applications against the 12-Factor methodology.
日本語の概要は準備中です。原文の説明を表示しています。
Simulate Joint Commission tracer methodology to assess compliance with accreditation standards across patient care processes and support systems
日本語の概要は準備中です。原文の説明を表示しています。
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
日本語の概要は準備中です。原文の説明を表示しています。
Technical research methodology with YAGNI/KISS/DRY principles. Phases: scope definition, information gathering, analysis, synthesis, recommendation. Capabilities: technology evaluation, architecture analysis, best practices research, trade-off assessment, solution design. Actions: research, analyze, evaluate, compare, recommend technical solutions. Keywords: research, technology evaluation, best practices, architecture analysis, trade-offs, scalability, security, maintainability, YAGNI, KISS, DRY, technical analysis, solution design, competitive analysis, feasibility study. Use when: researching technologies, evaluating architectures, analyzing best practices, comparing solutions, assessing technical trade-offs, planning scalable/secure systems.
日本語の概要は準備中です。原文の説明を表示しています。
Perform 12-Factor App compliance analysis on any codebase. Use when evaluating application architecture, auditing SaaS applications, or reviewing cloud-native applications against the original 12-Factor methodology.
日本語の概要は準備中です。原文の説明を表示しています。
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
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
Help job seekers use Otameshi Tenshoku to prepare profiles and applications, clarify trial conditions, plan learning visits or paid trial work, and reflect on the experience. Use when a candidate wants to apply for, prepare for, negotiate the scope of, or review an otameshi work experience; do not use to predict whether they will be hired or to judge their aptitude, to state fees, contract terms, or service conditions from memory, or to submit an application, update a profile, or send a message on their behalf. Employer-side requests belong to the employer skills (trial-work-design, trial-listing-draft, applicant-reply and others).
日本語の概要は準備中です。原文の説明を表示しています。
Research a specific company before applying or interviewing by gathering facts from primary and official sources, recording the source and date behind every claim, and keeping anonymous or unverifiable material clearly separated from confirmed fact. Use when a user asks what a company actually does, how it makes money, what its published conditions are, whether a posting matches the company's own disclosures, or what to verify before an interview; do not use to predict hiring outcomes, to repeat review-site content as fact, or to bulk-crawl sites that prohibit automated access.
日本語の概要は準備中です。原文の説明を表示しています。
Prepare the internal case for hosting an Otameshi Tenshoku trial: total what it costs the company with candidate pay, staff hours and platform or incidental fees kept apart, compare it with the budget, state what remains if no hire follows, and lay out the risks, stop conditions, decision owners and deadlines. Use when a hiring manager needs approval or budget from a decision maker, a recruiter has to explain the plan to the team that will host, or a small-business owner wants to see the full cost including their own time before posting; do not use to design the work (trial-work-design), to write the listing (trial-listing-draft), to predict whether a hire will follow, to state platform fees, agency fees or market rates from memory, or to submit the request or post the listing on the user's behalf.
日本語の概要は準備中です。原文の説明を表示しています。
Plan a resignation and the move to a new employer: check the intended notice date, last working day, and start date against the notice period the employer's own rules require, count the weekdays left against remaining paid leave, and work through the checklist of handover, documents to receive, items to return, and the insurance, pension, and residual tax steps that a gap between jobs creates. Use when a user has accepted an offer and needs to work out when and how to resign, or wants to know what to confirm before giving notice; do not use to rule on whether they can legally leave, to judge a non-compete clause, to promise the departure will go smoothly, or to notify anyone.
日本語の概要は準備中です。原文の説明を表示しています。
Prepare for a Japanese job interview by working from the documents already submitted: find where an interviewer will dig in (claims the applicant cannot back up, work described in the first person plural, outcomes with no measure, gaps or overlaps in the employment history, must-have requirements the documents never answer), and turn them into questions to prepare evidence for. Use when a user has an interview scheduled and wants to know what will be asked and what to have ready, or wants to prepare reverse questions from earlier company research; do not use to predict whether they will pass, to write answers containing experience they did not report, or to schedule or contact anyone.
日本語の概要は準備中です。原文の説明を表示しています。
Read a Japanese job posting closely and report what it actually states: base pay separated from fixed overtime allowance, the range converted to an hourly basis, required versus preferred requirements, and the terms left ambiguous. Use when a user wants a 求人票 or job description examined before applying, wants two postings compared on the same basis, or wants questions prepared about pay and working conditions; do not use to judge whether the user will be hired, to infer duties the posting does not state, or to evaluate the employer's reputation.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。