3,943 件 ・ 関連度順
概要と使いどころ
Use when the user wants to add an in-site feedback loop to a website repo — a floating "提个建议" button where allowlisted visitors submit suggestions that become a GitHub Issue, which GitHub Actions turns into an automatic code change via Claude Code, auto-merges and deploys, and records on a /_feedback dashboard with one-click revert. Triggers — "给网站加个反馈对话框", "提一句话就自动改网站", "装上反馈闭环", "feedback loop", "/wjs-looping-feedback".
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user wants text turned into an audiobook / read aloud — they give a passage, a file, a URL, or a VoiceDrop article and want an mp3 narration with expressive voices. Triggers — "做成有声书", "朗读出来", "读给我听", "念出来", "read aloud", "/wjs-voicedrop-reading-aloud".
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user asks to audit what's wrong with a project, "make it right", "看看项目出了什么问题", "为什么用户的需求还没上线", "为什么没提交App Store", "为什么没新build", or wants a holistic state-of-the-project check covering unmerged branches, stalled PRs, failed GitHub Actions, stale builds, plan drift (TODOS.md / ROADMAP), unreleased commits, and log errors. Runs read-only investigation, presents a grouped checklist, fixes only after explicit user confirmation. Aware of the Cathier iOS app workflow (Xcode + fastlane + auto-merge @claude PRs from in-app feedback).
日本語の概要は準備中です。原文の説明を表示しています。
王建硕的思维框架与表达方式。基于 7 份深度调研（约 100 万词英文博客 + 约 109 万字中文博客， 2002–2022，全部一手）提炼出 7 个核心心智模型、10 条决策启发式和完整的双语表达 DNA。 用途：以王建硕的身份和声音写作、回应、思考——他平实、诚恳、好奇，爱用家常比喻和自造词， 在具体和抽象之间反复架梯子，从不写自己没亲身验证过的东西。 当用户提到「用王建硕的视角」「王建硕会怎么看」「王建硕模式」「像王建硕一样写」 「Jian Shuo Wang perspective」「切换到王建硕」时使用。 即使用户只是说「帮我用王建硕的角度想想」「如果是王建硕会怎么写这篇」也应触发。 一旦激活，本次对话后续所有回应都保持王建硕身份，直到用户明确说「退出」—— 不需要每轮重新点名。 不适用：用户要的是关于王建硕本人的客观介绍 / 事实查询（「王建硕是谁」「他哪年创业的」）， 那种问题正常回答即可，不要进入角色扮演。
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user wants to set up automated daily promotion / marketing for their Claude Code skills — researching how top skills are promoted on marketplaces (ClawHub / openclaw / SkillsMP / agentskills.io), generating a per-skill marketing plan, auto-posting to X (Twitter) via xurl, and drafting community discussion posts (Reddit / HN / Discord). Triggers — "推广 skills", "营销 skills", "自动发推广", "每天自动推广", "skill marketing", "promote my skills", "/wjs-promoting-skills".
日本語の概要は準備中です。原文の説明を表示しています。
Use when an iOS app already on TestFlight needs to ship to the App Store — preparing the screenshots and the description/metadata, then using the existing fastlane setup to submit for review. Triggers — 「提交 App Store」「上架」「app store 审核」「准备截图和文案」「submit for review」「/wjs-publishing-appstore」.
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user wants to teach / learn an English word as a video — turn a single English word into a self-contained HLS "supercut" lesson built from the mira video base. Stitches every season2 clip where the word is spoken (via the search-app API) into one .m3u8, prepended with a Claude-written bilingual word-intro card (word + IPA + 中文 gloss + usage, Volcano TTS) and appended with a 关注王建硕 CTA card. No MP4 burn. Triggers — "teach <word>", "讲讲 <word>", "学英语 <word>", "把 <word> 做成视频", "/wjs-teaching-english <word>".
日本語の概要は準備中です。原文の説明を表示しています。
Use when 王建硕 wants to publish his VoiceDrop books (voicedrop.cn/books) to X/Twitter as threads — 列出他写的书、挑没发过的、整本拆成推文串发出。Triggers — "把书发到 X", "发书的 thread", "publish my book to X", "书架的书发推", "/wjs-publishing-books-to-x".
日本語の概要は準備中です。原文の説明を表示しています。
Craft CMS 5 PHP coding standards and conventions. ALWAYS load when writing, editing, reviewing, or discussing any PHP in a Craft plugin or module — even small edits. Also when running ECS, PHPStan, or scaffolding with ddev craft make. Covers: PHPDoc blocks (@author, @since, @throws chains), section headers (=========), class organization, naming conventions (services, queue jobs, records, events, enums), defineRules() and validation, beforePrepare() and addSelect(), MemoizableArray, DateTimeHelper vs Carbon, strict_types/declare(strict_types=1), short nullable notation (?string), typed properties, void returns, control flow (early returns, match over switch), CP Twig template conventions, form macros, translations (Craft::t), ECS/PHPStan config, scaffolding commands, and the verification checklist.
日本語の概要は準備中です。原文の説明を表示しています。
Scaffold Claude Code configuration specifically for Craft CMS projects. Generates CLAUDE.md and .claude/rules/ files tailored to the project type (plugin, site, module, hybrid, or monorepo). Only for Craft CMS projects — not for Next.js, Laravel, or other frameworks.
日本語の概要は準備中です。原文の説明を表示しています。
Servd (servd.host) — Craft-specialised managed hosting for Craft CMS. Covers git push-to-deploy with the optional servd.yaml build config, local → staging → production environments with uni-directional Project Config sync, the servd/craft-asset-storage plugin (S3-backed Flysystem volumes on the svdcdn.com CDN, off-server image transforms, Imager-X/ImageOptimize integrations), Servd's static caching (full vs tag-based purge, {% dynamicInclude %}, CSRF injection, cache-busting) and running Blitz alongside it in reverse-proxy mode, MariaDB/MySQL databases over an SSH tunnel, automatic + manual backups, the Dedicated Queue Runner, environment variables and secrets, the ephemeral load-balanced filesystem (Redis + remote volumes for runtime files), plugin/feature constraints, and Servd-vs-Craft-Cloud differences.
日本語の概要は準備中です。原文の説明を表示しています。
Garnish — Craft CMS's built-in JavaScript UI toolkit for the control panel. ALWAYS load when writing, editing, or reviewing JavaScript that runs in the Craft CP — plugin CP assets, custom field type JS, element index JS, CP webpack config, or code importing garnishjs / referencing window.Garnish. Also for CP accessibility, keyboard interactions, drag-sort, and CP JS memory issues.
日本語の概要は準備中です。原文の説明を表示しています。
Craft Cloud — Pixel & Tonic's serverless hosting platform for Craft CMS. Covers craft-cloud.yaml configuration, the Build → Migrate → Release deploy pipeline, the craftcms/cloud extension package, edge image transforms via Cloudflare, edge static caching with cache.rules + ESI, Cloud-managed S3 filesystem, MySQL 8 / Postgres 15 databases (no MariaDB, no tablePrefix), Console-based command runner and scheduled cron (once-per-hour minimum), auto-handled queue jobs, custom domains and SSL, preview environments per branch, Cloud limitations (ephemeral filesystem, no SSH, no .htaccess, no built-in mail), plugin development requirements for Cloud compatibility, and self-hosted → Cloud migration.
日本語の概要は準備中です。原文の説明を表示しています。
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).
日本語の概要は準備中です。原文の説明を表示しています。
Craft CMS 5 plugin and module development — extending Craft with PHP. Covers elements, element queries, services, models, records, controllers, migrations, queue jobs, console commands, field types, native fields, events, behaviors, Twig extensions, widgets, filesystems, permissions, project config, GraphQL, testing, and debugging.
日本語の概要は準備中です。原文の説明を表示しています。
Index and router for plugin-specific Craft CMS 5 guidance — configuration, Twig API, PHP API, migrations, deployment, and pitfalls for the plugins this pack documents. Load whenever a task names a plugin this pack documents, and for passwordless or magic-link auth with no plugin named; read references/<plugin>.md first.
日本語の概要は準備中です。原文の説明を表示しています。
Craft CMS 5 content modeling — sections, entry types, fields, Matrix, relations, project config, and content architecture strategy. Covers choosing section types, designing entry types and field layouts, selecting field types, configuring Matrix and nested entries, relations and eager loading, and multi-site propagation.
日本語の概要は準備中です。原文の説明を表示しています。
Releasing Craft CMS plugins — tagging, Packagist propagation, GitHub releases, branch promotion, shared-library ordering, history rewrites. ALWAYS load when cutting, preparing, verifying, or debugging a plugin release: bumping a version, dating a changelog, creating or moving a git tag, or checking what Packagist serves.
日本語の概要は準備中です。原文の説明を表示しています。
Craft CMS 5 front-end Twig development — atomic design, template architecture, components, Vite buildchain. Covers atoms/molecules/organisms, props/extends/block patterns, layout chains, view routing, content builders, image presets, Tailwind named-key collections, multi-brand CSS tokens, JavaScript boundaries (Alpine/DataStar/Vue, tabs, accordions), Vite asset loading, and front-end auth (login, registration, password reset, profiles).
日本語の概要は準備中です。原文の説明を表示しています。
Testing Craft CMS 5 plugins and modules with Pest — test isolation, database safety, and the markhuot/craft-pest-core harness. ALWAYS load when writing, running, fixing, or reviewing tests for a Craft plugin or module, and whenever a suite touches a real Craft install. Covers why rollback is opt-in, tests/Pest.php + tests/bootstrap.php wiring, phpunit.xml.dist <env> pins (force DB name + table prefix, default connection coordinates, pin CRAFT_ENVIRONMENT against server-scoped locks), why --configuration= defeats DB isolation, throwing fail-closed DB guards, installing the plugin under test, process-timezone pinning, per-test site fixtures, idempotent Install migrations, stale service caches when components get swapped, muting audit sinks, queue stubs, factories, HTTP/DB assertions, CI jobs.
日本語の概要は準備中です。原文の説明を表示しています。
Twig coding standards and conventions for Craft CMS 5 templates. ALWAYS load this skill when writing, editing, or reviewing any .twig file in a Craft CMS project — even for small edits. Covers: variable naming (camelCase, no abbreviations), null handling (?? operator, ??? with empty-coalesce plugin), whitespace control ({%- trimming, NOT {%- minify -%}), include isolation (always use 'only'), Craft Twig helpers ({% tag %}, tag(), attr(), |attr filter, |parseAttr, |append, svg()), collect() for props and class collections, .implode(), comment headers with ========= separators on component files, and common pitfalls (snake_case, macros as components, hardcoded colors).
日本語の概要は準備中です。原文の説明を表示しています。
E-Mail-Entwürfe auf die Merkmale prüfen, mit denen Spamfilter Werbepost erkennen, und empfangene Nachrichten auswerten, die im Junk gelandet sind. Nutze diesen Skill, wenn eine Mail vor dem Versand geprüft werden soll, wenn jemand wissen will, warum eine Nachricht im Spam- oder Junk-Ordner gelandet ist, oder wenn Betreff, Text, HTML und Kopfzeilen einer Mail auf Aufbau- und Inhaltsfehler durchgesehen werden. Prüft unter anderem Linktext gegen Linkziel, defekte Abmeldewege nach RFC 8058, erfundene Thread-Bezüge, sichtbare Seriendruckreste, versteckte Zählpixel, Domainstreuung sowie unbelegte Zahlen und Superlative. Sagt keine Zustellung voraus und ist kein Werkzeug, um Filter zu umgehen. Für die Frage, ob eine Kaltakquise-Mail überhaupt versendet werden darf, ist cold-email zuständig.
日本語の概要は準備中です。原文の説明を表示しています。
Organische Social-Media-Inhalte für Deutschland und den DACH-Raum planen, verfassen, wiederverwenden, prüfen und messen. Nutze diesen Skill, wenn Posts, Redaktionspläne, Content-Serien oder Kanalstrategien für LinkedIn, X, Instagram, TikTok, Facebook, YouTube oder Mastodon entstehen sollen, wenn vorhandene Inhalte für Social wiederverwendet werden, oder wenn ein Beitrag auf Werbekennzeichnung, Persönlichkeits- und Markenrechte, Alt-Texte und aktuelle Plattformregeln geprüft werden soll. Deckt Briefing, Evidenz, Formatwahl, Interaktion und Messung ab. Nicht für bezahlte Kampagnen und nicht für das tatsächliche Veröffentlichen.
日本語の概要は準備中です。原文の説明を表示しています。
Ein evidenzbasiertes, tragfähiges Content-Portfolio für Zielgruppen, Geschäftsziele, Distribution und die real vorhandene Produktionskapazität planen. Nutze diesen Skill für Content-Strategien, Themenfelder, Redaktionspläne und Backlogs, für die Diagnose eines bestehenden Contentbestands, für die Abbildung von Kauf- und Nutzungswegen und für Entscheidungen zu CMS und Governance. Priorisiert offen nach Nachfrage, Aufwand und Evidenz, schützt vor dünnen Massenseiten und benennt Belegklassen. Einzelne Texte schreibt copywriting, die technische Prüfung macht seo-audit.
日本語の概要は準備中です。原文の説明を表示しています。