「ada」の検索結果

Art direction for survival and survival-horror gameplay spaces in Blender emphasizing resource props, crafting readability, and tension routes.

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

Art direction for metroidvania, roguelike, and roguelite games in Blender with biome gates, room modules, and run-readable props.

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

Art direction for soulslike games in Blender with monumental melancholy spaces, fog gates, bonfire landmarks, and lethal readability.

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

Art direction for racing and sports games in Blender with track landmarks, stadium kits, and high-speed readability.

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

Art direction for action, hack-and-slash, beat 'em up, and fighting-game readable combat spaces and prop language in Blender.

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

Cartoon art direction for Blender with squash-stretch readable shapes, bold colors, and graphic silhouettes for games and animation.

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

Provide comprehensive techniques for penetration testing AWS cloud environments. Covers IAM enumeration, privilege escalation, SSRF to metadata endpoint, S3 bucket exploitation, Lambda code extraction, and persistence techniques for red team operations.

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

Geracao de imagens humanizadas via Google AI Studio (Gemini). Fotos realistas estilo influencer ou educacional com iluminacao natural e imperfeicoes sutis.

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

Use when checking skill metadata, references or repository boundaries, or preparing an explicitly requested skills release.

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

Use when adding, editing or reviewing skills, role prompts or skill metadata.

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

拆解已筛选爆款内容为什么能传播，分析受众情绪、分享动机、有效立场、首批传播者和可迁移元素。用户问一条内容为什么爆、打中了谁，或哪些机制能跨赛道借鉴时使用。 English: Explain why a selected breakout post spreads by analyzing audience emotions, sharing motives, effective positioning, early sharers, and transferable elements. Use when the user asks why content went viral, whom it resonated with, or what can be adapted across categories.

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

把已验证的传播机制转成适合目标账号的内容选题，并完成生成、迁移、评分和筛选，让选题自然连接人设、产品或门店。用户要从低粉爆款、垂直样本、邻近受众或跨赛道内容中寻找新选题时使用。 English: Turn validated content mechanisms into topics that fit the target account, then generate, adapt, score, and filter them while connecting naturally to the persona, product, or store. Use to find ideas from low-follower breakouts, niche examples, adjacent audiences, or other categories.

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

Implements email and internet monitoring compliance in the workplace per Barbulescu v Romania (ECHR Grand Chamber), EDPB guidance, and national labour law. Covers acceptable use policies, legitimate expectation of privacy, proportionality testing, and content vs metadata monitoring. Keywords: email monitoring, Barbulescu, workplace privacy, internet monitoring, acceptable use policy, ECHR, proportionality.

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

Implement the Kantara Initiative consent receipt specification including machine-readable receipt structure, JWT-based verification mechanisms, receipt lifecycle management, and integration patterns for consent management platforms. Supports ISO/IEC 27560 consent record information structure.

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

OI-3 spike harness — heavy consumer skill, INLINE arm. Builds an incident post-mortem and sources the readability standard mid-workflow via an inline (non-forked) guidance skill. Use only when explicitly invoked by the spike harness with a TRIAL_ID and data path.

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

Internal harness probe for the OI-3 readability-guidance spike. Use only when explicitly told to invoke spike-probe. Verifies that a freshly-created project skill renders into a subagent's context via the Skill tool.

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

OI-3 spike harness — the FORKED (context fork) readability-guidance variant. Same payload as the inline variant but declared to run in a forked context. Use only when a spike consumer skill invokes it.

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

Produces a human-readable, progressive-disclosure overview of unfamiliar code or a pull request's changes — why it exists (the real problem it solves or goal it serves for the business or a user), and from there what it does, how it flows, and where to start — so you can get up to speed before working on or reviewing it. Use when you want to understand, get oriented in, make sense of, explain, or get up to speed on a chunk of code, a file, a directory, a symbol, or a PR's changes. Writes the overview to a scratch file and changes no code. Does not review code quality or raise findings — use code-review for auditing changes or post-code-review-to-pr for posting them. Does not produce durable feature or system documentation — use project-documentation. Does not assess architecture or structural risk — use architectural-analysis. Does not diagnose bugs or root-cause failures — use investigate. Does not pace a person through the code one step at a time in conversation — use code-walkthrough.

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

Performs a gap analysis between two artifacts (a current state and a desired state) and produces a plain-language, stakeholder-readable report indexed by stable gap IDs. Use when the user wants to compare, evaluate, audit, or reconcile one artifact against another. Does not investigate runtime bugs — use investigate. Does not assess module-level architecture — use architectural-analysis. Does not research open-ended options with no second artifact to compare against — use research.

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

Surfaces Han's shared standard for explaining technical work to a reader who will not implement it into the calling skill's own context, so the caller writes its escalations, confirmation turns, and stops as a concrete outcome the reader could observe rather than as a mechanism. Use when a skill is about to ask a person a question, stop for an input, or explain a technical consequence to someone who will not open the code. Governs what a run says to a person in a turn, where readability-guidance governs the shape of a written deliverable. Runs in the caller's context and hands control straight back; it does not produce a deliverable of its own, rewrite anything, or judge the caller's work. Carries guidance only and adds no self-check step.

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

OI-3 spike harness — heavy consumer skill, FORKED arm. Builds an incident post-mortem and sources the readability standard mid-workflow via a forked (context fork) guidance skill. Use only when explicitly invoked by the spike harness with a TRIAL_ID and data path.

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

OI-3 spike harness — heavy consumer skill, BASELINE arm. Builds an incident post-mortem and sources the readability standard mid-workflow by reading a file directly, with NO Skill-tool call. Use only when explicitly invoked by the spike harness with a TRIAL_ID and data path.

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

Owns platform splits for Compose Multiplatform apps: places declarations in commonMain, chooses expect/actual vs interface plus DI, wires host adapters and ports, and validates iOS/Swift interop, desktop and web targets, and platform lifecycle. Use when touching commonMain, expect, actual, iosMain, Swift, SKIE, Flow to Swift, desktop, wasm, web target, or platform-specific code. Do NOT use for routing or architecture (compose-architecture), feature slices (compose-feature), composables or resources (compose-ui), repositories or persistence (compose-data), or Gradle target setup (compose-project).

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

Search oip-visual-v2 for traceable prompt-image pairs and open local result galleries. Use when finding, inspecting, comparing, browsing, or copying real image-generation references or exact source prompts. After references are selected, adapt them into a derived bilingual prompt when requested; use img-gen-taste first when the visual direction is still unclear.

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