Implement Thistle Tea CMSG_* client messages following our architecture patterns. Use this when asked to implement a new message or you need to use one that isn't implemented yet.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
151건 · 관련도순
Implement Thistle Tea CMSG_* client messages following our architecture patterns. Use this when asked to implement a new message or you need to use one that isn't implemented yet.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
This skill should be used when the user asks to "set up Nuxt Studio", "configure Studio OAuth", "deploy Studio to Cloudflare", "add visual editor to Nuxt", "configure studio.domain.com subdomain", "Studio authentication", "Nuxt CMS", or mentions visual content editing, Nuxt Studio module, TipTap editor, Monaco editor, or content management for Nuxt websites.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Nuxt Content v3 Git-based CMS for Markdown/MDC content sites. Use for blogs, docs, content-driven apps with type-safe queries, schema validation (Zod/Valibot), full-text search, navigation utilities. Supports Nuxt Studio production editing, Cloudflare D1/Pages deployment, Vercel deployment, SQL storage, MDC components, content collections.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Hugo static site generator with Tailwind v4, headless CMS (Sveltia/Tina), Cloudflare deployment. Use for blogs, docs sites, or encountering theme installation, frontmatter, baseURL errors.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Think and work like an expert Metabolomics Scientist. Use when a task calls for Metabolomics Scientist judgment. Reasons from MSI annotation levels, pooled-QC RSD and D-ratio gates, MZmine/MS-DIAL/XCMS pipelines, HMDB/GNPS identification, and MetaboAnalyst batch correction (ComBat, QC-RLSC); treats injection-order drift, ComBat over-correction, and Level-5 pathway stories as first-class failure modes.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Think and work like an expert Edge / Embedded AI Engineer. Use when a task calls for Edge / Embedded AI Engineer judgment. Reasons from tensor-arena budgets, full-int8 PTQ with representative calibration, and TFLM/CMSIS-NN or Vela/Ethos-U compile paths through ONNX Runtime QNN HTP and mobile delegates—treating train–serve preprocessing skew, float thresholds on quantized outputs, and NPU operator fallback as first-class failure modes.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Think and work like an expert Coastal Engineer. Use when a task calls for Coastal Engineer judgment. Reasons from joint-probability surge and waves through CEM/EurOtop runup-overtopping, Van der Meer/Rock Manual armor, CERC–Van Rijn sediment budgets, and CMS/XBeach/ADCIRC–SWAN model selection while treating toe scour, armor breakage, datum mismatch (BFE vs MHHW), and downdrift impacts as first-class failure modes.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Device-track catalyst analysis: 510(k), PMA, and De Novo decision events, CMS coverage and NTAP milestones, recalls and watch actions as risk signals, and post-market surveillance obligations — dated, verified, and sized per event for any medtech ticker or watchlist.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Identify the technology stack powering any website — frameworks, CMS, analytics, hosting, CDN, payment processors, and marketing tools. Useful for competitive intelligence, sales prospecting, and technology landscape research.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
You are an expert in Contentful, the API-first content platform for enterprise teams. You help developers integrate Contentful's Content Delivery API (CDN-backed, read), Content Management API (write), and Content Preview API (draft content) into websites and apps — using typed content models, localization, rich text rendering, image transformations, and webhooks for build triggers.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Extract, suggest, and sync tags and categories for blog posts across all major CMS platforms. Supports WordPress REST API, Shopify GraphQL, Ghost Content API, Strapi REST/GraphQL, and Sanity GROQ. Generates tag suggestions from content analysis (keyword frequency, heading extraction, semantic grouping), enforces minimum post-count thresholds to prevent thin tag archives, and syncs taxonomy via authenticated API calls. Use when user says "tags", "categories", "taxonomy", "tag suggestions", "sync tags", "WordPress tags", "Shopify tags".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
One-command multilingual blog creation. Writes a blog post, translates it into user-specified languages, applies cultural adaptation, and emits hreflang tags, sitemap entries, and a CMS-ready language map. The complete write-to-publish pipeline for international content. Orchestrates blog-write, blog-translate, blog-localize, and (optionally) seo-hreflang. Use when user says "multilingual blog", "blog multilingual", "write in multiple languages", "international blog", "mehrsprachiger Blog", "blog multilingue", "blog multilingue", "create blog in German and French".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Runs a full dead-end page audit for any website. Discovers all blog/content pages, detects which ones have zero outgoing links to any URL on the same domain, fetches keywords, clusters pages by topic, and generates 3 outgoing link suggestions per dead-end page with anchor text, placement guidance, and ready-to-paste context copy. Outputs a styled HTML report matching report-style-reference.html. Automatically detects site framework (Next.js, static, WordPress) and uses the correct detection method: RSC header for Next.js/Vercel sites, standard curl for static and traditional CMS sites. Trigger when a user provides a domain or URL and asks for a dead-end page audit, outgoing internal links audit, "which pages don't link out", "find pages with no internal links in the content", "pages that are link dead-ends", or any variation of finding pages that have zero outgoing links to the same domain. Always use this skill for dead-end page audits — never attempt the workflow without following every step here.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
当用户想给自己的 Hugo 静态博客(如 maggiacito.com)新增或编辑帖子、管理类目、上传图片并发布上线时使用——对话式后台,说一句就改文件、commit、推送、自动部署,不需要任何 CMS/服务器。触发词:「发一篇博客」「给 Hugo 加文章」「写篇帖子到博客」「管理博客类目」「上传图片到博客」「博客后台」「/wjs-publishing-hugo」。
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Verifies provider credentials via NPI MCP, searches Medicare coverage policies via CMS Coverage MCP, and maps clinical evidence to policy criteria with MET/NOT_MET/INSUFFICIENT assessment, per-criterion confidence scoring, and documentation gap analysis.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Transform any research material into SEO+GEO-optimized blog posts for Knox Hub. Takes any input (URL, article text, notes, video transcript, competitor post, topic idea) and rewrites it as natural human-sounding content, then fills in all fields for the Knox Hub post editor: title, excerpt, SEO settings, FAQ schema, table of contents, sticky sidebar, and full article content in Markdown. Output is ready to copy-paste into your blog/CMS post editor. Use when asked to "write a post", "rewrite this", "сделай пост", "напиши статью", "перепиши это для блога", "create blog post", or any content creation task.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
HTTP/HTTPS application-layer reconnaissance after a web service is identified: fingerprinting, content/API discovery, JS/source maps, proxy/cache topology, WAF, CMS, and known CVE/PoC candidates. Recon only — do not exploit, write files, or obtain a shell. Hand CVE candidates and attack surface to the operator, who may select /web-attack. Non-HTTP ports belong to /recon.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Identify exact technology stack, frameworks, versions, and CMS on live hosts. Use when the user has a live host list and needs to know what's running before choosing vuln classes to test.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Build, review, and browser-test interactive website page or module HTML from a confirmed UI Architecture Map and visual direction. Use for HTML First Drafts, restrained motion implementation, full-page or module-first prototypes, rendered design review, responsive and interaction QA, page composition, and implementation handoff. Do not use for design exploration, unconfirmed visual or motion direction, content strategy, Design Systems, Elementor controls, CMS templates, or framework components.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Design and visually validate implementation-agnostic website pages or modules from an approved Design System and confirmed content. Use for Module Design Solutions, Page UI Architecture Maps, media, evidence, page motion budgets, section motion intent, visual-direction images, and direction review before HTML. Do not use to write or review HTML/CSS/JS, run browser implementation QA, plan platform fields, or implement CMS components.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
非公開のセキュリティアドバイザリ(下書き)で扱う修正を、人の確認を待たずに「準備 → 実装 → 範囲の照合 → 検証 → 自己レビュー → 一時的な非公開フォークへの push → フォーク内の PR」まで進めるスキル。`/run-advisory <GHSA-ID> <計画のパス>` を提供する。ユーザーが「/run-advisory」「アドバイザリを自走で直して」「非公開フォークで修正を進めて」と依頼したときに使う。公開の Issue や ExecPlan を回すなら exec-plan-runner を使う。
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Issue または ExecPlan を、人の確認を待たずに「準備 → 実装 → 範囲の照合 → 検証 → 自己レビュー → push → PR」まで進めるスキル。`/run-issue <番号>`・`/run-plan <ExecPlan のパス>`・`/finish-task` を提供する。ユーザーが「/run-issue」「/run-plan」「Issue を自走で直して」「ExecPlan を最後まで進めて」「0 節の Issue を順に片付けて」と依頼したときに使う。ExecPlan を作るだけなら exec-plan、次のタスクを選ぶだけなら roadmap-manager を使う。
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Issue または ExecPlan を、人の確認を待たずに「準備 → 実装 → 範囲の照合 → 検証 → 自己レビュー → push → PR」まで役割を分けて進めるスキル。`/run-issue <番号>`・`/run-plan <ExecPlan のパス>`・`/finish-task` を提供する。ユーザーが「/run-issue」「/run-plan」「Issue を自走で直して」「ExecPlan を最後まで進めて」「0 節の Issue を順に片付けて」と依頼したときに使う。ExecPlan を作るだけなら exec-plan、次のタスクを選ぶだけなら roadmap-manager を使う。
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.