「som」の検索結果

Enter explore mode - a thinking partner for exploring ideas, investigating problems, and clarifying requirements. Use when the user wants to think through something before or during a change.

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

Delegate tasks to AI agents via Box0. Use when the user asks to review code, check security, run tests, compare tools, get multiple perspectives, research a topic, analyze data, write docs, or any task that could benefit from specialized or parallel execution. Also use when the user mentions agent names or says "ask", "delegate", "get opinions from", or "have someone".

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

Plan and run manual tests of the project's running app. Runs a session in one of five modes: exploratory, verification, smoke, assessment (UX, localization, accessibility, improvement review), or AI probe. Also writes a manual test plan that holds only what automated tests cannot judge. Use whenever the user asks, in any language, for something to be tested by hand or for a manual test plan — "manual test", "exploratory test", "bug hunt", "verify the bug fix", "smoke test", "QA this screen", "review this screen's UX", "what would you improve", "check the localized copy", "test the AI agent's answers", "write manual test cases", "kịch bản test manual" — or assigns a test design, test plan or test-case IDs to execute by hand. Not for writing automated tests.

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

Coach structured brainstorming sessions on any topic: diverge on ideas together, then converge on priorities and next steps in a session document. Use whenever the user wants ideas or wants to think out loud, in any language ("brainstorm with me", "give me ideas for…", "help me come up with…", "let's explore options for…", "I'm stuck on the name / the features"; Vietnamese "brainstorm cùng tôi", "cho tôi ý tưởng", "nghĩ cùng tôi xem"), even when they never say "brainstorm". Also use when the user wants multiple perspectives or a devil's-advocate pass on their ideas ("give me different angles", "phản biện mấy ý tưởng này", "party mode"). Not for diagnosing why something is failing (problem-solver), user research (design-thinking), or company-level strategic bets (strategy-board).

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

Conduct rigorous, citation-backed desk market research: quick go/no-go market scans, market sizing (TAM/SAM/SOM), competitor analysis, customer demand signals, and trend/macro (PESTEL) analysis. Use this skill whenever the user wants to research, size, validate, or enter a market — "is there a market for…", "how big is the market for…", "who are the competitors of…", "should I build/launch/sell…", "validate this business idea", "market research for…", "market entry" — in any language and for any country's market (e.g. "nghiên cứu thị trường", "étude de marché", "市場調査", "análisis de mercado"), even when the user never says the words "market research". Also use it when another skill or workflow (strategy-board, design-thinking, a product brief) needs external market facts delivered into its fact base or research folder.

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

Diagnose problems before solving them: turn "X is broken and we don't know why" into a precise problem statement, verified root causes, solutions traced to those causes, and a rollout plan. Use whenever the user reports something failing, breaking, slowing, or recurring without a known cause: "sales dropped and we don't know why", "this keeps happening", "why does X keep failing", "find the root cause", "run a post-mortem", "5 whys"; Vietnamese "sao cứ bị vậy hoài", "tìm nguyên nhân gốc", "X đang hỏng mà không rõ vì sao". Trigger even when the user asks for solutions directly: "give me ideas to fix falling sales" is a diagnosis request. Not for open-ended ideation when nothing is broken (brainstorm-coach), understanding user needs (design-thinking), or company-level strategic bets (strategy-board).

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

Socratic questioning partner named Gadfly for deep learning through dialogue. Use this skill when the user wants to learn, understand, or explore a topic through questions rather than explanations. Trigger when the user says "teach me about...", "help me understand...", "I want to learn...", "ask me questions about...", "quiz me", "Socratic method", "Gadfly", or wants to deeply understand something through dialogue rather than passive reading. Also trigger when the user provides a text or document and wants to be questioned about it, or wants to check their own understanding of a concept.

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

Enter explore mode - a thinking partner for exploring ideas, investigating problems, and clarifying requirements. Use when the user wants to think through something before or during a change.

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

Debug validator checkpoint inconsistencies where some validators are behind others. Use when alerts mention "checkpoint inconsistency", "validators behind", or "inconsistent latest checkpoints", or when asked to debug validator sets, investigate validator delays, or troubleshoot metadata fetch failures for a chain. Defaults to default_ism app context if not specified.

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

A skill that allows a user to validate that a warp route deployment will be in the expected state after applying some configuration

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

Estate Planning & Legacy Protection for the Owens family. Tracks wills, trusts, beneficiary designations, life insurance, survivor benefits, and powers of attorney. Ensures Lindsey and the kids are protected if something happens to Tory. Triggers on: "Estate plan", "Will", "Life insurance", "Beneficiaries", "What happens if", "Legacy", "Survivor benefits", "Power of attorney", "Trust", "Estate check", "Beneficiary audit", "SGLI", "FSGLI", "Dependent education", "Chapter 35". The only estate plan that fails worse than a bad one is no plan at all.

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

Elite frontend design taste for building, reviewing, and polishing web interfaces. Use whenever the user wants to design, redesign, shape, critique, audit, polish, or improve any UI (landing pages, portfolios, dashboards, product UI, components, forms, onboarding, empty states) or asks to make something look better / premium / modern, fix the styling, add or fix animations, or make a design feel less generic ("AI slop"). Covers typography, color, spacing, layout, visual hierarchy, motion, micro-interactions, component states, accessibility, responsive behavior, UX copy, and anti-pattern detection.

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

Guide a researcher step by step into an unfamiliar research field, or decode a paper, abstract, figure caption, or referee comment they cannot parse. Builds understanding in rungs (motivation, vocabulary, core framework, methods, frontier), anchored to what the user already knows, with a checkpoint before each advance. Use when the user says they are new to a field, asks what a research area or method is, says an explanation was too technical, asks to be walked through something step by step, asks for a reading path, or supplies dense research text. Trigger even when the user only names an unfamiliar field or pastes an abstract without asking to be taught. Do not trigger for a one-line summary, a short overview request, or a direct factual answer; do not use it for translation, editing, search, debugging, or specialist questions inside the user's own field. Also trigger in other languages, including Chinese such as 入门, 一步一步讲, 看不懂, 这篇论文讲什么, 帮我理解这个领域.

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

Use when asked to write a product brief, turn a feature idea into a spec, define requirements for something to build, or clarify what a product should do and why. Examples: "write a brief for X", "turn this idea into a spec", "what should we build here", "help me define requirements".

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

Design direction advisor — generates 3 differentiated visual directions with live HTML demos for selection. Use when the brief is vague ("make something nice", "pick a style", "explore directions"), when no design system exists, or when the user wants to compare visual approaches before committing. Richer than /form-style: produces actual visual demos, not just recommendations. Trigger words: "design direction", "style exploration", "pick a direction", "what should this look like", "give me options", "explore styles", "design philosophy".

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

Ship the Seekter kit to git. Branch, commit and push the tracked, person-independent files (skills, references, scripts, templates) after a run has taught the kit something. Use when the user runs /seekter-git or asks to commit, push, or open a PR for the changes made to Seekter itself.

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

Foundational concepts in nutrition science — macronutrients, micronutrients, energy balance, Atwater factors, reference intakes (DRI/RDA/AI/UL), food composition tables, and the methods of human nutrition research. Grounds the rest of the department in a shared vocabulary and in the measurement limits of the field, including controlled-trial history, observational-study limits, and the biochemical basis for calorie accounting. Use when a question asks what something "is" nutritionally, how energy and nutrients are measured, or what the reference numbers mean.

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

Extending propositional and predicate logic with modal operators -- necessity and possibility, and their relatives (obligation, knowledge, belief, time). Covers Kripke possible-worlds semantics, accessibility relations, the main modal systems (K, T, S4, S5), translation from natural language, and applications in epistemic, deontic, and temporal reasoning. Use when ordinary logic is insufficient to capture distinctions like "must" vs "might," "knows" vs "believes," "always" vs "sometimes."

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

Economics of low-income countries and the structural transformation from agrarian poverty to industrial prosperity. Covers growth models (Solow, endogenous growth, unified growth theory), the role of institutions (inclusive vs. extractive), inequality measurement and dynamics (Gini, Lorenz curve, Kuznets), poverty traps and their mechanisms (nutritional, financial, geographical), foreign aid debates, and the capability approach as an alternative development metric. Use when analyzing why some countries are rich and others poor, evaluating development interventions, or reasoning about the relationships between growth, inequality, institutions, and human well-being.

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

Carbon chemistry, functional groups, IUPAC nomenclature, isomerism, reaction mechanisms (substitution, elimination, addition), polymers, and biochemistry basics. Covers hydrocarbon classes (alkanes, alkenes, alkynes, aromatics), common functional groups (alcohols, aldehydes, ketones, carboxylic acids, esters, amines, amides), stereochemistry, condensation and addition polymerization, and the four biomolecule classes (carbohydrates, lipids, proteins, nucleic acids). Use when analyzing organic structures, predicting reaction products, or connecting chemistry to biology.

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

Practical naked-eye and binocular sky observing. Covers dark adaptation, limiting magnitude, constellation recognition, star hopping, the messier and Caldwell catalogs accessible without a telescope, the Moon, planets, meteor showers, aurorae, and the ethics and habits of observing under light-polluted and dark skies. Use when teaching someone to find their way around the sky, planning a naked-eye session, or choosing a first binocular tour.

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

Transform a user's builder vision into a complete, executable GSD mission package. Use this skill whenever a user has described what they want to BUILD (a product, tool, feature, system, educational pack, or ecosystem component) and wants it structured for GSD execution. Triggers include: 'structure this for GSD', 'make this into a milestone', 'turn this vision into a mission', 'package this up for Claude Code', 'create the mission files', 'I want to hand this to GSD', 'make me a mission package', or any request to decompose a described system into wave-based executable tasks. Also trigger when the user has a vision doc already written and needs mission decomposition. Prefer this skill over generic document creation whenever the GSD ecosystem is mentioned alongside building something.

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

Project state awareness and session recovery for GSD-managed projects. Use this skill whenever: starting a new work session, resuming after a break, the user asks "where did we leave off" or "what's the current state", before making substantial code changes (to check for existing plans), the user seems disoriented about project status, or when something seems off and STATE.md might have relevant context. Also activates when the user references .planning/ files, milestones, phases, or project progress.

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

Generates engineering-standard drawings (P&ID, SLD, floor plans, isometric) with ISA-5.1 and IEEE symbol libraries in SVG/DXF format. Activates for drawing generation, diagram creation, blueprint packaging, and output formatting from verified engineering calculations.

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