「rizin」の検索結果

Applies the analytical and therapeutic philosophy of Ludwig Wittgenstein, 20th-century philosopher of language (Tractatus / Philosophical Investigations). Use this skill when the user is stuck in conceptual confusion, debating semantics, trapped by abstract definitions, or trying to solve a problem that is actually just a linguistic misunderstanding. Trigger this for topics involving the limits of language, meaning as use, logical clarification, or when the user is over-theorizing instead of looking at practical applications. It helps dissolve 'fly-bottle' traps by examining how words are actually used in context.

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

Rewrite existing text so it stops sounding AI-generated. Triggers on "humanize this", "un-ChatGPT it", "doesn't scream LLM", "strip the AI voice", or naming specific AI tells (em dashes, "it's not just X it's Y", "stands as a testament", "thrilled to announce", emoji-headed bullets, LinkedIn cringe). Works on any draft — blog posts, memos, READMEs, essays, PR descriptions — inline or in files. Keeps facts; changes voice. Do NOT use for writing new content, summarizing, translating, or pure-explanation requests with no draft to rewrite.

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

Linearizing nonlinear dynamics around operating points for control design.

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

Drive a local ComfyUI install for image, video, and audio generation via its HTTP API. Use WHENEVER generating, rendering, or editing images/video/audio/hero assets with ComfyUI, Z-Image, Ideogram, FLUX, LTX, Wan, or when building, parameterizing, or running ComfyUI workflows. Covers the API client, workflow JSON format, model patterns, dual/multi-GPU placement, the MCP driver, in-graph Claude nodes, and VRAM coordination.

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

This skill should be used before answering "does Genesis have X", "does Genesis lack X", auditing Genesis capabilities, comparing Genesis to an external system, or reviewing/summarizing the architecture. It routes to the canonical judgment-layer subsystem map so audits start from the map, not from a cold grep. Also fires after changing a subsystem's capabilities, to keep the map current.

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

Builds and reviews desktop apps. Use when choosing a stack, signing or notarizing releases, adding auto-update, or reviewing Electron/Tauri security.

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

Use this when summarizing analysis results, writing reports, documenting experiment outcomes, or presenting model evaluation — including structuring findings in Japanese with conclusions, facts, assumptions, interpretations, and caveats.

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

Produces structured, citation-backed summaries of U.S. insurance policies, endorsements, claims files, and coverage correspondence for coverage analysis and insurance litigation. Use when summarizing policies, declarations, claims files, reservation-of-rights letters, denial letters, or coverage disputes.

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

Produces structured summaries of insurance claims correspondence including coverage letters, reservation of rights (ROR), denial letters, and claim file documents. Extracts policy details, coverage positions, claims chronology, settlement posture, and liability exposure. Use when summarizing claim files, coverage disputes, ROR letters, denial letters, or multi-document insurance correspondence threads.

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

Meta-cognitive and practical strategies for learning any language -- learner autonomy, goal setting, strategy taxonomy (Oxford's SILL framework), memory strategies, cognitive strategies (note-taking, summarizing, analyzing, reasoning), compensation strategies, metacognitive strategies (planning, monitoring, evaluating), affective strategies (managing anxiety, self-encouragement), social strategies (collaboration, questioning, empathy), immersion design, study habit optimization, plateau diagnosis, and motivation maintenance. Use when designing a language learning plan, diagnosing a learner's stuck points, selecting study methods, or building self-directed learning skills.

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

Bench instruments and measurement techniques for electronics — digital multimeter, oscilloscope, logic analyzer, spectrum analyzer, function generator, power supply, and their proper use. Covers probing technique, ground loops, loading effects, trigger modes, FFT mode pitfalls, signal integrity, noise budget analysis, and debugging workflows from "it doesn't work" to "here is the failure mechanism." Use when measuring, debugging, or characterizing any electronic circuit or firmware-hardware interaction.

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

Classical control and system dynamics for engineered systems — feedback and closed-loop control, transfer functions and block diagrams, poles/zeros and stability, time-domain response (rise time, overshoot, settling time), PID controllers and tuning, and frequency response (Bode plots, gain and phase margin). Traces feedback control from the flyball governor to modern controllers. Use when analyzing feedback loops, designing or tuning a PID controller, assessing stability from poles or margins, or characterizing transient response of a dynamic system.

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

Automatically creates user-facing changelogs from git commits by analyzing commit history, categorizing changes, and transforming technical commits into clear, customer-friendly release notes. Turns hours of manual changelog writing into minutes of automated generation.

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

Use when the primary outcome is authoring, rewriting, summarizing, or validating user-facing documentation without implementation comparison or required source attribution, including READMEs, tutorials, API docs, GitLab Markdown, source-faithful summaries, and audience-specific prose.

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

Use when generating weekly GTM performance reports, summarizing pipeline activity, reviewing outreach metrics, or creating executive updates. Triggers: 'weekly report', 'GTM report', 'pipeline review', 'weekly update', 'outreach summary', 'Friday report'.

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

Use when cutting a release, writing a CHANGELOG entry, or summarizing what changed since a tag — when the repo's commits follow (or mostly follow) Conventional Commits and a mechanically-accurate section breakdown beats a model's reading of the diff.

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

Catch insensitive, inconsiderate writing with alex. This CLI tool and Node.js library scans Markdown and plain text for gender-biased, polarizing, or exclusionary language and suggests inclusive alternatives.

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

DevOps patterns: containerization, CI/CD, deployment strategies, monitoring. Use when containerizing apps, setting up pipelines, or deploying services.

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

Structures LPA terms with investment period, harvesting period, key person provisions, and investor governance rights. Use when preparing LPA terms, negotiating fund documents, or summarizing partnership provisions.

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

Structures preliminary transaction terms including price, consideration, conditions, reps/warranties, and indemnification. Use when drafting LOIs, preparing term sheets, or summarizing negotiated deal points.

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

Structured workflow for summarizing code changes after completing tasks. Creates clear, actionable summaries of what was changed, why, and what to verify.

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

Draft a changelog for the next release by summarizing git commits since the last tag. Use only when the user asks to draft release notes, write a changelog entry, or prepare the next version's notes — never trigger automatically.

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

Sustained neutral pattern recognition across systems without urgency or intervention. Maps naturalist field study methodology to AI reasoning: framing the observation target, witnessing with sustained attention, recording patterns, categorizing findings, generating hypotheses, and archiving a pattern library for future reference. Use when a system's behavior is unclear and action would be premature, when debugging an unknown root cause, when a codebase change needs its effects witnessed before further changes, or when auditing own reasoning patterns for biases or recurring errors.

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

Generate a project status report by reading existing artifacts (charter, backlog, sprint plan, WBS), calculating metrics, identifying blockers, and summarizing progress with RAG indicators for schedule, scope, budget, and quality. Use at the end of a sprint or reporting period, when stakeholders request a health update, before steering committee or governance meetings, or when a new blocker or risk materializes mid-project.

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