[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7FADVMQ0KC82R2D49SHP25K":3,"skill-same:01M7FADVMQ0KC82R2D49SHP25K":78},{"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},"01M7FADVMQ0KC82R2D49SHP25K","liuguang-banlan-ui",null,"Builds two parameterized UI modes—流光溢彩白 (iridescent white) and 五彩斑斓黑 (colorful black)—with OKLCH, WebGL\u002FCSS fallback, vision gating, screenshot QA, and total\u002Fper-color intensity reports. Use when a UI request names either mode or needs measured color parameters.","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\u002F06-前端与设计\u002Fliuguang-banlan-ui\u002FSKILL.md",[],[],"2026-11-16 10:05:34",false,"---\nname: liuguang-banlan-ui\ndescription: Builds two parameterized UI modes—流光溢彩白 (iridescent white) and 五彩斑斓黑 (colorful black)—with OKLCH, WebGL\u002FCSS fallback, vision gating, screenshot QA, and total\u002Fper-color intensity reports. Use when a UI request names either mode or needs measured color parameters.\ncategory: creative\nrisk: critical\nsource: self\nsource_type: self\ndate_added: \"2026-08-15\"\nauthor: 3516027002att-ui\ntags: [ui, frontend, oklch, webgl, accessibility]\ntools: [codex, claude, cursor, gemini]\n---\n\n# 流光斑斓 UI 工坊\n\n## Overview\n\nUse one skill with two explicit modes, not a generic material library. Preserve a stable information workspace while treating the spectral field as a controlled environmental layer. Keep the implementation parameterized so every output can report total color intensity, per-color intensity, OKLCH values, peak opacity, spatial scale, phase, and measured coverage.\n\nRead [style-contract.md](references\u002Fstyle-contract.md) before choosing a mode or changing palette semantics. Read [verification.md](references\u002Fverification.md) before claiming visual or screenshot validation.\n\n## When to Use\n\n- Use when a user names 流光溢彩白 or 五彩斑斓黑, asks for one unified skill covering both, or needs a reusable parameterized starter.\n- Use when the final report must include total color intensity, each color's intensity, OKLCH values, and screenshot measurements.\n- Do not use for a generic theme-token library or an unparameterized visual mockup.\n\n## Workflow\n\n### 1. Classify the request\n\n- Map “流光溢彩白” to `opal` and “五彩斑斓黑” to `obsidian`.\n- If both are requested, keep one shared implementation and two explicit theme manifests.\n- Inspect the existing project, framework, route, build system, and uncommitted work before copying starter assets.\n- Use the smallest appropriate change surface; do not replace an existing design system without authorization.\n\n### 2. Gate visual verification\n\n- Confirm that the executing model can directly inspect images before taking a screenshot-based visual claim.\n- If native image inspection is unavailable, continue with code and deterministic pixel checks but mark the result `visual-unverified`; never infer visual quality from DOM or CSS alone.\n- Record `modelVision`, `screenshotCapture`, `deterministicPixelMetrics`, and `visualVerificationMode` in the final report.\n\n### 3. Establish the scene and structure\n\n- Choose a neutral, information-dense workbench domain such as field research, inventory, monitoring, or operations.\n- Use a continuous three-pane or similarly coherent workspace: navigation, queue\u002Flist, detail, metadata, and one signature observation band.\n- Keep color in the field, ribbon, markers, and state accents; keep text, controls, boundaries, and semantic hierarchy stable.\n- Prefer restrained surfaces and weak fills. Avoid turning every region into a floating card.\n\n### 4. Implement the parameter contract\n\nMaintain a serializable manifest with these top-level fields:\n\n```js\n{\n  schemaVersion, mode, label, preset, seed,\n  overallColorIntensity,\n  base: { oklch },\n  colors: [{\n    id, label, oklch, srgbFallback,\n    intensity, peakOpacity, lightnessBias,\n    fieldScale, phase,\n    measuredCoverage, effectiveShare\n  }],\n  field: { scale, octaves, warpStrength, motionSpeed, staticTime, ditherStrength, luminanceCap },\n  output: { colorSpace, p3Enhancement, reducedMotion }\n}\n```\n\n- Keep every intensity in `[0, 1]`; make `overallColorIntensity` the global budget and `colors[].intensity` the per-color budget.\n- Use OKLCH as the authoring space and provide an sRGB fallback for non-OKLCH contexts.\n- Keep the seed, static frame, phases, and field scales deterministic; do not use random per render.\n- Expose sliders for the global intensity and every configured color. Make reset, JSON export, and copy actions available.\n\n### 5. Build the spectral field\n\n- Use a procedural fBm\u002Fdomain-warp field or an equivalent continuous field; keep it behind the interface with `pointer-events: none`.\n- Use broad flowing hue regions or ribbons, not obvious radial blobs, spotlight circles, or hard rainbow bands.\n- Upload the complete palette and per-color field scales to the renderer. Apply the dark-mode luminance cap after palette mixing.\n- Provide a CSS fallback with comparable visual intent when WebGL is unavailable.\n- Pause or freeze motion when the document is hidden or `prefers-reduced-motion` is active.\n- Keep the renderer local and dependency-light; do not require remote fonts, images, or APIs for the starter.\n\n### 6. Preserve interaction and accessibility\n\n- Keep semantic headings, labels, focus-visible states, keyboard escape behavior, and readable contrast.\n- Test navigation, record\u002Flist selection, tab selection, parameter panel open\u002Fclose, slider input, reset, export, and copy fallback.\n- Make the workbench responsive at a narrow mobile viewport; collapse navigation and metadata without losing the primary record flow.\n\n### 7. Validate and report\n\n- Scaffold a clean starter with `scripts\u002Fscaffold_template.py` when a neutral implementation is needed.\n- The bundled helpers parse only the restricted data-literal assignment used by\n  the starter. They reject expressions, function calls, duplicate keys,\n  unsupported syntax, trailing statements, and oversized manifests without\n  executing JavaScript. Keep runtime theme configs data-only as well.\n- Run `scripts\u002Fvalidate_manifest.py` on each theme config before rendering.\n- Capture desktop and mobile screenshots with a real browser. Inspect them directly if visual capability is available.\n- Run `scripts\u002Fmeasure_preview.py` on the pure field screenshot and retain measured chromatic ratio, luminance statistics, per-color coverage, and effective share.\n- Report configured parameters separately from measured values; do not imply that pixel attribution is an exact shader contribution.\n- Use `partial`, `visual-unverified`, or `blocked` when a required capability or native check is unavailable.\n\n## Limitations and capability states\n\n- WebGL is optional. The starter switches to a CSS spectral fallback when a WebGL context cannot be created or shader\u002Fprogram setup fails; fallback rendering is parameterized but is not pixel-identical to the shader.\n- Native image inspection and browser screenshot capture are runtime capabilities, not guaranteed by this skill. If either is unavailable, keep the result visual-unverified and report the missing capability explicitly.\n- The deterministic measurement helper requires the optional Python packages listed in scripts\u002Frequirements.txt. Without them it exits with an unavailable-capability message instead of producing a misleading report.\n- Manifests may contain 3 to 12 colors. The renderer uploads every configured entry up to that validated limit, while the shader ignores only unused capacity slots.\n- Configured values, fallback values, and measured pixel attribution describe different things; do not treat measured per-color coverage as an exact decomposition of shader energy.\n\n## Anti-pattern guardrails\n\n- Do not rename the two modes into a vague “reusable UI material” abstraction.\n- Do not use pure white as the only white-mode signal, black crush as the only dark-mode signal, or RGB neon as a shortcut to “colorful”.\n- Do not hide weak structure behind full-page glass, excessive blur, or giant gradients.\n- Do not report visual success from screenshot dimensions, DOM state, or static CSS alone.\n- Do not include private project names, links, repository identifiers, or source-chat contents in generated assets or reports.\n\n## Bundled resources\n\nUse the bundled starter under `assets\u002Fstarter\u002F` as a neutral base. Copy only the selected mode when integrating into an existing project, and preserve the existing project’s content and build conventions.\n\n### scripts\u002F\n\n- `scaffold_template.py`: copy the neutral starter for `opal`, `obsidian`, or both.\n- `manifest_parser.py`: statically parse the restricted data-only manifest grammar without executing JavaScript.\n- `validate_manifest.py`: validate required manifest fields and ranges.\n- `measure_preview.py`: measure a rendered pure-field PNG against the configured OKLCH palette.\n\n### references\u002F\n\n- `style-contract.md`: mode-specific visual rules and recommended parameter ranges.\n- `verification.md`: visual-capability gate, browser QA, pixel measurement, and report schema.\n\n### assets\u002F\n\n`starter\u002F` contains a neutral static workbench, shared renderer, and both theme variants. Treat it as output material, not as documentation to paste into context wholesale.\n","# 流光斑斓 UI 工坊\n\n## Overview\n\nUse one skill with two explicit modes, not a generic material library. Preserve a stable information workspace while treating the spectral field as a controlled environmental layer. Keep the implementation parameterized so every output can report total color intensity, per-color intensity, OKLCH values, peak opacity, spatial scale, phase, and measured coverage.\n\nRead [style-contract.md](references\u002Fstyle-contract.md) before choosing a mode or changing palette semantics. Read [verification.md](references\u002Fverification.md) before claiming visual or screenshot validation.\n\n## When to Use\n\n- Use when a user names 流光溢彩白 or 五彩斑斓黑, asks for one unified skill covering both, or needs a reusable parameterized starter.\n- Use when the final report must include total color intensity, each color's intensity, OKLCH values, and screenshot measurements.\n- Do not use for a generic theme-token library or an unparameterized visual mockup.\n\n## Workflow\n\n### 1. Classify the request\n\n- Map “流光溢彩白” to `opal` and “五彩斑斓黑” to `obsidian`.\n- If both are requested, keep one shared implementation and two explicit theme manifests.\n- Inspect the existing project, framework, route, build system, and uncommitted work before copying starter assets.\n- Use the smallest appropriate change surface; do not replace an existing design system without authorization.\n\n### 2. Gate visual verification\n\n- Confirm that the executing model can directly inspect images before taking a screenshot-based visual claim.\n- If native image inspection is unavailable, continue with code and deterministic pixel checks but mark the result `visual-unverified`; never infer visual quality from DOM or CSS alone.\n- Record `modelVision`, `screenshotCapture`, `deterministicPixelMetrics`, and `visualVerificationMode` in the final report.\n\n### 3. Establish the scene and structure\n\n- Choose a neutral, information-dense workbench domain such as field research, inventory, monitoring, or operations.\n- Use a continuous three-pane or similarly coherent workspace: navigation, queue\u002Flist, detail, metadata, and one signature observation band.\n- Keep color in the field, ribbon, markers, and state accents; keep text, controls, boundaries, and semantic hierarchy stable.\n- Prefer restrained surfaces and weak fills. Avoid turning every region into a floating card.\n\n### 4. Implement the parameter contract\n\nMaintain a serializable manifest with these top-level fields:\n\n```js\n{\n  schemaVersion, mode, label, preset, seed,\n  overallColorIntensity,\n  base: { oklch },\n  colors: [{\n    id, label, oklch, srgbFallback,\n    intensity, peakOpacity, lightnessBias,\n    fieldScale, phase,\n    measuredCoverage, effectiveShare\n  }],\n  field: { scale, octaves, warpStrength, motionSpeed, staticTime, ditherStrength, luminanceCap },\n  output: { colorSpace, p3Enhancement, reducedMotion }\n}\n```\n\n- Keep every intensity in `[0, 1]`; make `overallColorIntensity` the global budget and `colors[].intensity` the per-color budget.\n- Use OKLCH as the authoring space and provide an sRGB fallback for non-OKLCH contexts.\n- Keep the seed, static frame, phases, and field scales deterministic; do not use random per render.\n- Expose sliders for the global intensity and every configured color. Make reset, JSON export, and copy actions available.\n\n### 5. Build the spectral field\n\n- Use a procedural fBm\u002Fdomain-warp field or an equivalent continuous field; keep it behind the interface with `pointer-events: none`.\n- Use broad flowing hue regions or ribbons, not obvious radial blobs, spotlight circles, or hard rainbow bands.\n- Upload the complete palette and per-color field scales to the renderer. Apply the dark-mode luminance cap after palette mixing.\n- Provide a CSS fallback with comparable visual intent when WebGL is unavailable.\n- Pause or freeze motion when the document is hidden or `prefers-reduced-motion` is active.\n- Keep the renderer local and dependency-light; do not require remote fonts, images, or APIs for the starter.\n\n### 6. Preserve interaction and accessibility\n\n- Keep semantic headings, labels, focus-visible states, keyboard escape behavior, and readable contrast.\n- Test navigation, record\u002Flist selection, tab selection, parameter panel open\u002Fclose, slider input, reset, export, and copy fallback.\n- Make the workbench responsive at a narrow mobile viewport; collapse navigation and metadata without losing the primary record flow.\n\n### 7. Validate and report\n\n- Scaffold a clean starter with `scripts\u002Fscaffold_template.py` when a neutral implementation is needed.\n- The bundled helpers parse only the restricted data-literal assignment used by\n  the starter. They reject expressions, function calls, duplicate keys,\n  unsupported syntax, trailing statements, and oversized manifests without\n  executing JavaScript. Keep runtime theme configs data-only as well.\n- Run `scripts\u002Fvalidate_manifest.py` on each theme config before rendering.\n- Capture desktop and mobile screenshots with a real browser. Inspect them directly if visual capability is available.\n- Run `scripts\u002Fmeasure_preview.py` on the pure field screenshot and retain measured chromatic ratio, luminance statistics, per-color coverage, and effective share.\n- Report configured parameters separately from measured values; do not imply that pixel attribution is an exact shader contribution.\n- Use `partial`, `visual-unverified`, or `blocked` when a required capability or native check is unavailable.\n\n## Limitations and capability states\n\n- WebGL is optional. The starter switches to a CSS spectral fallback when a WebGL context cannot be created or shader\u002Fprogram setup fails; fallback rendering is parameterized but is not pixel-identical to the shader.\n- Native image inspection and browser screenshot capture are runtime capabilities, not guaranteed by this skill. If either is unavailable, keep the result visual-unverified and report the missing capability explicitly.\n- The deterministic measurement helper requires the optional Python packages listed in scripts\u002Frequirements.txt. Without them it exits with an unavailable-capability message instead of producing a misleading report.\n- Manifests may contain 3 to 12 colors. The renderer uploads every configured entry up to that validated limit, while the shader ignores only unused capacity slots.\n- Configured values, fallback values, and measured pixel attribution describe different things; do not treat measured per-color coverage as an exact decomposition of shader energy.\n\n## Anti-pattern guardrails\n\n- Do not rename the two modes into a vague “reusable UI material” abstraction.\n- Do not use pure white as the only white-mode signal, black crush as the only dark-mode signal, or RGB neon as a shortcut to “colorful”.\n- Do not hide weak structure behind full-page glass, excessive blur, or giant gradients.\n- Do not report visual success from screenshot dimensions, DOM state, or static CSS alone.\n- Do not include private project names, links, repository identifiers, or source-chat contents in generated assets or reports.\n\n## Bundled resources\n\nUse the bundled starter under `assets\u002Fstarter\u002F` as a neutral base. Copy only the selected mode when integrating into an existing project, and preserve the existing project’s content and build conventions.\n\n### scripts\u002F\n\n- `scaffold_template.py`: copy the neutral starter for `opal`, `obsidian`, or both.\n- `manifest_parser.py`: statically parse the restricted data-only manifest grammar without executing JavaScript.\n- `validate_manifest.py`: validate required manifest fields and ranges.\n- `measure_preview.py`: measure a rendered pure-field PNG against the configured OKLCH palette.\n\n### references\u002F\n\n- `style-contract.md`: mode-specific visual rules and recommended parameter ranges.\n- `verification.md`: visual-capability gate, browser QA, pixel measurement, and report schema.\n\n### assets\u002F\n\n`starter\u002F` contains a neutral static workbench, shared renderer, and both theme variants. Treat it as output material, not as documentation to paste into context wholesale.\n",{"name":5,"risk":24,"tags":25,"tools":31,"author":36,"source":37,"category":38,"date_added":39,"description":7,"source_type":37},"critical",[26,27,28,29,30],"ui","frontend","oklch","webgl","accessibility",[32,33,34,35],"codex","claude","cursor","gemini","3516027002att-ui","self","creative","2026-08-15","main","d69096e239f2a89aabc2cd078c47664a9d3b1e11","06-前端与设计\u002Fliuguang-banlan-ui",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 liuguang-banlan-ui",{"tool":54,"command":55},"bunx","bunx skills add lza6\u002FArmor-piercing-system-prompts --skill liuguang-banlan-ui",{"tool":57,"command":58},"pnpm","pnpm dlx skills add lza6\u002FArmor-piercing-system-prompts --skill liuguang-banlan-ui","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F06-前端与设计\u002Fliuguang-banlan-ui\u002FSKILL.md",true,[62,68,72],{"path":63,"resourceType":64,"resourceTypeDesc":65,"sizeBytes":66,"sourceHtmlUrl":67},"references\u002Fstyle-contract.md","REFERENCE","参考文档",3122,"https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F06-前端与设计\u002Fliuguang-banlan-ui\u002Freferences\u002Fstyle-contract.md",{"path":69,"resourceType":64,"resourceTypeDesc":65,"sizeBytes":70,"sourceHtmlUrl":71},"references\u002Fverification.md",2957,"https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F06-前端与设计\u002Fliuguang-banlan-ui\u002Freferences\u002Fverification.md",{"path":73,"resourceType":74,"resourceTypeDesc":75,"sizeBytes":76,"sourceHtmlUrl":77},"scripts\u002Frequirements.txt","SCRIPT","脚本",30,"https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F06-前端与设计\u002Fliuguang-banlan-ui\u002Fscripts\u002Frequirements.txt",[79,86,91,98,105,112],{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"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":87,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"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":92,"name":93,"nameZh":6,"description":94,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":95,"categories":96,"keywords":97,"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":99,"name":100,"nameZh":6,"description":101,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":102,"categories":103,"keywords":104,"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":106,"name":107,"nameZh":6,"description":108,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":109,"categories":110,"keywords":111,"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":113,"name":114,"nameZh":6,"description":115,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":116,"categories":117,"keywords":118,"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",[],[]]