「style」の検索結果

Druckenmiller Strategy Synthesizer - Integrates 8 upstream skill outputs (Market Breadth, Uptrend Analysis, Market Top, Macro Regime, FTD Detector, VCP Screener, Theme Detector, CANSLIM Screener) into a unified conviction score (0-100), pattern classification, and allocation recommendation. Use when user asks about overall market conviction, portfolio positioning, asset allocation, strategy synthesis, or Druckenmiller-style analysis. Triggers on queries like "What is my conviction level?", "How should I position?", "Run the strategy synthesizer", "Druckenmiller analysis", "総合的な市場判断", "確信度スコア", "ポートフォリオ配分", "ドラッケンミラー分析".

Monitor dividend portfolios with Kanchi-style forced-review triggers (T1-T5) and convert anomalies into OK/WARN/REVIEW states without auto-selling. Use when users ask for 減配検知, 8-Kガバナンス監視, 配当安全性モニタリング, REVIEWキュー自動化, or periodic dividend risk checks.

Convert Kanchi-style dividend investing into a repeatable US-stock operating procedure. Use when users ask for かんち式配当投資, dividend screening, dividend growth quality checks, PERxPBR adaptation for US sectors, pullback limit-order planning, or one-page stock memo creation. Covers screening, deep dive, entry planning, and post-purchase monitoring cadence.

Define an illustration style guide — visual language, colour usage, and application rules. Use when commissioning or standardising illustration. For icons, use `icon-system` (design-systems).

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

Generate prompts for AI image tools to produce modern ML/RL paper-style figures matching the aesthetic of recent ICLR/NeurIPS/ICML 2024-2025 publications. Key traits — pure white canvas, white panels with soft drop shadow, rounded friendly font (Nunito/Poppins), densely packed but uncluttered floating elements, small pastel token squares, rich inline illustrations, colored keyword text, pill-shaped concept labels. Trigger phrases — "pastel风格论文配图", "现代ML论文配图", "modern ML figure prompt".

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

Audit, write, and improve developer documentation using Google's Developer Documentation Style Guide and Technical Writing courses. Use this skill for any documentation work, even when the user names no style guide: "audit our docs", "review this README", "write a README", "getting started guide", "how-to or tutorial", "API reference", "docstrings", "CLI help text", "changelog or release notes", "migration guide", or "our docs are confusing". Also use it when writing docs from code, rewriting a doc for clarity, fixing headings, procedures, or code samples, or enforcing consistent voice and terminology across a docs set — prefer it over editing documentation unaided. Covers reader and doc-type fit, second person and active voice, procedures, headings, lists and tables, code samples and placeholders, link text, notices, the word list, timeless docs, and accessibility. For code comments and naming, see clean-code. For marketing or landing-page copy, see storybrand-messaging.

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

Use when users ask for a hand-drawn or illustrated image prompt, name one of the repository's 20 numbered styles or the 3.1 stable variant, or mention triggers such as 亲子手绘、家庭蜡笔画、蜡笔、吉卜力、水墨、像素、淡彩速写、动画概念、水粉、北欧绘本、纸雕、软胶潮玩、墨线绘本、暖色扁平绘本、圆头红线、暖黄墨线、family-crayon-card、warm-flat-storybook、roundhead-redline、warm-yellow-ink-story. Produces prompt text or a formal reference-bearing call bundle and does not generate images.

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

Create and manage writing personas with NNGroup 4-dimension tone framework (Funny-Serious, Formal-Casual, Respectful-Irreverent, Enthusiastic-Matter-of-fact). Personas define readability targets, sentence length distribution, vocabulary tier, contraction frequency, and summary box label. Used by blog-write and blog-rewrite to enforce consistent voice. Use when the user says "create persona", "use persona", "list personas", or wants tone sliders and writing rules saved as structured JSON. Not for measuring style from existing posts (blog-style) or for audience, positioning, and taboo-phrase context files (blog-brand).

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

How to develop, modify, and extend the Claude Code codebase following its established programming style, patterns, and conventions. Use this skill whenever working on the claude-code source — adding tools, commands, utils, components, types, hooks, services, or fixing bugs. Also use when the user asks about claude-code architecture, coding standards, file organization, or wants to understand how the codebase works. This skill ensures all contributions match the existing codebase style exactly.

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

Create engaging Xiaohongshu (RED/小红书) content including titles, body text, hashtags, and image style recommendations. Supports multiple content types such as product reviews, tutorials, lifestyle sharing, and shopping guides with platform-specific optimization.

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

poteto's agent style for concise, detailed responses, deliberate subagents, unslopped prose, simple code, and verified work. Use for poteto, /poteto-mode, or requests to work in this style.

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

Analyze data with `forest-plot-styler` using a reproducible workflow, explicit validation, and structured outputs for review-ready interpretation.

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

Use facs gating viz style for data analysis workflows that need structured execution, explicit assumptions, and clear output boundaries.

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

Use when evaluating crypto through a Grayscale-style Crypto Sectors lens: sector taxonomy, FTSE/Grayscale index eligibility, fee/usage fundamentals, sector-share valuation, ETP/trust wrappers, and Zcash-style privacy-as-money theses.

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

Use when evaluating crypto narratives, attention rotation, memecoin cycles, Solana-style ecosystem momentum, social distribution, and reflexive retail flows in an Ansem-style crypto market framework.

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

Use this skill when the user wants a .pptx with smooth cross-slide animation — PowerPoint Morph transitions, Keynote-style continuous motion, shapes that grow / move / rotate as the slide advances. Trigger on: 'morph', 'morph transition', 'smooth transition', 'continuous animation across slides', 'Keynote-style transition', 'animated slide sequence', 'shape continuity across slides'. Output is a single .pptx. This skill is a scene layer on top of officecli-pptx — inherits every pptx v2 rule (visual floor, grid, palettes, connector canon, Delivery Gate 1–5a). DO NOT invoke for a generic deck, pitch deck, or board review without cross-slide motion — route those to officecli-pptx base or officecli-pitch-deck.

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

poteto's agent style for concise, detailed responses, deliberate subagents, unslopped prose, simple code, and verified work. Use for poteto, /poteto-mode, or requests to work in this style.

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

House style for user-facing documentation — voice, scope, structure, and what to leave out. Use this skill whenever writing, editing, or reviewing anything a user reads to learn how to use a tool — help center articles, getting-started guides, tutorials, feature docs, README usage sections, in-app help, release notes, or FAQ entries. Trigger it even when the request is phrased plainly — "document this feature", "write docs for X", "explain this to users", "write a README for this library", "turn these notes into a guide" — and even when no style guidelines are mentioned. Also use it to review existing docs for tone, bloat, or leaked implementation detail. Do not use it for internal engineering docs, architecture write-ups, RFCs, or code comments.

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

Korean and French screenwriting practice (韩国/法国编剧方法) — from the international masterclass; Oh Seung-uk (Christmas in August, The Shameless; field research in disguise, "write the emotion", first act and last act first, spaces as skeleton, reading to hostile listeners, surviving producers), Choi Seok-hwan (King and the Clown; genre as promise to the audience, "story = deepening crisis + intensifying desire", two reversals and bittersweet endings, the producer/director/writer trio), and Frédéric Auburtin (Paris je t'aime; dialogue last, Italian-style table reads, "12 lines not 13", dignity for characters, originals born from commissions, editing by emotion). Use when working in a Korean-style commercial drama or genre film, a French auteur/commission context, when planning field research, when a producer relationship is the problem, or when you need the Korean "three live together" development model or the French "emotion first, structure second" editing approach.

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

Writing screenplays in the style of Ozu Yasujiro and Noda Kogo (小津安二郎・野田高梧) — distilled from six complete screenplays (晚春 Late Spring, 麦秋 Early Summer, 东京物语 Tokyo Story, 浮草 Floating Weeds, 秋日和 Late Autumn, 秋刀鱼之味 An Autumn Afternoon). Covers the "family member leaves" master plot, off-screen events / on-screen reactions, lie-driven plots, minimal-syllable confessions, go-between characters, faceless suitors, pillow-shot scene breaks, echoing objects, mirror characters, children's subplots as metaphor, displaced quarrels, the single-monologue rule, diminishing endings, Ozu's script format and stage-direction vocabulary. Use when the user wants to write a quiet family drama, a 小津风 / 侘寂 / 日常系 script, a story about marrying off a daughter, aging parents, or wants dialogue that says less and means more.

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

Screenplay format, page craft, the writing process and adaptation (剧本格式/写作流程/改编) — merged from Wendy Henson (spec format rules), Richard Walter (page craft, revision), Neill Hicks (selling vs shooting script, draft chain), Syd Field (master shot, card method, adaptation as original work), Robert McKee (step outline → treatment → screenplay), Julian Hoxter (format elements, adaptation four questions), Diamond & Weissman (one-page nine-step) and Eric Bork — plus an exact typographic grid, element conventions (V.O./O.S., MORE/CONT'D, dual dialogue), a machine-writable output contract (Fountain, with forced markers for Chinese), and Asian industry formats (Chinese 场号制 影视剧本格式, Japanese 柱・ト書き・セリフ / 決定稿). Use when formatting a spec script, choosing the output file format, deciding what goes in action lines, planning drafts and outlines, cutting pages, adapting a novel, play or true story, writing a Chinese TV/film or Japanese-style script page, or preparing a submission-ready draft.

Create Ian Xiaohei-style HTML/SVG motion illustrations for Chinese articles, scripts, storyboard scenes, workflow explanations, concept metaphors, and short video visual aids. Use when the user asks for 小黑 SVG、漫画感 HTML、分层 SVG 动效、把小黑生图做成 HTML/SVG、可编辑矢量动效、口播流程动画、手绘漫画动效、正文配图动画, or wants a Xiaohei illustration style adapted into controllable HTML/SVG/GSAP output instead of raster image generation.

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

Create or revise Chinese social-media covers through the registered Skill-封面 asset system, reusable styles, presenter identities, ratio-specific layouts, and exact replacement prompts. Use only when the user explicitly says“skill-cover”“Skill-封面”“实战风格”, requests the registered style/gesture assets, asks for simultaneous 3:4 and 4:3 registered-layout output, replaces a reference cover's person with the current digital-human frame, or extends this registered cover system. Do not use for a generic“制作封面/生成封面”request; generic cover requests belong to dog-skill.

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

Production pipeline for mathematical and technical animations using Manim Community Edition. Creates 3Blue1Brown-style explainer videos, algorithm visualizations, equation derivations, architecture diagrams, and data stories. Use when users request: animated explanations, math animations, concept visualizations, algorithm walkthroughs, technical explainers, 3Blue1Brown style videos, or any programmatic animation with geometric/mathematical content.

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