「how to」の検索結果

Reference for the `odu` runner — how to invoke a full pipeline, a single recipe, or a platform-pinned node, and how to attach to a live run, from a project whose CI odu runs. Trigger when the user asks to "run CI", "run the pipeline", "re-run a check", or names a specific recipe by `<recipe>@<platform>`.

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

REQUIRED before writing code for any feature touching auth, payments, credentials, tokens, sessions, file upload, user data, untrusted input, deserialization, network endpoints, or data deletion. Scope by that surface, not the task label — a research/experimental/local-only feature with none of it doesn't need this. Invoke it, record answers inline in the design doc or PR description, then write the code. Skipping this is how auth bypass, token leakage, and delete-the-wrong-record bugs ship. If the feature touches any of those surfaces and this hasn't run, the design is incomplete — do not proceed to implementation.

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

"Apply the Dynamic Capabilities framework (Teece et al., 1997) — sensing, seizing, and transforming — to analyze how firms adapt, integrate, and reconfigure competences in rapidly changing environments. Use this skill when the user needs to explain why some firms sustain advantage while others decline, evaluate organizational agility, distinguish operational from strategic capabilities, or when they ask 'how do we stay competitive as the market shifts', 'why did this firm fail to adapt', or 'what capabilities do we need to build'.".

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

"Apply the Knowledge-Based View (Grant, 1996) and Nonaka and Takeuchi's SECI model to analyze how organizations create, transfer, and integrate knowledge for competitive advantage. Use this skill when the user needs to design knowledge management systems, understand why knowledge transfer fails across teams, evaluate knowledge creation processes, or when they ask 'how do we capture tacit knowledge', 'why does knowledge stay siloed', or 'how can we turn individual expertise into organizational capability'.".

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

"Apply framing theory to analyze how selection, emphasis, and exclusion shape interpretation of issues. Use this skill when the user needs to deconstruct media or organizational frames, evaluate how different frames affect audience perception and decision-making, or design strategic communication frames — even if they say 'how is this issue being portrayed', 'why do people see this differently', or 'how should we frame this message'.".

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

"Apply the Elaboration Likelihood Model to design persuasion strategies by matching message type to audience elaboration level. Use this skill when the user needs to craft persuasive communications, choose between argument-based and cue-based messaging, predict attitude durability after a campaign, or when they ask 'why did the message fail to persuade', 'how to change resistant attitudes', or 'should we use data or endorsements'.".

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

"Apply Bhaskar's critical realism to analyze phenomena through three ontological domains (real, actual, empirical), identify generative causal mechanisms via retroduction, and examine structure-agency interplay. Use this skill when the user needs to go beyond surface correlations to underlying causes, design research that distinguishes mechanisms from events from experiences, or when they ask 'what causes this beyond the observed pattern', 'what structures enable or constrain this behavior', or 'how do I move from correlation to causal explanation'.".

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

"Apply behavioral economics concepts including bounded rationality, prospect theory, mental accounting, and nudge theory to analyze decision-making biases. Use this skill when the user needs to understand why people make irrational economic decisions, design choice architectures, or apply nudges to influence behavior — even if they say 'why do customers make bad choices', 'how do we encourage people to save more', or 'design a better default option'.".

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

"Apply Moore's business ecosystem framework to analyze how firms co-evolve through four stages (birth, expansion, authority, renewal) and occupy different ecosystem roles. Use this skill when the user needs to map ecosystem dynamics in a platform or industry, evaluate keystone vs dominator strategies, assess ecosystem health, or when they ask 'what stage is this ecosystem in', 'how should we position in this ecosystem', or 'why is this ecosystem declining despite having a dominant player'.".

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

"Apply agenda-setting theory (McCombs & Shaw) to analyze how media salience transfers to public perception. Use this skill when the user needs to study media influence on public opinion priorities, evaluate issue salience transfer across media and public agendas, or design communication strategies that leverage agenda-setting effects — even if they say 'why is everyone talking about this topic', 'how does media shape public priorities', or 'which issues get attention and why'.".

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

"Apply the Balanced Scorecard (BSC) framework to translate strategy into measurable objectives across Financial, Customer, Internal Process, and Learning & Growth perspectives. Use this skill when the user needs to set strategic KPIs, create a strategy map, align organizational goals, or connect daily operations to strategic vision — even if they say 'how do we measure strategy execution' or 'our KPIs feel disconnected'.".

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

"Apply Ansoff Matrix to evaluate growth strategy options across market and product dimensions. Use this skill when the user needs to decide how to grow — through existing vs new markets and existing vs new products. Also use when the user asks 'how should we grow', 'should we launch a new product or expand to new markets', or 'what's our growth strategy'.".

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

"Calculate price elasticity of demand to quantify how price changes affect sales volume. Use this skill when the user needs to estimate demand sensitivity, set optimal prices, or evaluate the revenue impact of price changes — even if they say 'how sensitive are customers to price', 'will a price increase hurt sales', or 'elasticity calculation'.".

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

Hand a Prisma Next question or report off to the team — file a GitHub issue (bug or feature request), or route Q&A / design discussion / direct-team-contact to the Prisma Discord at pris.ly/discord. Use for bug, bug report, file an issue, report a bug, feature request, missing feature, this should be a feature, file this, this is a bug, this is broken, surprising behaviour, this doesn't work, file feedback, send feedback, capability gap, file via prisma-next-feedback, ask the team, talk to the team, talk to the Prisma team, talk to Prisma, Discord, Prisma Discord, Q&A, design feedback, is this the intended way, how should I do X, extension author question, extension author needs help.

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

Use when asked how other design systems handle a component, prop, token or pattern; to name a component, prop or token; to research best practices (composition, when to split, a11y, responsiveness, motion) before building; or for a design-system discovery or benchmark report. Compares Coinbase CDS, Adobe Spectrum, Astryx, Material, Primer, MetaMask DS and Base UI, anchors the recommendation in Lumen's code, and outputs a shareable HTML report.

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

Use when implementing or updating a component from a Figma link — how to turn the Figma design variables into code tokens, on both platforms: Tailwind classnames for libs/ui-react and themeJS (`t.*`) paths for libs/ui-rnative. For the full token catalogues and styling mechanics, see component-styling.

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

Identify and exploit misconfigured Spring Boot Actuator endpoints. This skill covers how to extract sensitive configuration details, heap dumps, environment variables, and ultimately escalating to Remote Code Execution (RCE) via `spring-cloud-starter` vulnerabilities.

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

Exploit JSON Web Tokens (JWT) by implementing the 'None' algorithm attack. This skill details how to bypass authentication mechanisms when a server improperly accepts JWTs with the `alg` header set to `none`, allowing attackers to forge tokens without a valid signature.

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

Generate interactive, animated, responsive HTML-based terminal simulators to showcase CLI commands, scripts, pipelines, or interactive workflows. Use this whenever you need to visually showcase a command line sequence, mock interactive CLI tools, or simulate code executions.

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

Use this skill whenever the user wants to see how their branch will look on the live Gaia website before merging — "preview this branch", "show me what this looks like", "deploy a preview", "trigger a design preview", "can I see the site with these changes", "preview the skill profile", "check how this renders on the site", "spin up a preview deployment". This skill dispatches a Cloudflare Worker preview deployment for the current branch via GitHub Actions — no local build tooling required. Ideal for containerized environments, design reviews, and confirming that newly curated skills or profile pages render correctly before a PR is merged to main. The preview does NOT regenerate docs; it deploys `docs/` from the branch as-is. If your change depends on regenerated Class S artifacts, run `gaia dev docs` and commit those first — the preview then reflects them.

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

Explains DSP math concepts to developers who need the theory behind an algorithm. Use whenever the user asks how a signal-processing concept works, wants intuition behind a formula, or hits a math-shaped bug. Trigger on phrases like "how does a Fourier transform work", "explain z-transforms", "what is convolution", "why does my biquad ring", "what is windowing for", "what causes aliasing", or "how do I convert gain to dB". Also trigger when the user pastes DSP code and asks why it behaves a certain way.

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

Guides implementation of custom Wwise or FMOD DSP plugins from scratch — effect, source, and mixer plugin types. Use when the user wants to create a new Wwise plugin, build an FMOD DSP effect, or implement a custom game audio middleware plugin. Trigger on phrases like "create a Wwise effect plugin", "build an FMOD DSP", "implement custom game audio middleware plugin", "how do I write a Wwise source plugin", or "set up an FMOD DSP description".

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

Show a Google Search Console performance dashboard for the last 28 days. Displays total clicks, impressions, CTR, and average position, plus top 25 queries and top 25 pages. Use when user says "GSC overview", "search console performance", "how is my site doing in Google", "clicks and impressions", or "show me my GSC data".

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

How to use the coding agents installed on this machine (claude, codex, droid, grok, vktr, hermes, opencode, copilot, pi) as plain sub-agents in orchestrated workflows: one headless invocation, one prompt in, one result out. Deliberately ignores each CLI's own orchestration features (droid --mission, codex multi_agent, hermes delegation/moa/kanban, grok --agents, opencode personas). The orchestrator is whatever session is running the skill; the CLIs are interchangeable workers. Use when the user asks "which agent should run this", "fan out workers", "run X headless", or when a lifeos skill (overnight, timeboxed-iterating, workgraph, gauntlet, bughunt, dark-factory) needs to launch an agent CLI, or when a worker needs company context it should ask Viktor for (vktr).

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