「ada」の検索結果

当用户要把教材/考纲/讲义/某领域知识加工成 AI 苏格拉底老师能拿去上课的教学蓝本（pure-blueprint）或一本给人读的流畅教材（human-readable，AI 也能直接教）时使用。适用任何学科，有教师用书可针对应试。触发词："造一本教学蓝本/做一本 XX 教材/按这套方法写一本书/复刻这个 skill 的写法"。

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

Use when website or web app UI work needs practical design guidance for hierarchy, layout, readability, responsiveness, and interaction quality.

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

Creates demand generation campaigns, optimizes paid ad spend across LinkedIn, Google, and Meta, develops SEO strategies, and structures partnership programs for Series A+ startups scaling internationally. Use when planning marketing strategy, growth marketing, advertising campaigns, PPC optimization, lead generation, pipeline generation, or startup marketing budgets. Covers multi-channel acquisition (Google Ads, LinkedIn Ads, Meta Ads), CAC analysis, MQL/SQL workflows, attribution modeling, technical SEO, and co-marketing partnerships for hybrid PLG/Sales-Led motions in EU/US/Canada markets.

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

Use when existing copy needs tightening for clarity, accuracy, tone consistency, or executive readability without changing the underlying message.

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

Adapt and audit a PFC 5.0 asphalt Marshall stability/flow simulation using the external fistPkg26 dc.fis two-head controller as a starting skeleton; use for curved-head geometry, PFC5 wall/contact kinematics, load-deformation histories, peak stability, edition-specific flow processing, and validation against laboratory data.

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

Build PFC 5.0 asphalt-mixture specimens with explicit aggregate objects, a declared homogenized-mastic or fine-particle abstraction, residual air voids, measured gradation conversion, contact-pair assignment, compaction, equilibrium, and mass-volume closure; use before Marshall, rutting, creep, or strength tests.

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

Writes expert academic paper summaries for social science research, particularly political science and applied statistics. Use when asked to summarize, review, or create a reading summary of an academic paper, PDF, or research article. Accepts a file (PDF or text format) or a directory of papers. Produces a structured markdown summary — approximately 400–600 words — covering primary contributions, major questions and answers with point estimates, methods and data, and limitations and robustness. Includes BibTeX citation retrieved from Google Scholar and keyword metadata.

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

"Apply organizational ecology (Hannan and Freeman) to analyze population-level dynamics of organizational founding, failure, and selection. Use this skill when the user needs to explain industry-level patterns of birth and death rates, analyze structural inertia and liabilities of newness or aging, evaluate why adaptation is rare relative to selection, or when they ask 'why do most startups fail', 'why is this industry dominated by old firms', or 'why do organizations resist change despite environmental pressure'.".

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

"Apply Complex Adaptive Systems theory to analyze phenomena exhibiting emergence, self-organization, co-evolution, and edge-of-chaos dynamics. Use this skill when the user needs to understand why a system behaves unpredictably despite known components, model agent-based interactions that produce emergent outcomes, analyze fitness landscapes, or when they ask 'why does this system behave in ways no one designed', 'how do local interactions create global patterns', or 'why do small changes sometimes cause massive system shifts'.".

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

Draft blog posts, social media, email newsletters, landing pages, press releases, and case studies with channel-specific formatting and SEO recommendations. Use when writing any marketing content, when you need headline or subject line options, or when adapting a message for a specific platform, audience, and brand voice.

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

"Analyze business cycle phases (expansion, peak, contraction, trough) and their implications for business strategy and policy response. Use this skill when the user needs to identify the current economic phase, anticipate cyclical turning points, or adapt business strategy to macroeconomic cycles — even if they say 'are we heading into a recession', 'how should we prepare for a downturn', or 'when will the economy recover'.".

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

"Develop e-commerce strategy for Southeast Asian markets including platform selection, payment infrastructure, logistics challenges, and localization requirements. Use this skill when the user is expanding e-commerce to SEA, evaluating Shopee vs Lazada vs Tokopedia, or needs to understand SEA market differences — even if they say 'sell to Southeast Asia', 'which platform in Vietnam', 'SEA payment methods', or 'cross-border e-commerce in ASEAN'.".

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

Plan deprecation and migration—replacement first, consumer migration, strangler and adapter patterns, zombie code removal. Use when sunsetting APIs, libraries, or legacy modules.

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

Prepare iOS App Store and Google Play submissions—metadata, assets, compliance checks, and release checklist. Use before store upload or review submission.

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

Assess, adapt, and apply specified discussions, feedback, findings, or references to existing project work. Preserve coverage, corrections, and selected intent; judge fit and carry adopted effects through the authorized result. Includes technical review feedback; incidental sources or understanding material without a target-work adoption question need no separate incorporation workflow.

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

Audits whether a machine-readable regelrecht law model is faithful to the LETTER of the wettekst — and strictly separates the wettekst (leading) from the toelichting (Nota/Memorie van Toelichting; explanatory, not a norm). Runs in critical passes per article/lid and detects four deviation classes: toelichting-bleed (a modeled criterion that the letter only states as an open norm, or not at all), missing verbatim elements (a word/condition such as a "tenzij" or a qualifier dropped from the model), wrong legal_basis anchoring (an endpoint hung on a "kapstok"-article while the operative norm lives elsewhere), and verbatim-drift in text: (an ingetrokken/older redaction). Also detects positief-lid vs uitsluitings-lid conflicts and checks the chapeau for an explicit derogation rule ("zo nodig in afwijking van het eerste lid") before judging precedence. Classifies every finding as modelfout (fix), wettekst-gevolg (report, do not fix), or letter-vs-toelichting-question (jurist decides what is leading + revision signal). Use when the user wants to know if a model is "dicht bij de letter", mentions letter vs toelichting/bedoeling, fidelity, "natuurgetrouw", or before trusting feature outcomes.

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

Detects version drift between machine-readable law YAML files and the binding geldende wettekst on wetten.overheid.nl at the YAML's claimed valid_from. Catches the silent failure where authored content lags behind ingevoerde wijzigingen — a YAML dated 2025-01-01 still carrying pre-Stb.-X text. Activate as Step 0 of every regelrecht-stelselanalyse micro-cycle, before any YAML edit. Strict by design: no bypass, no normalization beyond whitespace within a single paragraph; the geldende wettekst is leading and is mirrored verbatim, including errata. Use proactively when starting a stelselanalyse cycle, before harvest/migrate/extend, or when user mentions "drift", "versie", "geldende tekst", or worries that a YAML may be stale relative to wetten.overheid.nl.

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

Review a Go design spec before implementation begins - dispatch a subagent that checks a design doc for completeness, consistency, and idiomatic Go (simplicity, small consumer-defined interfaces, explicit wrapped errors, context propagation). Use when a user has a Go spec to review, asks "is this spec ready?", or is about to implement from a written design. Distilled from spf13/go-skills and adapted to this repo's conventions.

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

Idiomatic Go - package and interface design, error wrapping, table-driven tests, generics, the modern standard library (slices/maps/cmp/errors.Join), current syntax, and logging discipline. Use when writing, reviewing, or refactoring any Go code, especially code drifting toward Java/Spring shapes (deep layer trees, generic repositories, heavy frameworks) - even if the user never says "idiomatic". Distilled from spf13/go-skills and adapted to this repo.

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

Use when research writing, reviews, rebuttals, or related-work planning needs academic evidence. Searches literature, screens candidate papers, audits novelty and missing work, verifies DOI/BibTeX/reference metadata and citation authenticity, and checks whether sources support the stated claims.

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

Use when designing, redrawing, or validating research-paper figures and tables, including Matplotlib plots, LaTeX tables, benchmarks, captions, legends, annotations, color, and typography. Preserves exact evidence and checks rendered PDFs for clipping, overlap, and readability.

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

Build multi-project RAID and RAG views for portfolios, programs, or cross-functional workstreams. Use when PMOs, program managers, or leaders need a real status picture across milestones, dependencies, owners, and escalations. Do not use for a single standup note, one issue ticket, or generic meeting minutes.

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

Write structured job descriptions with clear requirements, responsibilities, and employer value proposition. Follows SHRM BASK competency framework. Adapts tone to employer brand and industry context. Use when creating new positions or updating existing JDs. Do not use for internal performance criteria or career ladder definitions.

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

Use when implementing a PlayCanvas feature the project does not use yet, to find and adapt the official example matching the installed version.

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