「raft」の検索結果

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

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

Cosmic, eldritch, and Lovecraftian horror art direction for Blender with non-Euclidean cues, impossible scale, and incomprehensible forms.

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

Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.

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

Use when reviewing mathematical validity, evidence, reproducibility, figures or a submission draft.

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

检查文稿里的 AI 味和账号语气偏差，包括机器化表达、翻译腔、虚构脆弱感和过度金句。用户问文案是否像 AI 写的、是否像本人说话，或希望降低 AI 痕迹时使用。 English: Check drafts for AI-writing signals and voice mismatch, including robotic phrasing, translation-like prose, fabricated vulnerability, and forced quotable lines. Use when the user wants the copy to sound more human or more like the target account.

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

把账号档案、研究证据、选题卡、成稿、发布数据和复盘结论整理成能长期积累和复用的内容资产。用户要保存生产结果、建立主题地图、复用旧选题或维护长期内容库时使用。 English: Organize account profiles, research evidence, topic cards, drafts, publishing data, and review findings into reusable long-term content assets. Use to archive production work, build a topic map, reuse past ideas, or maintain a content library.

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

把已经确认的选题写成可以直接拍摄或发布的内容，包括选择形式、搭建结构、写口播逐字稿或图文正文，并让产品自然出现。用户要求把选题变成成稿、拍摄稿或发布稿时使用。 English: Turn an approved topic into shoot-ready or publish-ready content by choosing the format, building the structure, writing a spoken script or post, and integrating the product naturally. Use when the user wants a topic developed into a finished draft.

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

从传播心理和受众感受检查成稿是否真正有共鸣，定位受众不明确、主张过多、立场漂移和分享动机不足等问题。用户担心内容不打动人、没流量，或发布前想检查共鸣结构时使用。 English: Review a finished draft for audience resonance and communication psychology, identifying vague audiences, too many claims, shifting positions, and weak sharing motives. Use when content may not connect, may underperform, or needs a pre-publish resonance check.

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

把已经完成并通过质检的 Markdown 内容转换成可粘贴到微信公众号后台的 HTML，并支持选择样式、生成预览和检查粘贴兼容性。用户要制作公众号排版稿或微信发布版本时使用。 English: Convert a finished, quality-checked Markdown draft into HTML that can be pasted into the WeChat Official Accounts editor, with style selection, preview generation, and paste-compatibility checks. Use when the user needs a formatted WeChat publishing version.

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

根据主题、正文或已有标题生成并筛选小红书标题，提供改写和 A/B 方案，同时检查账号调性、真实性以及正文能否兑现标题承诺。用户要起标题、改标题、套用标题模式或检查标题时使用。 English: Generate and filter Xiaohongshu titles from a topic, draft, or existing title, offering rewrites and A/B options while checking voice, truthfulness, and whether the content fulfills the promise. Use to write, improve, pattern-match, or review titles.

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

Guides implementation of EU Standard Contractual Clauses under Commission Decision 2021/914 across all four modules (C2C, C2P, P2P, P2C). Covers clause-by-clause completion, Annex I-III drafting, and SCC module selection. Keywords: SCCs, standard contractual clauses, module selection, data transfers, Annex completion.

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

Guides development of GDPR Article 40-41 codes of conduct for industry sectors including drafting, submission, and monitoring body requirements. Activate when creating industry codes or establishing monitoring bodies. Keywords: codes of conduct, Article 40, Article 41, monitoring body, industry code.

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

Guides EU Code of Conduct adherence under GDPR Articles 40-41 including EDPB approval requirements, monitoring body accreditation, code drafting, adherence declaration, compliance verification, and complaint handling. Covers sector-specific codes, transnational codes, and Art. 40(3) approval by supervisory authorities. Keywords: code of conduct, Article 40, Article 41, EDPB, monitoring body, adherence.

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

Guides privacy audit report writing including executive summary drafting, findings classification (critical, high, medium, low), evidence referencing, root cause analysis documentation, recommendation formulation, management response tracking, and report distribution protocols. Covers report structure from scope definition through appendices and sign-off. Keywords: audit report, findings documentation, executive summary, recommendations, report structure, privacy audit deliverables.

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

Produce a plain-language manual test plan from the context supplied to it — an executive summary, a high-level list of named tests, and a detail section per test with the steps a person follows by hand and the outcomes they should expect. Use when you want to create, draft, generate, or outline a manual test plan, manual QA steps, hands-on verification steps, or an acceptance walkthrough for a feature, change, branch, plan, or PR. When the plan holds more than five tests and at least two natural categories emerge, both the test list and the detail sections are organized under plain-language categories. When nothing in the supplied context can be manually tested, it says so and asks for more context instead of producing a document. Does not analyze code for automated test coverage gaps — use automated-test-planning. Does not write test code — use tdd. Does not review code quality — use code-review. Does not stress-test an existing plan — use iterative-plan-review.

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

Create or update a runbook for an operational scenario — an incident an alert fires for, a recurring scheduled task, or a known failure mode on a live service — using a consistent template. Use when writing, drafting, authoring, or updating a runbook for an alert, incident, on-call procedure, scheduled maintenance, or operational SOP. Applies a YAGNI preflight requiring the scenario to be real before producing the runbook. Does not produce feature or system documentation — use project-documentation. Does not record architectural decisions — use architectural-decision-record. Does not create coding standards — use coding-standard.

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

Builds a new Claude Code skill from scratch through a relentless, evidence-based interview that walks the skill's design tree decision-by-decision — entity fit, use cases, name, description, workflow steps, tools, and progressive-disclosure layout — then reviews the finished skill against the plugin-building guidance and applies every fix it finds. Use when creating, authoring, scaffolding, designing, or drafting a new skill or slash command. Does not build an agent or subagent — use agent-builder. Does not serve, vendor, or refresh the authoring guidance itself — use guidance.

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

Produces a plain-language stakeholder summary from an existing feature specification, for sharing with non-technical stakeholders before implementation kicks off. Use when the user wants to draft a stakeholder summary, executive summary, or business summary of a feature spec or PRD. Does not write the spec itself — use plan-a-feature. Does not sequence the build into phases — use plan-a-phased-build. Does not produce an implementation plan — use plan-implementation.

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

Generate a PR description from the current branch's changes against a GitHub PR, using the gh CLI. Use when writing, drafting, or updating pull request descriptions, PR summaries, or PR bodies. Does not review code or post review comments — use code-review for local review or post-code-review-to-pr for posting a review to GitHub.

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

Produce a standalone test plan by analyzing code for test coverage gaps and edge cases. Use when you need to create, generate, or draft a test plan for a branch, need to analyze test coverage, or need to identify what tests to write for specific files or directories. Does not produce a plain-language plan for a person to run tests by hand — use manual-test-planning for that. Does not write test code — use tdd to implement behavior test-first. Does not refine existing plans — use iterative-plan-review. Does not review code quality, security, or style — use code-review for full code review. Does not evaluate architectural testability or structural coupling — use architectural-analysis for architectural assessment.

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

Builds a new Claude Code agent (subagent) from scratch through a relentless, evidence-based interview that walks the agent's design tree decision-by-decision — entity fit, domain focus and vocabulary, role identity, anti-patterns, description, model tier, tools, and self-containment — then reviews the finished agent against the plugin-building guidance and applies every fix it finds. Use when creating, authoring, scaffolding, designing, or drafting a new agent or subagent. Does not build a skill or slash command — use skill-builder. Does not serve, vendor, or refresh the authoring guidance itself — use guidance.

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

Adds, changes, or reviews a screen, sheet, dialog, or destination slice (endpoint to repository to ViewModel to UI to navigation to DI to tests) in a Compose or CMP project. Use when adding a screen, building a new feature, adding a ViewModel or destination, wiring list/detail or a form screen, scaffolding a slice, or reviewing a feature change. Covers Contract.kt, launchGuarded wiring, SavedStateHandle drafts, the state matrix, and new-feature.sh. Do NOT use for routing or architecture (compose-architecture), pure refactors, Gradle work (compose-project), recomposition or styling (compose-ui), repository or persistence work (compose-data), or expect/actual splits (compose-platform).

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

Cut a Runner production release — bump the workspace version, tag vX.Y.Z, let release.yml build the draft for both platforms, write bilingual release notes (English, with 中文 collapsed in a details block), hand the publish switch to the user, and sweep the shipped work's docs once the release is live

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

Create original short videos using the 手作角色扮演｜分工亮相、道具误伤与集体和解 Creative DNA for MiniMax H3 or Seedance 2.0. Use when the user wants this causal, camera, motion, rhythm, or payoff structure with new subjects and surfaces.

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