「craft」の検索結果

The art and science of narrative-driven brand communication. This skill transforms brand messages into compelling stories that connect emotionally, build memory, and drive action. In a world of infinite content, story is the only thing that cuts through. Great brands don't sell products—they tell stories. Apple tells the story of creative rebels. Nike tells the story of human potential. Patagonia tells the story of environmental stewardship. This skill teaches you to find, craft, and tell your brand's story across every touchpoint. AI amplifies storytelling capability—generating variations, adapting across channels, maintaining consistency—but the human insight that identifies the true story remains essential. This skill bridges narrative craft with AI execution. Use when "story, storytelling, narrative, brand story, origin story, hero journey, emotional connection, customer story, testimonial, case study, brand film, about us, storytelling, narrative, brand-story, emotional, hero-journey, content" mentioned.

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

The specialized craft of writing copy that sells—headlines that stop thumbs, body copy that persuades, CTAs that convert. This is copywriting specifically tuned for advertising: paid media, performance marketing, direct response. Ad copy is different from content writing. Every word costs money (CPM/CPC). Every character competes for attention. There's no time for warm-up—you have one chance to hook, persuade, and convert. The best ad copy feels effortless but is engineered word by word. In the age of AI-generated creative at scale, ad copywriting becomes both more important (you need more variations) and more challenging (everyone has access to the same tools). The differentiation is in the strategy, the insight, and the craft that AI assists but doesn't replace. Use when "ad copy, headline, ad text, CTA, call to action, Facebook ad, Google ad, ad variations, direct response, performance copy, primary text, ad headline, ad-copy, headlines, direct-response, performance, conversion, cta, advertising" mentioned.

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

产品设计 / UX 设计 (产品设计 / UX 设计 (Product Design / UX Design) — 数字产品的用户体验设计：从用户研究 → 信息架构 → 交互设计 → 视觉/UI → 可用性测试 → 设计系统的认知操作系统，面向 UX designer / product designer / interaction designer / UX researcher / design systems engineer / design lead，以及想入行、转岗、服务这行(设计外包、设计工具厂商、研究平台)的视角。覆盖: (a) 第一性张力 — **用户中心/研究驱动 (user-centered, 'you are not the user', research before pixels, observe behavior not opinions) ⇄ 商业目标/约束/交付 (business goals, north-star metrics, ship it, designer 服务于产品成功不是个人作品集)**; **设计直觉/品味/craft (taste, aesthetics, 'attractive things work better' — Norman 情感化设计) ⇄ 数据/实验/A-B 测试 (data-driven, metrics, experimentation, 'opinions are not data')**; **用户说的 (stated preference, 访谈里说喜欢) ⇄ 用户做的 (revealed behavior, 行为观察 > 自陈, usability test 看人真实卡在哪)**; **一致性/设计系统/规范 (consistency, design system, Jakob's law 用户带着别处的习惯来, 复用组件) ⇄ 创新/打破模式 (innovation, 该不该破规范)**; **减法/简化 (simplicity, Krug 'Don't Make Me Think', less but better — Dieter Rams) ⇄ 功能丰富/利益相关者塞需求 (feature creep, stakeholder pressure)**; **UX(体验/流程/研究) ⇄ UI(视觉/像素/组件)** 的职责之争, **designer 该不该写代码 (design engineer / 'should designers code')**; (b) 核心工作流 / pipeline (最标准、最易蒸高质量+CLI 化) — Double Diamond (发现 discover → 定义 define → 开发 develop → 交付 deliver) / Design Thinking (共情 empathize → 定义 → 构思 ideate → 原型 prototype → 测试 test) / Design Sprint (Jake Knapp 5 天冲刺); 完整链: 用户研究 (访谈/问卷/可用性测试/卡片分类) → persona / journey map / JTBD → 信息架构 IA + 用户流 user flow → 线框 wireframe (低保真) → 交互/原型 prototype (高保真) → 视觉 UI / 设计系统落地 → 可用性测试 usability testing → handoff 给开发 → 度量迭代 (北极星 / HEART 框架); (c) 工具栈 — 设计/原型 (Figma 绝对主导 / Sketch 衰退 / Adobe XD 已停更 / Framer 高保真+建站 / Penpot 开源 / Principle / ProtoPie 微交互); 协作白板 (FigJam / Miro / Mural); 用户研究 (Maze / UserTesting / Lookback / Dovetail 研究库 / Optimal Workshop 卡片分类树测试 / Hotjar / Microsoft Clarity 热图); 设计系统/交付 (Storybook / 蓝湖(中) / Zeplin / design tokens / Tokens Studio); 度量 (Amplitude / Mixpanel / 北极星指标); AI 新兴 (Figma AI / v0 by Vercel / Galileo AI / Uizard / Cursor 给 design engineer); (d) 知识正典 — Don Norman《The Design of Everyday Things》(affordance/signifier/mapping 圣经)、Steve Krug《Don't Make Me Think》(可用性入门)、Alan Cooper《About Face》《The Inmates Are Running the Asylum》(交互设计/persona 起源)、Jakob Nielsen 10 Usability Heuristics + NN/g 文章库、Jake Knapp《Sprint》、Jeff Gothelf《Lean UX》、Teresa Torres《Continuous Discovery Habits》、Erika Hall《Just Enough Research》、Julie Zhuo《The Making of a Manager》、《Refactoring UI》(Adam Wathan/Steve Schoger)、《Universal Principles of Design》、Laws of UX (Jon Yablonski)、《100 Things Every Designer Needs to Know About People》(Susan Weinschenk)、IDEO/Stanford d.school 设计思维材料; (e) figures/流派 — 认知心理/人因派 (Don Norman 认知科学奠基、Susan Weinschenk 行为心理、Kathryn Whitenton); 可用性工程派 (Jakob Nielsen 启发式/折扣可用性、Steve Krug、Jared Spool UIE); 交互设计/目标导向派 (Alan Cooper goal-directed/persona、Kim Goodwin); 设计思维派 (IDEO Tim Brown、David Kelley d.school); 精益/持续探索派 (Jeff Gothelf Lean UX、Teresa Torres continuous discovery、Marty Cagan《Inspired》产品发现); 设计系统/系统化派 (Brad Frost Atomic Design、Nathan Curtis design tokens、Alla Kholmatova); 视觉/UI craft 派 (Adam Wathan & Steve Schoger Refactoring UI、Dieter Rams 'less but better' 工业设计遗产); 设计领导/职业派 (Julie Zhuo、Aarron Walter 情感化设计、John Maeda); 移动优先 (Luke Wroblewski 'Mobile First'); (f) 行业话术/黑话 — affordance 可供性 / signifier 意符 / mental model 心智模型 / IA 信息架构 / heuristic evaluation 启发式评估 / usability 可用性 / a11y accessibility 无障碍 / WCAG / persona 用户画像 / journey map 用户旅程 / JTBD jobs-to-be-done / north-star metric 北极星 / HEART 框架 / wireframe 线框 / mockup / prototype 原型 / fidelity 保真度 (lo-fi/hi-fi) / design system 设计系统 / design token 设计令牌 / atomic design 原子设计 / component library 组件库 / handoff 交付 / red routes 关键路径 / dark pattern 暗黑模式 / Fitts's law / Hick's law / Jakob's law / Miller 7±2 / progressive disclosure 渐进披露 / above the fold / hamburger menu / skeuomorphism vs flat / micro-interaction / empty state / edge case / happy path / design debt 设计债 / dogfooding / dot voting / affinity mapping 亲和图 / card sorting 卡片分类 / tree testing / A/B test / NPS / SUS (System Usability Scale); (

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

Sentence-level and section-level craft for instructions Claude will actually follow, in any container — project instructions, a standalone prompt, or skill body text. Use when the text exists or is being drafted and the question is quality: "why is Claude ignoring this instruction", "rewrite this prompt so it works", "improve my project instructions", "make this instruction stick", "is this too prescriptive", "how much structure does Sonnet need versus Opus". Covers imperative construction, positive framing, strategic-versus-procedural calibration per model, extended thinking, complexity scaling, and a quality checklist. For deciding WHICH container the instruction belongs in, use crafting-instructions. For building, testing and packaging a whole skill directory, use creating-skill.

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

Craft-first interface design for dashboards, admin panels, SaaS apps, tools, settings pages, data interfaces, and interactive products. Use when designing, building, reviewing, auditing, or refining product UI where visual craft, layout hierarchy, tokens, states, visual direction, or design-system consistency matter. Not for marketing pages, landing pages, campaigns, or brand-only work.

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

Applies the reasoning of Mary Wollstonecraft (18th-century English philosopher and author of A Vindication of the Rights of Woman) to evaluate situations involving power dynamics, education, independence, gender roles, and systemic inequality. Use this skill whenever Claude encounters career trade-offs involving financial dependence, analyzing structural oppression, questioning societal norms, or balancing reason against emotion. It helps dismantle arbitrary hierarchies, prioritize rational capability over superficial elegance, and frame personal struggles as political realities.

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

Build conversion-optimized landing pages with CRO frameworks (Conversion Research, LIFT Model), scroll effects, A/B testing, personalization, form optimization, and Core Web Vitals (INP, LCP, CLS). Use when user asks to create a landing page, sales page, lead generation page, or improve conversion rates. Do NOT use for full product design (use component-forge), animation-specific (use motion-craft), or brand identity (use design).

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

Design multi-device layouts with Container Queries, clamp() fluid typography, :has() selector, subgrid, and modern CSS units (dvh/svh/lvh). Use when user asks to make a layout responsive, handle mobile/tablet/desktop breakpoints, create fluid typography, or use Container Queries. Do NOT use for full-page layouts (use landing-craft), component design (use component-forge), or animation-specific responsive (use motion-craft).

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

🇺🇸 GitHub README Writing System — Craft a README that converts visitors to stars in <3 seconds. Proven structure from AFFiNE's 0→60K star journey: tagline engineering, first-screen law, section-by-section copywriting guide, Claude Code integration section, anti-patterns, and a pre-publish checklist. Use when you need to write or rewrite a specific README file. 🇨🇳 GitHub README 写作系统 — 打造 3 秒内把访客转化为 star 的 README。来自 AFFiNE 0→60K star 实战：tagline 工程、首屏法则、逐节文案指南、Claude Code 集成板块、反模式、发布前自检清单。需要写或改一个具体 README 文件时使用。 🇯🇵 GitHub README 作成システム — 3秒以内にビジターをスターに変えるREADMEを作る。AFFiNE 0→60Kスター実績から: タグライン設計、ファーストスクリーン法則、セクション別ライティングガイド、Claude Codeインテグレーション、アンチパターン、公開前チェックリスト。 🇰🇷 GitHub README 작성 시스템 — 3초 안에 방문자를 스타로 전환하는 README 작성법. AFFiNE 0→60K 스타 실전: 태그라인 설계, 첫 화면 법칙, 섹션별 카피라이팅 가이드, Claude Code 통합 섹션, 안티패턴, 게시 전 체크리스트. Triggers: "write README" | "README template" | "GitHub README" | "project description" | "tagline" | "open source README" | "README structure" | "README review" | "fix README" | "rewrite README" | "README写作" | "写README" | "README模板" | "项目介绍" | "开源项目文案" | "改README" | "README检查" | "README 구조" | "README 작성" | "README 검토" | "READMEの書き方" | "READMEレビュー"

DDEV local development environment for Craft CMS projects. ALWAYS load this skill when running any ddev command, configuring .ddev/config.yaml, or troubleshooting local container issues. Covers config.yaml (project type, PHP/Node versions, database, docroot), shorthand commands, add-ons and built-in Mailpit, custom commands, Vite dev server exposure, database import/export, Xdebug toggling, sharing local sites, and troubleshooting (port conflicts, container restarts, ddev-injected env vars silently overriding your .env or config/general.php).

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

Hacker News post crafter — given a product, feature, or story produces a ready-to-post HN submission (title ≤80 chars, no marketing), honest body text with technical depth, no outbound links, predicted reception analysis, and comment-response templates for likely pushback. Use when asked to "write an HN post", "craft a Show HN", "prepare our Hacker News launch", or "help me post on HN".

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

Request write permission from the user before making file changes. MUST be invoked before any write attempt when the write gate is closed. Creates scoped approval via AskUserQuestion + TaskCreate, opens the write gate, and closes it when work is done. Triggers: write hook blocks an edit, agent is about to write files outside .craft/, agent needs to modify project source files. This skill requires user approval 100% of the time - never bypass AskUserQuestion.

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

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 the user asks to "brainstorm", "explore options", "get creative", "what if we...", or selects "Let's get creative" during story or cycle creation. NOT for a bare vague feature idea where generating options would mean inventing the premise first - that routes to /craft:riff (riff first, options after). Generates 2-3 creative options with trade-offs, visual direction for UI stories, and wireframes.

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

House rules and craft for LaTeX Beamer slide decks (lectures, seminars, talks), drawn from the author's own Overleaf edits and published slide-design guidance. Covers storyboarding, frame titles, slide prose, word and frame budgets, layout without overfull boxes, XeLaTeX fonts and Korean (xeCJK), color, figures and screenshots, Overleaf source hygiene, speaker notes, and a build-and-QA loop with a contact sheet. Use when writing, editing, reviewing, or building a Beamer deck, theme, or storyboard. A course skill supplies course facts and the frame skeleton; this skill supplies the craft. Not for HTML or PowerPoint decks, posters, or papers.

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

Orchestrates the AI-Controlled Party mixer/Soundcraft Ui24R design team. Use whenever the user wants to design, update, refine, re-run, or implement-plan the Soundcraft Ui24R scene-arming expansion, mixer-aware AI party, operator-approved mixer cues, snapshots/cues/show control, Companion bridge, or any follow-up based on prior mixer design results. Produces a spec for tdmcp-pipeline; does not implement runtime code.

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

Create stunning, animation-rich HTML presentations from scratch or by converting PowerPoint files. Use when the user wants to build a presentation, convert a PPT/PPTX to web, or create slides for a talk/pitch.

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

Design new proteins that bind a chosen surface, using BindCraft's AlphaFold2-guided hallucination or the RFdiffusion backbone plus ProteinMPNN sequence pipeline. Use this skill to specify a target epitope by hotspot residue, trim a receptor to the region worth designing against, set up a design campaign, and filter the output on the in-silico metrics that predict experimental success — interface predicted TM-score, predicted aligned error at the interface, buried surface area, and shape complementarity. Also trigger on BindCraft, RFdiffusion, ProteinMPNN, minibinder, hallucination, inverse folding, hotspot residue, epitope targeting, ipTM, or de novo binder.

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

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 evidence needs grading before anyone reasons from it — the user asks "how reliable is this?", "grade this source", "check this report", "can I trust this article?", "is this corroborated?", or hands over a URL, a pasted report or a Liberty91 event ahead of an ACH or assessment. The Quality of Information Check from the CIA Tradecraft Primer, adapted for vendor and press CTI reporting. Resolves each document to its originating source, splits it into claims, and grades every claim on two written elements, access level (how the source knows) and claim support (what backs the statement), with a stated rationale, using a fixed rubric with hard caps. The grade is not an Admiralty rating. Five outlets citing one vendor report count as one source; anything that cannot be traced to a primary is capped, not guessed. Returns a graded claim table, gaps, a deception screen and JSON. /ach, /threat-assessment and /writing-assessments run it first by default.

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

当用户要把教材/考纲/讲义/某领域知识加工成 AI 苏格拉底老师能拿去上课的教学蓝本（pure-blueprint）或一本给人读的流畅教材（human-readable，AI 也能直接教）时使用。适用任何学科，有教师用书可针对应试。触发词："造一本教学蓝本/做一本 XX 教材/按这套方法写一本书/复刻这个 skill 的写法"。

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

Use when a task needs the judgment of an Aircraft Structure, Surfaces, Rigging, and Systems Assembler — deciding whether an out-of-tolerance hole or fastener needs a nonconformance report versus a field fix, verifying torque and calibration status before a fastener installation, diagnosing a FOD (foreign object debris) risk before closing a structure, or reading a drawing callout against a conflicting work instruction.

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

Write, restructure, or review documentation — tutorials, how-to guides, reference pages, concept/explanation docs, API references, READMEs, changelogs, release notes, and troubleshooting guides. Distills documentation craft from Mintlify's guides (compiled from technical writers at Stripe, GitHub, Amplitude, and Anaconda), the Diátaxis framework (including the compass and per-type voice), the Google and Microsoft style guides, Every Page Is Page One, Write the Docs, and Docs for Developers: audience analysis, content-type selection, style and word-level rules, procedure writing, structure for humans and AI agents, code-example standards, page templates (templates.md), mechanical enforcement and llms.txt (mechanics.md), maintenance, and success metrics. Use this skill when the user asks to "write docs", "document this feature", "improve this page", "review these docs", "write a tutorial / how-to / reference page", "structure the docs", "write API documentation", "write a README / changelog", or when authoring any file under a `docs/` tree. For SKMTC docs specifically, this skill governs the *craft* (what makes the page good); the content split between skills, `llms.md`, and the docs tree is governed by `docs/skills/README.md`. Distinct from `skmtc-retro` (captures observations about work) and the `skmtc-*` operational skills (guide doing the work) — this skill guides writing *about* the work for readers.

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

Operate Aavegotchi Gotchiverse player workflows on Base mainnet (8453): alchemica channeling, surveying and harvesting, crafting installations/tiles, building on parcels (equip/unequip/move/batch equip), installation upgrades, craft/upgrade queue management, and parcel access-right management. Use when interacting with Realm/Installation/Tile diamonds via subgraph-first discovery and onchain verification/execution with Foundry cast.

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