「how to use」の検索結果

Use the `mt` tool to work with this repo’s Mighty graph: run `mt prime` at session start; prefer `mt search`/`mt tree`/`mt show` before reading code; create specs/decisions/tasks and link evidence; triage `mt inbox`; and close out with `mt closeout` then `mt commit`. For full workflow + templates, run `mt prime`.

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

Use when the operator asks what Odylith can do for a repo, requests an advisory repo demo, or asks for the clean scenario-aware show-me output.

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

Create polished audio content and save to Spotify. Produces episodes with TTS narration, a rich timeline (chapters plus in-player images, external links, and Spotify entity cards), and a cover image. Also use for raw media saves, show/episode management, and timeline navigation.

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

This skill should be used when the user asks to "make a whiteboard animation", "draw-on explainer", "VideoScribe style", "hand-drawn explainer video", "animate a sketch being drawn", "do a doodle/scribe video", "show a hand drawing the illustration", or "animate handwriting appearing on a whiteboard". Covers SVG stroke draw-on, a marker hand that follows the path tip, staggered reveal, erase/wipe transitions, and narrated export.

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

Mirror an explicit NowStack iOS Simulator through serve-sim into a live browser preview, then drive the app from that browser. Use for `/ns preview`, showing the Expo app, or collecting browser-visible mobile UI proof.

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

Audits existing landing pages for conversion rate optimization. Scores hero section, CTA placement, social proof, objection handling, and form friction on a 1-10 scale. Use when someone says 'audit my landing page', 'improve conversions', 'why isn't my page converting', 'CRO audit', 'landing page feedback', 'optimize my signup page', 'page review', 'conversion rate', 'bounce rate is high', 'nobody is signing up', or anything about improving an existing page's performance. Even if they just share a URL and say 'what do you think' or 'how can I improve this' — if there's a page involved and conversion matters, this is the skill. Always use this over generic advice when an actual page exists to audit.

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

Use when creating or updating a pull request in this repository — how to fill in each section of the PR template with concise, reviewer-friendly content, including the behavior-change table.

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

Fetch the team's shared skills — reset each disposable team clone to origin/main — and show the outcome per team as a Markdown board from the terum-skills CLI. Use when the user wants the newest catalogue, receipts or roster before listing, searching or installing.

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

Show the state of terum-skills on this machine — team, clone, session hook, pending work, machine facts — and whether a newer CLI release exists, as Markdown boards. Use when the user asks whether terum-skills is set up, in sync or up to date, or when something about it seems off.

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

Search the team's shared skills by name, description or category, optionally narrowed by author or project, and show the matches as a Markdown board from the terum-skills CLI. Use when the user asks whether the team has a skill for something or wants to find one by keyword.

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

Evaluate architecture and module boundaries for volatility-based decomposition using Juval Lowy's framework (from "Righting Software", building on Parnas 1972). Use when reviewing module splits, service boundaries, new abstractions, or any decomposition decision. Trigger on phrases like "where should this boundary be", "how to split this", "module boundaries", "encapsulate change", "volatility", or references to Lowy, Parnas, or "Righting Software". Complements /hickey (interleaved concerns) with a different lens (change encapsulation).

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

DECIDE-phase doctrine for an Arbor research run: when to merge, prune, combine, or finalize; how the held-out merge gate works; and the rule that the final report uses TEST scores. Load before deciding what to do with completed experiments.

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

Use when phrasing a forward-looking statement, the user asks "how likely is X?" / "what's the likelihood?", or the tradecraft pipeline applies a probability yardstick to a finished product. Standardised likelihood language across all products.

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

Use when the user asks about the CTI Hyperloop framework, the intelligence lifecycle as a high-tempo loop, or how to map intelligence work across strategic / operational / tactical levels with bidirectional feedback. Liberty91's operational doctrine.

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

Use when the user asks about ISAC participation, TAXII feeds, MISP communities, FIRST, STIX-based sharing, or how to publish intelligence externally. Covers sharing models, standards, communities, and TLP-governed dissemination.

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

Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup

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

Initialize or improve AGENTS.md files that define how coding agents operate in a repo. Use when asked to set up or replace an agent init command (Codex, Claude), standardize multi-agent behavior, or audit an existing AGENTS.md for clarity, commands, boundaries, and repo-specific context. For Claude Code, also create CLAUDE.md as a symlink to AGENTS.md.

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

Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup

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

"Build three-statement financial models (Income Statement, Balance Sheet, Cash Flow) with revenue forecasting, assumption management, and scenario analysis. Use this skill when the user needs to project financials, build a fundraising model, create financial projections for a business plan, or evaluate M&A targets — even if they say 'build a financial model', 'project our revenue', 'how much money will we make next year', or 'model this acquisition'.".

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

"Implement Generalized Second Price auction for ad slot allocation and pricing. Use this skill when the user needs to understand search ad auctions, compute ad positions and costs-per-click, or analyze bidding dynamics — even if they say 'how does Google Ads auction work', 'ad rank calculation', or 'second price auction for ads'.".

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

"Calculate text similarity using lexical and semantic methods for matching and deduplication. Use this skill when the user needs to find similar documents, detect near-duplicates, or measure semantic closeness between texts — even if they say 'how similar are these texts', 'find duplicates', or 'semantic matching'.".

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

Stack-specific security implementation guidance (backend, frontend, database, infrastructure, operations) with auto-detection from your changes. Use when implementing a feature securely or hardening code as you write it. Trigger on "how do I secure this", "security best practices", "is this secure", "harden this". For scanning existing code use /security-verify.

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

Design component architecture, REST API contracts, and data models (Pydantic schemas) before implementation. Use when planning how to build a feature, defining endpoints, or modeling data. Trigger on "design the architecture", "design the API", "data model", "how should I structure this feature".

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

Exploit exposed GraphQL introspection endpoints to map the entire API schema. This skill details how to extract available queries, mutations, types, and fields, which significantly aids in identifying hidden endpoints, Broken Object Level Authorization (BOLA/IDOR), and mass assignment vulnerabilities.

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