[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7EWM1P6C3W89BJD7AY90ZPS":3,"skill-same:01M7EWM1P6C3W89BJD7AY90ZPS":46},{"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":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":6,"ownerDescription":30,"updatedAt":31,"install":32,"resources":45},"01M7EWM1P6C3W89BJD7AY90ZPS","agentica-prompts",null,"Write reliable prompts for Agentica\u002FREPL agents that avoid LLM instruction ambiguity","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\u002F05-技能与代理开发\u002Fagentica-prompts\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: agentica-prompts\ndescription: Write reliable prompts for Agentica\u002FREPL agents that avoid LLM instruction ambiguity\nuser-invocable: false\n---\n\n# Agentica Prompt Engineering\n\nWrite prompts that Agentica agents reliably follow. Standard natural language prompts fail ~35% of the time due to LLM instruction ambiguity.\n\n## The Orchestration Pattern\n\nProven workflow for context-preserving agent orchestration:\n\n```\n1. RESEARCH (Nia)     → Output to .claude\u002Fcache\u002Fagents\u002Fresearch\u002F\n       ↓\n2. PLAN (RP-CLI)      → Reads research, outputs .claude\u002Fcache\u002Fagents\u002Fplan\u002F\n       ↓\n3. VALIDATE           → Checks plan against best practices\n       ↓\n4. IMPLEMENT (TDD)    → Failing tests first, then pass\n       ↓\n5. REVIEW (Jury)      → Compare impl vs plan vs research\n       ↓\n6. DEBUG (if needed)  → Research via Nia, don't assume\n```\n\n**Key:** Use Task (not TaskOutput) + directory handoff = clean context\n\n## Agent System Prompt Template\n\nInject this into each agent's system prompt for rich context understanding:\n\n```\n## AGENT IDENTITY\n\nYou are {AGENT_ROLE} in a multi-agent orchestration system.\nYour output will be consumed by: {DOWNSTREAM_AGENT}\nYour input comes from: {UPSTREAM_AGENT}\n\n## SYSTEM ARCHITECTURE\n\nYou are part of the Agentica orchestration framework:\n- Memory Service: remember(key, value), recall(query), store_fact(content)\n- Task Graph: create_task(), complete_task(), get_ready_tasks()\n- File I\u002FO: read_file(), write_file(), edit_file(), bash()\n\nSession ID: {SESSION_ID} (all your memory\u002Ftasks scoped here)\n\n## DIRECTORY HANDOFF\n\nRead your inputs from: {INPUT_DIR}\nWrite your outputs to: {OUTPUT_DIR}\n\nOutput format: Write a summary file and any artifacts.\n- {OUTPUT_DIR}\u002Fsummary.md - What you did, key findings\n- {OUTPUT_DIR}\u002Fartifacts\u002F - Any generated files\n\n## CODE CONTEXT\n\n{CODE_MAP}  \u003C- Inject RepoPrompt codemap here\n\n## YOUR TASK\n\n{TASK_DESCRIPTION}\n\n## CRITICAL RULES\n\n1. RETRIEVE means read existing content - NEVER generate hypothetical content\n2. WRITE means create\u002Fupdate file - specify exact content\n3. When stuck, output what you found and what's blocking you\n4. Your summary.md is your handoff to the next agent - be precise\n```\n\n## Pattern-Specific Prompts\n\n### Swarm (Research)\n\n```\n## SWARM AGENT: {PERSPECTIVE}\n\nYou are researching: {QUERY}\nYour unique angle: {PERSPECTIVE}\n\nOther agents are researching different angles. You don't need to be comprehensive.\nFocus ONLY on your perspective. Be specific, not broad.\n\nOutput format:\n- 3-5 key findings from YOUR perspective\n- Evidence\u002Fsources for each finding\n- Uncertainties or gaps you identified\n\nWrite to: {OUTPUT_DIR}\u002F{PERSPECTIVE}\u002Ffindings.md\n```\n\n### Hierarchical (Coordinator)\n\n```\n## COORDINATOR\n\nTask to decompose: {TASK}\n\nAvailable specialists (use EXACTLY these names):\n{SPECIALIST_LIST}\n\nRules:\n1. ONLY use specialist names from the list above\n2. Each subtask should be completable by ONE specialist\n3. 2-5 subtasks maximum\n4. If task is simple, return empty list and handle directly\n\nOutput: JSON list of {specialist, task} pairs\n```\n\n### Generator\u002FCritic (Generator)\n\n```\n## GENERATOR\n\nTask: {TASK}\n{PREVIOUS_FEEDBACK}\n\nProduce your solution. The Critic will review it.\n\nOutput structure (use EXACTLY these keys):\n{\n  \"solution\": \"your main output\",\n  \"code\": \"if applicable\",\n  \"reasoning\": \"why this approach\"\n}\n\nWrite to: {OUTPUT_DIR}\u002Fsolution.json\n```\n\n### Generator\u002FCritic (Critic)\n\n```\n## CRITIC\n\nReviewing solution at: {SOLUTION_PATH}\n\nEvaluation criteria:\n1. Correctness - Does it solve the task?\n2. Completeness - Any missing cases?\n3. Quality - Is it well-structured?\n\nIf APPROVED: Write {\"approved\": true, \"feedback\": \"why approved\"}\nIf NOT approved: Write {\"approved\": false, \"feedback\": \"specific issues to fix\"}\n\nWrite to: {OUTPUT_DIR}\u002Fcritique.json\n```\n\n### Jury (Voter)\n\n```\n## JUROR #{N}\n\nQuestion: {QUESTION}\n\nVote independently. Do NOT try to guess what others will vote.\nYour vote should be based solely on the evidence.\n\nOutput: Your vote as {RETURN_TYPE}\n```\n\n## Verb Mappings\n\n| Action | Bad (ambiguous) | Good (explicit) |\n|--------|-----------------|-----------------|\n| Read | \"Read the file at X\" | \"RETRIEVE contents of: X\" |\n| Write | \"Put this in the file\" | \"WRITE to X: {content}\" |\n| Check | \"See if file has X\" | \"RETRIEVE contents of: X. Contains Y? YES\u002FNO.\" |\n| Edit | \"Change X to Y\" | \"EDIT file X: replace 'old' with 'new'\" |\n\n## Directory Handoff Mechanism\n\nAgents communicate via filesystem, not TaskOutput:\n\n```python\n# Pattern implementation\nOUTPUT_BASE = \".claude\u002Fcache\u002Fagents\"\n\ndef get_agent_dirs(agent_id: str, phase: str) -> tuple[Path, Path]:\n    \"\"\"Return (input_dir, output_dir) for an agent.\"\"\"\n    input_dir = Path(OUTPUT_BASE) \u002F f\"{phase}_input\"\n    output_dir = Path(OUTPUT_BASE) \u002F agent_id\n    output_dir.mkdir(parents=True, exist_ok=True)\n    return input_dir, output_dir\n\ndef chain_agents(phase1_id: str, phase2_id: str):\n    \"\"\"Phase2 reads from phase1's output.\"\"\"\n    phase1_output = Path(OUTPUT_BASE) \u002F phase1_id\n    phase2_input = phase1_output  # Direct handoff\n    return phase2_input\n```\n\n## Anti-Patterns\n\n| Pattern | Problem | Fix |\n|---------|---------|-----|\n| \"Tell me what X contains\" | May summarize or hallucinate | \"Return the exact text\" |\n| \"Check the file\" | Ambiguous action | Specify RETRIEVE or VERIFY |\n| Question form | Invites generation | Use imperative \"RETRIEVE\" |\n| \"Read and confirm\" | May just say \"confirmed\" | \"Return the exact text\" |\n| TaskOutput for handoff | Floods context with transcript | Directory-based handoff |\n| \"Be thorough\" | Subjective, inconsistent | Specify exact output format |\n\n## Expected Improvement\n\n- Without fixes: ~60% success rate\n- With RETRIEVE + explicit return: ~95% success rate\n- With structured tool schemas: ~98% success rate\n- With directory handoff: Context preserved, no transcript pollution\n\n## Code Map Injection\n\nUse RepoPrompt to generate code map for agent context:\n\n```bash\n# Generate codemap for agent context\nrp-cli --path . --output .claude\u002Fcache\u002Fagents\u002Fcodemap.md\n\n# Inject into agent system prompt\ncodemap=$(cat .claude\u002Fcache\u002Fagents\u002Fcodemap.md)\n```\n\n## Memory Context Injection\n\nExplain the memory system to agents:\n\n```\n## MEMORY SYSTEM\n\nYou have access to a 3-tier memory system:\n\n1. **Core Memory** (in-context): remember(key, value), recall(query)\n   - Fast key-value store for current session facts\n\n2. **Archival Memory** (searchable): store_fact(content), search_memory(query)\n   - FTS5-indexed long-term storage\n   - Use for findings that should persist\n\n3. **Recall** (unified): recall(query)\n   - Searches both core and archival\n   - Returns formatted context string\n\nAll memory is scoped to session_id: {SESSION_ID}\n```\n\n## References\n\n- ToolBench (2023): Models fail ~35% retrieval tasks with ambiguous descriptions\n- Gorilla (2023): Structured schemas improve reliability by 3x\n- ReAct (2022): Explicit reasoning before action reduces errors by ~25%\n","# Agentica Prompt Engineering\n\nWrite prompts that Agentica agents reliably follow. Standard natural language prompts fail ~35% of the time due to LLM instruction ambiguity.\n\n## The Orchestration Pattern\n\nProven workflow for context-preserving agent orchestration:\n\n```\n1. RESEARCH (Nia)     → Output to .claude\u002Fcache\u002Fagents\u002Fresearch\u002F\n       ↓\n2. PLAN (RP-CLI)      → Reads research, outputs .claude\u002Fcache\u002Fagents\u002Fplan\u002F\n       ↓\n3. VALIDATE           → Checks plan against best practices\n       ↓\n4. IMPLEMENT (TDD)    → Failing tests first, then pass\n       ↓\n5. REVIEW (Jury)      → Compare impl vs plan vs research\n       ↓\n6. DEBUG (if needed)  → Research via Nia, don't assume\n```\n\n**Key:** Use Task (not TaskOutput) + directory handoff = clean context\n\n## Agent System Prompt Template\n\nInject this into each agent's system prompt for rich context understanding:\n\n```\n## AGENT IDENTITY\n\nYou are {AGENT_ROLE} in a multi-agent orchestration system.\nYour output will be consumed by: {DOWNSTREAM_AGENT}\nYour input comes from: {UPSTREAM_AGENT}\n\n## SYSTEM ARCHITECTURE\n\nYou are part of the Agentica orchestration framework:\n- Memory Service: remember(key, value), recall(query), store_fact(content)\n- Task Graph: create_task(), complete_task(), get_ready_tasks()\n- File I\u002FO: read_file(), write_file(), edit_file(), bash()\n\nSession ID: {SESSION_ID} (all your memory\u002Ftasks scoped here)\n\n## DIRECTORY HANDOFF\n\nRead your inputs from: {INPUT_DIR}\nWrite your outputs to: {OUTPUT_DIR}\n\nOutput format: Write a summary file and any artifacts.\n- {OUTPUT_DIR}\u002Fsummary.md - What you did, key findings\n- {OUTPUT_DIR}\u002Fartifacts\u002F - Any generated files\n\n## CODE CONTEXT\n\n{CODE_MAP}  \u003C- Inject RepoPrompt codemap here\n\n## YOUR TASK\n\n{TASK_DESCRIPTION}\n\n## CRITICAL RULES\n\n1. RETRIEVE means read existing content - NEVER generate hypothetical content\n2. WRITE means create\u002Fupdate file - specify exact content\n3. When stuck, output what you found and what's blocking you\n4. Your summary.md is your handoff to the next agent - be precise\n```\n\n## Pattern-Specific Prompts\n\n### Swarm (Research)\n\n```\n## SWARM AGENT: {PERSPECTIVE}\n\nYou are researching: {QUERY}\nYour unique angle: {PERSPECTIVE}\n\nOther agents are researching different angles. You don't need to be comprehensive.\nFocus ONLY on your perspective. Be specific, not broad.\n\nOutput format:\n- 3-5 key findings from YOUR perspective\n- Evidence\u002Fsources for each finding\n- Uncertainties or gaps you identified\n\nWrite to: {OUTPUT_DIR}\u002F{PERSPECTIVE}\u002Ffindings.md\n```\n\n### Hierarchical (Coordinator)\n\n```\n## COORDINATOR\n\nTask to decompose: {TASK}\n\nAvailable specialists (use EXACTLY these names):\n{SPECIALIST_LIST}\n\nRules:\n1. ONLY use specialist names from the list above\n2. Each subtask should be completable by ONE specialist\n3. 2-5 subtasks maximum\n4. If task is simple, return empty list and handle directly\n\nOutput: JSON list of {specialist, task} pairs\n```\n\n### Generator\u002FCritic (Generator)\n\n```\n## GENERATOR\n\nTask: {TASK}\n{PREVIOUS_FEEDBACK}\n\nProduce your solution. The Critic will review it.\n\nOutput structure (use EXACTLY these keys):\n{\n  \"solution\": \"your main output\",\n  \"code\": \"if applicable\",\n  \"reasoning\": \"why this approach\"\n}\n\nWrite to: {OUTPUT_DIR}\u002Fsolution.json\n```\n\n### Generator\u002FCritic (Critic)\n\n```\n## CRITIC\n\nReviewing solution at: {SOLUTION_PATH}\n\nEvaluation criteria:\n1. Correctness - Does it solve the task?\n2. Completeness - Any missing cases?\n3. Quality - Is it well-structured?\n\nIf APPROVED: Write {\"approved\": true, \"feedback\": \"why approved\"}\nIf NOT approved: Write {\"approved\": false, \"feedback\": \"specific issues to fix\"}\n\nWrite to: {OUTPUT_DIR}\u002Fcritique.json\n```\n\n### Jury (Voter)\n\n```\n## JUROR #{N}\n\nQuestion: {QUESTION}\n\nVote independently. Do NOT try to guess what others will vote.\nYour vote should be based solely on the evidence.\n\nOutput: Your vote as {RETURN_TYPE}\n```\n\n## Verb Mappings\n\n| Action | Bad (ambiguous) | Good (explicit) |\n|--------|-----------------|-----------------|\n| Read | \"Read the file at X\" | \"RETRIEVE contents of: X\" |\n| Write | \"Put this in the file\" | \"WRITE to X: {content}\" |\n| Check | \"See if file has X\" | \"RETRIEVE contents of: X. Contains Y? YES\u002FNO.\" |\n| Edit | \"Change X to Y\" | \"EDIT file X: replace 'old' with 'new'\" |\n\n## Directory Handoff Mechanism\n\nAgents communicate via filesystem, not TaskOutput:\n\n```python\n# Pattern implementation\nOUTPUT_BASE = \".claude\u002Fcache\u002Fagents\"\n\ndef get_agent_dirs(agent_id: str, phase: str) -> tuple[Path, Path]:\n    \"\"\"Return (input_dir, output_dir) for an agent.\"\"\"\n    input_dir = Path(OUTPUT_BASE) \u002F f\"{phase}_input\"\n    output_dir = Path(OUTPUT_BASE) \u002F agent_id\n    output_dir.mkdir(parents=True, exist_ok=True)\n    return input_dir, output_dir\n\ndef chain_agents(phase1_id: str, phase2_id: str):\n    \"\"\"Phase2 reads from phase1's output.\"\"\"\n    phase1_output = Path(OUTPUT_BASE) \u002F phase1_id\n    phase2_input = phase1_output  # Direct handoff\n    return phase2_input\n```\n\n## Anti-Patterns\n\n| Pattern | Problem | Fix |\n|---------|---------|-----|\n| \"Tell me what X contains\" | May summarize or hallucinate | \"Return the exact text\" |\n| \"Check the file\" | Ambiguous action | Specify RETRIEVE or VERIFY |\n| Question form | Invites generation | Use imperative \"RETRIEVE\" |\n| \"Read and confirm\" | May just say \"confirmed\" | \"Return the exact text\" |\n| TaskOutput for handoff | Floods context with transcript | Directory-based handoff |\n| \"Be thorough\" | Subjective, inconsistent | Specify exact output format |\n\n## Expected Improvement\n\n- Without fixes: ~60% success rate\n- With RETRIEVE + explicit return: ~95% success rate\n- With structured tool schemas: ~98% success rate\n- With directory handoff: Context preserved, no transcript pollution\n\n## Code Map Injection\n\nUse RepoPrompt to generate code map for agent context:\n\n```bash\n# Generate codemap for agent context\nrp-cli --path . --output .claude\u002Fcache\u002Fagents\u002Fcodemap.md\n\n# Inject into agent system prompt\ncodemap=$(cat .claude\u002Fcache\u002Fagents\u002Fcodemap.md)\n```\n\n## Memory Context Injection\n\nExplain the memory system to agents:\n\n```\n## MEMORY SYSTEM\n\nYou have access to a 3-tier memory system:\n\n1. **Core Memory** (in-context): remember(key, value), recall(query)\n   - Fast key-value store for current session facts\n\n2. **Archival Memory** (searchable): store_fact(content), search_memory(query)\n   - FTS5-indexed long-term storage\n   - Use for findings that should persist\n\n3. **Recall** (unified): recall(query)\n   - Searches both core and archival\n   - Returns formatted context string\n\nAll memory is scoped to session_id: {SESSION_ID}\n```\n\n## References\n\n- ToolBench (2023): Models fail ~35% retrieval tasks with ambiguous descriptions\n- Gorilla (2023): Structured schemas improve reliability by 3x\n- ReAct (2022): Explicit reasoning before action reduces errors by ~25%\n",{"name":5,"description":7,"user-invocable":20},"main","d69096e239f2a89aabc2cd078c47664a9d3b1e11","05-技能与代理开发\u002Fagentica-prompts",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":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add lza6\u002FArmor-piercing-system-prompts --skill agentica-prompts",{"tool":38,"command":39},"bunx","bunx skills add lza6\u002FArmor-piercing-system-prompts --skill agentica-prompts",{"tool":41,"command":42},"pnpm","pnpm dlx skills add lza6\u002FArmor-piercing-system-prompts --skill agentica-prompts","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F05-技能与代理开发\u002Fagentica-prompts\u002FSKILL.md",true,[],[47,55,60,67,74,81],{"skillNo":48,"name":49,"nameZh":6,"description":50,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":51,"categories":52,"keywords":53,"publishedAt":54},"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",[],[],"2026-11-16 10:05:34",{"skillNo":56,"name":49,"nameZh":6,"description":50,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":57,"categories":58,"keywords":59,"publishedAt":54},"01M7FFG0T6AZ0STEJPSB3CX84K","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobsidian-clipper-template-creator-antigravity-awesome-skills-main\u002FSKILL.md",[],[],{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":54},"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":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":54},"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":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":54},"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":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":54},"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",[],[]]