「ipa」の検索結果

Definition of Ready checklist criteria, antipattern detection patterns, UAT quality rules, and domain language enforcement for product owner review

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

生成用于构建和发布 .NET 6 MAUI iOS 项目的 Azure Pipelines YAML 配置，包含 DotNetCoreCLI 任务配置、RuntimeIdentifier 设置及 IPA 文件重命名功能。

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

Use for authorized Android or iOS application reverse engineering and security testing, including APK or IPA analysis, runtime instrumentation, SSL pinning, and platform protection checks.

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

한국+일본 병기 처리방침·이용약관 자동 생성. 한국 본사가 일본 사용자까지 대상으로 서비스할 때 사용. 한국어(PIPA)·일본어(APPI) 두 세트 문서를 동시 생성하고, Footer에 언어·관할 전환 링크 자동 삽입.

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

처리방침·이용약관 자동 생성 스킬 패키지 (v4.0). 호출 시 privacy-kr·privacy-eu·privacy-us·privacy-global 4개 하위 스킬을 번호 메뉴로 제시하고 번호 입력 즉시 해당 스킬 인터뷰로 직행. 한국 PIPA + EU GDPR + US CCPA/CPRA 대응.

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

한국+EU 병기 처리방침·이용약관 자동 생성. 한국 본사가 EU 사용자까지 대상으로 서비스할 때 사용. 한국어(PIPA)·영문(GDPR) 두 세트 문서를 동시 생성하고, Footer에 언어·관할 전환 링크 자동 삽입.

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

Deep Mobile Security Red Team persona. Executes OWASP MASTG procedures including APK/IPA decompilation, Frida dynamic hooking, biometric bypasses, and local database decryption.

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

Implement and maintain compliance with SOC 2, HIPAA, PCI-DSS, and GDPR using unified control mapping, policy-as-code enforcement, and automated evidence collection. Use when building systems requiring regulatory compliance, implementing security controls across multiple frameworks, or automating audit preparation.

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

DO NOT INVOKE when the primary request explicitly asks to convert, migrate, modernize, or rewrite a legacy/old-style project to SDK style; use msbuild-modernization. Migration prompts often mention ToolsVersion, explicit Compile/Reference entries, packages.config, or Microsoft.CSharp.targets, but merely reviewing or auditing a file that contains those patterns remains in scope here. USE FOR broad review, audit, lint, or maintainability/correctness checks of project/build files, including custom targets; prioritized cross-cutting findings; discrete anti-patterns; F# ordering/FS0039; cross-platform paths; and focused Import safety verdicts. Review/audit is analysis-only unless fixes are requested. For concrete property/item defects use property-patterns/item-management; use target-authoring for implementation and extension-points for NuGet auto-import/layout discovery. Exclude non-MSBuild systems.

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

Canonical patterns for writing custom MSBuild targets. USE FOR: diagnosing and fixing custom target authoring anti-patterns; broken SDK target chains across files (e.g., Directory.Build.targets silently redefining SDK targets); targets that replace CompileDependsOn instead of extending it with $(CompileDependsOn); query targets returning stale results from Outputs vs Returns misuse; missing Inputs/Outputs causing unnecessary rebuilds; missing FileWrites registration. Covers DependsOnTargets vs BeforeTargets vs AfterTargets, the Build→CoreBuild three-level pattern, and the $(XxxDependsOn) chain-extension pattern. DO NOT USE FOR: incremental build tuning (use incremental-build), parallelization (use build-parallelism), general anti-patterns (use msbuild-antipatterns), non-MSBuild build systems.

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

Own MSBuild import and hook discovery. USE FOR: CustomBefore/CustomAfter hooks, ordered wildcard and NuGet auto-imports, control properties, build/buildTransitive packed layout, package ID and file-name matching, per-TFM forwarders, and tracing why assets or hooks are missing, broken, or replaced. An import guard remains in scope when it is one defect in a broader hook/import flow. DO NOT USE for a focused safety verdict on whether one specific Import needs Exists or is an intentionally unguarded package contract; use msbuild-antipatterns. NEVER INVOKE when imports and hook placement already work and the request is only target Inputs/Outputs, incremental skipping, or FileWrites clean tracking; use incremental-build or target-authoring. Exclude props-versus-targets placement and non-MSBuild systems.

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

Work on C# and .NET-adjacent mixed-reality solutions around HoloLens, MRTK, OpenXR, Azure services, and integration boundaries where .NET participates in the stack. USE FOR: building or integrating mixed-reality solutions with C#; working on HoloLens, MRTK, Azure mixed-reality services, or OpenXR-related code; reviewing how .NET services. DO NOT USE FOR: unrelated stacks; generic tasks that do not need this specific guidance. INVOKES: inspect the repository context, edit targeted files, and run relevant build, test, lint, or validation commands when changes are made.

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

Use when user asks about 藏传, 噶当派, Kadam, 三士道, 菩提道灯论, Bodhipathapradīpa, 阿底峡, Atiśa, 金洲大师, 七因果, 自他相换, 菩提心, 依止善知识, 暇满, 业果, 噶当六论, 仲敦巴, 热振寺, 藏地后弘期, or wants teaching in 阿底峡尊者 Atiśa's voice. Triggers include "阿底峡"、"觉沃杰"、"Atisha"、"Jowo Je"、"菩提道灯"、"道灯论"、"三士道"、"七因果"、"自他相换"、"金洲"、"噶当"、"仲敦巴"、"热振寺"、"道次第之祖" — invoke whenever user's question touches Kadam / lamrim foundations / bodhicitta cultivation, even without explicit request.

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

Generate a pre-meeting prep brief in Claude Code. Researches participants, pulls vault context, builds agenda, surfaces sharp questions. Use when user says "prep for this meeting," "I have a call with," "meeting tomorrow with," or "prep brief for [name/company]."

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

Trigger for: OT project description, OTA scope, Research OT under 10 U.S.C. 4021, Prototype OT under 10 U.S.C. 4022, follow-on production scope under 10 U.S.C. 4022(f), milestone-based project scope, prototype objective, phase or go/no-go structure, BAA white-paper conversion, SOO conversion, transition planning, or scope reduction before OT cost analysis. Produce a milestone-based .docx plus a separate chat-only handoff to OT Cost Analysis. Use TRL only when the project supports it. Never place cost estimates, funding profiles, contribution calculations, prices, or skill-routing content in the document. Do NOT use for a FAR SOW/PWS, OT cost analysis, IGCE, agreement terms and conditions, or an Agreements Officer's authority, participant-status, successful-completion, or follow-on determination.

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

Use when working with Canton Network participants, DAML smart contracts, Splice applications, or debugging LF version and package ID issues.

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

한국 정부·공공기관 지원사업(창업지원, 사업화 자금, 입주공간, R&D, 바우처, 경진대회) 전수조사 및 프로젝트 적합성 판정 스킬. K-Startup·기업마당(bizinfo)·NIPA·KOCCA·SMTECH 공고를 크롤링해 현재 작업 폴더의 프로젝트(아이템) 프로필에 맞는 사업을 "즉시 지원 가능 / 요건 충족 시 / 변형하면 가능" 3단계로 분류하고 마감일·자격요건을 원문 검증해 보고서를 만든다. 사용자가 "지원사업 찾아줘", "정부지원", "창업지원 사업", "입주공간/사업화 자금 알아봐", "공모전/경진대회 조사", "우리 아이템에 맞는 지원사업", "K-Startup/기업마당 조사" 등을 요청하면 반드시 이 스킬을 사용한다. 이전에 조사한 적이 있는 프로젝트에서 "재조사", "새로 나온 지원사업 있나", "지난번 이후 뭐 올라왔나"를 물으면 diff 모드(증분 재조사)로 이 스킬을 사용한다. 특정 사이트를 지목하지 않아도 지원사업·보조금·정부과제 탐색 의도가 보이면 트리거된다. 단, 이미 운영 중인 소상공인·가게·점포·자영업자의 지원(소상공인 지원금, 정책자금 대출, 가게 시설개선, 소상공인24, 폐업·재기 지원)은 이 스킬이 아니라 sole-search 스킬을 사용한다. 신호가 섞이면(예: '온라인 셀러 지원금') 어느 쪽인지 한 번 묻는다. 사용자 신분보다 요청 목적이 우선이다 — 가게 사장이라도 신규 아이템 창업지원·R&D를 찾으면 ir-search. 한국 지원사업 전용.

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

omics-plotting: publication-style figure authoring for omics / bioinformatics results with matplotlib / seaborn. Read this before writing any plotting or figure code in any omics analysis — RNA-seq, proteomics, single-cell, variant, or database results — not only when a plot is explicitly requested: whenever an analysis will produce a figure, load this first and follow its recipes. Covers volcano, MA, expression / correlation heatmap, GSEA bar / dot plot, box / violin / bar / ridgeline, PCA / UMAP / t-SNE scatter, Kaplan–Meier, Manhattan / QQ / forest. Supplies a shared journal-ready style and copy-paste recipes so every figure looks like one consistent system. To combine several plots into ONE multi-panel composite figure, use the sibling `multipanel` skill.

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

Assemble multiple plots into ONE publication-ready multi-panel journal figure (e.g. Figure 1 with panels A, B, C). Use whenever the user asks to combine, compose, or lay out several plots as a single composite figure — newly plotted from data or from already-rendered panels the user supplies (PNG/PDF). Ask the user to pick one of two approaches: (1) redraw every panel into one unified figure using independent, tightly packed `subfigures` (each sized to its own labels, so axes need NOT align), consistent style, correctly placed panel letters, and per-panel legends/colorbars; (2) composite already-rendered PNG/PDF panels onto a mosaic canvas and add panel letters (image compositing, not plotting). Both export vector PDF + high-DPI PNG. For a SINGLE plot from a data table, use the sibling `omics-plotting` skill instead.

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

Prepare a sourced site-visit record separating direct observations, participant reports, interpretations, limitations and proposed follow-ups.

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

AI-powered multi-agent code review. Simulates a team of Principal Engineers reviewing code from different perspectives. Use when asked to review code, check a PR, analyze changes, or perform code review.

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

Provides Amazon S3 patterns and examples using AWS SDK for Java 2.x. Use when working with S3 buckets, uploading/downloading objects, multipart uploads, presigned URLs, S3 Transfer Manager, object operations, or S3-specific configurations.

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

Automate construction permit tracking and management. Monitor application status, track renewal deadlines, manage document requirements, and integrate with municipal systems.

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

Audits a codebase or business process for regulatory compliance across GDPR, HIPAA, SOC2, CCPA, and PCI-DSS. Scans for PII handling, data retention, encryption, access controls, audit logging, consent management, and data transfer issues. Generates a structured compliance report with findings, gap analysis, remediation steps, and evidence requirements.

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