「writing」の検索結果

Use when writing, reviewing, or refactoring Rust code. Covers ownership, borrowing, error handling, async patterns, API design, memory optimization, performance, testing, and common anti-patterns. Targets Rust 1.80+ and Edition 2024. Invoke with /rust-core.

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

Use when doing structural code search and rewriting - ast-grep linting, refactoring, multi-language patterns

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

Use when writing or reviewing functions, classes, naming, or non-trivial logic (≥3 lines)

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

Use when writing, reviewing, or changing build scripts, CI workflows, deploy pipelines, repo setup, or evaluating a new tool/dependency

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

Use when writing or reviewing error handling, floating-point math, concurrent code, remote calls, singletons/globals, hot-path data structures, or high-volume log statements

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

Use when writing or reviewing code that parses user input, builds SQL/shell commands, handles secrets/credentials, hashes passwords, changes auth checks, deserializes untrusted data, or constructs paths/URLs from input

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

Use when writing or reviewing request handlers, RPCs, or background jobs for production; adding tracing, metrics, or structured-log calls; or making diagnosability decisions

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

说明如何读取 IELTS Buddy 浏览器写作练习的不可变版本与结构化批改结果；不定义本地批改方法。

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

Frappe-native SQL and ORM guidance for `frappe.db`, Query Builder, `tab{DocType}` tables, permission-sensitive queries, and raw SQL review. Use when writing or reviewing database access in Frappe.

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

React Testing Library — query hierarchy, userEvent, async utilities, renderHook, custom render with providers. Load when writing or reviewing tests that render React components or hooks.

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

Vue Test Utils — mount vs shallowMount, the wrapper API, awaiting DOM updates, flushPromises, testing composables, and the global mounting options. Load when writing or reviewing tests that mount Vue components.

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

SolidJS fine-grained reactivity — signals, effects, memos, stores, resources, control-flow components. Load when writing Solid components or reactive state.

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

Svelte 5 runes — $state, $derived, $effect, $props, $bindable, snippets, callback props, context. Load when writing Svelte 5 components or reactive modules.

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

Vue 3 Composition API — reactivity primitives, composables, lifecycle, the 3.4+ and 3.5+ macros. Load when writing Vue 3 components or composables.

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

Angular 17–19 standalone components, signals, built-in control flow, inject() DI, the resource API. Load when writing or migrating Angular components.

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

BLE scanning/connecting/GATT operations with react-native-ble-plx, NFC tag reading/writing with react-native-nfc-manager, permissions, background mode, battery-efficient patterns

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

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 writing or editing Storybook MDX docs (*.mdx) — the two-tab Overview/Implementation structure, story-backed `<Source>` examples, and doc table guidelines.

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

Use when building or styling a component in libs/ui-react or libs/ui-rnative — the cross-platform styling principles, plus routing to the platform mechanics: Tailwind + cva + cn on web, useStyleSheet + themeJS + lx on React Native. Load this before writing component styles.

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

Phase 2 of the feature-pipeline suite. Use this after /fp-explore has filed issues and printed the M1 stop hook — when you need to turn a set of filed GitHub issues into an approved implementation plan and a draft PR. Triggers on: "plan the fix", "create the branch and PR", "draft the implementation plan", "ready to plan", "fp-plan", "next step after explore", "convert issues to a plan", "plan phase". Reads issueNumbers from state, writes a Problem Statement, opens a feature branch + draft PR, spawns a HEAVIER sub-agent for the numbered plan, and blocks on explicit user approval before writing plan to state. Does NOT write any code — that is /fp-implement.

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

Publish finished creatives as live Meta (Facebook/Instagram) ads via the Meta Marketing API, plus research and ad-copy support. Uploads an image or video, builds a multi-variant creative (5 bodies / 5 titles / 3 descriptions in an asset feed), and creates a PAUSED ad in an existing ad set. Also pulls top-performing ads (ranked by ROAS) and competitor ads from the Ad Library to inform copy. Use when the user asks to deploy / publish / launch a creative as a Meta or Facebook ad, build a Meta ad, push a video or image into an ad set, pull their top ads, or research competitor ads. Not for generating creative (use the image/video skills) and not for writing ad-table rows.

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

Revise an already accepted article, essay, paper, statement, or manuscript under strict minimal-change constraints while still satisfying reviewer comments, supervisor feedback, or requested edits. Use when the user asks for minimal edits, smallest necessary changes, preserve the current voice, keep the existing style, avoid broad rewriting, or implement requested revisions without unnecessary polishing.

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

Replace sentence-by-sentence revised or paraphrased text back into an original paper or document while preserving the original formatting, typography, paragraph settings, citation layout, and document conventions as the source of truth. Use when the user provides revised text that maps back to original sentences, paragraphs, sections, or the whole document, but may also contain clear local sentence merges or splits, and asks to replace it back into the source, keep the original formatting, do sentence-by-sentence replacement, preserve original formatting, or only swap wording without rewriting the document. Only allow minimal edits to the rewritten text when fixing citation formatting, restoring protected original content, restoring the original person reference, or minimally splitting/merging text back into original sentence slots; otherwise do not improve grammar, style, logic, or wording.

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

Plan a feature before writing any code. Use this skill at the START of non-trivial feature work — when the user says they want to "add", "build", "implement", "create", "develop", or "ship" a feature, endpoint, component, page, service, or capability. Especially trigger when the user's prompt is short or under-specified ("add a dashboard", "build an auth flow", "let's do user activity reports") — those need planning, not direct execution. The skill walks through requirements clarification, codebase exploration, sketches a Mermaid architecture/flow diagram of the proposed design, and produces a plan.md document the user can hand off to a fresh AI session for execution. Skip only when the change is genuinely trivial (typo fixes, single-line tweaks, renames). When in doubt, plan.

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