「community」の検索結果

Build, deploy, and maintain applications on Hugging Face Spaces — Gradio / Docker / Static SDKs, ZeroGPU and dedicated hardware, model loading, debugging, buckets, inference providers, community grants. Use whenever the user asks to create or host an app on Hugging Face, port code onto ZeroGPU, fix a Space that won't build or run, or otherwise work with `hf spaces …`, `@spaces.GPU`, Space README frontmatter, or the `spaces` Python package.

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

Expert en developer advocacy (communauté, contenu, docs, demos, feedback loop, métriques)

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

Expert en écosystème d'agents IA (plugins, extensions, thèmes, communauté, contributions, gouvernance)

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

Search and analyze Reddit discussions for market research, product feedback, and community insights using Xpoz. Use when asked to "search Reddit", "what does Reddit think about X", "Reddit feedback on X", "subreddit analysis", or "Reddit market research".

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

Use this skill whenever the user asks to inspect JoCoHunt, 조코헌트, jocohunt.jocoding.io products, ideas, rankings, makers, public security headers, or wants a CLI workflow for the Korean builder community. It runs the local `jocohunt` Go CLI, including authenticated product submission when explicitly requested.

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

Discuss a community-edition product requirement with the user, draft a bilingual (Chinese + English) PRD for review, then — after explicit user approval — create the English-only issue on GitHub (<OWNER/REPO>). Use whenever the user wants to turn a requirement (from a Feishu doc, a meeting note, a customer ask, or a rough idea) into a GitHub issue. Triggers on phrases like "create requirement doc", "create a requirement", "put this requirement on GitHub", "create new feature issue", "draft an issue for...", or anytime the user describes a product feature/improvement they want tracked. The format is opinionated (Background / Goal / Spec / Verification / Related, NO implementation details, draft shown bilingually for human review, issue itself written in English only).

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

Shared foundation for all human-voice writing skills. Load before any profession-specific skill. Contains: burstiness principle, perplexity principle, soul injection techniques, community-discovered AI patterns with sources, additional core patterns, banned AI vocabulary, and scoring rubric.

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

To access Anthropic's official brand identity and style resources, use this skill.

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

Finish an existing Japanese creator, challenge, comeback, vlog, or community-building vertical social rough cut as an evidence-grounded short-form story. Use for strong opening declarations, identity and struggle arcs, crisis-to-goal recovery, multi-source B-roll and evidence stills, emotional typography, semantic punch-ins, pinned SFX, dialogue-first audio, platform-added music delivery, and creator-short retention QA.

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

Installs, configures, and tunes Snort 3 intrusion detection system to monitor network traffic for malicious activity using custom and community rulesets, preprocessors, and alert output plugins on authorized network segments.

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

Conduct internal Active Directory reconnaissance using BloodHound Community Edition to map attack paths, identify privilege escalation chains, and discover misconfigurations in domain environments.

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

Builds vendor-agnostic detection rules using the Sigma rule format for threat detection across SIEM platforms including Splunk, Elastic, and Microsoft Sentinel. Use when creating portable detection logic from threat intelligence, mapping rules to MITRE ATT&CK techniques, or converting community Sigma rules into platform-specific queries using sigmac or pySigma backends.

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

Authors reproducible Nextflow DSL2 pipelines built on reactive dataflow, where processes communicate only through channels and execution order is not guaranteed. Use when deciding channel/dataflow (Nextflow) vs rule-based (Snakemake) authoring; wiring queue vs value channels and fixing shared-reference exhaustion with .first(); composing DSL2 modules and subworkflows with take/main/emit; selecting container/conda profiles and pinning images by digest for portability across local/SLURM/LSF/AWS Batch/Google Batch/Kubernetes executors; diagnosing why -resume misses the cache (nondeterministic input order, mtime on network filesystems, mutable :latest tags) with cache 'lenient' and -dump-hashes; managing work/ vs publishDir and dynamic retry escalation; and choosing whether to adopt an nf-core community pipeline or author from scratch.

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

Stellar standards, ecosystem, and reference. Covers SEPs (Stellar Ecosystem Proposals), CAPs (Core Advancement Proposals), and a quick map for picking the right standard for wallets, anchors, payments, deposits/withdrawals, federation, deep links, and KYC. Also bundles ecosystem references (DeFi protocols, dev tools, wallets, infra, community projects), curated documentation links, and MCP servers (live tools such as Raven). Use when you need to know which SEP applies, or want a starting point for ecosystem integrations, official docs, or live MCP tooling.

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

Draft Stellar Community Fund Build Award applications interactively. Use when helping teams write their SCF submission — walks through project description, Stellar integration rationale, technical architecture, team section, deliverables, budget, and traction evidence. Produces a complete draft aligned with what funded projects look like.

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

Review Stellar Community Fund (SCF) Build Award applications. Use when evaluating SCF submissions, covering project fit assessment, technical architecture evaluation, team readiness, traction validation, budget analysis, and funding recommendations.

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

App Router の Server Component でクライアント専用APIを使っていないか確認する。

Detects tables created without ROW LEVEL SECURITY enabled, over-permissive policies (USING (true) / WITH CHECK (true) without owner conditions), and service_role key exposure in client code.

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

Checks Tailwind utility class hygiene at the syntax level: arbitrary-value overuse that bypasses the theme scale, conflicting/duplicate utilities on one element, and hardcoded arbitrary colors that should use design tokens.

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

legacy workaround を避け、semantic HTML / Web Platform Native API / modern CSS の利用機会を提示する。

画像・スクリプト・スタイル・interaction 変更が LCP / INP / CLS / リソースコストに与える影響を suggestion で提示する。

複数の AI / 人間レビュー結果 (review-self / review-external / findings-pool) を統合し、実在性・重大度・対応優先度・merge 可否を検証する。

新しい Web API / CSS の利用追加に対し、Baseline 状態とブラウザ互換性 / progressive enhancement の有無を suggestion で示す。

キーボード操作 / focus 管理 / 動的コンテンツ更新 / ARIA role / フォームの自動遷移など、インタラクティブ UI のアクセシビリティ観点を suggestion で提示する。