UI/UX, logos, slides, and image generation (7.4K skills)
Cold outbound sequence builder — produces multi-touch email + LinkedIn sequences (5-7 touchpoints) personalized by persona type (technical buyer, economic buyer, champion). Use when asked to "write cold emails", "build an outbound sequence", "create prospecting emails", "write my LinkedIn outreach", or "design a cold email campaign".
The English summary is being prepared. Showing the original description.
Design an A/B test — power analysis, randomization, and success metrics. Use when asked to "design an A/B test", "how many users do we need", or "run a power analysis".
The English summary is being prepared. Showing the original description.
Design an edge routing and geo-distribution strategy — latency routing, failover, and edge logic. Use when asked to "geo-route our traffic", "reduce global latency", or "design edge failover".
The English summary is being prepared. Showing the original description.
Design a CDN configuration — caching rules, TTLs, and origin shield setup. Use when asked to "configure the CDN", "set cache headers", or "set up an origin shield".
The English summary is being prepared. Showing the original description.
Use when asked to structure a landing page, design page layout for conversion, or plan landing page information architecture. Examples: "landing page structure for SaaS", "conversion-optimized layout"
The English summary is being prepared. Showing the original description.
Design drift alerts and escalation — thresholds, runbooks, and retrain triggers. Use when asked to "alert on model drift", "when should we retrain", or "write a drift escalation runbook".
The English summary is being prepared. Showing the original description.
UX designer — user flows, information architecture, wireframes, and interaction design. Use when asked to "design a user flow", "map the IA", "wireframe this screen", or "review UX before shipping".
The English summary is being prepared. Showing the original description.
Use when asked about UX patterns, interaction best practices, form design, navigation patterns, or loading states. Examples: "best practice for form validation", "navigation pattern for dashboard", "loading state UX"
The English summary is being prepared. Showing the original description.
Design an API versioning and deprecation policy — semver rules, sunset timelines, and communication channels. Use when asked to "design a deprecation policy", "how should we version the API", or "set a sunset timeline".
The English summary is being prepared. Showing the original description.
Design a dependency scanning program — CVE detection, license checks, and CI gates. Use when asked to "scan our dependencies", "set up CVE detection", or "add a dependency CI gate".
The English summary is being prepared. Showing the original description.
Write UX copy for a feature, flow, or component — buttons, errors, empty states, tooltips. Use when asked to "write the copy for this flow", "word this error message", or "write empty state copy".
The English summary is being prepared. Showing the original description.
Design and execute a launch plan — Product Hunt, HN Show HN, newsletter coordination, social posts, and community launch moment. Use when asked to "launch [feature/product]", "plan a launch", "help us do a Product Hunt launch", or "coordinate the announcement".
The English summary is being prepared. Showing the original description.
OKR design — create objectives and key results with a North Star metric, input metrics tree, and cadence. Use when asked to "set OKRs", "define our objectives", "what should we measure this quarter", "design our OKR framework", "build a metrics tree", or "what's our North Star".
The English summary is being prepared. Showing the original description.
Design a caching strategy for an application — pattern selection, key design, TTL, and eviction policy. Use when asked to "add caching to this", "design a cache strategy", or "what should we cache".
The English summary is being prepared. Showing the original description.
Design an API compatibility and deprecation policy — stability tiers, sunset timelines, and CI gates. Use when asked to "define an API stability policy", "set our deprecation timeline", or "write semver rules".
The English summary is being prepared. Showing the original description.
Design a chaos engineering experiment — hypothesis, blast radius, steady state, and abort conditions. Use when asked to "design a chaos experiment", "inject a failure", or "test the resilience of this service".
The English summary is being prepared. Showing the original description.
Design customer support onboarding flow -- first-contact experience, proactive support touchpoints, and setup success checklist. Use when asked to "design our onboarding support", "how do we support new customers during onboarding", or "reduce early churn from setup failures".
The English summary is being prepared. Showing the original description.
Design ticket triage system -- routing rules, priority tags, queue structure, and first-response automation. Use when asked to "design our ticket routing", "how should we tag tickets", "set up our helpdesk", or "reduce time to first response".
The English summary is being prepared. Showing the original description.
Design detection rules for a threat — SIEM queries, alert logic, and MITRE ATT&CK mapping. Use when asked to "write a detection rule", "how do we detect this attack", or "build a SIEM query for this TTP".
The English summary is being prepared. Showing the original description.
Design escalation path -- Tier 1 to Tier 2 to Engineering handoff, decision criteria, and communication templates. Use when asked to "design our escalation process", "when should support escalate to engineering", "build an escalation runbook", or "reduce escalation rate".
The English summary is being prepared. Showing the original description.
Developer relations playbook builder — produces a DevRel program design covering community platform, contributor program tiers, ambassador criteria, event strategy, and success metrics. Use when asked to "build a DevRel program", "design our developer community", "create a contributor program", "start a developer advocacy program", or "how do we grow our dev community".
The English summary is being prepared. Showing the original description.
Build and manage open source community — Discord/Slack structure, contributor onboarding, ambassador program, community flywheel design, and GitHub community health. Use when asked to "build a community", "grow our Discord", "improve contributor experience", or "design a developer ambassador program".
The English summary is being prepared. Showing the original description.
UI building guidelines for Datagrok TypeScript components, viewers, and drag-and-drop
The English summary is being prepared. Showing the original description.
店長が承認した発注案を、発注単位・締め時刻・便を確かめてから Dataverse の発注テーブルに登録し、登録結果を報告するスキル。承認の前に必ず最終の一覧（Render UI のグラフ付き）を見せ、登録後は HTML レポート「発注の記録」を作る。 Use when ユーザーが「この内容で発注して」「承認します」「発注を登録して」「さっきの発注はどうなった？」と依頼したとき、または tanpin-kanri の発注案が承認されたとき。 Dataverse MCP コネクタ（describe / read_query / create_record）を使う。create_record はこのスキルでだけ、店長の明示的な承認の後に、発注テーブルにだけ使う。
The English summary is being prepared. Showing the original description.