Expert en technologies éducatives avancées (LMS, MOOC, adaptive learning, gamification, analytics, accessibilité)
日本語の概要は準備中です。原文の説明を表示しています。
3,752 件 ・ 関連度順
概要と使いどころ
Expert en technologies éducatives avancées (LMS, MOOC, adaptive learning, gamification, analytics, accessibilité)
日本語の概要は準備中です。原文の説明を表示しています。
Expert en technologies éducatives avancées (LMS, MOOC, adaptive learning, AI tutoring, assessment, DZ context)
日本語の概要は準備中です。原文の説明を表示しています。
EdTech Specialist IA — Expert en technologies éducatives (LMS, SCORM, adaptive learning, gamification, assessment)
日本語の概要は準備中です。原文の説明を表示しています。
Expert en gouvernance d'entreprise (board management, compliance, DZ regulations, OHADA)
日本語の概要は準備中です。原文の説明を表示しています。
Accessibility Compliance Specialist IA — Expert en conformité accessibilité (ADA, Section 508, RGAA, EN 301 549, WCAG legal)
日本語の概要は準備中です。原文の説明を表示しています。
Expert en RAG agentique (retrieval multi-étapes, self-query, chunking adaptatif, tool-augmented generation)
日本語の概要は準備中です。原文の説明を表示しています。
Expert en localisation d'agents IA (i18n, l10n, RTL, adaptation culturelle, arabe DZ/darija)
日本語の概要は準備中です。原文の説明を表示しています。
Guides migration of .NET Framework Thread.Abort usage to cooperative cancellation in modern .NET. USE FOR: modernizing code that calls Thread.Abort, catching ThreadAbortException, replacing Thread.ResetAbort, replacing Thread.Interrupt for thread termination, resolving PlatformNotSupportedException or SYSLIB0006 after retargeting to .NET 6+, migrating ASP.NET Response.End or Response.Redirect(url, true) which internally call Thread.Abort. DO NOT USE FOR: code that only uses Thread.Join, Thread.Sleep, or Thread.Start without any abort, interrupt, or ThreadAbortException usage — these APIs work identically in modern .NET and need no migration. Also not for projects staying on .NET Framework, or Thread.Abort usage inside third-party libraries you do not control.
日本語の概要は準備中です。原文の説明を表示しています。
Patterns for managing MSBuild item groups: Include/Remove/Update semantics, item metadata, batching with %(Metadata), transforms, per-item filtering, and cross-product batching pitfalls. Only activate in MSBuild/.NET build context. USE FOR: diagnosing and fixing item group anti-patterns in .csproj files, reviewing item management for correctness, fixing CS2002 duplicate file warnings from SDK globbing, fixing targets that run more times than expected due to cross-product batching, fixing Include vs Update misuse on SDK-globbed items, fixing FileWrites registration for generated file clean support, moving generated files to IntermediateOutputPath. DO NOT USE FOR: target chain architecture (use target-authoring), property patterns (use property-patterns), incrementality (use incremental-build), general anti-patterns (use msbuild-antipatterns), non-MSBuild build systems.
日本語の概要は準備中です。原文の説明を表示しています。
Scan an iOS/macOS Xcode project for common App Store rejection patterns before submission. Use when preparing an app for App Store review, after receiving a rejection from Apple, or when auditing metadata, subscriptions, privacy manifests, entitlements, or design compliance. Integrates with the asc CLI for metadata inspection.
日本語の概要は準備中です。原文の説明を表示しています。
Automatically translate and sync App Store metadata (description, keywords, what's new, subtitle) to multiple languages using LLM translation and asc CLI. Use when asked to localize an app's App Store listing, translate app descriptions, or add new languages to App Store Connect.
日本語の概要は準備中です。原文の説明を表示しています。
Generate engaging, localized App Store release notes (What's New) from git log, bullet points, or free text using canonical metadata under `./metadata`. Optionally pairs with promotional text updates.
日本語の概要は準備中です。原文の説明を表示しています。
When the user wants to discover, evaluate, or prioritize App Store keywords. Also use when the user mentions "keyword research", "find keywords", "search volume", "keyword difficulty", "keyword ideas", or "what keywords should I target". For implementing keywords into metadata, see metadata-optimization. For auditing current keyword performance, see aso-audit.
日本語の概要は準備中です。原文の説明を表示しています。
When the user wants to A/B test App Store product page elements to improve conversion rate. Also use when the user mentions "A/B test", "product page optimization", "test my screenshots", "test my icon", "conversion rate optimization", "CPP", or "custom product pages". For screenshot design, see screenshot-optimization. For metadata optimization, see metadata-optimization.
日本語の概要は準備中です。原文の説明を表示しています。
When the user wants a full ASO health audit, review their App Store listing quality, or diagnose why their app isn't ranking. Also use when the user mentions "ASO audit", "ASO score", "why am I not ranking", "listing review", or "optimize my app store page". For keyword-specific research, see keyword-research. For metadata writing, see metadata-optimization.
日本語の概要は準備中です。原文の説明を表示しています。
When the user wants to analyze competitors' App Store strategy, find keyword gaps, or understand competitive positioning. Also use when the user mentions "competitor analysis", "competitive research", "keyword gap", "what are my competitors doing", or "compare my app to". For keyword-specific research, see keyword-research. For metadata writing, see metadata-optimization.
日本語の概要は準備中です。原文の説明を表示しています。
Use this skill when creating routes, pages, layouts, or deciding Server vs Client Component boundaries in Next.js 16 App Router. Trigger words: ルーティング, ページ追加, layout, route, app router, Server Component, use client, dynamic route, generateMetadata.
Improves typography by fixing font choices, hierarchy, sizing, weight, and readability so text feels intentional. Use when the user mentions fonts, type, readability, text hierarchy, sizing looks off, or wants more polished, intentional typography.
日本語の概要は準備中です。原文の説明を表示しています。
Use when: 'intake this repo/skill', 'evaluate external skill', 'should we adopt X', a candidate repo URL plus an adoption question, or any external skill/workflow/tool surfaces as a possible fit for Agistra. Structured front-door evaluation of external skills, workflows, and similar capability artifacts before any install, promotion, or adaptation decision. Ends in exactly one classification: Install candidate, Adapt concept, or Reject. Never install first — intake first.
日本語の概要は準備中です。原文の説明を表示しています。
Vendor (copy-import) a single external Claude Code skill into your own skills repo correctly — with license compliance and full provenance/attribution. Deterministic, idempotent primitive: given an upstream ref (owner/repo/path@sha or a GitHub URL) it fetches the skill, detects and gates on the license, copies the folder, injects a provenance frontmatter block (license + metadata: author/source/upstream_commit/vendored_at/provenance), ships the upstream LICENSE, adds a ## Credits section, and records a CREDITS.md ledger entry. Use when the user asks to "vendor a skill", "import a skill", "clone a skill", "borrow someone's skill", "add an external skill with attribution/credit", or スキルを取り込む / vendoring / 他人のスキルを自分のリポに取り込む. This is the import primitive that a skill-scout/curator orchestrator calls; it does NOT discover or evaluate — it correctly imports ONE skill you already chose.
Kent Beck/t-wada 流の TDD でテストコードとプロダクションコードを実装する。Triggers on: '/tdd-impl', 'TDDで実装', 'TDD実装'
Curate Busabase training examples, create immutable dataset snapshots, run reproducible LoRA or QLoRA fine-tunes on a local Apple Silicon Mac with MLX-LM, compare the untouched baseline and adapter on locked evaluations, and register approved adapters. Use when the user wants to train, fine-tune, evaluate, compare, promote, or manage a local language model with Busabase as the workflow source of truth. Do not use for RAG-only knowledge retrieval, cloud training, or training a foundation model from scratch.
日本語の概要は準備中です。原文の説明を表示しています。
Build and verify Adaptive navbar for Mobile-first interface with Bootstrap v5.3 using a working semantic implementation, responsive RTL/LTR behavior, theme tokens, test plan and design verification.
日本語の概要は準備中です。原文の説明を表示しています。
Build and verify Adaptive navbar for Data-heavy application with Bootstrap v5.3 using a working semantic implementation, responsive RTL/LTR behavior, theme tokens, test plan and design verification.
日本語の概要は準備中です。原文の説明を表示しています。