「book」の検索結果

Use this skill when the user asks about Stripe Connect configuration, charge patterns, Dashboard access, or how to get started with Connect, is building a marketplace, platform, multi-vendor store, gig platform, or subscription platform, needs to pay out sellers, vendors, or providers, mentions split payments, revenue sharing, multi-party payments, or similar payment distribution concepts, provides a company URL or business description for a recommendation, builds SaaS that routes money between parties (for example, POS, booking, invoicing — not operational SaaS without payment routing), asks about onboarding or KYC for merchants, sellers, and vendors, mentions connected account Dashboard or responsibility configurations, or asks about payment flows, white-label payments, or embedded payments.

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

Design an auditable playbook when no narrower one fits: a large migration, an ambitious multi-part change, or work a human reviews after stepping away. Scales rigor to the task, runs a hypothesis loop, and logs decisions. Use for /figure-it-out or 'figure it out'.

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

Guides users through pstack setup, /poteto-mode, and picking the skill, playbook, or principle for a task. Type /poteto-help with a question.

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

Build a dense, data-heavy screen - an analytics console or a trading terminal - with real charts drawn from tokens: candlestick, volume, depth, stacked area, waterfall, scatter, correlation matrix, donut, gauge, sparklines, heatmaps and order books. Use when the request is a dashboard, terminal, monitoring view, data console, or any screen whose job is to show many numbers at once. Covers the layout sequence, the SVG geometry, the accessibility contract per chart type, and the contrast traps that only appear in dark mode.

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

Deterministic handbook-grounded retrieval and thermocouple computations for reflow profile compliance outputs such as ramp, TAL, peak, feasibility, and selection.

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

Comprehensive spreadsheet creation, editing, and analysis with support for formulas, formatting, data analysis, and pivot tables. When Claude needs to work with spreadsheets (.xlsx files) for: (1) Creating new spreadsheets with data and formatting, (2) Reading or analyzing Excel data with pandas, (3) Creating pivot tables programmatically with openpyxl, (4) Building multi-sheet workbooks with source data and pivot table sheets, or (5) Any Excel file operations

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

Google Text-to-Speech (gTTS) for converting text to audio. Use when creating audiobooks, podcasts, or speech synthesis from text. Handles long text by chunking at sentence boundaries and concatenating audio segments with pydub.

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

Read Microsoft Excel (.xlsx) files robustly with `openpyxl` (or `pandas`). Covers multi-sheet workbooks, header rows, empty cells, merged cells, comma-separated list cells, and converting a sheet to a list-of-dicts the rest of your code can consume. Use when a task input or reference document is an `.xlsx` file rather than JSON/CSV.

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

Standing rules for how any role in an OpenOPC company coordinates with its peers — work-item discipline, messaging, meetings, and blocking collaboration. Loaded only in company_mode.

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

Automatically organizes invoices and receipts for tax preparation by reading messy files, extracting key information, renaming them consistently, and sorting them into logical folders. Turns hours of manual bookkeeping into minutes of automated organization.

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

Extracts and analyzes competitors' ads from ad libraries (Facebook, LinkedIn, etc.) to understand what messaging, problems, and creative approaches are working. Helps inspire and improve your own ad campaigns.

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

Creates comprehensive technical documentation from existing codebases. Analyzes architecture, design patterns, and implementation details to produce long-form technical manuals and ebooks. Use PROACTIVELY for system documentation, architecture guides, or technical deep-dives.

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

Mainland-Chinese TV-series craft, documents and production chain (国产剧创作体系与制片链) — the China layer parallel to the Japanese and Korean/French skills. Distilled from Yao Kougen 姚扣根《电视剧写作概论》(2016; series taxonomy, four Chinese script formats, the 3-minute/15-minute/episode-end suspense law, 36 situations), Zhang Wei 张巍《电视剧改编教程》(2014; five source types, sell-point migration, six case studies), Zhang Mingzhi & Song Peiyi《电视剧出品人与制片人教程》(2016; running-time rules, two-stage censorship, scene-breakdown sheet, contracts), Zhao Binbin《影视剧片段改编教程》(2016; film to stage fragment), plus official Chinese renderings of US TV terms from the translated Douglas and Blum textbooks. Use when writing or judging a 国产剧, turning a novel or IP into a 30–50 episode drama, writing a 策划书 / 分集梗概 / 人物小传, formatting a Chinese teleplay, sizing episode count and word count, checking content red lines and the 立项/备案/审查 chain, reading a Chinese screenwriter contract, or mapping US series vocabulary onto Chinese usage.

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

Worked full-length scripts of banqiang-system Chinese opera with their creation records (板腔体全本语料库). Primary texts; 翁偶虹《锁麟囊》 (the revised score edition, 65 arias, 15 self-account-vs-score checks), 汪曾祺等《沙家浜》 (the 1965 text, not the 1970 one; 36 arias, a 12-row two-version diff), 田汉《白蛇传》 (the 1955 book, not the web revision; 16 scenes, 王瑶卿说腔五条), 杨兰春《朝阳沟》 (1978 revival, 50 arias, 口语入唱, per-scene sung/spoken ratios), 魏明伦《潘金莲》 (跨时空, missing pages), 罗怀臻's 越剧《李清照》《真假驸马》, 淮剧《金龙与蜉蝣》, 甬剧《典妻》; plus index tables of 翁偶虹's 60 创作记 and 范钧宏's seven 改编札记. Use when you want to see how a 唱工戏 lays out its 板式, need real scene counts, aria counts and 辙口 to imitate, want the road from raw material to 审腔, are writing a 现代戏 or colloquial lyrics, or compare one author across two声腔 systems. Method is in sw-chinese-opera-banqiang; this skill holds the worked scripts and their creation records.

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

终极口播视频 skill：中文口播稿 + 成品配音 → CPU 字级时间戳 → SHOTBOOK 层矩阵分镜 → Remotion 电影感成片（横屏默认/竖屏）。当用户要"做口播视频"、"解说/科普视频"、"把文案变成视频"、"给配音配画面动效"时使用。默认使用成品配音，可选 Fish Audio 从稿子合成配音与时间戳；数字人生成技术不在本 skill 内（人物素材是输入）。含统一视觉语言（Apple 范式）、108 张动效配方卡、镜头三面分层工作单、七层镜头反PPT系统（极缓推拉相机/让位，运动做减法）、六式运动承接转场（每式一卡）、长镜头世界画布、anime.js+three.js 桥、自动静止检测 + 独立 subagent 评估循环。

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

Generate synthetic datasets in a Jupyter notebook after the dataops synthetic-data preflight passes. Use when creating new synthetic data or preparing a guarded local replacement candidate from an approved source.

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

OpenVEX v0.2.0 specification reference plus VEX management playbooks - Brought to you by microsoft/hve-core.

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

Research-only RPI playbook that gathers task evidence, writes dated research artifacts under .copilot-tracking/research/ or a caller's trusted evidence root, and hands off planning-ready findings. Use when the user needs evidence, alternatives, or task framing first.

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

Combined codebase health dashboard that scores a project across all four quality dimensions — PR quality, architecture, tech debt, and test quality — in a single pass, drawing on twelve classic engineering books. Triggers when: user wants an overall quality assessment, asks "how healthy is this codebase?", "run all the checks", "I need a health score before the release", or wants to onboard a new team with a quality overview. Do NOT trigger for: server health checks, HTTP health endpoints, Kubernetes liveness/readiness probes, database health, or application uptime. Also do not trigger when the user specifically requests only one dimension — use the corresponding focused skill instead (brooks-review / brooks-audit / brooks-debt / brooks-test).

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

Test quality review drawing on twelve classic engineering books — with primary focus on xUnit Test Patterns, The Art of Unit Testing, How Google Tests Software, and Working Effectively with Legacy Code — that diagnoses structural problems in an existing test suite: brittleness, mock abuse, coverage illusions, slow execution, poor readability. Triggers when: user asks about test quality, shares test files for review, or expresses frustration: "tests keep breaking whenever I change anything", "our tests take forever", "tests pass but bugs still reach production", or "we have too many mocks". Do NOT trigger for: writing new tests from scratch (use the regular test-writing workflow) or testing framework/syntax questions — this skill reviews an existing suite for structural quality problems, not individual test authoring.

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

PR code review that surfaces decay risks, design smells, and maintainability issues with concrete Symptom → Source → Consequence → Remedy findings, drawing on twelve classic engineering books. Triggers when: user asks to review code, check a PR, shares a diff or pastes code asking "does this look right?" / "any issues here?" / "ready to merge?", or asks for feedback on a function, class, or file. Also triggers when user mentions: code smells / refactoring / clean architecture / DDD / SOLID principles / Hyrum's Law / deep modules / tactical programming / conceptual integrity / Brooks's Law / Mythical Man-Month / second system effect. Do NOT trigger for: questions about how to write code from scratch, language syntax questions, or framework/tool questions where no existing code is shared.

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

Architecture audit that maps module dependencies, checks layering integrity, and flags structural decay across a codebase, drawing on twelve classic engineering books. Triggers when: user asks to audit architecture, review folder/module structure, check for circular imports, understand how the codebase is organized, or asks "does this follow clean architecture?" or "why does everything depend on everything?". Also triggers for onboarding requests: "explain this codebase to a new developer" or "give me a codebase tour" (use onboarding mode). Do NOT trigger for: PR-level code review (use brooks-review) or line-level refactoring questions — this skill analyzes structural/module-level concerns, not individual functions.

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

Full-sweep mode: runs a unified analysis across all quality dimensions — code decay, architecture, tech debt, and test quality — then applies fixes directly to the codebase. Safe changes are auto-applied; risky changes are confirmed before execution. Drawing on twelve classic engineering books. Triggers when: user wants to "fix everything", "sweep the codebase", "auto-fix all issues", "clean up the whole project", or asks for a single command that both diagnoses and remediates quality problems. Do NOT trigger for: read-only audits or health reports where the user only wants findings without code changes; single-dimension reviews (use the focused skill instead: brooks-review / brooks-audit / brooks-debt / brooks-test); server health checks, HTTP /health endpoints, Kubernetes probes, database health, or application uptime.

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

Tech debt assessment that identifies, classifies, and prioritizes maintainability problems — helping teams build a refactoring roadmap — drawing on twelve classic engineering books. Triggers when: user asks about tech debt, refactoring priorities, what to clean up first, or asks "why is this so hard to change?", "what should we fix first?", or "how do I justify refactoring to management?". Do NOT trigger for: server health checks, HTTP /health endpoints, Kubernetes probes, database health, or application uptime — "health" in those contexts is infrastructure, not code quality. Also not for single-function refactoring questions.

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