「what」の検索結果

Turn the current conversation into a PRD file in the project folder — no interview, just synthesis of what you've already discussed.

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

Ведёт задачи штаба: по итогам сессии обновляет файл задачи или issue на GitHub и отвечает на вопрос „что по задаче“. Если задачи лежат в файлах, обновляет файл задачи отдела и сводку дня в штабе. Если задачи на GitHub, ищет issue во всех репозиториях, обновляет описание issue, пишет комментарий о сделанной работе, следит за parent epic, W-label и местом на доске Project, убирает закрытые задачи из плана дня и недели. Применять по: „/manager“, „синкни сессию“, „обнови issues“, „зафиксируй прогресс“, „создай issue“, „статус задачи“, „что по …“, „есть ли issue по …“, „sync session“, „track status“, „what about …“. Не применять: план дня — daily, ретро — retro.

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

Use when user asks for Claude Code usage stats, weekly analytics, project activity summary, or wants to see what projects were worked on. Triggers on "аналитика", "статистика claude", "cc stats", "weekly report", "что делал"

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

Build a precise, step-by-step action plan before making any code changes. Use this skill whenever the user describes a feature, bug fix, refactor, or any multi-file change. Also use when the user says "plan", "think through", "what would it take", or describes a problem without jumping to code. TRIGGER BEFORE writing any code for non-trivial changes. Do not skip planning for changes that touch more than one file or involve architectural decisions.

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

Write outbound promotional copy for a product or project: launch and update posts for community platforms and social media, store page descriptions and short blurbs, landing page headlines and calls to action, press-style announcements, and the naming of a product for another language or market. Covers what may be disclosed publicly, keeping claims traceable to shipped changes, and writing a headline that carries information instead of hype. Use when drafting or revising anything aimed at people who do not use the product yet, and when deciding whether a link, key, price, or unreleased detail can appear in public copy.

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

Guide a user from an unclear idea to an actionable plan through the agent harness's native ask tool and clickable choices. Use when the user wants a guided requirements interview, step-by-step questions, help deciding what to build, or a button-led path from goals to scope, solution, and technology choices. Do not turn an ordinary implementation request or a single clarification into an interview.

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

Profile and debug Hermes sessions from their JSONL transcripts. Find a session and its subagents, build a queryable event table, summarize the work as a hierarchical table of contents, break down wall time, inference, tools, tokens, and estimated cost per agent, identify errors and improvement opportunities, and export a shareable Perfetto trace. Use when a user wants to inspect what a Hermes session did, debug agent or subagent activity, understand session cost or latency, create a session timeline, generate a trace, or learn how to improve the next agent run.

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

Map the big picture around a topic or software repository by identifying its boundaries, layers, actors, components, relationships, flows, history, fault lines, and open questions, then explain how the pieces fit together and where to look next. Use when a user asks to understand a whole field, domain, technology, ecosystem, industry, codebase, architecture, unfamiliar repo, or phrases such as "give me the big picture", "map the landscape", "how does this all fit together?", "help me get oriented", or "what am I missing?"

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

Indie maker playbook for bootstrapped apps inspired by Pieter Levels' MAKE: The Indie Maker Blueprint. Use when a user is starting or sizing an app idea, choosing what to build next, building a minimal product, preparing a launch, diagnosing stalled growth, deciding pricing or monetization, automating operations, maintaining a per-app MAKE.md tracker, or evaluating whether to sell a product.

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

Teach any topic deeply from first principles and build evidence-based paths toward exceptional capability. Use when a user asks to understand, explain, learn, or deep-dive into a topic; asks why or how something works, why it matters, how alternatives compare, or what different perspectives reveal; requests current paradigms, a complete roadmap or curriculum, deliberate practice and feedback, or a top-1%-level mastery plan. Answer explanation questions completely before offering a curriculum; route explicit mastery goals to an adaptive practice and proof-of-capability system.

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

Dead code and dependency cleanup, repo-wide: unused deps, unreferenced exports, unreachable code, orphaned files — removed only with tool evidence, in reversible waves. Runs on green main. For diff-scoped cleanup use absolute-simplify. Triggers on "absolute prune", "remove dead code", "find unused deps/exports", "what can we delete", "clean up orphaned files".

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

Turn whatever the agent just produced — a conversation, an analysis, an artifact, a markdown file — into a live shareable URL in seconds, published as-is via ReportRoom. Use when the user says "share this", "give me a link", "put this online", "make this a page", "send this to someone". This is the fast, verbatim path — for a restructured, designed report use report-publisher; for a view-tracked proposal use proposal-tracker.

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

Active Directory Certificate Services (AD CS) escalation techniques ESC1 through ESC17, driven by hand with Certipy (ly4k). Use when the target runs a Certificate Authority and you want to find vulnerable certificate templates or CA misconfigurations, request a certificate that impersonates a privileged user, and know the exact certipy command, what each ESC actually checks, the Windows Event IDs that fire, and the remediation. ESC1 and ESC8 are the two you hit most in the field.

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

Composite any two HTML screens into a locked photo plate of hands holding an open foldable phone — a 1448×1086 still with two blank 495×849 / 498×849 screen slots (left and right) — to make side-by-side meme and comparison videos: TikTok vs Reels, ChatGPT vs Claude, "me vs my friend", before/after, two apps racing. Trigger on: "foldable phone meme", "put X on the left screen and Y on the right", "two-screen comparison video", "the dual-screen phone meme", or any request that names two apps/feeds/chats to show at once. The plate, geometry, and camera are finished — the agent only authors what plays INSIDE the two screens and renders.

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

Emit the content signals reimagine-it reads from an HTML file — title, anchors, proper nouns, dates, numbers, emails, links, source hex colors, and the derived palette — as JSON without generating a redesign. Use when the user says /reimagine-it extract, "what does the engine see in this page", "extract the palette", "pull the facts from this page", or wants content analysis for research, migration, or design-system work. CLI: npx reimagine-it extract -i page.html -o signals.json. Part of the reimagine-it Content-Derived Design suite.

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

wacrawl: WhatsApp Desktop archive import/search, slices, backups, repo/release work.

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

Business model classification, business model analysis, structural analysis of how a company makes money, product offering decomposition, distribution channel analysis, customer segment analysis, revenue model identification, market sizing TAM SAM SOM, competitive positioning, business unit performance, management team & leadership analysis, what does the company sell, how does the company go to market, business model type platform service product, channel mix direct vs indirect, revenue concentration risk, CEO CFO executive backgrounds and changes

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

Weekly clinical-trial status diff — the 11-category change report over the stored weekly snapshots (spec 055 FR-B03). Surfaces exactly what changed on the trial registry for your coverage: New / Suspended / Withdrawn / Terminated / Recruiting / Recruitment-Complete / Completed / Ahead / Delayed / Upsized / Downsized, every row carrying previous and new values, with risk flags on Terminated and Downsized and re-timing flags on Ahead and Delayed. The stored-previous-value discipline makes each week's diff reproducible.

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

Post-event analyst note (conferences, KOL events, site visits) with the professional note anatomy — headline verdict, per-stock takeaways with model numbers, KOL distillation, cross-trial comparison lattices, modeled deltas vs consensus (peak × POS), three what's-changed vectors, risk bullets, and materiality-rated conflicting views. Use after any med event to convert the event into actionable takeaways.

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

Testing workflow skill for finding high-value test candidates, writing focused tests, generating realistic workloads, reviewing test value, and diagnosing test-suite health. Use for prompts about what to test next, adding or improving tests, reviewing whether a test is worth keeping, low-signal or flaky tests, workload scenarios, or test-suite trust. Do not use for general QA discussion unless the user wants a concrete testing workflow or artifact.

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

Plan and scope production work with Odyssey's real-time interactive video world models (odyssey.ml — Odyssey-1/Odyssey-2/Starchild-1/Agora-1). Use when a request involves generating video that a user steers live with keyboard, text, speech, or controller input (streamed frames that respond in the moment), or when someone must decide between Odyssey-style interactive generation and offline clip generators (Sora/Veo/Kling) or downloadable 3D / game engines. Covers what is verified versus announced, current access routes, latency and coherence limits, feasible-now versus speculative use cases, pricing/access terms, and content/rights considerations. This is a fast-moving research-stage product; the skill teaches honest scoping, not a promise of production reliability.

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

Generate persistent, explorable 3D worlds/environments with Marble by World Labs — from text, a single image, multiple images, video, or a 360 panorama, plus coarse-structure blocking with Chisel. Use this skill when a task needs a navigable 3D scene, VR/immersive backdrop, virtual-production environment, previz set, game-blockout, or web/engine-ready Gaussian splat or mesh, and you must choose an input mode, a Marble model, an export format, and a plan/API route, then review world quality. Covers the Marble web app and the World API, editing/expansion, output formats and what each supports downstream, import into Unity/Unreal/Blender/Houdini/web, pricing/credits, capability limits, and rights/licensing. Not for flat text-to-image, text-to-video clips, or real-time on-the-fly world models (Marble outputs are downloadable, static 3D environments).

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

Produce video with Moonvalley's Marey model family (Marey Realism v1.5) — a filmmaker-oriented, 1080p/24fps generative video model marketed as trained exclusively on licensed data. Use this skill when a task asks for Marey or Moonvalley specifically, when a brief demands brand-safe / legally reviewed AI video for commercial or studio work, or when the request needs Marey's director-style controls (camera trajectory, motion transfer, pose transfer, keyframing, reference conditioning). It covers what "commercially safe" really means versus the actual terms of service, access routes (Moonvalley web / Voyager, the fal API, ComfyUI), pricing, capability limits, prompt and reference strategy, where Marey fits production versus where other models win, iteration, and quality review. Do not use it for audio generation, for photoreal talking-head dialogue, or as a generic "best video model" default.

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

Generate music with Suno (v5 / v5.5 era, 2026) and advise a production team on what they may legally do with the output. Use this skill when a user wants to create, extend, remaster, or stem-separate a track in Suno; craft Suno prompts (style field, lyrics/metatags, exclude-styles, personas, custom voices); choose a subscription tier for a given use; or get accurate answers about ownership, commercial rights, distribution/monetization on DSPs, the Warner Music Group settlement, the ongoing label/publisher litigation, and Suno's API situation. Do not use it for other music generators (Udio, ElevenLabs Music, Google Lyria) except by explicit contrast, and do not use it as a substitute for a lawyer on a specific commercial deal.

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