[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7FEE10GD8QXPKRTWV48X6RE":3,"skill-same:01M7FEE10GD8QXPKRTWV48X6RE":62},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":40,"commitSha":41,"skillDirectory":42,"forksCount":43,"repositoryHtmlUrl":44,"repositoryHomepageUrl":6,"ownerHtmlUrl":45,"ownerBlogUrl":6,"ownerDescription":46,"updatedAt":47,"install":48,"resources":61},"01M7FEE10GD8QXPKRTWV48X6RE","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.","lza6\u002FArmor-piercing-system-prompts","lza6","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F128880206?v=4","01M7EB3K7WPX5T28EJ2NVHE6EG","Chinese-tingfeng","01M7EB3K97E1KQ16QWKJMFNGX8",11,"MIT","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fdesign-patterns\u002FSKILL.md",[],[],"2026-11-16 10:05:34",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":24,"effort":30,"triggers":31,"description":7,"allowed-tools":36},[25,5,26,27,28,29],"rust","architecture","newtype","builder","rtk","medium",[32,33,34,35],"design pattern","how to structure","best pattern for","refactor to pattern",[37,38,39],"Read","Grep","Glob","main","d69096e239f2a89aabc2cd078c47664a9d3b1e11","07-后端与架构\u002Fdesign-patterns",3,"https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts","https:\u002F\u002Fgithub.com\u002Flza6","个人vx：Tf00798\r\n个人✈：@TFGY999","2026-10-08 14:29:22",{"source":8,"skillName":5,"commands":49,"prompt":59,"zipAvailable":60},[50,53,56],{"tool":51,"command":52},"npx","npx skills add lza6\u002FArmor-piercing-system-prompts --skill design-patterns",{"tool":54,"command":55},"bunx","bunx skills add lza6\u002FArmor-piercing-system-prompts --skill design-patterns",{"tool":57,"command":58},"pnpm","pnpm dlx skills add lza6\u002FArmor-piercing-system-prompts --skill design-patterns","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fdesign-patterns\u002FSKILL.md",true,[],[63,70,75,82,89,96],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":19},"01M7FFG485KY83TD6HSC4YPCMC","obsidian-clipper-template-creator","Guide for creating templates for the Obsidian Web Clipper. Use when you want to create a new clipping template, understand available variables, or format clipped content.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobsidian-clipper-template-creator\u002FSKILL.md",[],[],{"skillNo":71,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":19},"01M7FFG0T6AZ0STEJPSB3CX84K","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobsidian-clipper-template-creator-antigravity-awesome-skills-main\u002FSKILL.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":19},"01M7FFFY0QEM14SKWPDYGMXM2P","python-api","Programmatic Object-Detection-Metrics API guidance for BoundingBox, BoundingBoxes, Evaluator, enums, coordinate conversion, AP\u002FmAP semantics, and source-style import diagnostics.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobject-detection-metrics\u002Fsub-skills\u002Fpython-api\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":19},"01M7FFFVZQZ2GJ0C0TGP7JHD20","file-evaluation","Folder-based PASCAL VOC AP\u002FmAP evaluation from ground-truth and detection text files.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobject-detection-metrics\u002Fsub-skills\u002Ffile-evaluation\u002FSKILL.md",[],[],{"skillNo":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":93,"categories":94,"keywords":95,"publishedAt":19},"01M7FFFSFNYSE77SJ6PE1CK2DA","object-detection-metrics","Guides legacy Object-Detection-Metrics PASCAL VOC AP\u002FmAP evaluation from detection text folders and direct Python API classes.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobject-detection-metrics\u002FSKILL.md",[],[],{"skillNo":97,"name":98,"nameZh":6,"description":99,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":100,"categories":101,"keywords":102,"publishedAt":19},"01M7FFFP0GCK1RVXBCPQ8APBMT","nx-workspace-patterns","Configure and optimize Nx monorepo workspaces. Use when setting up Nx, configuring project boundaries, optimizing build caching, or implementing affected commands.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fnx-workspace-patterns\u002FSKILL.md",[],[]]