「how to use」の検索結果

Fix ArgoCD ExternalSecret deployment failing with "namespace X is not permitted in project Y". Use when: (1) ExternalSecret shows OutOfSync in ArgoCD but won't sync, (2) ArgoCD application status shows "namespace X is not permitted in project 'infrastructure'", (3) ExternalSecret targets a namespace managed by a different ArgoCD project, (4) Using apps-of-apps pattern with separate infrastructure and application projects.

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

Fix "Fastly error: unknown domain" 500 errors when custom domains return "Domain Not Found" despite being created with domain-v1 CLI. Use when: (1) fastly domain-v1 create succeeds but domain returns 500, (2) Domain shows activated:false in API response, (3) Classic domain API returns "deprecated" error, (4) Custom domain works on edgecompute.app but not on your domain. Covers Fastly Compute domain setup post-September 2025.

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

Use when implementing show users that content is being loaded.

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

Use when implementing show users that content is being loaded.

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

Analyze and improve business processes. Trigger with "this process is slow", "how can we improve", "streamline this workflow", "too many steps", "bottleneck", or when the user describes an inefficient process they want to fix.

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

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).

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

One-time setup for absolute: interview how you want it to behave (output style, autonomy, TDD strictness, spec dir, families) + detect the stack once, then write `.absolute.config.json` (project, committed) and `~/.absolute/config.json` (user defaults + per-project overrides). Every other absolute-* command reads it instead of re-detecting; non-blocking — commands proceed without it and soft-recommend it. Triggers on "absolute init", "set up absolute", "initialize absolute", "configure absolute", "first-time setup", "remember my conventions for this repo".

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

Think and work like an expert Cellular Neuroscientist. Use when a task calls for Cellular Neuroscientist judgment. Treat the neuron as a cable with active channels, not a point integrator unless you have shown it is one for your question. Separate voltage, calcium, and fluorescence observables. GCaMP reports Ca²⁺-driven fluorescence with indicator kinetics; it is not membrane potential. FRET sensors (ArcLight, ASAP) trade speed and dynamic range differently.

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

Use when an agent must make TwelveLabs do real video-understanding work: indexing footage, semantic/visual search across an archive, generating descriptions, summaries, chapters, highlights, and tags from video, producing multimodal embeddings, or wiring TwelveLabs into a media-production pipeline (NLE panels, logging, compliance review, metadata). Covers the current model families (Marengo for search/embeddings, Pegasus for video-to-text analysis), the v1.3 Video Understanding API (indexes, assets, tasks, search, analyze, embed), prompt construction for analysis, capability and format limits, pricing/quota math, output quality review (hallucination and timestamp accuracy), and privacy/rights obligations when footage shows real people. Not for generating or editing video pixels — this is analysis and retrieval.

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

Use this skill to plan, direct, troubleshoot, and hand off provider-independent live or hybrid livestream event productions, including run of show, crew, capture, audio, graphics, switching, guests, encoding, ingest, transport choices, latency, redundancy, accessibility, moderation, monitoring, incidents, recording, and delivery.

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

Use when an agent needs to make a HyperFrames video of a Strudel live-coding track, where the code itself is the picture and every token lights up on the note it plays. Trigger on: "strudel video", "live coding video", "show my code playing", "make a video of this track with the code", "prod by claude". Covers composing the track, recording it offline from pinned Strudel, and building the 1080x1080 video (typed opener, parts powering on, real Strudel theme switches, graffiti ASCII drops, typed sign-off).

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

Build Sankey, alluvial, river, and CONSORT-style flow diagrams to visualize cohort transitions, cell-state changes, or pipeline filtering using ggalluvial, networkD3, plotly, and consort. Use when showing how entities move between categories across timepoints (cell states, drug response classes, patient flow through a trial) or filtering pipelines (variants filtered through QC stages).

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

Remove sequencing adapters from FASTQ files using Cutadapt and Trimmomatic. Supports single-end and paired-end reads, Illumina TruSeq, Nextera, and custom adapter sequences. Use when FastQC shows adapter contamination or before alignment of short reads.

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

A warm-canvas editorial interface for Anthropic's Claude product. The system anchors on a tinted cream canvas with serif display headlines, warm coral CTAs, and dark navy product surfaces (code editor mockups, model showcase cards). Brand voltage comes from the cream/coral pairing — deliberately warm and humanist where most AI brands use cool blue + slate. Type voice runs a slab-serif display ("Copernicus" / Tiempos Headline) for h1/h2 and a humanist sans for body. The signature Anthropic black-radial-spike mark anchors the wordmark.

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

MiniMax presents itself as a premium AI infrastructure brand through a striking duality — bold black-pill CTAs and stark white canvas for marketing, paired with vibrant gradient product cards (orange-red, magenta-pink, purple, blue) that turn each model release into a distinctive visual identity. The system uses DM Sans across all surfaces, employs an oversized 80px hero display, anchors major actions in deep near-black pills, and layers content density via a 3-column documentation grid with sidebar nav, prose body, and TOC. Coverage spans the marketing homepage, model showcase pages, developer documentation, and platform pricing surfaces.

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

Build Rust TUI apps with SuperLightTUI v0.20 (immediate-mode terminal UI). Use this skill when the user asks to create, modify, or debug terminal UI code in this repo, or asks "how do I X in SLT / TUI / terminal", or types Korean triggers like "터미널 UI", "TUI 만들어줘", "SLT로", "ratatui 대신". Read REFERENCES.md for feature flags and doc pointers; grep `src/context/` and `src/widgets/` before inventing any API.

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

Build Rust TUI apps with SuperLightTUI v0.23 (immediate-mode terminal UI). Use this skill when the user asks to create, modify, or debug terminal UI code in this repo, or asks "how do I X in SLT / TUI / terminal", or types Korean triggers like "터미널 UI", "TUI 만들어줘", "SLT로", "ratatui 대신". Read REFERENCES.md for feature flags and doc pointers; grep `src/context/` and `src/widgets/` before inventing any API.

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

Classify product approach into one of six types (Clone, Unbundle, Undercut, Slice, Wrapper, Innovation) based on competitive landscape. Triggers on PRD v0.2 work after competitive analysis, or when user asks "what type of product should we build?", "should we clone or innovate?", "is this a fast-follow opportunity?", "how should we position against competitors?", "clone vs undercut", "unbundle vs slice", or requests help choosing product strategy. Outputs BR- entries for product type classification and inherited GTM constraints.

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

Define how system components connect, establishing boundaries, patterns, and integration approaches during PRD v0.6 Architecture. Triggers on requests to design architecture, create system design, define component relationships, or when user asks "design architecture", "system design", "how do components connect?", "architecture decisions", "technical architecture", "system overview". Consumes TECH- (stack selections), RISK- (constraints), FEA- (features). Outputs ARC- entries documenting architecture decisions with rationale. Feeds v0.6 Technical Specification.

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

Define success criteria and tracking setup for launch during PRD v0.9 Go-to-Market. Triggers on requests to define launch metrics, set up tracking, or when user asks "how do we measure launch success?", "launch KPIs", "tracking setup", "success criteria", "analytics", "launch goals". Outputs KPI- entries specialized for launch measurement.

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

Explain a body of work plainly so a person actually understands it. Runs the `how` and `why` skills and weaves what they find into one clear explanation. Use for 'teach me this', 'help me really understand X', 'explain this change or subsystem to me'.

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

Designs the public interface of a module before any implementation exists: writes the caller scenarios first, produces three candidates with genuinely different shapes, type-checks each one against the scenarios, scores them on measurable criteria and records the decision. Use when someone says "design the API for this module", "what should this signature look like", "compare interface options", "this function is awkward to call", "show me alternatives before I build it", or is about to add a module, library entry point, endpoint or command that other code will depend on.

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

World-class growth strategy expertise combining Andrew Chen's marketplace and network effects wisdom, Brian Balfour's growth frameworks, Casey Winters' Pinterest/Grubhub playbooks, and the best of Silicon Valley growth thinking. Growth is not marketing. Growth is the systematic application of product, engineering, and data to create compounding user acquisition, activation, and retention. It's a mindset, not a department. Use when "growth strategy, how do we grow, acquisition strategy, retention strategy, viral growth, network effects, growth loops, product-led growth, plg, ltv cac, unit economics, growth model, flywheel, compound growth, channel strategy, referral program, activation rate, magic moment, aha moment, growth experimentation, growth, strategy, acquisition, retention, viral, network-effects, plg, loops, experimentation" mentioned.

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

Expert in understanding and navigating legacy codebases. Covers code archaeology techniques, finding hidden knowledge, mapping dependencies, and extracting understanding from code without documentation. Knows how to read the stories that old code tells. Use when "legacy code, old codebase, understand this code, archaeology, what does this do, no documentation, ancient code, " mentioned.

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