[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M72BCHBYEJS7QG3E2WGGNJTR":3,"skill-same:01M72BCHBYEJS7QG3E2WGGNJTR":65},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":39,"commitSha":40,"skillDirectory":41,"forksCount":13,"repositoryHtmlUrl":42,"repositoryHomepageUrl":6,"ownerHtmlUrl":43,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":44,"install":45,"resources":58},"01M72BCHBYEJS7QG3E2WGGNJTR","design-patterns",null,"Rust design patterns for RTK. Newtype, Builder, RAII, Trait Objects, State Machine. Applied to CLI filter modules. Use when designing new modules or refactoring existing ones.","Sansar35\u002Fclaude-agent","Sansar35","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F145020281?v=4","01M724CQ2SCC86MGNSD87D0D4K","01M724CQ3965G9WJ3QXE3AJ5YY",1,"MIT","https:\u002F\u002Fgithub.com\u002FSansar35\u002Fclaude-agent\u002Fblob\u002Fmain\u002Fclaude-config\u002Fskills\u002Fdesign-patterns\u002FSKILL.md",[],[],"2026-11-10 18:39:20",false,"---\nname: design-patterns\ndescription: Rust design patterns for RTK. Newtype, Builder, RAII, Trait Objects, State Machine. Applied to CLI filter modules. Use when designing new modules or refactoring existing ones.\ntriggers:\n  - \"design pattern\"\n  - \"how to structure\"\n  - \"best pattern for\"\n  - \"refactor to pattern\"\nallowed-tools:\n  - Read\n  - Grep\n  - Glob\neffort: medium\ntags: [rust, design-patterns, architecture, newtype, builder, rtk]\n---\n\n# RTK Rust Design Patterns\n\nPatterns that apply to RTK's filter module architecture. Focused on CLI tool patterns, not web\u002Fservice patterns.\n\n## Pattern 1: Newtype (Type Safety)\n\nUse when: wrapping primitive types to prevent misuse (command names, paths, token counts).\n\n```rust\n\u002F\u002F Without Newtype — easy to mix up\nfn track(input_tokens: usize, output_tokens: usize) { ... }\ntrack(output_tokens, input_tokens);  \u002F\u002F Silent bug!\n\n\u002F\u002F With Newtype — compile error on swap\npub struct InputTokens(pub usize);\npub struct OutputTokens(pub usize);\nfn track(input: InputTokens, output: OutputTokens) { ... }\ntrack(OutputTokens(100), InputTokens(400));  \u002F\u002F Compile error ✅\n```\n\n```rust\n\u002F\u002F Practical RTK example: command name validation\npub struct CommandName(String);\nimpl CommandName {\n    pub fn new(s: &str) -> Result\u003CSelf> {\n        if s.contains(';') || s.contains('|') || s.contains('`') {\n            anyhow::bail!(\"Invalid command name: shell metacharacters\");\n        }\n        Ok(Self(s.to_string()))\n    }\n    pub fn as_str(&self) -> &str { &self.0 }\n}\n```\n\n## Pattern 2: Builder (Complex Configuration)\n\nUse when: a struct has 4+ optional fields, many with defaults.\n\n```rust\n#[derive(Default)]\npub struct FilterConfig {\n    max_lines: Option\u003Cusize>,\n    strip_ansi: bool,\n    show_warnings: bool,\n    truncate_at: Option\u003Cusize>,\n}\n\nimpl FilterConfig {\n    pub fn new() -> Self { Self::default() }\n    pub fn max_lines(mut self, n: usize) -> Self { self.max_lines = Some(n); self }\n    pub fn strip_ansi(mut self, v: bool) -> Self { self.strip_ansi = v; self }\n    pub fn show_warnings(mut self, v: bool) -> Self { self.show_warnings = v; self }\n}\n\n\u002F\u002F Usage — readable, no positional arg confusion\nlet config = FilterConfig::new()\n    .max_lines(50)\n    .strip_ansi(true)\n    .show_warnings(false);\n```\n\nWhen NOT to use Builder: if the struct has 1-3 fields with obvious meaning. Over-engineering for simple cases.\n\n## Pattern 3: State Machine (Parser\u002FFilter Flows)\n\nUse when: parsing multi-section output (test results, build output) where context changes behavior.\n\n```rust\n\u002F\u002F RTK example: pytest output parsing\n#[derive(Debug, PartialEq)]\nenum ParseState {\n    LookingForTests,\n    InTestOutput,\n    InFailureSummary,\n    Done,\n}\n\nfn parse_pytest(input: &str) -> String {\n    let mut state = ParseState::LookingForTests;\n    let mut failures = Vec::new();\n\n    for line in input.lines() {\n        match state {\n            ParseState::LookingForTests => {\n                if line.contains(\"FAILED\") || line.contains(\"ERROR\") {\n                    state = ParseState::InFailureSummary;\n                    failures.push(line);\n                }\n            }\n            ParseState::InFailureSummary => {\n                if line.starts_with(\"=====\") { state = ParseState::Done; }\n                else { failures.push(line); }\n            }\n            ParseState::Done => break,\n            _ => {}\n        }\n    }\n    failures.join(\"\\n\")\n}\n```\n\n## Pattern 4: Trait Object (Command Dispatch)\n\nUse when: different command families need the same interface. Avoids massive match arms.\n\n```rust\n\u002F\u002F Define a common interface for filters\npub trait OutputFilter {\n    fn filter(&self, input: &str) -> Result\u003CString>;\n    fn command_name(&self) -> &str;\n}\n\npub struct GitFilter;\npub struct CargoFilter;\n\nimpl OutputFilter for GitFilter {\n    fn filter(&self, input: &str) -> Result\u003CString> { filter_git(input) }\n    fn command_name(&self) -> &str { \"git\" }\n}\n\n\u002F\u002F RTK currently uses match-based dispatch in main.rs (simpler, no dynamic dispatch overhead)\n\u002F\u002F Trait objects are useful if filter registry becomes dynamic (e.g., TOML-loaded plugins)\n```\n\nNote: RTK's current `match` dispatch in `main.rs` is intentional — static dispatch, zero overhead. Only move to trait objects if the match arm count exceeds ~20 commands.\n\n## Pattern 5: RAII (Resource Management)\n\nUse when: managing resources that need cleanup (temp files, SQLite connections).\n\n```rust\n\u002F\u002F RTK tee.rs — RAII for temp output files\npub struct TeeFile {\n    path: PathBuf,\n}\n\nimpl TeeFile {\n    pub fn create(content: &str) -> Result\u003CSelf> {\n        let path = tee_path()?;\n        fs::write(&path, content)\n            .with_context(|| format!(\"Failed to write tee file: {}\", path.display()))?;\n        Ok(Self { path })\n    }\n\n    pub fn path(&self) -> &Path { &self.path }\n}\n\n\u002F\u002F No explicit cleanup needed — file persists intentionally (rotation handled separately)\n\u002F\u002F If cleanup were needed: impl Drop { fn drop(&mut self) { let _ = fs::remove_file(&self.path); } }\n```\n\n## Pattern 6: Strategy (Swappable Filter Logic)\n\nUse when: a command has multiple filtering modes (e.g., compact vs. verbose).\n\n```rust\npub enum FilterMode {\n    Compact,    \u002F\u002F Show only failures\u002Ferrors\n    Summary,    \u002F\u002F Show counts + top errors\n    Full,       \u002F\u002F Pass through unchanged\n}\n\npub fn apply_filter(input: &str, mode: FilterMode) -> String {\n    match mode {\n        FilterMode::Compact => filter_compact(input),\n        FilterMode::Summary => filter_summary(input),\n        FilterMode::Full => input.to_string(),\n    }\n}\n```\n\n## Pattern 7: Extension Trait (Add Methods to External Types)\n\nUse when: you need to add methods to types you don't own (like `&str` for RTK-specific parsing).\n\n```rust\npub trait RtkStrExt {\n    fn is_error_line(&self) -> bool;\n    fn is_warning_line(&self) -> bool;\n    fn token_count(&self) -> usize;\n}\n\nimpl RtkStrExt for str {\n    fn is_error_line(&self) -> bool {\n        self.starts_with(\"error\") || self.contains(\"[E\")\n    }\n    fn is_warning_line(&self) -> bool {\n        self.starts_with(\"warning\")\n    }\n    fn token_count(&self) -> usize {\n        self.split_whitespace().count()\n    }\n}\n\n\u002F\u002F Usage\nif line.is_error_line() { ... }\nlet tokens = output.token_count();\n```\n\n## RTK Pattern Selection Guide\n\n| Situation | Pattern | Avoid |\n|-----------|---------|-------|\n| New `*_cmd.rs` filter module | Standard module pattern (see CLAUDE.md) | Over-abstracting |\n| 4+ optional config fields | Builder | Struct literal |\n| Multi-phase output parsing | State Machine | Nested if\u002Felse |\n| Type-safe wrapper around string | Newtype | Raw `String` |\n| Adding methods to `&str` | Extension Trait | Free functions |\n| Resource with cleanup | RAII \u002F Drop | Manual cleanup |\n| Dynamic filter registry | Trait Object | Match sprawl |\n\n## Anti-Patterns in RTK Context\n\n```rust\n\u002F\u002F ❌ Generic over-engineering for one command\npub trait Filterable\u003CT: CommandArgs + Send + Sync + 'static> { ... }\n\n\u002F\u002F ✅ Just write the function\npub fn filter_git_log(input: &str) -> Result\u003CString> { ... }\n\n\u002F\u002F ❌ Singleton registry with global state\nstatic FILTER_REGISTRY: Mutex\u003CHashMap\u003CString, Box\u003Cdyn Filter>>> = ...;\n\n\u002F\u002F ✅ Match in main.rs — simple, zero overhead, easy to trace\n\n\u002F\u002F ❌ Async traits for \"future-proofing\"\n#[async_trait]\npub trait Filter { async fn apply(&self, input: &str) -> Result\u003CString>; }\n\n\u002F\u002F ✅ Synchronous — RTK is single-threaded by design\npub trait Filter { fn apply(&self, input: &str) -> Result\u003CString>; }\n```\n","# RTK Rust Design Patterns\n\nPatterns that apply to RTK's filter module architecture. Focused on CLI tool patterns, not web\u002Fservice patterns.\n\n## Pattern 1: Newtype (Type Safety)\n\nUse when: wrapping primitive types to prevent misuse (command names, paths, token counts).\n\n```rust\n\u002F\u002F Without Newtype — easy to mix up\nfn track(input_tokens: usize, output_tokens: usize) { ... }\ntrack(output_tokens, input_tokens);  \u002F\u002F Silent bug!\n\n\u002F\u002F With Newtype — compile error on swap\npub struct InputTokens(pub usize);\npub struct OutputTokens(pub usize);\nfn track(input: InputTokens, output: OutputTokens) { ... }\ntrack(OutputTokens(100), InputTokens(400));  \u002F\u002F Compile error ✅\n```\n\n```rust\n\u002F\u002F Practical RTK example: command name validation\npub struct CommandName(String);\nimpl CommandName {\n    pub fn new(s: &str) -> Result\u003CSelf> {\n        if s.contains(';') || s.contains('|') || s.contains('`') {\n            anyhow::bail!(\"Invalid command name: shell metacharacters\");\n        }\n        Ok(Self(s.to_string()))\n    }\n    pub fn as_str(&self) -> &str { &self.0 }\n}\n```\n\n## Pattern 2: Builder (Complex Configuration)\n\nUse when: a struct has 4+ optional fields, many with defaults.\n\n```rust\n#[derive(Default)]\npub struct FilterConfig {\n    max_lines: Option\u003Cusize>,\n    strip_ansi: bool,\n    show_warnings: bool,\n    truncate_at: Option\u003Cusize>,\n}\n\nimpl FilterConfig {\n    pub fn new() -> Self { Self::default() }\n    pub fn max_lines(mut self, n: usize) -> Self { self.max_lines = Some(n); self }\n    pub fn strip_ansi(mut self, v: bool) -> Self { self.strip_ansi = v; self }\n    pub fn show_warnings(mut self, v: bool) -> Self { self.show_warnings = v; self }\n}\n\n\u002F\u002F Usage — readable, no positional arg confusion\nlet config = FilterConfig::new()\n    .max_lines(50)\n    .strip_ansi(true)\n    .show_warnings(false);\n```\n\nWhen NOT to use Builder: if the struct has 1-3 fields with obvious meaning. Over-engineering for simple cases.\n\n## Pattern 3: State Machine (Parser\u002FFilter Flows)\n\nUse when: parsing multi-section output (test results, build output) where context changes behavior.\n\n```rust\n\u002F\u002F RTK example: pytest output parsing\n#[derive(Debug, PartialEq)]\nenum ParseState {\n    LookingForTests,\n    InTestOutput,\n    InFailureSummary,\n    Done,\n}\n\nfn parse_pytest(input: &str) -> String {\n    let mut state = ParseState::LookingForTests;\n    let mut failures = Vec::new();\n\n    for line in input.lines() {\n        match state {\n            ParseState::LookingForTests => {\n                if line.contains(\"FAILED\") || line.contains(\"ERROR\") {\n                    state = ParseState::InFailureSummary;\n                    failures.push(line);\n                }\n            }\n            ParseState::InFailureSummary => {\n                if line.starts_with(\"=====\") { state = ParseState::Done; }\n                else { failures.push(line); }\n            }\n            ParseState::Done => break,\n            _ => {}\n        }\n    }\n    failures.join(\"\\n\")\n}\n```\n\n## Pattern 4: Trait Object (Command Dispatch)\n\nUse when: different command families need the same interface. Avoids massive match arms.\n\n```rust\n\u002F\u002F Define a common interface for filters\npub trait OutputFilter {\n    fn filter(&self, input: &str) -> Result\u003CString>;\n    fn command_name(&self) -> &str;\n}\n\npub struct GitFilter;\npub struct CargoFilter;\n\nimpl OutputFilter for GitFilter {\n    fn filter(&self, input: &str) -> Result\u003CString> { filter_git(input) }\n    fn command_name(&self) -> &str { \"git\" }\n}\n\n\u002F\u002F RTK currently uses match-based dispatch in main.rs (simpler, no dynamic dispatch overhead)\n\u002F\u002F Trait objects are useful if filter registry becomes dynamic (e.g., TOML-loaded plugins)\n```\n\nNote: RTK's current `match` dispatch in `main.rs` is intentional — static dispatch, zero overhead. Only move to trait objects if the match arm count exceeds ~20 commands.\n\n## Pattern 5: RAII (Resource Management)\n\nUse when: managing resources that need cleanup (temp files, SQLite connections).\n\n```rust\n\u002F\u002F RTK tee.rs — RAII for temp output files\npub struct TeeFile {\n    path: PathBuf,\n}\n\nimpl TeeFile {\n    pub fn create(content: &str) -> Result\u003CSelf> {\n        let path = tee_path()?;\n        fs::write(&path, content)\n            .with_context(|| format!(\"Failed to write tee file: {}\", path.display()))?;\n        Ok(Self { path })\n    }\n\n    pub fn path(&self) -> &Path { &self.path }\n}\n\n\u002F\u002F No explicit cleanup needed — file persists intentionally (rotation handled separately)\n\u002F\u002F If cleanup were needed: impl Drop { fn drop(&mut self) { let _ = fs::remove_file(&self.path); } }\n```\n\n## Pattern 6: Strategy (Swappable Filter Logic)\n\nUse when: a command has multiple filtering modes (e.g., compact vs. verbose).\n\n```rust\npub enum FilterMode {\n    Compact,    \u002F\u002F Show only failures\u002Ferrors\n    Summary,    \u002F\u002F Show counts + top errors\n    Full,       \u002F\u002F Pass through unchanged\n}\n\npub fn apply_filter(input: &str, mode: FilterMode) -> String {\n    match mode {\n        FilterMode::Compact => filter_compact(input),\n        FilterMode::Summary => filter_summary(input),\n        FilterMode::Full => input.to_string(),\n    }\n}\n```\n\n## Pattern 7: Extension Trait (Add Methods to External Types)\n\nUse when: you need to add methods to types you don't own (like `&str` for RTK-specific parsing).\n\n```rust\npub trait RtkStrExt {\n    fn is_error_line(&self) -> bool;\n    fn is_warning_line(&self) -> bool;\n    fn token_count(&self) -> usize;\n}\n\nimpl RtkStrExt for str {\n    fn is_error_line(&self) -> bool {\n        self.starts_with(\"error\") || self.contains(\"[E\")\n    }\n    fn is_warning_line(&self) -> bool {\n        self.starts_with(\"warning\")\n    }\n    fn token_count(&self) -> usize {\n        self.split_whitespace().count()\n    }\n}\n\n\u002F\u002F Usage\nif line.is_error_line() { ... }\nlet tokens = output.token_count();\n```\n\n## RTK Pattern Selection Guide\n\n| Situation | Pattern | Avoid |\n|-----------|---------|-------|\n| New `*_cmd.rs` filter module | Standard module pattern (see CLAUDE.md) | Over-abstracting |\n| 4+ optional config fields | Builder | Struct literal |\n| Multi-phase output parsing | State Machine | Nested if\u002Felse |\n| Type-safe wrapper around string | Newtype | Raw `String` |\n| Adding methods to `&str` | Extension Trait | Free functions |\n| Resource with cleanup | RAII \u002F Drop | Manual cleanup |\n| Dynamic filter registry | Trait Object | Match sprawl |\n\n## Anti-Patterns in RTK Context\n\n```rust\n\u002F\u002F ❌ Generic over-engineering for one command\npub trait Filterable\u003CT: CommandArgs + Send + Sync + 'static> { ... }\n\n\u002F\u002F ✅ Just write the function\npub fn filter_git_log(input: &str) -> Result\u003CString> { ... }\n\n\u002F\u002F ❌ Singleton registry with global state\nstatic FILTER_REGISTRY: Mutex\u003CHashMap\u003CString, Box\u003Cdyn Filter>>> = ...;\n\n\u002F\u002F ✅ Match in main.rs — simple, zero overhead, easy to trace\n\n\u002F\u002F ❌ Async traits for \"future-proofing\"\n#[async_trait]\npub trait Filter { async fn apply(&self, input: &str) -> Result\u003CString>; }\n\n\u002F\u002F ✅ Synchronous — RTK is single-threaded by design\npub trait Filter { fn apply(&self, input: &str) -> Result\u003CString>; }\n```\n",{"name":5,"tags":23,"effort":29,"triggers":30,"description":7,"allowed-tools":35},[24,5,25,26,27,28],"rust","architecture","newtype","builder","rtk","medium",[31,32,33,34],"design pattern","how to structure","best pattern for","refactor to pattern",[36,37,38],"Read","Grep","Glob","main","d046d088ce5a79a083f0abc0fe1b7ded73bc5b1f","claude-config\u002Fskills\u002Fdesign-patterns","https:\u002F\u002Fgithub.com\u002FSansar35\u002Fclaude-agent","https:\u002F\u002Fgithub.com\u002FSansar35","2026-05-10 16:04:53",{"source":8,"skillName":5,"commands":46,"prompt":56,"zipAvailable":57},[47,50,53],{"tool":48,"command":49},"npx","npx skills add Sansar35\u002Fclaude-agent --skill design-patterns",{"tool":51,"command":52},"bunx","bunx skills add Sansar35\u002Fclaude-agent --skill design-patterns",{"tool":54,"command":55},"pnpm","pnpm dlx skills add Sansar35\u002Fclaude-agent --skill design-patterns","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FSansar35\u002Fclaude-agent\u002Fblob\u002Fmain\u002Fclaude-config\u002Fskills\u002Fdesign-patterns\u002FSKILL.md",true,[59],{"path":60,"resourceType":61,"resourceTypeDesc":62,"sizeBytes":63,"sourceHtmlUrl":64},".skill-source.json","REFERENCE","参考文档",387,"https:\u002F\u002Fgithub.com\u002FSansar35\u002Fclaude-agent\u002Fblob\u002Fmain\u002Fclaude-config\u002Fskills\u002Fdesign-patterns\u002F.skill-source.json",[66,73,80,87,94,102],{"skillNo":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"publishedAt":18},"01M72DVAN1JYEA302MT0C5MGD6","zustand-store-ts","Create Zustand stores following established patterns with proper TypeScript types and middleware.","https:\u002F\u002Fgithub.com\u002FSansar35\u002Fclaude-agent\u002Fblob\u002Fmain\u002Fclaude-config\u002Fskills\u002Fzustand-store-ts\u002FSKILL.md",[],[],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":18},"01M72DV8J5NBRRM4RPDFRV95N7","zod-validation-expert","Expert in Zod — TypeScript-first schema validation. Covers parsing, custom errors, refinements, type inference, and integration with React Hook Form, Next.js, and tRPC.","https:\u002F\u002Fgithub.com\u002FSansar35\u002Fclaude-agent\u002Fblob\u002Fmain\u002Fclaude-config\u002Fskills\u002Fzod-validation-expert\u002FSKILL.md",[],[],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":18},"01M72DV5EMHW0BHP9BZ167MDCB","zinc-database","Access ZINC (230M+ purchasable compounds). Search by ZINC ID\u002FSMILES, similarity searches, 3D-ready structures for docking, analog discovery, for virtual screening and drug discovery.","https:\u002F\u002Fgithub.com\u002FSansar35\u002Fclaude-agent\u002Fblob\u002Fmain\u002Fclaude-config\u002Fskills\u002Fzinc-database\u002FSKILL.md",[],[],{"skillNo":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":91,"categories":92,"keywords":93,"publishedAt":18},"01M72DV216QY0E693ZPEVQ0DBS","zarr-python","Chunked N-D arrays for cloud storage. Compressed arrays, parallel I\u002FO, S3\u002FGCS integration, NumPy\u002FDask\u002FXarray compatible, for large-scale scientific computing pipelines.","https:\u002F\u002Fgithub.com\u002FSansar35\u002Fclaude-agent\u002Fblob\u002Fmain\u002Fclaude-config\u002Fskills\u002Fzarr-python\u002FSKILL.md",[],[],{"skillNo":95,"name":96,"nameZh":6,"description":97,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":98,"sourceHtmlUrl":99,"categories":100,"keywords":101,"publishedAt":18},"01M72DTXQREMCRKA8NHCVKHN4W","zapier-workflows","Manage and trigger pre-built Zapier workflows and MCP tool orchestration. Use when user mentions workflows, Zaps, automations, daily digest, research, search, lead tracking, expenses, or asks to \"run\" any process. Also handles Perplexity-based research and Google Sheets data tracking.","https:\u002F\u002Fgithub.com\u002FSansar35\u002Fclaude-agent\u002Fblob\u002Fmain\u002Fclaude-config\u002Fskills\u002Fzapier-workflows\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FSansar35\u002Fclaude-agent\u002Fblob\u002Fmain\u002Fclaude-config\u002Fskills\u002Fzapier-workflows\u002FSKILL.md",[],[],{"skillNo":103,"name":104,"nameZh":6,"description":105,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":106,"categories":107,"keywords":108,"publishedAt":18},"01M72DTT17TBSJ0Y8J2XZ4C9TZ","zapier-make-patterns","No-code automation democratizes workflow building. Zapier and Make (formerly Integromat) let non-developers automate business processes without writing code. But no-code doesn't mean no-complexity - these platforms have their own patterns, pitfalls, and breaking points.  This skill covers when to use which platform, how to build reliable automations, and when to graduate to code-based solutions. Key insight: Zapier optimizes for simplicity and integrations (7000+ apps), Make optimizes for power","https:\u002F\u002Fgithub.com\u002FSansar35\u002Fclaude-agent\u002Fblob\u002Fmain\u002Fclaude-config\u002Fskills\u002Fzapier-make-patterns\u002FSKILL.md",[],[]]