[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6EGEJS5KTXNDYD3FJXAQB7H":3,"skill-same:01M6EGEJS5KTXNDYD3FJXAQB7H":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":23,"publishedAt":34,"linkOnly":35,"markdownContent":36,"markdownBody":37,"frontMatter":38,"refName":39,"commitSha":40,"skillDirectory":41,"forksCount":42,"repositoryHtmlUrl":43,"repositoryHomepageUrl":6,"ownerHtmlUrl":44,"ownerBlogUrl":45,"ownerDescription":46,"updatedAt":47,"install":48,"resources":61},"01M6EGEJS5KTXNDYD3FJXAQB7H","ln-404-test-executor",null,"Executes Story Finalizer test tasks (label \"tests\") from Todo -> To Review. Enforces risk-based limits and priority.","levalencia\u002Fagent-god-mode","levalencia","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F6962857?v=4","01M6EB0FZZ4BPQPC4HET4QY6NM","Luis Valencia ","01M6EB0G4HWHPWW0H9X7QKSAHP",3,"MIT","https:\u002F\u002Fgithub.com\u002Flevalencia\u002Fagent-god-mode\u002Fblob\u002Fmain\u002Forganized-skills\u002Fln-404-test-executor\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32,33],"test","executor","ln 404 test executor","review","tasks","risk","risk-based","Story","todo","tests","2026-11-10 10:12:30",false,"---\nname: ln-404-test-executor\ndescription: Executes Story Finalizer test tasks (label \"tests\") from Todo -> To Review. Enforces risk-based limits and priority.\nlicense: MIT\n---\n\n> **Paths:** File paths (`shared\u002F`, `references\u002F`, `..\u002Fln-*`) are relative to skills repo root. If not found at CWD, locate this SKILL.md directory and go up one level for repo root.\n\n# Test Task Executor\n\nRuns a single Story final test task (label \"tests\") through implementation\u002Fexecution to To Review.\n\n## Purpose & Scope\n- Handle only tasks labeled \"tests\"; other tasks go to ln-401.\n- Follow the 11-section test task plan (E2E\u002FIntegration\u002FUnit, infra\u002Fdocs\u002Fcleanup).\n- Enforce risk-based constraints: Priority ≥15 scenarios covered; each test passes Usefulness Criteria; no framework\u002FDB\u002Flibrary\u002Fperformance tests.\n- Update Linear\u002Fkanban for this task only: Todo -> In Progress -> To Review.\n\n## Inputs\n\n| Input | Required | Source | Description |\n|-------|----------|--------|-------------|\n| `taskId` | Yes | args, parent Story, kanban, user | Test task to execute |\n\n**Resolution:** Task Resolution Chain.\n**Status filter:** Todo (label: tests)\n\n## Task Storage Mode\n\n**MANDATORY READ:** Load `shared\u002Freferences\u002Ftools_config_guide.md`, `shared\u002Freferences\u002Fstorage_mode_detection.md`, and `shared\u002Freferences\u002Finput_resolution_pattern.md`\n\nExtract: `task_provider` = Task Management → Provider (`linear` | `file`).\n\n| Aspect | Linear Mode | File Mode |\n|--------|-------------|-----------|\n| **Load task** | `get_issue(task_id)` | `Read(\"docs\u002Ftasks\u002Fepics\u002F...\u002Ftasks\u002FT{NNN}-*.md\")` |\n| **Load Story** | `get_issue(parent_id)` | `Read(\"docs\u002Ftasks\u002Fepics\u002F...\u002Fstory.md\")` |\n| **Update status** | `save_issue(id, state)` | `Edit` the `**Status:**` line in file |\n| **Test results** | `create_comment({issueId, body})` | `Write` comment to `...\u002Fcomments\u002F{ISO-timestamp}.md` |\n\n**File Mode transitions:** Todo → In Progress → To Review\n\n## Workflow (concise)\n1) **Resolve taskId:** Run Task Resolution Chain per guide (status filter: [Todo, label: tests]).\n2) **Load task:** Fetch full test task description (Linear: get_issue; File: Read task file); read linked guides\u002Fmanuals\u002FADRs\u002Fresearch; review parent Story and manual test results if provided.\n2b) **Goal gate:** **MANDATORY READ:** `shared\u002Freferences\u002Fgoal_articulation_gate.md` — State REAL GOAL of these tests (which business behavior must be verified, not \"write tests\"). NOT THE GOAL: testing infrastructure or framework behavior instead of business logic. HIDDEN CONSTRAINT: which existing tests might break from implementation changes.\n3) **Read environment docs:** **Read `docs\u002Fproject\u002Finfrastructure.md`** — get server IPs, ports, service endpoints. **Read `docs\u002Fproject\u002Frunbook.md`** — understand test environment setup, Docker commands, test execution prerequisites. Use exact commands from runbook.\n4) **Validate plan:** Check Priority ≥15 coverage and Usefulness Criteria; ensure focus on business flows (no infra-only tests).\n5) **Start work:** Set task In Progress (Linear: update_issue; File: Edit status line); move in kanban.\n6) **Implement & run:** **MANDATORY READ:** `shared\u002Freferences\u002Fcode_efficiency_criterion.md` — Author\u002Fupdate tests per plan; reuse existing fixtures\u002Fhelpers; run tests; fix failing existing tests; update infra\u002Fdoc sections as required. Before handoff, verify 3 efficiency self-checks (especially: reuse fixtures instead of duplicating setup).\n7) **Complete:** Ensure counts\u002Fpriority still within limits; set task To Review; move in kanban; add comment summarizing coverage, commands run, and any deviations.\n\n## Critical Rules\n- Single-task only; no bulk updates.\n- Do not mark Done; the reviewer approves. Task must end in To Review.\n- Keep language (EN\u002FRU) consistent with task.\n- No framework\u002Flibrary\u002FDB\u002Fperformance\u002Fload tests; focus on business logic correctness (not infrastructure throughput).\n- Respect limits and priority; if violated, stop and return with findings.\n- **Do NOT commit.** Leave all changes uncommitted — the reviewer reviews and commits.\n\n## Definition of Done\n- Task identified as test task and set to In Progress; kanban updated.\n- Plan validated (priority\u002Flimits) and guides read.\n- Tests implemented\u002Fupdated and executed; existing failures fixed.\n- Docs\u002Finfra updates applied per task plan.\n- Task set to To Review; kanban moved; summary comment added with commands and coverage.\n\n## Test Failure Analysis Protocol\n\n**CRITICAL:** When a **newly written test** fails, STOP and analyze BEFORE changing anything (failing new tests often indicate implementation bugs, not test issues — fixing blindly masks root cause).\n\n**Step 1: Verify Test Correctness**\n- Does test match AC requirements exactly? (Given\u002FWhen\u002FThen from Story)\n- Is expected value correct per business logic?\n- If uncertain: Query `ref_search_documentation(query=\"[domain] expected behavior\")`\n\n**Step 2: Decision**\n| Test matches AC? | Action |\n|------------------|--------|\n| YES | **BUG IN CODE** → Fix implementation, not test |\n| NO | Test is wrong → Fix test assertion |\n| UNCERTAIN | **MANDATORY:** Query MCP Ref + ask user before changing |\n\n**Step 3: Document in Linear comment**\n\"Test [name] failed. Analysis: [test correct \u002F test wrong]. Action: [fixed code \u002F fixed test]. Reason: [justification]\"\n\n**RED FLAGS (require user confirmation):**\n- ⚠️ Changing assertion to match actual output (\"make test green\")\n- ⚠️ Removing test case that \"doesn't work\"\n- ⚠️ Weakening expectations (e.g., `toContain` instead of `toEqual`)\n\n**GREEN LIGHTS (safe to proceed):**\n- ✅ Fixing typo in test setup\u002Fmock data\n- ✅ Fixing code to match AC requirements\n- ✅ Adding missing test setup step\n\n## Test Writing Principles\n\n### 1. Strict Assertions - Fail on Any Mismatch\n\n**Use exact match assertions by default:**\n\n| Strict (PREFER) | Loose (AVOID unless justified) |\n|-----------------|--------------------------------|\n| Exact equality check | Partial\u002Fsubstring match |\n| Exact length check | \"Has any length\" check |\n| Full object comparison | Partial object match |\n| Exact type check | Truthy\u002Ffalsy check |\n\n**WARN-level assertions FORBIDDEN** - test either PASS or FAIL, no warnings.\n\n### 2. Expected-Based Testing for Deterministic Output\n\n**For deterministic responses (API, transformations):**\n- Use **snapshot\u002Fgolden file testing** for complex deterministic output\n- Compare actual output vs expected reference file\n- Normalize dynamic data before comparison (timestamps → fixed, UUIDs → placeholder)\n\n### 3. Golden Rule\n\n> \"If you know the expected value, assert the exact value.\"\n\n**Forbidden:** Using loose assertions to \"make test pass\" when exact value is known.\n\n## Reference Files\n- **Tools config:** `shared\u002Freferences\u002Ftools_config_guide.md`\n- **Storage mode operations:** `shared\u002Freferences\u002Fstorage_mode_detection.md`\n- Kanban format: `docs\u002Ftasks\u002Fkanban_board.md`\n- **MANDATORY READ:** `shared\u002Freferences\u002Fresearch_tool_fallback.md`\n\n---\n**Version:** 3.2.0\n**Last Updated:** 2026-01-15\n","> **Paths:** File paths (`shared\u002F`, `references\u002F`, `..\u002Fln-*`) are relative to skills repo root. If not found at CWD, locate this SKILL.md directory and go up one level for repo root.\n\n# Test Task Executor\n\nRuns a single Story final test task (label \"tests\") through implementation\u002Fexecution to To Review.\n\n## Purpose & Scope\n- Handle only tasks labeled \"tests\"; other tasks go to ln-401.\n- Follow the 11-section test task plan (E2E\u002FIntegration\u002FUnit, infra\u002Fdocs\u002Fcleanup).\n- Enforce risk-based constraints: Priority ≥15 scenarios covered; each test passes Usefulness Criteria; no framework\u002FDB\u002Flibrary\u002Fperformance tests.\n- Update Linear\u002Fkanban for this task only: Todo -> In Progress -> To Review.\n\n## Inputs\n\n| Input | Required | Source | Description |\n|-------|----------|--------|-------------|\n| `taskId` | Yes | args, parent Story, kanban, user | Test task to execute |\n\n**Resolution:** Task Resolution Chain.\n**Status filter:** Todo (label: tests)\n\n## Task Storage Mode\n\n**MANDATORY READ:** Load `shared\u002Freferences\u002Ftools_config_guide.md`, `shared\u002Freferences\u002Fstorage_mode_detection.md`, and `shared\u002Freferences\u002Finput_resolution_pattern.md`\n\nExtract: `task_provider` = Task Management → Provider (`linear` | `file`).\n\n| Aspect | Linear Mode | File Mode |\n|--------|-------------|-----------|\n| **Load task** | `get_issue(task_id)` | `Read(\"docs\u002Ftasks\u002Fepics\u002F...\u002Ftasks\u002FT{NNN}-*.md\")` |\n| **Load Story** | `get_issue(parent_id)` | `Read(\"docs\u002Ftasks\u002Fepics\u002F...\u002Fstory.md\")` |\n| **Update status** | `save_issue(id, state)` | `Edit` the `**Status:**` line in file |\n| **Test results** | `create_comment({issueId, body})` | `Write` comment to `...\u002Fcomments\u002F{ISO-timestamp}.md` |\n\n**File Mode transitions:** Todo → In Progress → To Review\n\n## Workflow (concise)\n1) **Resolve taskId:** Run Task Resolution Chain per guide (status filter: [Todo, label: tests]).\n2) **Load task:** Fetch full test task description (Linear: get_issue; File: Read task file); read linked guides\u002Fmanuals\u002FADRs\u002Fresearch; review parent Story and manual test results if provided.\n2b) **Goal gate:** **MANDATORY READ:** `shared\u002Freferences\u002Fgoal_articulation_gate.md` — State REAL GOAL of these tests (which business behavior must be verified, not \"write tests\"). NOT THE GOAL: testing infrastructure or framework behavior instead of business logic. HIDDEN CONSTRAINT: which existing tests might break from implementation changes.\n3) **Read environment docs:** **Read `docs\u002Fproject\u002Finfrastructure.md`** — get server IPs, ports, service endpoints. **Read `docs\u002Fproject\u002Frunbook.md`** — understand test environment setup, Docker commands, test execution prerequisites. Use exact commands from runbook.\n4) **Validate plan:** Check Priority ≥15 coverage and Usefulness Criteria; ensure focus on business flows (no infra-only tests).\n5) **Start work:** Set task In Progress (Linear: update_issue; File: Edit status line); move in kanban.\n6) **Implement & run:** **MANDATORY READ:** `shared\u002Freferences\u002Fcode_efficiency_criterion.md` — Author\u002Fupdate tests per plan; reuse existing fixtures\u002Fhelpers; run tests; fix failing existing tests; update infra\u002Fdoc sections as required. Before handoff, verify 3 efficiency self-checks (especially: reuse fixtures instead of duplicating setup).\n7) **Complete:** Ensure counts\u002Fpriority still within limits; set task To Review; move in kanban; add comment summarizing coverage, commands run, and any deviations.\n\n## Critical Rules\n- Single-task only; no bulk updates.\n- Do not mark Done; the reviewer approves. Task must end in To Review.\n- Keep language (EN\u002FRU) consistent with task.\n- No framework\u002Flibrary\u002FDB\u002Fperformance\u002Fload tests; focus on business logic correctness (not infrastructure throughput).\n- Respect limits and priority; if violated, stop and return with findings.\n- **Do NOT commit.** Leave all changes uncommitted — the reviewer reviews and commits.\n\n## Definition of Done\n- Task identified as test task and set to In Progress; kanban updated.\n- Plan validated (priority\u002Flimits) and guides read.\n- Tests implemented\u002Fupdated and executed; existing failures fixed.\n- Docs\u002Finfra updates applied per task plan.\n- Task set to To Review; kanban moved; summary comment added with commands and coverage.\n\n## Test Failure Analysis Protocol\n\n**CRITICAL:** When a **newly written test** fails, STOP and analyze BEFORE changing anything (failing new tests often indicate implementation bugs, not test issues — fixing blindly masks root cause).\n\n**Step 1: Verify Test Correctness**\n- Does test match AC requirements exactly? (Given\u002FWhen\u002FThen from Story)\n- Is expected value correct per business logic?\n- If uncertain: Query `ref_search_documentation(query=\"[domain] expected behavior\")`\n\n**Step 2: Decision**\n| Test matches AC? | Action |\n|------------------|--------|\n| YES | **BUG IN CODE** → Fix implementation, not test |\n| NO | Test is wrong → Fix test assertion |\n| UNCERTAIN | **MANDATORY:** Query MCP Ref + ask user before changing |\n\n**Step 3: Document in Linear comment**\n\"Test [name] failed. Analysis: [test correct \u002F test wrong]. Action: [fixed code \u002F fixed test]. Reason: [justification]\"\n\n**RED FLAGS (require user confirmation):**\n- ⚠️ Changing assertion to match actual output (\"make test green\")\n- ⚠️ Removing test case that \"doesn't work\"\n- ⚠️ Weakening expectations (e.g., `toContain` instead of `toEqual`)\n\n**GREEN LIGHTS (safe to proceed):**\n- ✅ Fixing typo in test setup\u002Fmock data\n- ✅ Fixing code to match AC requirements\n- ✅ Adding missing test setup step\n\n## Test Writing Principles\n\n### 1. Strict Assertions - Fail on Any Mismatch\n\n**Use exact match assertions by default:**\n\n| Strict (PREFER) | Loose (AVOID unless justified) |\n|-----------------|--------------------------------|\n| Exact equality check | Partial\u002Fsubstring match |\n| Exact length check | \"Has any length\" check |\n| Full object comparison | Partial object match |\n| Exact type check | Truthy\u002Ffalsy check |\n\n**WARN-level assertions FORBIDDEN** - test either PASS or FAIL, no warnings.\n\n### 2. Expected-Based Testing for Deterministic Output\n\n**For deterministic responses (API, transformations):**\n- Use **snapshot\u002Fgolden file testing** for complex deterministic output\n- Compare actual output vs expected reference file\n- Normalize dynamic data before comparison (timestamps → fixed, UUIDs → placeholder)\n\n### 3. Golden Rule\n\n> \"If you know the expected value, assert the exact value.\"\n\n**Forbidden:** Using loose assertions to \"make test pass\" when exact value is known.\n\n## Reference Files\n- **Tools config:** `shared\u002Freferences\u002Ftools_config_guide.md`\n- **Storage mode operations:** `shared\u002Freferences\u002Fstorage_mode_detection.md`\n- Kanban format: `docs\u002Ftasks\u002Fkanban_board.md`\n- **MANDATORY READ:** `shared\u002Freferences\u002Fresearch_tool_fallback.md`\n\n---\n**Version:** 3.2.0\n**Last Updated:** 2026-01-15\n",{"name":5,"license":15,"description":7},"main","fa638b97a18ff6d9f26cf0eaf3dfa123531bcc87","organized-skills\u002Fln-404-test-executor",1,"https:\u002F\u002Fgithub.com\u002Flevalencia\u002Fagent-god-mode","https:\u002F\u002Fgithub.com\u002Flevalencia","https:\u002F\u002Fmedium.com\u002F@luisevalencia","Microsoft MVP - Artificial Intelligence\r\nMachine Learning Enthusiast\r\n","2026-05-02 06:55:36",{"source":8,"skillName":5,"commands":49,"prompt":59,"zipAvailable":60},[50,53,56],{"tool":51,"command":52},"npx","npx skills add levalencia\u002Fagent-god-mode --skill ln-404-test-executor",{"tool":54,"command":55},"bunx","bunx skills add levalencia\u002Fagent-god-mode --skill ln-404-test-executor",{"tool":57,"command":58},"pnpm","pnpm dlx skills add levalencia\u002Fagent-god-mode --skill ln-404-test-executor","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Flevalencia\u002Fagent-god-mode\u002Fblob\u002Fmain\u002Forganized-skills\u002Fln-404-test-executor\u002FSKILL.md",true,[],[63,85,121,148,172,199],{"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":34},"01M6EM8ES5M9J4S8N78NJST0YC","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\u002Flevalencia\u002Fagent-god-mode\u002Fblob\u002Fmain\u002Forganized-skills\u002Fzarr-python\u002FSKILL.md",[],[70,71,72,73,74,75,76,77,78,79,80,81,82,83,84],"python","zarr python","storage","integration","s3","gcs","cloud","dask","parallel","pipelines","arrays","numpy","scientific computing","scale","scientific",{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":102,"publishedAt":34},"01M6EM8AR6ZFKZ9YVW8TTG850Z","zabbix","Zabbix monitoring system automation via API and Python. Use when: (1) Managing hosts, templates, items, triggers, or host groups, (2) Automating monitoring configuration, (3) Sending data via Zabbix trapper\u002Fsender, (4) Querying historical data or events, (5) Bulk operations on Zabbix objects, (6) Maintenance window management, (7) User\u002Fpermission management","https:\u002F\u002Fgithub.com\u002Flevalencia\u002Fagent-god-mode\u002Fblob\u002Fmain\u002Forganized-skills\u002Fzabbix-api-skill\u002FSKILL.md",[91,94,97],{"categoryNo":92,"categoryName":93,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000010","后端与接口",{"categoryNo":95,"categoryName":96,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":98,"categoryName":99,"taxonomyType":100,"taxonomyTypeDesc":101},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[87,70,103,104,105,106,107,108,109,110,111,112,113,114,115,116,117,118,119,120],"automation","window management","monitoring","data","templates","api","system","operations","use","maintenance","objects","permission","bulk operations","triggers","host","events","via","bulk",{"skillNo":122,"name":123,"nameZh":6,"description":124,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":125,"categories":126,"keywords":127,"publishedAt":34},"01M6EM6Q9JG846ECQY9A210A26","x-twitter-growth","X\u002FTwitter growth engine for building audience, crafting viral content, and analyzing engagement. Use when the user wants to grow on X\u002FTwitter, write tweets or threads, analyze their X profile, research competitors on X, plan a posting strategy, or optimize engagement. Complements social-content (generic multi-platform) with X-specific depth: algorithm mechanics, thread engineering, reply strategy, profile optimization, and competitive intelligence via web search.","https:\u002F\u002Fgithub.com\u002Flevalencia\u002Fagent-god-mode\u002Fblob\u002Fmain\u002Forganized-skills\u002Fx-twitter-growth\u002FSKILL.md",[],[128,129,130,131,132,133,134,135,136,137,138,139,140,141,142,143,144,145,146,147],"twitter","x twitter growth","growth","competitive intelligence","search","analyzing","plan","marketing","web search","competitors","analyze","write","optimize","social","intelligence","viral","growth engine","mechanics","grow","competitive",{"skillNo":149,"name":150,"nameZh":6,"description":151,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":152,"categories":153,"keywords":154,"publishedAt":34},"01M6EM3FQNPYNKPC4CV9TCVNGD","what-if-oracle","Run structured What-If scenario analysis with multi-branch possibility exploration. Use this skill when the user asks speculative questions like \"what if...\", \"what would happen if...\", \"what are the possibilities\", \"explore scenarios\", \"scenario analysis\", \"possibility space\", \"what could go wrong\", \"best case \u002F worst case\", \"risk analysis\", \"contingency planning\", \"strategic options\", or any question about uncertain futures. Also trigger when the user faces a fork-in-the-road decision, wants to stress-test an idea, or needs to think through consequences before committing.","https:\u002F\u002Fgithub.com\u002Flevalencia\u002Fagent-god-mode\u002Fblob\u002Fmain\u002Forganized-skills\u002Fwhat-if-oracle\u002FSKILL.md",[],[155,156,24,157,158,159,29,160,161,162,163,164,111,165,166,167,168,169,170,171],"oracle","what if oracle","planning","ux","futures","analysis","explore","decision","branch","question","exploration","options","stress-test","strategies","trigger","case","multi",{"skillNo":173,"name":174,"nameZh":6,"description":175,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":176,"categories":177,"keywords":181,"publishedAt":34},"01M6EM08C06RGDYCJ86HAPK0FF","vercel-react-best-practices","React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React\u002FNext.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.","https:\u002F\u002Fgithub.com\u002Flevalencia\u002Fagent-god-mode\u002Fblob\u002Fmain\u002Forganized-skills\u002Fvercel-react-best-practices\u002FSKILL.md",[178],{"categoryNo":179,"categoryName":180,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000009","前端开发",[182,183,184,185,186,187,188,189,190,191,28,192,193,106,194,195,196,197,198,116],"react","vercel react best practices","best practices","react best practices","vercel","writing","performance","components","react components","guidelines","code","Optimization","Next.js","refactoring","performance optimization","next","pages",{"skillNo":200,"name":201,"nameZh":6,"description":202,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":203,"categories":204,"keywords":215,"publishedAt":34},"01M6EM00S13326QM08DTM94J6Z","venue-templates","Access comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.","https:\u002F\u002Fgithub.com\u002Flevalencia\u002Fagent-god-mode\u002Fblob\u002Fmain\u002Forganized-skills\u002Fvenue-templates\u002FSKILL.md",[205,208,211,212],{"categoryNo":206,"categoryName":207,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":209,"categoryName":210,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000021","资料检索与研究",{"categoryNo":95,"categoryName":96,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":213,"categoryName":214,"taxonomyType":100,"taxonomyTypeDesc":101},"01JBSEEDCAT000000000000036","内容创作者",[107,216,217,191,218,219,220,221,222,223,224,139,225,226,227,228,229,230,84,231],"venue templates","research","NeurIPS","ICML","LaTeX","science","Bash","access","read","edit","proposals","Academic","requirements","formatting","journal","chi"]