「store」の検索結果

Calendar skill with user-adaptive backend selection (Flag 3). Default: local SQLite store. Optional: Google Calendar MCP, Routinika or UpToday as backend — controlled via assist/prefs.json. Without preference the LLM asks the user interactively.

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

Developer assistant (ATI successor). Provides a quick project overview via headless scan and routes to the available coding tools: CodeCommander MCP (analysis/refactor/diagnose) and the ellmos-code-tools module. Pure tool routing + scan, no own store.

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

Local, private capture of medical data: diagnoses, symptom histories and examination plans. No BACH origin — custom design with its own SQLite store. Strictly local, no cloud transfer.

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

Creates a personalised daily newspaper from RSS feeds and web sources. Ported from the BACH news system (news.py + newspaper_generator.py). Own SQLite store (no Origin-DB). feedparser optional — XML fallback via stdlib. PDF export via Edge Headless (msedge.exe).

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

Regelmäßiger Pflegedurchlauf für ein bereits veröffentlichtes GitHub-Repository (Stufe 1, günstig und oft wiederholbar): zuerst alle Distributionsflächen des Projekts ermitteln (npm, PyPI, Registries, Marketplaces, Stores, Website) und Änderungen später dorthin spiegeln, dann Topics setzen, Privacy-Gate, Dokumente auf Veröffentlichungsabsicht prüfen und interne Planungsdateien nachträglich ignorieren, Banner ergänzen, Aussagen im README gegen den echten Code-Stand abgleichen, Darstellung verbessern, Sprachfassungen der README vervollständigen, Sichtbarkeitsmaßnahmen umsetzen, Eintrag auf der Organisationsseite prüfen sowie offene Issues und Pull Requests abarbeiten. Nutze diesen Skill, wenn ein bestehendes Repo gepflegt, aufgeräumt, aktualisiert, aufgehübscht oder "mal wieder durchgesehen" werden soll, wenn ein Repo veraltet oder unaufgeräumt wirkt, bei Formulierungen wie "Repo-Pflege", "after care", "Nachpflege", "Repo auf Stand bringen", "aufräumen und pushen" oder bei rotierenden Qualitätsrunden über mehrere Repos. Für die tiefe Runde inkl. Rechtscheck und orga-übergreifenden Querverweisen stattdessen full-after-care nutzen; für die Erstveröffentlichung github-repo-care.

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

Turns one meeting transcript or recap into a DRAFT action-items document (decisions, owned and dated action items with verbatim source quotes, open questions), a task list ready for the user to enter into their task tracker, and one DRAFT follow-up email per action owner, all returned in the chat for the user to store, create or send. Use when the user shares, names or points to a meeting transcript or recap and asks to "pull the action items from this transcript", "who owns what after today's call", "draft follow-up emails to each owner" or "turn this recap into tasks". Do not use for full minutes, use meeting-minutes-writer instead; a brief before a meeting is meeting-prep-onepager. Drafts for human review; never approves, authorises or signs off.

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

Operate Lemon Squeezy — the Merchant of Record for digital products and SaaS — via its JSON:API REST endpoints. Covers stores, products, variants, checkouts, orders, subscriptions, customers, and license keys. Use when the user wants MoR billing (EU VAT, chargebacks, sales tax all handled for ~5% + fees) instead of rolling their own with Stripe.

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

Tidy an agent's always-loaded memory index (MEMORY.md) on macOS or Linux: trim long lines, move closed entries to an archive, fold domains into hub files, restore dropped pins and add pointers for orphan memory files. Use when the index is over budget or has orphans. Triggers: /memory-tidy, /mt, tidy memory.

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

Mine the day's sessions for the owner's intentions, cluster them into distinct ones, store them, and write two or three detailed posts with an explicit ask per channel, plus a loop tracking who answered. Drafts only. Triggers: "/intention", "mine today's intentions", "intention posts".

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

Change a Mac's main display resolution in one command: real pixels instead of 4K HiDPI so remote desktop (AnyDesk), screen recording and Screenpipe stop lagging. Use when a remote session is slow or a lower or original resolution is needed: lists modes, picks by width, height, pixel width and refresh rate, self-tests five known traps, verifies after the change and prints a one-line rollback. Triggers: /display-mode, lower the resolution, set 1920x1080, AnyDesk is slow, restore resolution.

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

Diagnose and restore the Claude Desktop app when it will not start, crashes, or runs with no visible window. Use for Windows MSIX launch failures, 'Not main instance', stale AppX job containers, NeedsRemediation or 0x80070020 errors. Separates Desktop from the CLI, reads fresh logs, picks a narrow fix and proves a visible working window. Triggers: /claude-repair, Claude Desktop won't open, Claude app crashed.

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

Operational guide for integrating the NV oOS Complete purchase flow (vendor checkout API client) into standalone WordPress plugins — docs-hub 0.5.3 (stack added in PR #6963, shipped 0.5.2 → 0.5.3) and nvoos-content-graph 1.0.10 (live). Covers the vendor API contract (session/verify/health, nvoos-oos-complete product, 424/502 error passthrough), the five-class client stack (config, vendor client, license store, installer, REST controller), the purchase-modal JS/CSS port recipe (class-prefix rename, keep-the-JS-identical trick), wp.org commerce compliance (External Services disclosure, WPORG-REVIEW-COMMERCE-NOTES.md, js.stripe.com service exception), and the checkout test conventions (direct controller calls, pi_ fixture rules, zero-HTTP assertions). Use when adding the Get NV oOS Complete upsell/checkout to a plugin, porting the commerce stack to a new standalone plugin, extending the purchase flow, or debugging a checkout integration.

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

WooCommerce store operations through NV oOS Pro — product research, catalog cross-referencing, inventory lookups, and Shopify or Flowhub comparisons where integrations are configured.

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

Operating NV oOS WordPress sites through scoped MCP operator credentials — tool groups, task recipes, and site disambiguation. Use when working with NV oOS tools (create_post, woo_products, toolkit_cpt, paper_store, jetengine) on any managed site.

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

Research products via AI tools, cross-reference live stock, generate WooCommerce-ready copy, and extract marketing angles. Covers the full research-to-copy pipeline with remote_wp_connection stock checks and paper_store persistence. Use when researching products by SKU/name/category, generating WooCommerce descriptions, preparing product data for campaigns, or cross-referencing catalog files against live inventory.

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

Generate output schemas (dataset_schema.json, output_schema.json, key_value_store_schema.json) for an Apify Actor by analyzing its source code. Use when creating or updating Actor output schemas.

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

Master modern Angular state management with Signals, NgRx, and RxJS. Use when setting up global state, managing component stores, choosing between state solutions, or migrating from legacy patterns.

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

Use when the user asks to "codify how our founder sounds", "build a founder voice dossier", or "set our content pillars"; runs an 80%-extraction interview over the user's OWN posts, emails, and decks (never competitor scraping, never an invented persona) and produces the versioned voice record — a per-platform register map (incl. 小红书/微信公众号), banned phrases, per-context disclosure lines (the ECHO C2 upstream), a few-shot bank built exclusively from own posts, and 3-5 content pillars with Estimated %-allocations — submitted via memory/events/channels.ndjson for channel-registry to store as voice-dossier.md, the record every Craft-phase skill reads first. Not for the brand-level voice canon — use brand-language-codifier; not for audience/persona research — use audience-mapper. 声音档案/品牌语气/创始人语气/内容支柱/披露声明

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

Use when the user asks to "triage launch feedback", "cluster reviews, comments, and board posts into themes", or "set up a you asked, we shipped loop"; produces a feedback theme digest (frequency, severity, representative quotes per theme), an open→planned→started→completed/declined status loop with duplicate-merge and notification rules, shipped-change announcement material, and a compliant social-proof harvest protocol (never incentivized store reviews). Not for repurposing or amplifying the harvested proof — use content-amplifier; not for executing testimonial outreach threads — use outreach-manager. 反馈分诊/状态环/社证收割/评测合规

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

Use when the user asks to "pick a launch date", "plan the launch window", or "set the embargo and lift time"; produces a candidate-window comparison table (conflict / tailwind / risk per window) built from industry-event cycles and the competitor launch calendar, a launch-week vs rolling-release format call, store-review buffer padding (labeled Estimated), and an embargo window definition (lift moment + timezone) submitted to the launch registry as a candidate. Not for judging the cultural moment itself — use trend-spotter; not for launch-day execution — use launch-day-conductor. 发布择时/发布窗口/竞品日历/禁运期窗口/审核缓冲

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

Use when the user asks to "plan how our narrative lands on every surface", "write per-surface message-match specs", or "brief each creative builder from the canon"; maps the narrative-registry canon onto every flagship surface (homepage, pricing, store listing, sales deck, social bio, docs, email) as a per-surface message-match spec — what claim, pillar, proof, and objection reframe each surface must carry — and cuts a handoff brief to each discipline's creative builder (content-writer, ad-creative-builder, email-creative-builder, social-creative-builder, message-house-builder), so the same story lands consistently everywhere. Not for writing the finished surface copy — use each discipline creative builder; not for the tier-scoped launch asset manifest — use launch-asset-packager; not for scoring cross-surface consistency — use narrative-quality-auditor; not for claim adjudication — use offer-claims-registry. 叙事落地/逐面消息一致/创意交接简报/画布传导

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

Use when the user asks to "monitor my launch", "track our Product Hunt / Hacker News ranking", or "watch the launch window"; runs the T-0 to T+30 window watch — pre-launch instrumentation verification (UTM/event checks, the upstream of RAMP P1), HN rank/points/comments polling with a comments-over-points flamewar early-warning (Estimated heuristic), PH votes/featured status, store charts and reviews, news echo, D0/W1/M1 KPI snapshots vs targets, spike-vs-sustain and owned-capture reads, and alert thresholds against the launch-tier KPI targets. Not for launch-day go/rollback calls — use launch-day-conductor; not for metric deep-dives — use performance-analyzer; not for SEO rank tracking — use rank-tracker. 发布监控/排名轮询/火焰战比/spike-sustain

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

Detects over-permissive Firestore/Storage rules (allow read, write: if true / auth-only without ownership), missing auth checks on writes, and admin SDK private key exposure to client bundles.

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

Firebase integration for Flutter including Auth, Firestore, FCM, Cloud Storage, Analytics, and Crashlytics. Use when implementing serverless backend features, real-time sync, or push notifications.

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