「entry」の検索結果

Look up EMDB cryo-EM density maps and fitted atomic models via the entry REST API + EBI Search WS. Fetch entry metadata (resolution, method, organism, sample), map download URLs, fitted PDB IDs, and citations. Keyword search via EBI Search. No auth. For atomic coordinates use pdb-database; for AlphaFold predictions use alphafold-database-access.

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

Use when writing, testing, or preparing ANY contribution or pull request to the JSONbored/awesome-claude (HeyClaude) repo — adding a community content entry (agent/MCP server/skill/hook/command/rule/guide/collection/statusline), or making a platform/code change (website, registry package, MCP package, scripts). The repo has two separate review paths: a private, one-shot "HeyClaude submission gate" that decides single-file content PRs, and the shared gittensory-orb bot that posts an advisory readiness/linked-issue comment on platform/code PRs but does not itself merge or close content PRs. Unlike JSONbored/gittensory and JSONbored/metagraphed, a linked issue is OPTIONAL here — do not import their mandatory-linked-issue rule into this repo. Invoke for any "contribute to / open a PR against / submit an entry to / fix a bug in awesome-claude (HeyClaude)" task.

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

Product marketing, positioning, GTM strategy, and competitive intelligence. Includes ICP definition, April Dunford positioning methodology, launch playbooks, competitive battlecards, and international market entry guides. Use when developing positioning, planning product launches, creating messaging, analyzing competitors, entering new markets, enabling sales, or when user mentions product marketing, positioning, GTM, go-to-market, competitive analysis, market entry, or sales enablement.

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

Fix LRU-bounded Flutter/bloc state classes that silently lose insertion-order updates. Use when: (1) a state class uses `Equatable` with a `LinkedHashMap<K, V>` field to preserve insertion order (LRU, MRU, recent-items caches), (2) `Cubit.emit` appears to drop emissions when an existing key is re-inserted or moved to most-recent, (3) LRU eviction evicts the "wrong" entry after a refresh, (4) a test that reports the same key twice and then overflows the cap sees the refreshed entry evicted instead of the oldest. Root cause: Equatable's default map comparison is structural (unordered), so reordering without changing keys/values produces an "equal" state that `Cubit.emit` suppresses.

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

Technical execution timing, entry exit signals, price action analysis, volume profile, market structure, support resistance levels, trend identification, Wyckoff method, auction market theory, trade management timing, position entry exit optimization

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

codeck entry point. Scans local files for materials, shows pipeline dashboard with diagnostic intelligence, guides user to the next step. Use when the user says "codeck", "new deck", "make a presentation", "make a deck", "new slides", "build a presentation", "export", "speech", "script", or wants to start or continue a presentation project. /codeck is the user-facing entry; legacy sub-skills are internal modules.

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

Writes architecture decision records (ADRs) and keeps the rest of a project's documentation true after a change: README, reference comments on public interfaces and the changelog. Use when a user says "write an ADR", "record this decision", "document why we chose X", "set up a decision log", "supersede the old decision", "update the README", "add a changelog entry" or "document this API". Produces records in the Nygard or MADR format, a Keep a Changelog entry, and a script that checks the log for gaps and broken supersession links.

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

Analyze application error logs and monitoring platform exports (Sentry, Datadog, Rollbar) to identify error patterns, duplicates, and severity. Use when someone asks to "audit errors", "analyze exceptions", "find noisy alerts", "deduplicate error groups", or "triage production errors". Parses JSON/CSV error exports and produces categorized reports with root cause analysis.

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

Expert at making systems observable and debuggable. Covers structured logging, metrics collection, distributed tracing, error tracking, and alerting. Knows how to find the needle in the haystack when production breaks at 3 AM. Use when "observability, logging, metrics, tracing, monitoring, error tracking, Sentry, Datadog, OpenTelemetry, debugging production, observability, logging, metrics, tracing, monitoring, sentry, prometheus, opentelemetry" mentioned.

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

Use when setting up a new or existing project on @drincs/pixi-vn, wiring the main.ts entry point, or calling the top-level Game API (Game.init, Game.start, Game.onEnd, Game.addOnError, Game.onNavigate, Game.clear) — this is the entry point every Pixi'VN project needs before touching canvas, narration, sound, storage, or history.

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

Comprehensive go-to-market strategy and launch execution skill. Use when planning a product launch, feature announcement, market entry, or release strategy. Activates for: go to market, GTM, product launch, launch strategy, launch plan, launch execution, launch marketing, GTM playbook, launch readiness, technical launch, beta launch, early access, waitlist, Product Hunt, feature release, announcement, how do I launch this, launch checklist, we're about to ship, market entry, startup GTM, PLG vs sales-led, GTM motion, launch marketing pack, press outreach, developer product launch.

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

Scaffold-time observability so a shipped product is not blind in prod from day one — error capture (Sentry), request-id structured logging, and /healthz + /readyz endpoints. stack-baseline pins Sentry but nothing wires it; this is the wiring. Loaded by app-scaffolder (bake into the scaffold), infra-provisioner (prod env + probes), and consumed by l3-support (traces) and devops (deploy gate).

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

🇺🇸 Hardware + SaaS GTM Playbook — End-to-end go-to-market for consumer hardware products with software subscription models. Covers crowdfunding engineering (Kickstarter/Indiegogo/Makuake), KOL matrix for physical products, hardware PMF validation metrics, device-as-funnel subscription design, localization entry timing, and community flywheel mechanics. Built from verified Plaud, Insta360, and DJI case data. 🇨🇳 硬件+软件订阅 GTM 实操手册 — 面向消费硬件产品的完整出海及增长打法。覆盖众筹超额工程（KS/IGG/Makuake）、硬件 KOL 矩阵策略、硬件 PMF 验证、设备即漏斗订阅设计、本地化进入时机判断、社区飞轮构建。基于 Plaud/Insta360/大疆真实案例数据撰写。 🇯🇵 ハードウェア＋SaaS GTMプレイブック — クラウドファンディング（Kickstarter/IGG/Makuake）を起点とした消費者向けハードウェア製品のGTM戦略。KOLマトリクス、PMF検証、デバイスをファネルとするサブスクリプション設計、ローカライゼーション進入タイミング、コミュニティフライホイールまで網羅。Plaud・Insta360・DJIの実例データに基づく。 🇰🇷 하드웨어+SaaS GTM 플레이북 — 크라우드펀딩(Kickstarter/IGG/Makuake) 기반 소비자 하드웨어 제품의 엔드투엔드 GTM 전략. KOL 매트릭스, PMF 검증, 디바이스-as-퍼널 구독 설계, 현지화 진입 타이밍, 커뮤니티 플라이휠 포함. Plaud·Insta360·DJI 실제 사례 데이터 기반. Triggers: "hardware GTM" | "crowdfunding strategy" | "hardware+SaaS" | "Kickstarter launch" | "hardware KOL" | "hardware PMF" | "device subscription" | "hardware product launch" | "consumer hardware growth" | "Makuake" | "众筹策略" | "硬件出海" | "硬件+订阅" | "硬件GTM" | "KS众筹" | "硬件PMF" | "设备订阅" | "硬件冷启动" | "ハードウェアGTM" | "クラファン" | "하드웨어 GTM" | "크라우드펀딩"

Craft CMS 5 content modeling — sections, entry types, fields, Matrix, relations, project config, and content architecture strategy. Covers choosing section types, designing entry types and field layouts, selecting field types, configuring Matrix and nested entries, relations and eager loading, and multi-site propagation.

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

Drafts U.S. commercial real estate access and indemnity (right-of-entry) agreements for pre-closing due diligence. Covers license grants, non-invasive vs invasive testing gates, insurance/endorsement requirements, indemnity with discovery carve-outs, restoration and lien remedies, confidentiality, and anti-indemnity guardrails. Trigger: access agreement, right of entry, due diligence access, Phase I/II, invasive testing, pre-PSA site inspection.

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

Write a changelog entry or release notes for an API version — breaking changes, new features, fixes. Use when asked to "write release notes", "add a changelog entry", or "document breaking changes".

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

Expert guide for structured logging (Pino, Winston), error tracking (Sentry), log aggregation (Axiom, Datadog), request correlation, and GDPR-compliant log management / Panduan ahli untuk logging terstruktur (Pino, Winston), pelacakan error (Sentry), agregasi log, korelasi request, dan manajemen log sesuai GDPR.

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

Expert guide for deploying SaaS applications with multiple entry points on modern edge and serverless platforms like Vercel and Cloudflare / Panduan ahli untuk mendeploy aplikasi SaaS dengan multiple entry points di platform edge dan serverless modern seperti Vercel dan Cloudflare.

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

This skill should be used when the user asks to "update the changelog", "add a changelog entry", "write a CHANGELOG entry", or when preparing a git commit in StreamFlow that requires updating the `## [Unreleased]` section of `CHANGELOG.md`.

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

Analyze live crypto K-line, price-volume, market-structure, and derivatives evidence, then turn it into a conditional trading plan with exact entry, invalidation, targets, position sizing, leverage, and three risk tiers. Use when a user wants both market analysis and an actionable risk-managed plan, asks whether or how to trade a coin, or requests entry/stop/target/size levels. Do not use for placing orders, managing an existing account, or guaranteeing returns.

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

Sentry error tracking and performance monitoring for real-time visibility into application errors, performance issues, and release health

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

Specialized business strategy prompt methodology for Claude. Provides 11 tested approaches (3 identity, 4 reasoning, 4 output formats) for consulting, M&A, corporate strategy, and strategic planning tasks. Use when building prompts for deal evaluation, due diligence, portfolio strategy, business model analysis, board narratives, investment cases, market entry plans, or strategic options assessments. Trigger on: "build a prompt for M&A analysis," "due diligence prompt," "board narrative," "investment case," "market entry strategy," "strategic options," "portfolio strategy prompt," "business model analysis prompt," "consulting-style analysis." Do NOT use for evaluating or scoring existing prompts (use rootnode-prompt-validation if available) or for auditing Claude Projects (use rootnode-project-audit if available).

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

8つの専門エージェント（市場規模分析・トレンド調査・競合インテリジェンス・投資シグナル・日本市場・ユーザー需要分析・規制調査・データ検証）が ディスカッション型でアプリ/デジタルプロダクトの市場調査を実施するスキル。 エージェント同士が対話・批判し合い、data-critic がライブモデレーターとして矛盾を検出・収束を判定する。 トライアンギュレーション（データ・方法論・調査者・理論の4種類）をディスカッションに組み込み、 確証バイアスを排除した信頼度付きレポートを出力する。 Gate 1（全員参加の合意形成）→ Gate 2（最終検証 + Devil's Advocate）の2段階ゲートで品質を担保。 コンテキストファイルで過去のセッションを引き継げる。 Use when: 市場調査をしたい、TAM/SAM/SOMを算出したい、市場の成長性を調べたい、 参入タイミングを判断したい、競合市場を分析したい、規制リスクを調べたい。 Triggers: "市場調査", "market research", "TAM", "SAM", "SOM", "市場規模", "市場分析", "market analysis", "参入", "market entry", "市場性", "market viability", "市場トレンド", "market trend"

Run the viz pipeline to render icons from existing glyphs. Entry point for the viz subproject covering palette generation, data building, manifest creation, and icon rendering for skills, agents, and teams. Always use build.sh as the pipeline entry point — never call Rscript directly.

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