4,834 件 ・ 関連度順
概要と使いどころ
Write a public post in the owner's own voice with a role model's style and idea palette layered on top, reading a style-palette file so the same engine works for any thinker the owner has profiled. Draft-first. Triggers: "/speak-as <name>", "write in the style of <X>".
日本語の概要は準備中です。原文の説明を表示しています。
Get a second opinion from an external LLM at three checkpoints: T1 is the plan valid, T2 which path at a fork, T3 finish plus a QA breaker that tries to break the result. One structured move per exchange (PROPOSE, COUNTER, VERIFY, ACCEPT, BLOCK) with memory across turns, and every exchange mirrored into a human-visible channel. Supports a multi-vendor panel instead of a single reviewer. Triggers: "/secondop", "get a second opinion", "run the review panel".
日本語の概要は準備中です。原文の説明を表示しています。
Track and collect promises: every promise, theirs to us and ours to them, goes into a registry with date and source, gets a reminder when due and is closed with evidence. Triggers: /promises, log this promise, who promised us what, what did we promise, overdue promises, promise tracker.
日本語の概要は準備中です。原文の説明を表示しています。
- СОРСИНГ ПОД РЕЙЗ в два трека: инвесторы из нашего VC-графа (leads.db) и покупатели-пилоты, найденные ПО СИМПТОМУ в интернете (GitHub issues, Hacker News, X, наши же репозитории, клуб СОСТАВ). Триггеры: “/raise-sourcing“, “/sourcing“, “собери список инвесторов“, “кому питчить“, “найди покупателей“, “добери лидов под рейз“, “кого звать в пилот“, “обнови стол сорсинга“, “raise sourcing“
日本語の概要は準備中です。原文の説明を表示しています。
Use Gemini as a third external reviewer alongside two other vendors: diff review with an APPROVE or REQUEST_CHANGES verdict, and QA-breaker duty in the post-build test ritual. Headless over REST with a CLI fallback, and verdicts go to a shared usage journal. Triggers: "/gemini review", "gemini opinion on this diff".
日本語の概要は準備中です。原文の説明を表示しています。
Write a self-contained handoff document so another session, person or machine continues the work without this session's context: decisions and why, what is done and tested, exact paths and values, open blockers, boundaries, and an explicit continue-from-here step. Lands in a synced folder with a short seed prompt. Triggers: "/handoff", "prepare a handoff", "hand this off".
日本語の概要は準備中です。原文の説明を表示しています。
Ask the second brain in plain words: semantic search over the curated vault with embeddings plus a reranker, returning the smallest relevant slice instead of a corpus dump. Token-cheap. Triggers: "/ask <question>", "what do I have on <topic>", "what did I write about X".
日本語の概要は準備中です。原文の説明を表示しています。
Finds free backlink and brand mention opportunities across Hacker News, Quora, GitHub, directories, and niche communities. Outputs a prioritized action plan with draft responses ready to post. Use after brand research and content creation to amplify reach and AI engine citations.
日本語の概要は準備中です。原文の説明を表示しています。
Build a complete but efficient Nature-style Chinese PPTX presentation from a remote-sensing, Earth-observation, geospatial AI, or broader scientific paper, preprint, PDF, article text, abstract, figure legends, or reading notes. Use this skill whenever the user asks to make slides/PPT/PPTX for journal club, group meeting, paper sharing, thesis seminar, lab meeting, department report, or academic presentation from a remote-sensing research paper. It identifies the paper type and argument, selects only the figures needed for the story, writes Chinese slide content and speaker notes, creates the actual .pptx deck, and runs an explicit self-review/corrective revision loop focused on figure quality, text overflow prevention, and non-template visual design before delivery. Also trigger on general academic-presentation requests even without the word "Nature", such as turning a paper into slides, building an academic talk deck, conference/defense presentations, and Chinese phrasings like 论文做PPT、遥感论文汇报、组会PPT、文献汇报、学术汇报、做幻灯片、讲paper、读书报告PPT.
日本語の概要は準備中です。原文の説明を表示しています。
Search indexed YouTube and podcast transcripts for quotes, speakers and clip boundaries with timestamped source links using Arcmira.
日本語の概要は準備中です。原文の説明を表示しています。
Operational guide for the NV oOS Model Foundry (Proposal 067) — the cluster fine-tuning flywheel. Phase 1 shipped: the Corpus Foundry (Pro addon, addons/pro/includes/model-foundry/) — consent-gated, deduplicated, PII-scrubbed corpus exporters (trajectory_v1, preference_v1, docs_v1) with deterministic holdout splits and R12 provenance manifests. Covers the governance contract, row schemas, output layout, filter seams, the registration pattern for foundry tool slices, how to add a new exporter, and the test/validation gates. Use when extending the Corpus Foundry, debugging corpus exports, wiring a new data source, or continuing Phases 2–6 (train-worker, registry/serving, eval gate, fleet sharing).
日本語の概要は準備中です。原文の説明を表示しています。
Operational guide for the NV oOS WordPress Playground demo blueprints — the Content Graph "Project Asteria" demo, the Complete bundle × local Ollama demo, and the Docs Hub wp.org Live Preview demo. Covers blueprint authoring patterns (embedded runPHP seed snippets, generator scripts, preview-safe vs standalone split), CORS hosting gotchas, the CI Plugin Check gate (built-ZIP scan, rsync/distignore sync, ABSPATH guards), Playground worker crash modes (PHP-side localhost fetches, inline-script UTF-8, SPA SSE-hold mount bursts, crash-truncation SyntaxErrors), local Ollama integration (OLLAMA_ORIGINS, browser policy matrix, plugin settings + assistant meta keys), and the CLI validation harness (probe builder, mount quirks, server-mode 502 boot). Use when extending or debugging the demo blueprints, adding a new Playground demo, or triaging a crashing Playground instance.
日本語の概要は準備中です。原文の説明を表示しています。
Operational guide for WordPress.org submission readiness of NV oOS standalone plugins (nvoos-docs-hub live at 0.5.3; nvoos-content-graph live at 1.0.10 in the re-submission loop; nvoos-design-system next in the pipeline — issue #6811). Covers the 18 wp.org guidelines, the Plugin Check (PCP) gate in CI and Docker, PCP finding triage, the reviewer-reply loop (findings taxonomy from the real 0.4.3 review, related-issue sweep checklist, reply-email template), packaging exclusion tri-sync, readme.txt standards, .wordpress-org listing assets, and the NV oOS Complete checkout-flow disclosure discipline (docs-hub 0.5.3, content-graph). Use when preparing a wp.org submission, responding to a reviewer email, fixing the plugin-check CI job, triaging PCP findings, or capturing listing screenshots.
日本語の概要は準備中です。原文の説明を表示しています。
Per-toolkit hardening audit loop for NV oOS Pro tools. Systematically scans each addons/pro/includes/tools/<toolkit> (and its plugins/nvoos-content-graph-pro mirror) for the four recurring production failure classes — unguarded shell calls that fatal on exec-disabled hosts, calls to nonexistent client methods, string-assuming parsing of provider responses that may be arrays, and provider enum/service mismatches — then fixes, tests (Docker PHPUnit), and validates (phpcs both standards) before moving to the next toolkit. Use when asked to audit a toolkit, review the X tools for similar issues, do the same for the other toolkits, or continue the toolkit audit loop. The first case study (document-generation) found 3 fatal bugs + 1 broken regex.
日本語の概要は準備中です。原文の説明を表示しています。
Repair and triage guide for the NV oOS PHPUnit test suite — Docker test environment (incl. cross-worktree one-off runners), CI log triage, and 71 recurring root-cause patterns (hook resets, singleton interference, WP_Error envelope drift, coverage-manifest drift, preset-accounting gaps, and more — see the patterns section). Covers the cluster-by-cluster PR workflow against alpha-working and validation gates. Use when fixing failing PHPUnit tests, triaging CI logs, repairing test drift, deciding between a production fix and a test fix, or starting a new fix cluster.
日本語の概要は準備中です。原文の説明を表示しています。
Operational guide for the base+pro → Content Graph ecosystem port loop — porting Pro addon files byte-identical into plugins/nvoos-content-graph-pro cluster-by-cluster (transform rules, byte-identity verifier, standalone-only wiring, dual-matrix validation, tracker updates, PR + self-merge). Use when the user asks to "continue the loop", "do the next cluster", "port <toolkit> to CG Pro", or resumes a Wave E/F port session.
日本語の概要は準備中です。原文の説明を表示しています。
Create and process videos using AI generation (Runway, Pika, Replicate, Sora, Veo) and FFmpeg processing. MCP bridge provides frame extraction (extract_video_frames); the Design Stack media worker handles full FFmpeg processing (resize, trim, compress, GIF, format conversion). Covers social-media-optimized video output. Use when generating AI videos, extracting frames/thumbnails, transcoding videos, creating GIFs from clips, or preparing video for social platforms.
日本語の概要は準備中です。原文の説明を表示しています。
Generate images using AI models — Gemini, DALL·E, Stable Diffusion, Midjourney, Flux, Leonardo, Ideogram, and more. MCP bridge tools are primary; the Design Stack media worker is the fallback for advanced providers. Covers prompt engineering, model selection, size/aspect ratios, style parameters, batch generation, multi-site awareness, and WordPress integration. Use when you need to create hero images, social graphics, product mockups, brand illustrations, or any visual asset for marketing, social media, or e-commerce.
日本語の概要は準備中です。原文の説明を表示しています。
Optimize images for web performance — format conversion (WebP, AVIF), responsive sizing, compression, background removal, lazy loading, and WordPress media library integration. Uses MCP bridge tools (resize_image, remove_background) as primary; the Design Stack media worker (Sharp) as fallback for advanced/batch processing. Use when you need to resize images for social media, convert formats for faster page loads, remove backgrounds from product photos, generate alt text, or batch-process an entire media library.
日本語の概要は準備中です。原文の説明を表示しています。
Publish and schedule content to social media platforms (Twitter/X, Facebook, Instagram, LinkedIn) via the MCP bridge schedule_social_post tool as primary. The Design Stack media worker API is the fallback for advanced platform management. Covers platform-specific formatting, media attachment, scheduling, and WordPress-to-social publishing workflows. Use when posting to social platforms, scheduling future posts, attaching media to posts, checking optimal timing, or debugging API delivery failures.
日本語の概要は準備中です。原文の説明を表示しています。
End-to-end media pipeline automation — from AI generation through optimization to social publishing. Covers workflow design, WordPress integration, Redis job queuing, batch processing, multi-site pipelines, and orchestration. MCP bridge tools are the primary interface for individual operations; the Design Stack media worker handles batch and advanced processing. Use when you need to automate image generation→optimization→publishing chains, set up cross-site media sync, design batch processing pipelines, or orchestrate multi-step media workflows triggered by post publish or cron.
日本語の概要は準備中です。原文の説明を表示しています。
Master software architect specializing in modern architecture
日本語の概要は準備中です。原文の説明を表示しています。
Alumni and re-hire register: former role, last working day, re-hire eligibility, current employer and re-engagement date, as CSV, SQL, JSON Schema or Notion on request. Use for alumni outreach.
日本語の概要は準備中です。原文の説明を表示しています。
Use when an agent workflow needs deterministic recovery evidence for sandbox, MCP/tool, worker, checkpoint, memory, or orchestration failures.
日本語の概要は準備中です。原文の説明を表示しています。