「framing」の検索結果

Naturalistic causal reasoning for failures and disputed attribution. Use when postmortems or root-cause debates need reframing. NOT for causal inference, fault trees, or fully observed failures.

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

Generate the ≤10-minute Loom walkthrough script for a completed Weekly Community Signal report — a plain spoken briefing that dives straight into what the team needs to know, walking the report top to bottom (CopilotKit page first, then AG-UI in the same order). Straightforward and factual, NOT a radio show or a performance; no hype opener, no blame framing. Runs after every report (invoked by weekly-report) and on "loom script", "walkthrough script", "record the loom", "narrate the report".

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

Orchestrate an end-to-end data analysis or machine learning project from decision framing through reproducible handoff. Use when a request spans multiple lifecycle stages or an ambiguous modeling request must become a decision-ready result; use narrower audit or experiment-design skills for isolated reviews.

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

Use when surfacing tech debt as trackable items — interest-vs-principal framing, prioritisation by carrying cost, repayment plan — even if the user just says 'this codebase is a mess'.

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

Use when surfacing and prioritising risk before commit — blast-radius framing, mitigations, residual-risk verdict — even if the user just says 'what could go wrong here?'.

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

Turn a shipped changelog into a release narrative — value-not-feature framing, audience-segmented surfaces. Triggers on 'announce the release', 'write changelog post'.

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

Use when shaping a fuzzy product ask into a refined backlog item — problem framing, user-story rewrite, AC tightening — even if the user just says 'help me write this ticket'.

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

Use when shaping a capital-raise pitch — why-now / why-us / why-this framing, market-size reasoning, traction-story construction. Triggers on 'tighten the pitch', 'why-now is weak'.

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

Transforms data into compelling visual narratives by applying narrative structure, annotation techniques, scrollytelling patterns, and honest framing to data journalism, presentations, and infographics. Use when creating data-driven articles or reports, designing infographics with narrative, building scrollytelling experiences, annotating charts to guide interpretation, or when user mentions data storytelling, presentation design, annotated chart, narrative visualization.

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

Produces a deep, honest peer-review of how someone uses Claude Code by statistically analyzing their local session data (~/.claude/usage-data/ and ~/.claude/projects/). Trigger whenever the user asks to review, analyze, audit, or critique their own Claude Code usage, workflow, habits, or skill level — including phrases like "analyze my cc usage", "review my cc sessions", "peer review my cc workflow", "deeper than /insights", or any ask for an honest audit of their AI workflow. Also covers portfolio/hiring-manager framings (e.g. "portfolio for Anthropic/OpenAI/xAI"), but ALWAYS ask the user in Step 0 which version to build (self / hr / both) before running — never silently produce an HR report, because that version goes to outsiders and needs explicit privacy setup. The HTML report is laid out ledger-first for SELF (opening band, output/team/leak/trend ledgers, then peer review, 9-dim scoring, try-this-week, case study, claim-indexed evidence). The HR variant is a recruiter version v1: identity card, earned badges (threshold-based, earned-only), allowlist-filtered output ledger, one case study, and a methodology & scope disclosure — no scores, no peer-review memo, no charts.

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

Use this skill for any website, web application, frontend UI, component, layout, styling, refactor, or review. It enforces a self-contained editorial output standard: image-first composition, oversized typography, visible hairline grids, hard-edged rectangular framing, restrained copy, and review.

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

Elite mobile app image-generation skill for creating premium, app-native screen concepts and flows. Designed for iOS, Android, and cross-platform mobile products. Prioritizes clean hierarchy, comfortably readable text, strong multi-screen consistency, controlled color palettes, non-generic creative direction, textured surfaces, image-led composition, tasteful custom iconography, and clean phone mockup framing. By default, screens should be shown inside a subtle premium iPhone or similar phone mockup with a visible frame, while the main focus stays on the app content itself. This skill generates images only. It does not write code.

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

Orchestrate iOS screenshot automation with xcodebuild/simctl for build-run, AXe for UI actions, JSON settings and plan files, Koubou-based framing (`asc screenshots frame`), and screenshot upload (`asc screenshots upload`). Use when users ask for automated screenshot capture, AXe-driven simulator flows, frame composition, or screenshot-to-upload pipelines.

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

Knowledge base from NIST AI Risk Management Framework 1.0 (NIST AI 100-1). Use for AI risk management, trustworthiness characteristics, GOVERN/MAP/MEASURE/MANAGE functions, bias management, AI actor roles, TEVV, AI RMF profiles, and socio-technical risk framing. Does not cover sector-specific regulations, EU AI Act, ISO 42001 in depth, or the AI RMF Playbook tactical detail.

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

Knowledge base from the SD-22 DMSMS Guidebook (DSPO, FY24 working draft). Use for managing Diminished Manufacturing Sources and Material Shortages (DMSMS) and obsolescence across a long-lived system's life cycle: the five-step process (Prepare, Identify, Assess, Analyze, Implement) plus the Strategize overlay; standing up a DMSMS Management Team (DMT) and Management Plan (DMP); risk-based monitoring and surveillance (the risk cube, predictive tools, vendor surveys, GIDEP/DLA PDNs, critical-materials analysis); health assessments and resolution timing; costing and selecting resolutions (life-of-need buys, substitutes, redesign, technology refreshment) by AoA/BCA; and budgeting/executing resolutions through modification funding and the ECP process. Defense-sustainment / DoD-acquisition framing throughout. Does NOT teach general systems engineering, parts-management standards, or contracting law in depth, and does not reproduce DoD policy text or the source's tables and figures.

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

Ideenschürf-Workflow für festgefahrene, schwere Probleme (Beweise, Forschungsfragen, hartnäckige Design-/Architekturprobleme): einen Ideenspeicher über acht Schürftechniken füllen (Wiedererkennung, Fern-Disziplin-Analogie, Alltags-Allegorie, Störgefühl/Ästhetik, Märchen-Reframing, Web-/Literatur-Recherche, Geschwisterprojekte, Bestandsquerlauf), dann gegen bereits Versuchtes filtern, eine Idee wählen und bis zur Substanz verfolgen. Nutze diesen Skill, wenn ein Problem trotz mehrerer Anläufe feststeckt, wenn „neue Ideen für X" gebraucht werden, bei „wir drehen uns im Kreis", oder für periodische Innovations-Läufe über ein Projekt. Für breites, freies Ideensammeln ohne festgefahrenes Problem stattdessen brainstorm (SCAMPER, Six Hats etc.).

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

Reimagine an everyday photograph as a cinematic live-action film still using motivated lighting, source-aware framing and restrained color, with optional original subtitles. Use for 电影剧照, 日常电影画面, cinematic photo scenes, or a film-like moment from a supplied photograph.

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

Sell layer: raise the framing of an artifact to the scale it actually deserves without touching a single number. Use before anything goes outbound (post, pitch, README, CV, PR comment, landing page, application, DM) or before showing a finished artifact. Triggers: /fake-it, /fi, sell it, make it louder, strengthen the frame.

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

When the user wants to plan, build, or optimize SMS or MMS marketing — including welcome flows, abandoned cart texts, post-purchase, win-back, promotional sends, or transactional/auth SMS. Also use when the user mentions "SMS marketing," "text message campaigns," "SMS sequence," "SMS automation," "abandoned cart text," "post-purchase SMS," "Klaviyo SMS," "Postscript," "Attentive," "Twilio," "A2P 10DLC," "TCPA," "SMS compliance," "short code," "toll-free SMS," "MMS campaign," "should I do SMS," or "SMS vs email." For email sequences, see emails. For SMS copy framing, see copywriting. For opt-in popups that capture phone numbers, see popups.

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

When the user wants to design, construct, or improve an offer — the thing they actually sell — including value framing, bonus stacking, guarantee design, scarcity/urgency, naming, and payment structure. Also use when the user mentions 'offer,' 'offer design,' 'build an offer,' 'grand slam offer,' 'irresistible offer,' 'value stack,' 'bonus stack,' 'guarantee,' 'risk reversal,' 'money-back guarantee,' 'scarcity,' 'urgency,' 'high-ticket offer,' 'productize a service,' 'naming an offer,' 'payment plan,' 'down-sell,' 'upsell offer,' or 'why isn't my offer converting.' Best for services, agencies, courses, coaching, info products, high-ticket B2B, and direct-response. If you run pure self-serve SaaS, read pricing first — tiers and packaging do more work there. For price level itself (tiers, freemium, value metric), see pricing. For the page that presents the offer, see copywriting. For the launch moment, see launch. For sales collateral, see sales-enablement.

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

Use when the user asks to "map the category narrative", "tear down how competitors tell their story", or "find the language conventions in our market"; produces a category narrative map — the dominant stories and points of view in the category, its language conventions and framing clichés, and a per-competitor narrative teardown (arc, claimed onlyness, proof pattern) plus how each rival's messaging has shifted over time (scraped copy vs archived copy). Not for the positioning canvas itself — use positioning-mapper; not for the beachhead's beliefs and objections — use audience-belief-mapper; not for SERP keyword targeting — use keyword-research; not for claim adjudication — use offer-claims-registry. 品类叙事/竞争叙事拆解/语言惯例/叙事演变

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

Turn an authorized long-form video into a ranked set of YouTube Shorts candidates with vertical framing, captions, timestamps, and source provenance.

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

Translate creative intent into coherent cinematography, framing, camera, lens, lighting, motion, and sound direction for a video shot.

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

Elite mobile app image-generation skill for creating premium, app-native screen concepts and flows. Designed for iOS, Android, and cross-platform mobile products. Prioritizes clean hierarchy, comfortably readable text, strong multi-screen consistency, controlled color palettes, non-generic creative direction, textured surfaces, image-led composition, tasteful custom iconography, and clean phone mockup framing. By default, screens should be shown inside a subtle premium iPhone or similar phone mockup with a visible frame, while the main focus stays on the app content itself. This skill generates images only. It does not write code.

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