Create technical diagrams using Mermaid syntax for architecture, sequences, ERDs, flowcharts, and state machines. Use for visualizing system design, data flows, and processes. Triggers: diagram, mermaid, architecture diagram, sequence diagram, flowchart, ERD, entity relationship, state diagram, C4 model, component diagram, visualize, draw.
日本語の概要は準備中です。原文の説明を表示しています。
David-Li0406/meta-skill-evloving☆ 22026年7月14日 更新
Draft professional emails for various contexts including business, technical, and customer communication. Use when the user needs help writing emails or composing professional messages.
日本語の概要は準備中です。原文の説明を表示しています。
David-Li0406/meta-skill-evloving☆ 22026年7月14日 更新
Systematically evaluate architecture decisions, document trade-offs, and select appropriate patterns. This skill should be used when the user asks about 'architecture decision', 'ADR', 'design pattern selection', 'technology choice', or needs to evaluate architectural trade-offs. Keywords: architecture, ADR, patterns, trade-offs, technical debt, quality attributes, decision record.
日本語の概要は準備中です。原文の説明を表示しています。
aAAaqwq/openclaw-team☆ 22026年6月18日 更新
Quarterly Silicon Agent performance evaluation with ByteDance-style calibration, forced distribution ranking, dual-track (technical/management) assessment, and automated score calculation. Includes real evaluation forms, calibration meeting scripts, and PIP templates.
日本語の概要は準備中です。原文の説明を表示しています。
aAAaqwq/openclaw-team☆ 22026年6月18日 更新
Write strategy-oriented Product Requirements Documents (PRDs) for AI product managers. Use when: (1) drafting a new PRD or strategy doc, (2) structuring a feature proposal with strategy rationale, (3) writing requirement docs that emphasize "why" over "how", (4) turning raw product ideas into structured requirement documents. NOT for: purely technical specs, engineering tickets, or UI copy.
日本語の概要は準備中です。原文の説明を表示しています。
aAAaqwq/openclaw-team☆ 22026年6月18日 更新
SEO, AEO and GEO — search, keywords, ranking, visibility, answer engine optimization, generative engine optimization, voice search, organic traffic, featured snippets, technical search audit, E-E-A-T, structured data.
日本語の概要は準備中です。原文の説明を表示しています。
DrNabeelKhan/maxim☆ 22026年9月17日 更新
Generate high-quality Product Requirements Documents (PRDs) for software systems and AI-powered features. Includes executive summaries, user stories, technical specifications, and risk analysis.
日本語の概要は準備中です。原文の説明を表示しています。
jcasnellie69/homelab-config☆ 22026年10月12日 更新
Use this skill when the user needs to transform business requirements, use case descriptions, or meeting transcripts into a technical Power Platform solution architecture, including component selection and Mermaid.js diagrams.
日本語の概要は準備中です。原文の説明を表示しています。
jcasnellie69/homelab-config☆ 22026年10月12日 更新
Prompt for creating an Epic Product Requirements Document (PRD) for a new epic. This PRD will be used as input for generating a technical architecture specification.
日本語の概要は準備中です。原文の説明を表示しています。
jcasnellie69/homelab-config☆ 22026年10月12日 更新
Prompt for creating the high-level technical architecture for an Epic, based on a Product Requirements Document.
日本語の概要は準備中です。原文の説明を表示しています。
jcasnellie69/homelab-config☆ 22026年10月12日 更新
Perform a final quality pass fixing alignment, spacing, consistency, and micro-detail issues before shipping. Use when the work is functionally complete and needs finishing touches—not when the hierarchy, structure, tone, or technical foundation still need major changes.
日本語の概要は準備中です。原文の説明を表示しています。
aladicf/better-react-web-ui☆ 22026年9月8日 更新
Run technical quality checks across accessibility, performance, theming, responsive design, and anti-patterns. Generates a scored report with P0-P3 severity ratings and actionable plan. Use when the user wants measurable accessibility, performance, responsive, theming, or anti-pattern findings—not when they mainly want an overall UX critique or final visual/detail polish.
日本語の概要は準備中です。原文の説明を表示しています。
aladicf/better-react-web-ui☆ 22026年9月8日 更新
Create standout, technically ambitious interfaces that feel extraordinary through cinematic transitions, advanced motion, heavy rendering, or other high-ambition implementation work. Use when the user wants to wow, impress, go all-out, or push a feature beyond conventional UI polish—not when simple visual confidence or routine cleanup is enough.
日本語の概要は準備中です。原文の説明を表示しています。
aladicf/better-react-web-ui☆ 22026年9月8日 更新
Ultra-compressed communication mode that preserves technical accuracy while dropping filler. Use when the user explicitly says "caveman mode", "talk like caveman", "use caveman", "less tokens", "be brief", or invokes /caveman.
日本語の概要は準備中です。原文の説明を表示しています。
jupes/agent-forge-harness☆ 22026年10月12日 更新
You are an **expert onboarding specialist and knowledge transfer architect** with deep experience in remote-first organizations, technical team integration, and accelerated learning methodologies. Your role is to ensure smooth, comprehensive onboarding that transforms new team members into productive contributors while preserving institutional knowledge.
日本語の概要は準備中です。原文の説明を表示しています。
itsimonfredlingjack/codex-dev-plugin☆ 22026年2月5日 更新
You are a documentation expert specializing in creating comprehensive, maintainable documentation from code. Generate API docs, architecture diagrams, user guides, and technical references using AI-powered analysis and industry best practices.
日本語の概要は準備中です。原文の説明を表示しています。
itsimonfredlingjack/codex-dev-plugin☆ 22026年2月5日 更新
Use when user requests research requiring multiple sources, comprehensive analysis, or synthesis across topics - technical research, domain knowledge gathering, market analysis, or learning about complex subjects
日本語の概要は準備中です。原文の説明を表示しています。
rudironsoni/Synaxis☆ 22026年3月17日 更新
Build structured communication templates for malware incidents including stakeholder notifications, executive briefings, technical advisories, and regulatory disclosures with severity-based escalation procedures.
日本語の概要は準備中です。原文の説明を表示しています。
aniket2348823/Vul-Agent☆ 22026年6月9日 更新
Creates professional PDF whitepapers from Markdown files. Use when the user wants to create a whitepaper, technical document, or PDF with professional formatting and typography.
日本語の概要は準備中です。原文の説明を表示しています。
aemgdc/aemdev☆ 22026年10月13日 更新
Use when the user wants to design, redesign, shape, critique, audit, polish, clarify, distill, harden, optimize, adapt, animate, colorize, extract, or otherwise improve a frontend interface. Covers websites, landing pages, dashboards, product UI, app shells, components, forms, settings, onboarding, and empty states. Handles UX review, visual hierarchy, information architecture, cognitive load, accessibility, performance, responsive behavior, theming, anti-patterns, typography, fonts, spacing, layout, alignment, color, motion, micro-interactions, UX copy, error states, edge cases, i18n, and reusable design systems or tokens. Also use for bland designs that need to become bolder or more delightful, loud designs that should become quieter, live browser iteration on UI elements, or ambitious visual effects that should feel technically extraordinary. Not for backend-only or non-UI tasks.
日本語の概要は準備中です。原文の説明を表示しています。
aemgdc/aemdev☆ 22026年10月13日 更新
Single entry point for all AEM as a Cloud Service Dispatcher skills. Covers config authoring, technical advisory, incident response, performance tuning, security hardening, and full lifecycle orchestration for the Adobe Dispatcher Apache HTTP Server module and its HTTPD/dispatcher configuration.
日本語の概要は準備中です。原文の説明を表示しています。
aemgdc/aemdev☆ 22026年10月13日 更新
Provide advisory guidance for the Adobe Dispatcher Apache HTTP Server module and related HTTPD configuration in AEMaaCS cloud workflows only, with public-doc citations and cloud-specific MCP verification plans. Use for conceptual questions such as `statfileslevel`, filter rules, URL decomposition, cache invalidation behavior, rewrite behavior, and security headers.
日本語の概要は準備中です。原文の説明を表示しています。
aemgdc/aemdev☆ 22026年10月13日 更新
Produces comprehensive system architecture plans for features and products including component breakdown, data flow diagrams, system boundaries, API contracts, and scaling considerations. Use for "system design", "architecture planning", "feature design", or "technical specs".
日本語の概要は準備中です。原文の説明を表示しています。
sathishssj3/Stereix-Engine☆ 22026年10月4日 更新
Use when the user wants to design, redesign, shape, critique, audit, polish, clarify, distill, harden, optimize, adapt, animate, colorize, extract, or otherwise improve a frontend interface. Covers websites, landing pages, dashboards, product UI, app shells, components, forms, settings, onboarding, and empty states. Handles UX review, visual hierarchy, information architecture, cognitive load, accessibility, performance, responsive behavior, theming, anti-patterns, typography, fonts, spacing, layout, alignment, color, motion, micro-interactions, UX copy, error states, edge cases, i18n, and reusable design systems or tokens. Also use for bland designs that need to become bolder or more delightful, loud designs that should become quieter, live browser iteration on UI elements, or ambitious visual effects that should feel technically extraordinary. Not for backend-only or non-UI tasks.
日本語の概要は準備中です。原文の説明を表示しています。
sathishssj3/Stereix-Engine☆ 22026年10月4日 更新