4,137 件 ・ 関連度順
概要と使いどころ
Tutorial patterns for documentation - learning-oriented guides that teach through guided doing. Use when writing a tutorial, learning guide, getting-started or onboarding guide, beginner/introductory guide, or any learn-by-doing hands-on guide. Builds on the docs-style core writing principles.
日本語の概要は準備中です。原文の説明を表示しています。
Use when writing or formatting an ADR document using the MADR template, applying Definition of Done (E.C.A.D.R.) criteria, or verifying ADR completeness. Triggers on "write the ADR", "format as MADR", "check ADR quality", "mark gaps in ADR". Also triggers when a decision has been extracted and needs to become a document. Does NOT extract decisions from conversations (use adr-decision-extraction) or orchestrate the full extract-confirm-write workflow (use write-adr).
日本語の概要は準備中です。原文の説明を表示しています。
Explanation documentation patterns for understanding-oriented content - conceptual guides that explain why things work the way they do. Use when writing an explanation doc, conceptual guide, understanding/background doc, design rationale, or architecture explanation, or when asked how/why something works. Builds on the docs-style core writing principles.
日本語の概要は準備中です。原文の説明を表示しています。
Core technical documentation writing principles for voice, tone, structure, and LLM-friendly patterns. Use when writing or reviewing any documentation.
日本語の概要は準備中です。原文の説明を表示しています。
Use when you need to mine a conversation, session transcript, or design discussion for architectural decisions before writing ADRs. Identifies problem-solution pairs, trade-off debates, technology choices, and explicit "[ADR]" tags. Triggers on "what decisions did we make", "extract decisions from this chat", "find the choices in our discussion", or "summarize architectural decisions". Also useful after long planning sessions to capture decisions that were made implicitly. Does NOT write ADR documents — use adr-writing or write-adr for that.
日本語の概要は準備中です。原文の説明を表示しています。
Klare, überprüfbare Website-Texte für eine definierte Zielgruppe entwerfen und überarbeiten. Nutze diesen Skill für Landingpages, Startseiten, Produkt- und Preisseiten, Überschriften, Handlungsaufforderungen, Nachweisabschnitte und die Überarbeitung vorhandener Texte. Führt ein Aussageverzeichnis, verbindet Fähigkeit, Wirkung und Beleg, erhält Einschränkungen statt sie zu glätten und verzichtet auf falsche Dringlichkeit, erfundene Referenzen und manipulative Muster. Achtet auf Anrede, Preisangaben, Rechte an Zitaten und Logos sowie Barrierefreiheit. Standard ist ein Entwurf im Chat, keine Veröffentlichung.
日本語の概要は準備中です。原文の説明を表示しています。
Expert-level insurance systems, underwriting, claims processing, actuarial analysis, risk assessment, and insurtech solutions
日本語の概要は準備中です。原文の説明を表示しています。
AI-powered insights, UX copywriting standards, and user experience guidelines for vehicle insurance platform. Use when designing insight panels, writing user-facing copy, implementing status messages, creating onboarding flows, or improving accessibility. Covers tone standards, interactive patterns, error messages, and empty states.
日本語の概要は準備中です。原文の説明を表示しています。
Proof writing and verification techniques for mathematical reasoning. Covers 13 proof strategies with canonical worked examples — direct, contrapositive, contradiction, cases, WLOG, vacuous/trivial, biconditional, counterexample, existence (constructive and non-constructive), uniqueness, induction (weak, strong, structural), pigeonhole/double-counting, and diagonal argument/invariants. Use when writing, verifying, or selecting proof strategies for any mathematical claim.
日本語の概要は準備中です。原文の説明を表示しています。
Bloom's Taxonomy of Educational Objectives and mastery learning as practical instructional design tools. Covers the six cognitive levels (remember, understand, apply, analyze, evaluate, create), the revised 2001 taxonomy, the knowledge dimension, mastery learning loops, formative vs. summative assessment, and the writing of learning objectives that are both specific and verifiable. Use when designing lessons, writing objectives, building assessments, or diagnosing why a learner is stuck at one cognitive level.
日本語の概要は準備中です。原文の説明を表示しています。
Contrapuntal writing and analysis covering species counterpoint, fugue structure, canon types, and imitative techniques. Covers Fux's five species, cantus firmus construction, consonance and dissonance treatment, invertible counterpoint, fugue anatomy (subject, answer, countersubject, episode, stretto), canon varieties, and contrapuntal practice from Palestrina through Shostakovich. Use when writing or analyzing counterpoint, studying fugue structure, or understanding the linear dimension of polyphonic music.
日本語の概要は準備中です。原文の説明を表示しています。
Engineering design cycle covering requirements elicitation, specifications writing, constraint identification, iterative prototyping, and design communication. Spans the full loop from problem definition through ideation, analysis, prototyping, testing, and redesign. Includes morphological charts, TRIZ, Pugh matrices, design reviews, and the distinction between functional and non-functional requirements. Use when framing engineering problems, generating design alternatives, writing specifications, or running design reviews.
日本語の概要は準備中です。原文の説明を表示しています。
当用户需要从零写一篇完整的销售型文案，或需要诊断一篇已有文案"为什么不卖货"时，调用此 skill。它是元框架，统领标题抓眼球、激发购买欲、赢得信任、引导马上下单四个不可跳过的步骤，并负责组合调度其他子 skill。当用户只需要优化某个局部环节（如只想写好标题）时，不调用此 skill，而是直接调用对应的子 skill。关键触发信号：用户提到"写文案卖货""文案转化率低""帮我写一篇推文/详情页/广告""文案不知道哪里出了问题"。
日本語の概要は準備中です。原文の説明を表示しています。
Writing effective code documentation - API docs, README files, inline comments, and technical guides. Use for documenting codebases, APIs, or writing developer guides.
日本語の概要は準備中です。原文の説明を表示しています。
Assists in writing high-quality content by conducting research, adding citations, improving hooks, iterating on outlines, and providing real-time feedback on each section. Transforms your writing process from solo effort to collaborative partnership.
日本語の概要は準備中です。原文の説明を表示しています。
Categorical Rewriting: Triad 4 (World Transformation)
日本語の概要は準備中です。原文の説明を表示しています。
Bridge layer connecting AlgebraicJulia/Catlab.jl to plurigrid/asi. Wires ACSets (attributed C-sets), wiring diagrams, decorated cospans, and the AlgebraicJulia ecosystem (AlgebraicDynamics, AlgebraicPetri, AlgebraicRewriting, Decapodes) into the ASI skill graph. ACSets generalize relational databases with categorical semantics; every diagram, network, and model in the ecosystem is an ACSet.
日本語の概要は準備中です。原文の説明を表示しています。
Category-theoretic graph rewriting with DPO, SPO, and SqPO pushouts for C-Sets. Declarative transformation of acset data structures.
日本語の概要は準備中です。原文の説明を表示しています。
When the user wants to edit, review, or improve existing marketing copy. Also use when the user mentions 'edit this copy,' 'review my copy,' 'copy feedback,' 'proofread,' 'polish this,' 'make this better,' 'copy sweep,' 'tighten this up,' 'this reads awkwardly,' 'clean up this text,' 'too wordy,' or 'sharpen the messaging.' Use this when the user already has copy and wants it improved rather than rewritten from scratch. For writing new copy, see copywriting.
日本語の概要は準備中です。原文の説明を表示しています。
Audits a methods section against a 45-item reporting checklist synthesized from the APSA Experimental Section rubric, JARS-Quant, CONSORT, and DA-RT, covering pre-registration, recruitment, randomization and treatments, sample flow and attrition, sample-size justification, three-tier results labeling, conjoint reporting, validity, and open-science infrastructure. Use when checking whether a methods section reports enough, preparing a submission or replication archive, asking what CONSORT, JARS, or DA-RT require, or documenting a deviation from a pre-analysis plan. Writing that plan before data collection goes to pre-registration-writing.
日本語の概要は準備中です。原文の説明を表示しています。
Comprehensive UI design guidance based on Refactoring UI principles covering design personality, color theory, layout strategy, visual hierarchy, typography, spacing, mobile-first responsive design, and writing copy that doesn't read like AI wrote it. Use this skill whenever the user is creating new pages, building components, making design additions or changes, reviewing UI code, asking about design decisions (colors, fonts, spacing, layout), writing or editing interface copy, or discussing visual improvements. Trigger for any design-related conversation including "how should this look", "what color", "font size", "spacing", "layout", "responsive", "mobile", "this copy", "headline", "button text", "microcopy", or when reviewing/critiquing existing interfaces.
日本語の概要は準備中です。原文の説明を表示しています。
Medical/scientific paper writing workflow skill. Manages the full pipeline from literature search to submission-ready manuscript. Creates and manages a project directory with IMRAD-format section files, literature matrix, reference management, and quality checklists. Supports both English and Japanese papers. Triggers: 'write paper', 'paper-write', 'start manuscript', '論文を書く', '論文執筆', '論文プロジェクト', 'manuscript', 'research paper', '原稿作成'.
How to write JSDoc (/** */) and inline (//) comments in the Astro codebase, for contributors reading the source — not end users. Use whenever writing or editing comments in .ts/.js source, including comments added incidentally while fixing bugs or building features. Does not cover the @docs-generated config/error reference.
日本語の概要は準備中です。原文の説明を表示しています。
Write tests for untested OSS code as a standalone contribution. Identifies coverage gaps, studies the repo's test conventions, and guides the user through writing tests that match existing patterns. Use when contributing tests to an open source repo, looking for a low-risk first contribution, or improving test coverage. Not for writing tests alongside a bug fix — use oss-contribute for that.
日本語の概要は準備中です。原文の説明を表示しています。