Business & Operations
Operations, strategy, finance, sales, support, management, and planning
Browse business & operations skills
Showing 31,441–31,464 of 32,296 skills
Apply sophisticated design system principles to HTML emails including typography hierarchy, color palettes, spacing systems, and layout patterns. Use when creating email templates that need cohesive, intentional design within email HTML constraints. Covers section composition, visual rhythm, and brand application.
Email delivery patterns including single, batch, scheduled emails and attachment handling. Use when building transactional email systems, batch communication workflows, scheduled delivery, or implementing file/URL attachments with reply-to and CC/BCC functionality.
Handle email delivery failures. Use when messages bounce or a customer reports not receiving emails.
Send and read emails via Gmail (User) and Transactional Dispatcher (System).
Transfer licenses to a new email address. Use when a customer wants to change account email, move a license, or update access after a job change.
Processes incoming emails for Unite-Hub. Extracts sender data, identifies communication intents, links to CRM contacts, analyzes sentiment, and updates contact records with AI insights.
Extract actionable tasks assigned to the user from email text. Filters out informational emails (announcements, newsletters, ads, automated reports) and only processes emails with clear action requests. Handles group emails by identifying user-specific assignments.
Use when navigating files and positions in Emacs - provides elisp patterns for finding files, searching, and position management
Use when manipulating Emacs buffers - provides elisp patterns for listing, switching, creating, killing, and working with buffer contents
Use when Elixir OTP patterns including GenServer, Supervisor, Agent, and Task. Use when building concurrent, fault-tolerant Elixir applications.
Use when designing or architecting Elixir/Phoenix/LiveView applications, creating comprehensive project documentation, planning OTP supervision trees, defining domain models, structuring multi-app projects with path-based dependencies, or preparing handoff documentation for Director/Implementor AI collaboration
Use when designing or architecting Elixir/Phoenix applications, creating comprehensive project documentation, planning OTP supervision trees, defining domain models with Ash Framework, structuring multi-app projects with path-based dependencies, or preparing handoff documentation for Director/Implementor AI collaboration
Create world-class PowerPoint presentations with professional design, consistent branding, sophisticated animations, and polished visual hierarchy. Use when users request presentations, slide decks, pitches, reports, or want to convert markdown to professionally designed PowerPoint with Apple/Microsoft/Google-level quality.
Provides elevator pitch and verbal brand communication frameworks including Donald Miller's StoryBrand (SB7), Nancy Duarte's Sparkline, Chris Westfall's CLARITY, Andy Raskin's Strategic Narrative, Simon Sinek's Golden Circle, and time-based pitch structures (10s, 30s, 60s). Auto-activates during elevator pitch creation, one-liner development, brand pitch refinement, and verbal communication work. Use when discussing elevator pitches, one-liners, brand intros, verbal pitches, pitch coaching, s...
Expert elevator pitch consultant for creating compelling, concise 30-60 second introductions tailored to specific audiences and contexts. This skill should be used when users need to craft elevator pitches for job interviews, networking events, investor meetings, or social media profiles. Guides users through structured discovery, applies proven frameworks (Three C's, Four-Part Structure), integrates storytelling techniques, and delivers multiple pitch versions with industry-specific hooks an...
Create sophisticated, Apple-inspired web interfaces with refined aesthetics and corporate elegance. Emphasizes generous whitespace, ultra-precise typography, asymmetric layouts, and purposeful interactions. Combines minimalist design philosophy with premium brand execution. Use when building premium landing pages, marketing sections, product showcases, or corporate interfaces that demand visual sophistication beyond standard business UI.
Classic writing guide by William Strunk Jr. (1918, public domain). Use when editing prose for clarity, conciseness, and proper grammar. Covers elementary rules of usage, composition principles, and style guidelines.
When the user wants to optimize electronics manufacturing supply chains, manage semiconductor sourcing, handle PCB assembly, or navigate component allocation. Also use when the user mentions "electronics manufacturing," "semiconductor supply chain," "PCB assembly," "EMS/ODM," "component allocation," "lead time management," "electronics sourcing," "PCBA," "contract manufacturing," or "electronics lifecycle management." For general manufacturing, see production-scheduling. For quality, see qual...
PCE (Process-Context Engine) のコンテキスト構造化スキル。収集した知識を適切な場所・粒度で構造化し、再利用可能にする。 トリガー条件: - 「CLAUDE.mdを更新して」 - 「ADRを整理して」 - 「知識を構造化して」 - 「pce-memoryに登録して」 - pce-collectionで蓄積された知見の整理時
PCE (Process-Context Engine) の知識移転スキル。セッション/メンバー間での知識の連続性を確保し、引き継ぎを円滑にする。 トリガー条件: - 「引き継ぎ資料を作って」 - 「次の人に渡す情報をまとめて」 - 新メンバーのオンボーディング時 - 長期プロジェクトの節目 - 「プロジェクトの状況を共有して」
PCE (Process-Context Engine) のコンテキスト圧縮スキル。長期タスクの履歴を要約・圧縮し、セッション継続を可能にする。 トリガー条件: - セッションが長くなった時 - コンテキストウィンドウが逼迫した時 - 「ここまでをまとめて」 - 「ノートを作成して」 - 複数セッションにまたがる作業の時 - 「次回のために記録して」
LDE(Law-Driven Engineering)のLink Map(連結表)管理スキル。 Law ↔ Term の相互参照関係を可視化し、孤立の検出と影響分析を行う。 使用タイミング: (1) Law Cardを作成した後、(2) Term Cardを作成した後、 (3) 「Link Mapを更新して」「孤立チェックして」、(4) 変更影響分析時
コードベースや要件からVocabulary(語彙)とLaw(守るべき条件)を自動発見するスキル。 名辞抽象(Term/Type)と関係抽象(Law/制約)の両方を抽出し、 /lde-term-card および /lde-law-card への入力を生成する。 使用タイミング: (1) 新規プロジェクトでVocabulary/Lawを洗い出す時、 (2) 既存コードからLaw/Termを抽出する時、(3) 「Lawを発見して」「語彙を抽出して」、 (4) LDEをレトロフィットする時、(5) Phase A-Bで初期Catalogを作る時
PCE (Process-Context Engine) の出力評価スキル。生成物の品質とLaw(法則)との整合性を検証する。 LDE(Law-Driven Engineering)との統合により、Law遵守チェックも実行。 トリガー条件: - コード生成後(「このコードをレビューして」) - 設計完了後(「設計をチェックして」) - PRマージ前(「マージ前の確認をして」) - 「品質チェックして」 - 「整合性を確認して」 - 「Law遵守をチェックして」