1,296 件 ・ 関連度順
概要と使いどころ
Author or edit a custom HyperFrames composition when no specialized workflow fits, or when BRIEF.md sets flow: companion. Use for longer or multi-scene pieces, brand and sizzle reels, montages, static loops, static title cards, footage remixes, and freeform builds. Use motion-graphics instead for a short unnarrated motion-first unit, including an animated title. Route fresh creation through hyperframes before using this skill.
日本語の概要は準備中です。原文の説明を表示しています。
Collect project brief and stack choices, then output canonical project-config.json for downstream web-builder skills.
日本語の概要は準備中です。原文の説明を表示しています。
Use when drafting, reviewing, or revising Xiaohongshu/Douyin/social-platform Chinese text so it has real internet-native judgment instead of README tone, technical-briefing tone, or mechanical meme-word stuffing.
日本語の概要は準備中です。原文の説明を表示しています。
End-of-session wrap-up. Save what was learned this session to auto-memory, verify the working tree is committed/pushed, and emit a brief resume prompt the user can paste next time. Invoke as /done to close a work session. Wrap-up is auto-memory ONLY — never writes a handoff.md or any handoff file.
日本語の概要は準備中です。原文の説明を表示しています。
確認点で利用者が見る深さを選んだあと打ち合わせ資料を作り手とは別の目で確かめたいとき、正確さ・言葉・見た目・シンプルさの指摘を資料の編集なしで受け取りたいときに使う。
検査を通した文書とボード PNG を目次つきの 1 ファイル HTML にまとめたいとき、版の一致と古い PNG や外部参照の有無を確かめてから渡したいときに使う。
素材フォルダと要望から業務システムの打ち合わせ資料一式を同じ工程で作りたいとき、打ち合わせメモから変更点をまとめて影響する工程だけ直し版を上げたいときに使う。
仕様書からページ構成を決めて画面ボードを型どおりに組みたいとき、組んだボードを PNG にしてはみ出しや注記の数を検査し目で確かめたいときに使う。
素材を読んだうえで、使う人や困りごとはあいまいなら促して聞き足し、画面や裏側のしくみと運用は既定案つきで短く聞き取りたいとき、確認点で増えた決めることを聞いてヒアリング.md に足したいときに使う。
ヒアリング結果と素材から要件定義書を決まった章立てで書きたいとき、確認を終えた要件定義から画面ごとの項目と動きやしくみを仕様書へ落としたいときに使う。
生成今日认知系统汇报：整合L3记录、待完成项、知识库状态，并主动提问帮助用户恢复上下文。触发词：「汇报」「今天有什么」「有什么更新」「同步一下状态」「有什么积压」「今日简报」「最近新了什么」。
日本語の概要は準備中です。原文の説明を表示しています。
后台认知合成器（DMN等效，Headless）。不被用户直接触发，由后台调度脚本每3天执行一次。跨碎片关联分析：找到不同时间捕捉的碎片之间的隐性关联，生成合成报告写入L3，等待daily-briefing展示给用户。触发词（人工触发时）：「执行后台合成」「cognitive-background-synthesizer」。
日本語の概要は準備中です。原文の説明を表示しています。
The Eterdis Strategy Diagnostic — an AI-guided conversation that helps leadership teams understand their strategic situation before committing to a direction. This is the entry point skill. It runs an open-ended discovery conversation, detects which strategic frameworks are most relevant, and produces a strategy-ready brief. Use this skill when someone asks for a general strategic assessment, when they don't know which framework they need, when they want to "figure out where we stand," or when they're preparing for a strategy engagement. This skill orchestrates other Eterdis skills — it does not replace them. Triggers on: "help me think through our strategy," "where should we start," "we need to figure out what's going on," "strategic health check," "prepare for a strategy review," or any open-ended request for strategic thinking. Based on 20 years of consulting practice by Eterdis (eterdis.com).
日本語の概要は準備中です。原文の説明を表示しています。
Use when implementing web UI in React, Next.js, Tailwind, CSS, or GSAP against an approved design, fast-path brief, or prototype UX contract.
日本語の概要は準備中です。原文の説明を表示しています。
Use when asking project status, next priority, sprint health, blockers, deadlines, risk register, or daily brief generation.
日本語の概要は準備中です。原文の説明を表示しています。
Anti-slop frontend skill for landing pages, portfolios, and redesigns. The agent reads the brief, infers the right design direction, and ships interfaces that do not look templated. Real design systems when applicable, audit-first on redesigns, strict pre-flight check.
日本語の概要は準備中です。原文の説明を表示しています。
Generate a context-rich briefing prompt for an external agent (Claude Code, Cursor, etc.)
日本語の概要は準備中です。原文の説明を表示しています。
Use when a user asks for a concise Solana token research snapshot with market, trade, and security context
日本語の概要は準備中です。原文の説明を表示しています。
Review a product requirement, PRD, brief, or meeting note before design or development; expose missing decisions, contradictions, edge cases, dependencies, and validation gaps without inventing business rules.
日本語の概要は準備中です。原文の説明を表示しています。
Ultra-compressed communication mode. Cuts output tokens 65% (measured) by speaking like caveman while keeping full technical accuracy. Supports intensity levels: lite, full (default), ultra, wenyan-lite, wenyan-full, wenyan-ultra. Use when user says "caveman mode", "talk like caveman", "use caveman", "less tokens", "be brief", or invokes /caveman. Also auto-triggers when token efficiency is requested.
日本語の概要は準備中です。原文の説明を表示しています。
Translate a fuzzy analytical question into a rigorous investigation plan. Interrogates the ask, grounds the plan in the available data dictionary, applies analytical best practices, and produces a structured brief of query specifications for a downstream query-writing skill. Plans, does not write SQL. Use when: "why did X drop", "is there a relationship between A and B", "who are our highest-value customers", "what's driving the change in Y", "investigate this trend", "design an analysis for", "scope this analytical question". (narrative-common)
日本語の概要は準備中です。原文の説明を表示しています。
Run a research project as a folder on disk — open the run root first, record the user's own instruction verbatim, open the two frame gates and stop for the human to answer them, and keep the stage the ledger says it is. Use when the user asks to start, resume or check a research run, a paper, a review, a brief, a report, a literature review or a protocol.
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user starts a non-trivial coding/building task in Claude Code (e.g. "帮我做个 X", "help me build Y", "add feature Z", "搭一个 Z"). Layers an AI-native pedagogical coat over normal coding work — surfaces implicit assumptions in user intent, annotates non-trivial design decisions inline with brief concept-scaffolding for terms the user may not know, and replaces "should I run it?" handoffs with rigorous AI self-verification plus a clean list of what only the user can verify. Skip for pure Q&A, single-line edits, read-only investigation, or refactoring along an existing pattern.
日本語の概要は準備中です。原文の説明を表示しています。
Product-discovery coach for Fishbowl engineers — inspired by Marty Cagan's work (never impersonates him). Stage-routes between opportunity brief, research, PRD, ticket drafting, and outcome review. Triggers on "product coach", "help me with product", "I need to write a PRD", "I want to do discovery", "opportunity assessment", "who is this for", "why are we building this", or when an engineer is starting, resuming, or post-mortem-ing product-adjacent work. Invoke with a short description of what you want to do, or invoke bare to be surveyed and routed.
日本語の概要は準備中です。原文の説明を表示しています。