「awe」の検索結果

Generates premium, multi-page, mobile-optimized (1:1 aspect ratio) PDF marketing brochures for exclusive retreats, workshops, luxury events, or any high-end product/service offering. Use this skill whenever a user asks to create a brochure, marketing PDF, event flyer, WhatsApp marketing material, social media brochure, or design a multi-page promotion document. Also trigger when users mention wanting to promote an experience, product, or service and need visual marketing material. Even if the user just says "make a brochure for my event" or "I need a PDF for my product," use this skill.

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

Use when the user wants to find or discover a Claude Code skill that is NOT already installed — e.g. "is there a skill for X", "find me a skill that…", "what skills exist for…", or "/find-skill <topic>". Searches the official plugin marketplace, GitHub, and curated awesome-lists for community skills matching a need, removes anything already installed, and recommends the top 5 with links. Do NOT use this to create or edit skills (that is skill authoring), or to pick among skills you already have.

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

生成中国中小学教案与配套材料。当用户要"备课""写教案""设计一节课""做课件大纲""出分层作业""写说课稿""评课"时使用。覆盖语文/数学/英语/科学等学科，小学到高中；先确认学段、教材版本与适用课程标准，再按学科核心素养、可观察任务和评价证据组织目标。

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

辅导中国中小学生作业的家长助手。当用户要"辅导作业""孩子这题不会""怎么给孩子讲""检查作业""孩子不想写作业"时使用。重点是教家长怎么引导，而不是直接给答案。

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

中式 DESIGN.md 设计系统。当用户要"中国风网页""国风页面""中式设计系统""给项目定个中式风格""DESIGN.md""让 AI 按设计规范生成界面""中文网页排版规范"时使用。提供 8 套可直接丢进项目根目录的 DESIGN.md，AI 读了就按这套规范生成界面。含西文设计系统普遍缺失的中文排版规则。

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

国潮/国风视觉生成助手。当用户要"国潮风""中国风插画""国漫风格""水墨风""新中式设计""古风头像""国风配图""汉服插画""传统文化海报"时使用。内置 12 种中国美学画风配方，输出可直接复制到 Midjourney/即梦/可灵/Nano Banana 的提示词。

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

用 AI 系统学习任何东西的教练。当用户要"学 XX""怎么入门""帮我制定学习计划""我想搞懂 XX""考证/备考""复习"时使用。不是直接讲答案，而是带着走完整的学习循环：定目标→输入→主动回忆→输出→纠错→间隔复习→项目交付。

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

生成中文职场汇报材料。当用户要"写周报""做月度总结""述职报告""项目汇报""向老板汇报""做汇报PPT大纲""写工作计划"时使用。按结论先行、数据支撑的中文职场表达习惯组织。

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

中文拆书与读书笔记助手。当用户要"拆书""读书笔记""这本书讲什么""帮我读这本书""做读书卡片""写书评""整理一本书的框架"时使用。重点是把书变成能用的东西，不是复述目录。

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

国风 3D 网页渲染。当用户要"水墨风 3D""中国风网页特效""Three.js 水墨""国风 H5""青绿山水 3D""非真实感渲染 NPR""古风 WebGL"时使用。提供可运行的中式渲染 shader 与实现方法，不是通用 Three.js 教程。

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

中文开源项目的 README 与仓库门面优化。当用户说"我的开源项目没人看""README 怎么写""GitHub 仓库怎么优化""帮我写 README""项目主页太丑""怎么让别人愿意 star"时使用。基于对 15 个近期高增长仓库的实测数据给出可执行建议，同时明确说明哪些是相关性、哪些无法验证——不承诺涨星。

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

中式网页主题库。当用户要"中国风网页""国风网站样式""古风博客主题""中式配色 CSS""水墨风页面""新中式网页""给网站换个中国风皮肤"时使用。提供 8 套可直接引入的 CSS 主题，内置中文排版规范。

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

中文排版规范助手。当用户要"排版""中文网页样式""文章排版""公众号排版""PDF/Word 排版""字体怎么选""中英混排""为什么我的中文网页很丑"时使用。处理中英间距、标点、行高、字体栈、CJK 断行等中文特有问题，输出可直接用的 CSS 或排版建议。

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

生成中文电商商品文案。当用户要"写商品详情""起标题""做卖点提炼""写主图文案""优化转化""写种草文案"时使用。覆盖淘宝/天猫/京东/拼多多/抖音小店/小红书，按平台规则和搜索逻辑组织。

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

中文记账与账目整理助手。当用户要"记账""整理流水""做收支表""对账""分类消费""做预算""看看钱花哪了"时使用。只做数据整理与呈现，不提供税务筹划或投资建议。

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

架构设计前系统搜索开源底座（GitHub/包注册表/Awesome/Web），输出 ADOPT/FORK_BASE/COMPOSE/REFERENCE/GREENFIELD 决策与改造蓝图。不用于市场调研或找单个依赖库。

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

Build UI interactions whose motion comes from a physical model instead of durations and easing curves. Turn a feel described in words ("a toggle that feels heavy", "a drawer with a magnetic snap", "a card you throw into a corner", "a knob with heavy detents", "a sticky slider") into a production component driven by mass, stiffness, damping and force fields (magnets, friction, walls), on a line, in a plane or around a dial, plus a test rig that plots position, velocity and the force field, overlays the model's prediction on the measured motion, and exports the same spring to Framer Motion, react-spring, SwiftUI, Compose or CSS linear(). Use this whenever someone asks for an animation, transition, spring, gesture, drag, flick, snap points, bottom sheet, toggle, slider, carousel or any micro-interaction that should "feel" a certain way, or wants to tune or explain a spring, even if they never say "physics".

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

Find niches, topics, audiences, products, channels, and content angles via deep web search. Use whenever Ahmad says "find me a niche", "hunt niches in X", "what's an underserved audience for Y", "find similar sites/videos to <example>", "research the X market", "what are people building in Y space", "/niche-hunter X", or any phrasing that asks for niche / market / topic / audience / product / channel discovery across the open web. Trusts domain + keyword search; chains web_search → web_fetch / web_extract / web_crawl + reddit_search + search_youtube + github_repo_intel. NEVER uses awesome-list shortcuts. Output shape is FLEXIBLE — list, table, report, suggestions, or normal prose — picked from how Ahmad phrased the ask.

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

Create concise checklist cheatsheets from official tool docs. Use for docs URLs, setup guides, or updating existing cheatsheets. Don't use for long tutorials or API references.

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

Prepares a discovery call brief from what the user has on a prospect (CRM record, inbound form, emails, notes, public material the user supplies): what is known with sources, gaps against the qualification dimensions, hypotheses to test, questions in priority order and what to listen for. Returns a DRAFT Markdown brief in the chat. Use when the user asks to "prep me for the discovery call with <prospect>", "what should I ask on this first call", "intro call brief", "questions for the qualification call" or "what do we know before we speak to them". Do not use for scoring leads against a rubric, use lead-qualification-scorer instead; for an existing customer's account review use account-plan-builder. Drafts for human review; never approves, authorises or signs off.

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

Produces a DRAFT product requirements document from the discovery notes, interview summaries, support themes, analytics notes and stakeholder messages the user provides: problem statement, target users, goals with measures as stated, numbered requirements each with a testable acceptance criterion, non-goals, constraints, dependencies and open questions, with every statement tagged evidenced, assumed or UNKNOWN so each assumption is visible for the product owner to confirm. Use when the user asks to "write a PRD", "draft the product requirements", "turn these discovery notes into requirements", "document what this feature needs to do" or "build the requirements doc for this epic". Do not use for supplier-facing requirements in a tender, use rfp-requirements-pack instead; for a technical design decision, use architecture-decision-record; for the change ticket that ships the work, use change-request-pack. Drafts for human review; never approves, authorises or signs off.

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

Turns a list of merged changes, closed work items or commit messages the user provides into DRAFT release notes under the version heading and date the user supplies, grouped as features, fixes and other, in the organisation's tone from the style guide or prior notes given, with every entry traced to its source item, breaking changes and required actions flagged first, and internal-only items held back for the release owner to confirm. Use when the user asks to "write the release notes for this version", "turn these merged pull requests into a changelog", "summarise what shipped this sprint for customers", "draft the what's new for this release" or "group these closed tickets into release notes". Do not use for an announcement email or intranet post about a launch, use announcement-drafter instead; for a change ticket, use change-request-pack; for a how-to article about one fix, use knowledge-article-drafter. Drafts for human review; never approves, authorises or signs off.

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

Synthesises retrospective notes, closing reports and post-implementation reviews into a DRAFT lessons-learned document: themed lessons with source counts, anonymised quoted evidence graded by strength, repeats against a prior register, contradictions, and a recommended owner with a stated basis for each follow-up. Names no individual or vendor and assigns no blame. Use when the user asks to "compile the lessons learned", "write up the retrospective", "theme the close-out notes", "what did we learn across these projects" or "refresh the lessons register". Do not use for a single sprint's review, use sprint-review-summary instead; for an incident investigation, use incident-postmortem-drafter; for customer feedback themes, use customer-feedback-theme-synthesis. Drafts for human review; never approves, authorises or signs off.

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

Maintains four living project files (overview and progress log, decision log, RAID log, links) from the mail, channel posts, documents and meeting notes the user attaches or the agent can reach, returns each touched file complete in the chat for the user to save, and builds a weekly DRAFT status report from those files. Use when the user asks to "set up tracking for project X", "catch the project files up", "log this decision against the project", "add this risk to the RAID log", "save this link to the project" or "write this week's status report". Do not use for reviewing an existing RAID log for stale or ownerless entries, use raid-log-review instead; for an HTML status page, use project-dashboard-builder; for minutes of one meeting, use meeting-minutes-writer. Drafts for human review; never approves, authorises or signs off.

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