「framing」の検索結果

Use when evaluating grant ideas, diagnosing proposal logic, framing fundable projects, strengthening reviewer-aware arguments, or preparing to write any section of a research proposal.

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

Satori is a clinically informed wisdom companion for navigating the inner life — emotions, meaning, grief, purpose, relationship, identity, and the questions that don't resolve easily. Activate when someone is processing something difficult, wrestling with a life question, seeking perspective, or simply needs to think alongside someone who won't rush them toward an answer. Also activate when someone uses language like "I've been struggling with," "I don't know what to do," or "I need to figure out" — or any emotionally charged framing. When in doubt, activate. Draws from Taoism, Buddhism, Stoicism, Christianity, Sufi wisdom, Hindu philosophy, Confucian ethics, and African thought, alongside modern psychology, neuroscience, and trauma-informed frameworks (IFS, DBT, CFT, Schema Therapy, Somatic). Uses Motivational Interviewing, Voss tactical empathy, McAdams Life Story, and Singer Self-Defining Memory — woven naturally, not mechanically.

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

Content distribution plan — takes a completed piece and produces a channel-by-channel plan covering HN, Reddit, LinkedIn, newsletter, and Twitter/X, with timing, per-channel framing, and a repurposing plan. Use when asked to "distribute this post", "how do we promote this article", "write distribution copy for this piece", or "where should we share this".

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

Engineering design cycle covering requirements elicitation, specifications writing, constraint identification, iterative prototyping, and design communication. Spans the full loop from problem definition through ideation, analysis, prototyping, testing, and redesign. Includes morphological charts, TRIZ, Pugh matrices, design reviews, and the distinction between functional and non-functional requirements. Use when framing engineering problems, generating design alternatives, writing specifications, or running design reviews.

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

Techniques for generating novel ideas, reframing problems, and escaping fixed mental models. Covers lateral thinking (de Bono), Six Thinking Hats, random stimulation, provocation operators (PO), analogical transfer, assumption challenging, and divergent-then-convergent thinking cycles. Use when the goal is to produce new options or perspectives rather than evaluate existing ones.

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

Supervised and unsupervised learning, bias-variance tradeoff, cross-validation, decision trees, ensemble methods, neural network fundamentals, and the practitioner's workflow from problem framing through deployment. Covers classification, regression, clustering, dimensionality reduction, regularization, hyperparameter tuning, and evaluation metrics. Use when building predictive models, selecting algorithms, or understanding the machine learning pipeline.

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

Recognition and mitigation of systematic reasoning errors documented in the heuristics and biases tradition. Covers confirmation bias, availability, anchoring, representativeness, framing effects, hindsight bias, overconfidence, and motivated reasoning. Each bias is presented with its mechanism, diagnostic signal, and structured mitigation. Use when you suspect your own or another reasoner's conclusions may be shaped by systematic cognitive distortion rather than evidence.

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

DRAFT. Score Luma/RSVP lists, approve against capacity, produce host-hit shortlists and day-of door packs. Systems framing — not a marketing CSV dump. Not installed by deepline skills.

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

Drafts or audits a scientific paper’s introduction and framing — the real-world "why", an evidence audit, the funnel from theory to a falsifiable if-then with a named estimand, bridges across experiments, and a contribution list matched to the design. Use when the user asks to write, restructure, or critique an introduction, motivate or frame a paper, repair a gap-in-the-literature opening, sharpen or calibrate a contribution claim, or connect experiments into one argument. Sentence-level flow and wording are out of scope.

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

Decompose work into stages with physical artifacts and acceptance checklists. Gap detector. Use when opening a WP ≥3h (open-loop/problem-framing) or on explicit request to break into stages. Executes R29 Decomposer role.

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

Senior engineer conducting thorough, constructive code reviews. Round-2+ reviews use adversarial framing to find missed cases and convergent failure modes.

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

Internal downstream skill for ctf-sandbox-orchestrator. CTF-sandbox workflow for parser differentials, HTTP normalization gaps, ambiguous headers, path decoding drift, transfer-framing mismatches, and request smuggling routes. Use when the user asks to trace proxy and backend parse differences, conflicting path normalization, Host or forwarded-header ambiguity, CL/TE issues, or routing outcomes that differ across hops. Use only after `$ctf-sandbox-orchestrator` has already established sandbox assumptions and routed here.

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

Expert sales negotiation strategist for B2B deal-making. Use when planning negotiation strategy, handling discount requests, closing deals, navigating procurement, or structuring win-win agreements. Covers anchoring, framing, BATNA development, multi-party negotiations, and contract terms. Use for enterprise deals, pricing discussions, and high-stakes negotiations.

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

Use when the user brings any fuzzy, half-formed, or interrupt-driven input — an order from a boss, a forwarded email thread, a ticket, a chat message, a "can you look into X", a raw idea — and it needs framing before work starts. Turns the input into a structured brief (Context · Desired outcome · Goal · Owner · Next step · Decision needed). This is the AIOS's front door; run most things through it first. Trigger on "/structure", "frame this", "what's the actual ask here", "structure this", or any vague task that lacks a defined outcome.

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

Use when the user asks for a client report, a monthly or activity report, a case study draft, or says 'what did i ship this month'. Turns the site audit log into a written report in one of six framings: agency client report, case study, internal recap, testimonial draft, build-in-public, personal recap.

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

Design focused empty states for zero-data, no-results, permission, and error situations with clear value framing, strong CTAs, and less dead chrome. Use when the user mentions blank pages, zero-data screens, no results, permission states, or dead controls—not broader onboarding strategy.

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

AI pressure redirection — handling conflicting demands, tool failures, and competing constraints by blending with incoming force then reframing. Use when receiving contradictory instructions from different sources, during tool failure cascades where the planned approach becomes unviable, when scope pressure threatens to expand the task beyond what was asked, or when user frustration or correction needs to be absorbed rather than deflected.

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

Sustained neutral pattern recognition across systems without urgency or intervention. Maps naturalist field study methodology to AI reasoning: framing the observation target, witnessing with sustained attention, recording patterns, categorizing findings, generating hypotheses, and archiving a pattern library for future reference. Use when a system's behavior is unclear and action would be premature, when debugging an unknown root cause, when a codebase change needs its effects witnessed before further changes, or when auditing own reasoning patterns for biases or recurring errors.

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

Use when one reviewer angle is insufficient or the user suspects a direction is tunnel-visioned or inherited its framing. Modes: artifact, direction. Not for source or remote-system changes.

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

This skill should be used when the user asks to "make a Spotify Wrapped style video", "build a year in review / year-in-review video", "create a personalized data video", "generate a recap video", "build a wrapped video generator", "turn a data table into shareable videos", or "make per-user stat videos". Covers the data row → one shareable video pattern, the Wrapped scene grammar (big-number reveals, top-X lists, superlatives), animated data counters, vertical 9:16 framing, and batch-rendering many personalized videos from one template.

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

Content angle generator for turning dry expert topics into high-engagement infotainment. Applies 7 journalistic angle types (Myth vs Reality, Paradox, Level Error, Price of Solution, Conditions, Hidden Driver, Contrary Thesis) + historical/future lens + news-hook framing. Use when experts need their content to become interesting rather than just informative - blog posts, video scripts, social content, newsletters, landing pages, ad hooks. For any niche: B2B, B2C, services, products, personal brand.

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

Use when a release needs launch framing, sequencing, channel choices, and rollout logic across product, growth, and support.

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

Assesses a research paper outline (.qmd file) against structured criteria from Kosuke Imai's empirical research guide. Evaluates the abstract and section outline for: research question clarity, stated contributions, hypotheses and testable implications, data description, planned results and inferential approach, and robustness checks. Detects causal papers from the abstract and conditionally assesses identification strategy only when causal framing is present. Produces a structured markdown report with PASS/PARTIAL/FAIL assessments and actionable suggestions. Use when asked to assess, evaluate, review, or check a paper outline, abstract-and-outline, or research plan in a .qmd file.

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

Phase 0 validation gate — problem framing, competitive analysis, feasibility, and a go/no-go checkpoint before committing to a feature. Use when evaluating whether an idea is worth building, before /story or /design. Trigger on "is this worth building", "validate this idea", "discovery", "should we build".

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