[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6EGMH9MJB0HMHFTDM2TM0ZW":3,"skill-same:01M6EGMH9MJB0HMHFTDM2TM0ZW":66},{"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":28,"linkOnly":29,"markdownContent":30,"markdownBody":31,"frontMatter":32,"refName":33,"commitSha":34,"skillDirectory":35,"forksCount":36,"repositoryHtmlUrl":37,"repositoryHomepageUrl":6,"ownerHtmlUrl":38,"ownerBlogUrl":39,"ownerDescription":40,"updatedAt":41,"install":42,"resources":55},"01M6EGMH9MJB0HMHFTDM2TM0ZW","ln-740-quality-setup",null,"Coordinates linters, pre-commit hooks, and test infrastructure setup","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-740-quality-setup\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27],"setup","quality","ln 740 quality setup","test","commit","infrastructure","pre-commit","hooks","coordinates","2026-11-10 10:12:30",false,"---\nname: ln-740-quality-setup\ndescription: Coordinates linters, pre-commit hooks, and test infrastructure setup\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# ln-740-quality-setup\n\n**Type:** L2 Domain Coordinator\n**Category:** 7XX Project Bootstrap\n**Parent:** ln-700-project-bootstrap\n\nCoordinates code quality tooling configuration for the project.\n\n---\n\n## Purpose & Scope\n\n**Does:**\n- Detects project technology stack (TypeScript\u002FReact, .NET, Python)\n- Checks for existing quality configurations\n- Delegates to specialized workers for each quality aspect\n- Verifies final configuration works correctly\n\n**Does NOT:**\n- Generate configuration files directly (workers do this)\n- Modify source code\n- Run in isolation (requires ln-720 structure first)\n\n---\n\n## When to Use\n\n| Trigger | Action |\n|---------|--------|\n| After ln-720-structure-migrator completes | Automatic delegation from ln-700 |\n| Manual quality setup needed | Invoke directly with project path |\n| Existing project needs quality tools | Run with existing config detection |\n\n---\n\n## Workflow Overview\n\n| Phase | Action | Output |\n|-------|--------|--------|\n| 1 | Stack Detection | Identified technologies |\n| 2 | Existing Config Check | Skip\u002Fmerge\u002Freplace decisions |\n| 3 | Parallel Delegation | Worker invocations |\n| 4 | Verification | Working quality pipeline |\n\n---\n\n## Phase 1: Stack Detection\n\nDetect project technologies to determine which quality tools to configure.\n\n**Detection Rules:**\n\n| File Pattern | Technology | Linter Stack |\n|--------------|------------|--------------|\n| `package.json` + `tsconfig.json` | TypeScript\u002FReact | ESLint + Prettier |\n| `*.csproj` or `*.sln` | .NET | editorconfig + Roslyn |\n| `pyproject.toml` or `requirements.txt` | Python | Ruff |\n| Multiple detected | Mixed | Configure all detected |\n\n**Actions:**\n1. Glob for technology indicators\n2. Build technology list\n3. Log detected stack to user\n\n---\n\n## Phase 2: Existing Configuration Check\n\nBefore delegating, check what configurations already exist.\n\n**Config Files to Check:**\n\n| Technology | Config Files |\n|------------|--------------|\n| TypeScript | `eslint.config.*`, `.prettierrc*`, `tsconfig.json` |\n| .NET | `.editorconfig`, `Directory.Build.props` |\n| Python | `ruff.toml`, `pyproject.toml [tool.ruff]` |\n| Pre-commit | `.husky\u002F`, `.pre-commit-config.yaml` |\n| Tests | `vitest.config.*`, `pytest.ini`, `*.Tests.csproj` |\n\n**Decision Matrix:**\n\n| Existing Config | Action | Confirmation |\n|-----------------|--------|--------------|\n| None found | Create new | No |\n| Partial found | Merge (add missing) | Ask user |\n| Complete found | Skip | Inform user |\n| User requests replace | Backup + replace | Yes |\n\n---\n\n## Phase 3: Parallel Delegation\n\nInvoke workers for each quality aspect. Workers can run in parallel as they configure independent tools.\n\n**Delegation Order:**\n\n```\nln-740 (this)\n    |\n    +---> ln-741-linter-configurator\n    |         - ESLint\u002FPrettier (TypeScript)\n    |         - editorconfig\u002FRoslyn (.NET)\n    |         - Ruff (Python)\n    |\n    +---> ln-742-precommit-setup\n    |         - Husky + lint-staged (Node.js)\n    |         - pre-commit framework (Python)\n    |         - commitlint\n    |\n    +---> ln-743-test-infrastructure\n              - Vitest (TypeScript)\n              - xUnit (.NET)\n              - pytest (Python)\n```\n\nPass detected stack and existing configs to workers via direct Skill tool invocation.\n\n---\n\n## Phase 4: Verification\n\nAfter all workers complete, verify the quality pipeline works.\n\n**Verification Steps:**\n\n| Check | Command | Expected |\n|-------|---------|----------|\n| Lint runs | `npm run lint` \u002F `ruff check .` \u002F `dotnet format --verify-no-changes` | No errors |\n| Format runs | `npm run format:check` \u002F `ruff format --check` | No changes needed |\n| Tests run | `npm test` \u002F `pytest` \u002F `dotnet test` | Sample tests pass |\n| Hooks work | Create test commit | Hooks trigger |\n\n**On Failure:**\n1. Log specific failure\n2. Suggest fix or re-run specific worker\n3. Do NOT mark as complete until verification passes\n\n---\n\n## Critical Rules\n\n> **RULE 1:** Never overwrite existing user configurations without explicit confirmation.\n\n> **RULE 2:** Workers run AFTER stack detection - do not invoke workers without knowing the stack.\n\n> **RULE 3:** Verification phase is MANDATORY - quality setup is not complete until tools run successfully.\n\n> **RULE 4:** eslint-config-prettier is REQUIRED when both ESLint and Prettier are configured.\n\n---\n\n## Definition of Done\n\n- [ ] All detected technology stacks have appropriate quality tools\n- [ ] Existing configurations preserved or backed up\n- [ ] Lint command runs without errors\n- [ ] Format command runs without errors\n- [ ] Test command runs and sample tests pass\n- [ ] Pre-commit hooks trigger on test commit\n- [ ] User informed of all installed tools and commands\n\n---\n\n## Reference Files\n\n| File | Purpose |\n|------|---------|\n| [stack_detection.md](references\u002Fstack_detection.md) | Detailed detection rules |\n| [verification_checklist.md](references\u002Fverification_checklist.md) | Full verification checklist |\n\n---\n\n## Error Handling\n\n| Error | Cause | Resolution |\n|-------|-------|------------|\n| No stack detected | Empty project | Ask user for intended stack |\n| Worker failed | Missing dependencies | Install prerequisites, retry |\n| Verification failed | Config error | Check specific tool output, fix |\n| Hooks not working | Git not initialized | Run `git init` first |\n\n---\n\n**Version:** 2.0.0\n**Last Updated:** 2026-01-10\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# ln-740-quality-setup\n\n**Type:** L2 Domain Coordinator\n**Category:** 7XX Project Bootstrap\n**Parent:** ln-700-project-bootstrap\n\nCoordinates code quality tooling configuration for the project.\n\n---\n\n## Purpose & Scope\n\n**Does:**\n- Detects project technology stack (TypeScript\u002FReact, .NET, Python)\n- Checks for existing quality configurations\n- Delegates to specialized workers for each quality aspect\n- Verifies final configuration works correctly\n\n**Does NOT:**\n- Generate configuration files directly (workers do this)\n- Modify source code\n- Run in isolation (requires ln-720 structure first)\n\n---\n\n## When to Use\n\n| Trigger | Action |\n|---------|--------|\n| After ln-720-structure-migrator completes | Automatic delegation from ln-700 |\n| Manual quality setup needed | Invoke directly with project path |\n| Existing project needs quality tools | Run with existing config detection |\n\n---\n\n## Workflow Overview\n\n| Phase | Action | Output |\n|-------|--------|--------|\n| 1 | Stack Detection | Identified technologies |\n| 2 | Existing Config Check | Skip\u002Fmerge\u002Freplace decisions |\n| 3 | Parallel Delegation | Worker invocations |\n| 4 | Verification | Working quality pipeline |\n\n---\n\n## Phase 1: Stack Detection\n\nDetect project technologies to determine which quality tools to configure.\n\n**Detection Rules:**\n\n| File Pattern | Technology | Linter Stack |\n|--------------|------------|--------------|\n| `package.json` + `tsconfig.json` | TypeScript\u002FReact | ESLint + Prettier |\n| `*.csproj` or `*.sln` | .NET | editorconfig + Roslyn |\n| `pyproject.toml` or `requirements.txt` | Python | Ruff |\n| Multiple detected | Mixed | Configure all detected |\n\n**Actions:**\n1. Glob for technology indicators\n2. Build technology list\n3. Log detected stack to user\n\n---\n\n## Phase 2: Existing Configuration Check\n\nBefore delegating, check what configurations already exist.\n\n**Config Files to Check:**\n\n| Technology | Config Files |\n|------------|--------------|\n| TypeScript | `eslint.config.*`, `.prettierrc*`, `tsconfig.json` |\n| .NET | `.editorconfig`, `Directory.Build.props` |\n| Python | `ruff.toml`, `pyproject.toml [tool.ruff]` |\n| Pre-commit | `.husky\u002F`, `.pre-commit-config.yaml` |\n| Tests | `vitest.config.*`, `pytest.ini`, `*.Tests.csproj` |\n\n**Decision Matrix:**\n\n| Existing Config | Action | Confirmation |\n|-----------------|--------|--------------|\n| None found | Create new | No |\n| Partial found | Merge (add missing) | Ask user |\n| Complete found | Skip | Inform user |\n| User requests replace | Backup + replace | Yes |\n\n---\n\n## Phase 3: Parallel Delegation\n\nInvoke workers for each quality aspect. Workers can run in parallel as they configure independent tools.\n\n**Delegation Order:**\n\n```\nln-740 (this)\n    |\n    +---> ln-741-linter-configurator\n    |         - ESLint\u002FPrettier (TypeScript)\n    |         - editorconfig\u002FRoslyn (.NET)\n    |         - Ruff (Python)\n    |\n    +---> ln-742-precommit-setup\n    |         - Husky + lint-staged (Node.js)\n    |         - pre-commit framework (Python)\n    |         - commitlint\n    |\n    +---> ln-743-test-infrastructure\n              - Vitest (TypeScript)\n              - xUnit (.NET)\n              - pytest (Python)\n```\n\nPass detected stack and existing configs to workers via direct Skill tool invocation.\n\n---\n\n## Phase 4: Verification\n\nAfter all workers complete, verify the quality pipeline works.\n\n**Verification Steps:**\n\n| Check | Command | Expected |\n|-------|---------|----------|\n| Lint runs | `npm run lint` \u002F `ruff check .` \u002F `dotnet format --verify-no-changes` | No errors |\n| Format runs | `npm run format:check` \u002F `ruff format --check` | No changes needed |\n| Tests run | `npm test` \u002F `pytest` \u002F `dotnet test` | Sample tests pass |\n| Hooks work | Create test commit | Hooks trigger |\n\n**On Failure:**\n1. Log specific failure\n2. Suggest fix or re-run specific worker\n3. Do NOT mark as complete until verification passes\n\n---\n\n## Critical Rules\n\n> **RULE 1:** Never overwrite existing user configurations without explicit confirmation.\n\n> **RULE 2:** Workers run AFTER stack detection - do not invoke workers without knowing the stack.\n\n> **RULE 3:** Verification phase is MANDATORY - quality setup is not complete until tools run successfully.\n\n> **RULE 4:** eslint-config-prettier is REQUIRED when both ESLint and Prettier are configured.\n\n---\n\n## Definition of Done\n\n- [ ] All detected technology stacks have appropriate quality tools\n- [ ] Existing configurations preserved or backed up\n- [ ] Lint command runs without errors\n- [ ] Format command runs without errors\n- [ ] Test command runs and sample tests pass\n- [ ] Pre-commit hooks trigger on test commit\n- [ ] User informed of all installed tools and commands\n\n---\n\n## Reference Files\n\n| File | Purpose |\n|------|---------|\n| [stack_detection.md](references\u002Fstack_detection.md) | Detailed detection rules |\n| [verification_checklist.md](references\u002Fverification_checklist.md) | Full verification checklist |\n\n---\n\n## Error Handling\n\n| Error | Cause | Resolution |\n|-------|-------|------------|\n| No stack detected | Empty project | Ask user for intended stack |\n| Worker failed | Missing dependencies | Install prerequisites, retry |\n| Verification failed | Config error | Check specific tool output, fix |\n| Hooks not working | Git not initialized | Run `git init` first |\n\n---\n\n**Version:** 2.0.0\n**Last Updated:** 2026-01-10\n",{"name":5,"license":15,"description":7},"main","fa638b97a18ff6d9f26cf0eaf3dfa123531bcc87","organized-skills\u002Fln-740-quality-setup",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":43,"prompt":53,"zipAvailable":54},[44,47,50],{"tool":45,"command":46},"npx","npx skills add levalencia\u002Fagent-god-mode --skill ln-740-quality-setup",{"tool":48,"command":49},"bunx","bunx skills add levalencia\u002Fagent-god-mode --skill ln-740-quality-setup",{"tool":51,"command":52},"pnpm","pnpm dlx skills add levalencia\u002Fagent-god-mode --skill ln-740-quality-setup","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Flevalencia\u002Fagent-god-mode\u002Fblob\u002Fmain\u002Forganized-skills\u002Fln-740-quality-setup\u002FSKILL.md",true,[56,62],{"path":57,"resourceType":58,"resourceTypeDesc":59,"sizeBytes":60,"sourceHtmlUrl":61},"references\u002Fstack_detection.md","REFERENCE","参考文档",2178,"https:\u002F\u002Fgithub.com\u002Flevalencia\u002Fagent-god-mode\u002Fblob\u002Fmain\u002Forganized-skills\u002Fln-740-quality-setup\u002Freferences\u002Fstack_detection.md",{"path":63,"resourceType":58,"resourceTypeDesc":59,"sizeBytes":64,"sourceHtmlUrl":65},"references\u002Fverification_checklist.md",3494,"https:\u002F\u002Fgithub.com\u002Flevalencia\u002Fagent-god-mode\u002Fblob\u002Fmain\u002Forganized-skills\u002Fln-740-quality-setup\u002Freferences\u002Fverification_checklist.md",[67,89,127,154,179,207],{"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":28},"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",[],[74,75,76,77,78,79,80,81,82,83,84,85,86,87,88],"python","zarr python","storage","integration","s3","gcs","cloud","dask","parallel","pipelines","arrays","numpy","scientific computing","scale","scientific",{"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":108,"publishedAt":28},"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",[95,100,103],{"categoryNo":96,"categoryName":97,"taxonomyType":98,"taxonomyTypeDesc":99},"01JBSEEDCAT000000000000010","后端与接口","SCENARIO","使用场景",{"categoryNo":101,"categoryName":102,"taxonomyType":98,"taxonomyTypeDesc":99},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":104,"categoryName":105,"taxonomyType":106,"taxonomyTypeDesc":107},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[91,74,109,110,111,112,113,114,115,116,117,118,119,120,121,122,123,124,125,126],"automation","window management","monitoring","data","templates","api","system","operations","use","maintenance","objects","permission","bulk operations","triggers","host","events","via","bulk",{"skillNo":128,"name":129,"nameZh":6,"description":130,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":131,"categories":132,"keywords":133,"publishedAt":28},"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",[],[134,135,136,137,138,139,140,141,142,143,144,145,146,147,148,149,150,151,152,153],"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":155,"name":156,"nameZh":6,"description":157,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":158,"categories":159,"keywords":160,"publishedAt":28},"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",[],[161,162,22,163,164,165,166,167,168,169,170,171,117,172,173,174,175,176,177,178],"oracle","what if oracle","planning","ux","futures","risk","analysis","explore","decision","branch","question","exploration","options","stress-test","strategies","trigger","case","multi",{"skillNo":180,"name":181,"nameZh":6,"description":182,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":183,"categories":184,"keywords":188,"publishedAt":28},"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",[185],{"categoryNo":186,"categoryName":187,"taxonomyType":98,"taxonomyTypeDesc":99},"01JBSEEDCAT000000000000009","前端开发",[189,190,191,192,193,194,195,196,197,198,199,200,201,112,202,203,204,205,206,122],"react","vercel react best practices","best practices","react best practices","vercel","writing","performance","components","react components","guidelines","tasks","code","Optimization","Next.js","refactoring","performance optimization","next","pages",{"skillNo":208,"name":209,"nameZh":6,"description":210,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":211,"categories":212,"keywords":223,"publishedAt":28},"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",[213,216,219,220],{"categoryNo":214,"categoryName":215,"taxonomyType":98,"taxonomyTypeDesc":99},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":217,"categoryName":218,"taxonomyType":98,"taxonomyTypeDesc":99},"01JBSEEDCAT000000000000021","资料检索与研究",{"categoryNo":101,"categoryName":102,"taxonomyType":98,"taxonomyTypeDesc":99},{"categoryNo":221,"categoryName":222,"taxonomyType":106,"taxonomyTypeDesc":107},"01JBSEEDCAT000000000000036","内容创作者",[113,224,225,198,226,227,228,229,230,231,232,145,233,234,235,236,237,238,88,239],"venue templates","research","NeurIPS","ICML","LaTeX","science","Bash","access","read","edit","proposals","Academic","requirements","formatting","journal","chi"]