「orr」の検索結果

Cards, drawers, carousels and other patterns borrowed from the physical world. Use when designing layout patterns, gestures or navigation paradigms.

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

Metallurgy of the major nonferrous structural and engineering alloys — aluminum, copper, titanium, nickel, magnesium, and their strengthening mechanisms. Covers precipitation (age) hardening in Al-Cu and Al-Zn-Mg systems, solid-solution strengthening in brass and bronze, alpha-beta titanium, nickel superalloys with gamma-prime, and the trade-offs in density, strength, corrosion resistance, and cost that decide when to leave steel for a lighter or more specialized metal.

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

Pragmatics and communicative competence across languages -- speech acts (Austin/Searle), Grice's conversational maxims and implicature, politeness theory (Brown & Levinson), face-threatening acts, discourse structure, turn-taking, repair strategies, register and formality, cross-cultural communication, communicative strategies (circumlocution, approximation, appeal for assistance), and the gap between grammatical competence and communicative performance. Use when teaching communication skills, analyzing cross-cultural misunderstandings, building conversational fluency, or understanding why grammatically correct sentences can be pragmatically inappropriate.

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

Catalog of informal fallacies with definitions, canonical examples, and detection heuristics. Covers relevance fallacies (ad hominem, straw man, red herring, appeal to authority, appeal to emotion), presumption fallacies (false dichotomy, complex question, begging the question), ambiguity fallacies (equivocation, amphiboly, accent), causal fallacies (post hoc, slippery slope, correlation-causation), and statistical fallacies (hasty generalization, cherry-picking). Use when evaluating arguments for rhetorical or informal reasoning errors.

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

Experience-based and environment-based learning design drawn from Dewey and Montessori. Covers Dewey's criterion of continuity and interaction, the reflective-thinking cycle, Montessori's prepared environment, sensitive periods, child-led inquiry, the role of self-correcting materials, project-based learning, and the relationship between autonomy and discipline. Use when designing hands-on activities, arranging learning spaces, integrating classroom work with real experience, or evaluating whether a lesson is genuinely experiential versus merely "activity-based."

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

Yoga practice with an emphasis on alignment, props, and staged progression as the Iyengar lineage teaches it, alongside enough context about the broader lineage landscape (Krishnamacharya's three students, modern Hatha, Ashtanga vinyasa, restorative, Yin, and chair yoga) that a routing agent can place a user correctly before giving instruction. Covers asana families, alignment heuristics, prop use, sequencing, and the non-negotiable injury-prevention rules. Use for any query about yoga postures, home practice design, teacher-training-level questions, or whether a given pose is safe for a given body.

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

Translation and interpretation as language meta-skills -- equivalence theory (Nida's formal vs. dynamic equivalence), translation strategies (borrowing, calque, transposition, modulation, adaptation), interpretation modes (simultaneous, consecutive, sight), source text analysis, register preservation, cultural adaptation, untranslatability and compensatory strategies, machine translation literacy, and back-translation for verification. Covers literary, technical, legal, and community interpreting contexts. Use when translating between languages, evaluating translation quality, teaching translation skills, or understanding the limits of cross-linguistic transfer.

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

Primary and secondary source analysis for historical reasoning. Covers source classification, sourcing (author/context/purpose), corroboration across multiple sources, contextualization within time and place, and bias detection. Use when evaluating historical evidence, assessing source reliability, or constructing evidence-based historical arguments.

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

Economic analysis of government intervention -- taxation (incidence, efficiency, optimal design), regulation (cost-benefit, market failure correction), externalities (Pigouvian taxation, cap-and-trade, Coasian bargaining), and public goods provision (non-rivalry, non-excludability, free-rider problem). Covers welfare analysis of policy interventions, government failure, and the institutional context of policy-making. Use when evaluating policy proposals, analyzing tax effects, assessing regulatory design, or reasoning about the appropriate scope of government action.

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

Designing interventions, systems, and policies for sustainability. Covers renewable energy (solar, wind, hydro, geothermal), sustainable agriculture (agroecology, permaculture, integrated pest management), conservation strategies (protected areas, corridors, rewilding), lifecycle analysis, circular economy principles, and policy instruments (carbon pricing, cap-and-trade, regulation). Use when evaluating or designing interventions that aim to reduce environmental impact while maintaining human well-being.

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

Reliability engineering for cloud systems — SLIs, SLOs, error budgets, SRE practices, runbooks, incident response, on-call rotation, blameless postmortems, chaos engineering, and the NASA Systems Engineering methodology (MCR/SRR/PDR/CDR/ORR phase gates, TAID verification, requirements tracing) adapted to cloud operations. Use when establishing SLOs for a new service, running an incident, writing a runbook, preparing a launch readiness review, or bringing NASA SE discipline to cloud deployments.

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

Systems programming from memory management through networking. Covers memory models (stack vs heap, manual allocation, garbage collection, ownership/borrowing), concurrency (threads, mutexes, channels, async/await, actor model, data races vs race conditions), operating system concepts (processes, virtual memory, page tables, system calls, file descriptors, signals), compilation (lexing, parsing, code generation, linking, static vs dynamic libraries), networking fundamentals (TCP/IP, sockets, HTTP, DNS, TLS), and the hardware-software boundary (caches, cache lines, false sharing, memory-mapped I/O). Use when working with low-level code, diagnosing system-level bugs, understanding performance characteristics, or bridging between high-level languages and machine behavior.

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

Use when the user asks "what should I work on", mentions GSD phases, ROADMAP, or .planning/ artifacts. Routes to the correct GSD command for the current project state.

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

Conversational guide for using tools/session-retro/observe.mjs to capture friction, wins, corrections, decisions, gaps, tool-use, and checkpoints as they happen during a session. Use at session start (to kick off the log), at inflection points (to record events), and at session end (to archive and feed the retrospective generator).

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

Before dispatching a multi-agent team, run a spectral diagnostic on the proposed communication graph and emit a (ρ, Δ, κ) coordination signature plus a pass/fail verdict against per-task-class thresholds. Builds the row-stochastic operator P from the team graph, computes the successor representation M = (I − γP)⁻¹, and ranks the topology for robustness (κ, condition number), consensus (Δ, spectral gap), and drift (ρ, spectral radius). Per Parks & Alharthi (arxiv 2605.11453), rank order on (κ, Δ, ρ) predicts coordination quality pre-execution with rank correlations of 1.0 / 0.5 / −1.0. Triggers: "dispatch the team", "team topology check", "before running the agents", "is this team configuration OK", "team pre-flight".

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

Manages skill-creator integration with GSD workflows including skill loading, session observation, bounded learning guardrails, and pattern detection. Use this skill whenever: executing any GSD phase (to ensure relevant skills are loaded first), starting or resuming a work session (to check for pending suggestions), the user asks about skills, patterns, or skill-creator status, performing code changes that might represent repeating patterns, the user corrects Claude's output (highest-signal observation), or when skill refinement, creation, or suggestion review is discussed. Critical for maintaining the adaptive learning layer.

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

Run this appropriateness check the moment you are about to integrate a retrieved long-term memory — a Grove content-addressed hit, a chroma/pgvector neighbour, a memory-consolidation digest, or a MEMORY.md line — into a response, especially anything touching private origins, Fox Companies IP, credentials, or Center Camp / consent-governed content. It answers a question intent-router never asks: not WHAT to fetch or HOW, but WHETHER a correctly-retrieved item should reach output. Relevance is not appropriateness — a perfect similarity match can still be a boundary violation. Default is FAIL-CLOSED: if in-context authorization is uncertain, the memory may inform behaviour but must not be surfaced. Backed by RBI-Eval (arxiv 2606.06055v1). Triggers on surfacing recalled sensitive memory into a response.

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

Use when you have captured session evidence — session-retro / session- observatory-live traces in .planning/patterns/, tool logs, correction records — and want to induce a reusable skill from it. Segments the traces into candidate skill units (an LLM judgment, not a deterministic parse) and decomposes each candidate into a four-part structured spec: workflow structure, execution semantics, and runtime attachments (verification, safety, rollback, state). It emits a spec object, NOT a finished SKILL.md, and hands that spec to skill-forge. It sits between skill-integration (upstream frequency detector) and skill-forge (downstream author). Backed by Agent-Trace-to-Skill Induction (arxiv 2606.06893v1). Triggers on inducing a skill from captured traces, turning a repeated pattern into a skill spec, and preparing evidence for skill-forge.

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

Produce valid, consistently named Gherkin story files with correct IDs, timestamps, and tags. Use when writing or updating story files.

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

Integrate MDMA into an application and build features with it — wire up parsing, the runtime store, React rendering, LLM streaming, custom components, prompts, and CI validation. Use this skill when the user asks to add MDMA to an app, build a chat that streams MDMA, author or maintain a custom prompt, validate MDMA documents, register a custom component, or expose MDMA to an agent via MCP. Generates focused, correct wiring that uses the right packages for the job instead of reinventing them.

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

This skill should be used when a story has been captured but content direction is unresolved - the spark describes WHAT to build structurally but not WHAT goes in it. Reads the story spark, splits it into Resolved (structurally clear) vs. Assumed (would have to guess) content dimensions, and surfaces each assumption for the human to confirm, correct, or expand. Also classifies implementation risk tags (has-variants, has-data-pipeline, has-animation, has-touch-targets, diverges-from-existing) so plan-chunks translates them into acceptance criteria that name the implementation mechanism. Captures answers into

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

Adhoc workflow for small targeted changes to existing behavior or appearance, without the full story ceremony. Use when the orchestrator encounters a bug with a clear root cause and surgical solution, OR a small enhancement to something already built (a different icon, wording, spacing, color). Triggers on: 'fix this', 'this is broken', 'the alignment is off', 'that button doesn't work', 'quick fix', 'patch this', 'tweak this', 'change the icon', 'adjust the wording', post-story corrections, or any situation where the write gate blocks a small targeted change. Acts NOW - a defect to file and fix later belongs in /craft:bugs, other deferred work in the notebook. Do NOT use for new features, design exploration, or changes requiring creative spark.

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

This skill should be used when validate-chunk reports test failures specifically, when the user says "tests are failing", "figure out what's wrong with the tests", "fix the failing tests", or when test assertions don't match expected output after chunk implementation. Triages whether the test or the implementation is wrong and fixes the correct one.

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

Use when skillsaw reports a likely false positive, misses an edge case, behaves incorrectly, or needs an RFE. Gather a safe report and, only with explicit user permission, create a feedback bundle or open a GitHub issue.

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