[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6EGBSG79PAS0MY9TK2ZZY6Z":3,"skill-same:01M6EGBSG79PAS0MY9TK2ZZY6Z":73},{"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":31,"linkOnly":32,"markdownContent":33,"markdownBody":34,"frontMatter":35,"refName":36,"commitSha":37,"skillDirectory":38,"forksCount":39,"repositoryHtmlUrl":40,"repositoryHomepageUrl":6,"ownerHtmlUrl":41,"ownerBlogUrl":42,"ownerDescription":43,"updatedAt":44,"install":45,"resources":58},"01M6EGBSG79PAS0MY9TK2ZZY6Z","ln-113-backend-docs-creator",null,"Creates 2 backend docs (api_spec.md, database_schema.md). Invoked when hasBackend or hasDatabase detected.","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-113-backend-docs-creator\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000010","后端与接口","SCENARIO","使用场景",[24,25,26,27,28,29,30],"docs","backend","ln 113 backend docs creator","spec","database","api","schema","2026-11-10 10:12:30",false,"---\nname: ln-113-backend-docs-creator\ndescription: Creates 2 backend docs (api_spec.md, database_schema.md). Invoked when hasBackend or hasDatabase detected.\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# Backend Documentation Creator\n\nL3 Worker that creates 2 backend documentation files. CONDITIONAL - only invoked when project has backend or database.\n\n## Purpose & Scope\n- Creates api_spec.md (if hasBackend)\n- Creates database_schema.md (if hasDatabase)\n- Receives Context Store from ln-110-project-docs-coordinator\n- OpenAPI 3.0 compliant API specification\n- ER diagrams in Mermaid for database schema\n- Never gathers context itself; uses coordinator input\n\n## Invocation (who\u002Fwhen)\n- **ln-110-project-docs-coordinator:** CONDITIONALLY invoked when:\n  - `hasBackend=true` (express, fastify, nestjs, fastapi detected)\n  - `hasDatabase=true` (pg, mongoose, prisma, sequelize detected)\n- Never called directly by users\n\n## Inputs\nFrom coordinator:\n- `contextStore`: Context Store with backend-specific data\n  - API_TYPE (REST, GraphQL, gRPC)\n  - API_ENDPOINTS (from route scan)\n  - AUTH_SCHEME (JWT, OAuth2, API keys)\n  - DATABASE_TYPE (PostgreSQL, MongoDB, MySQL)\n  - SCHEMA_OVERVIEW (from migrations\u002Fmodels)\n  - ER_DIAGRAM (generated from schema)\n- `targetDir`: Project root directory\n- `flags`: { hasBackend, hasDatabase }\n\n## Documents Created (2, conditional)\n\n| File | Condition | Questions | Auto-Discovery |\n|------|-----------|-----------|----------------|\n| docs\u002Fproject\u002Fapi_spec.md | hasBackend | Q39-Q40 | Medium |\n| docs\u002Fproject\u002Fdatabase_schema.md | hasDatabase | Q41-Q42 | High |\n\n## Workflow\n\n### Phase 1: Check Conditions\n1. Parse flags from coordinator\n2. If `!hasBackend && !hasDatabase`: return early with empty result\n3. Determine which documents to create\n\n### Phase 2: Create Documents\nFor each applicable document:\n1. Check if file exists (idempotent)\n2. If exists: skip with log\n3. If not exists:\n   - Copy template\n   - Replace placeholders with Context Store values\n   - Generate ER diagram for database_schema.md\n   - Mark `[TBD: X]` for missing data\n\n### Phase 3: Self-Validate\n1. Check SCOPE tag\n2. Validate format:\n   - api_spec.md: endpoint table, request\u002Fresponse examples\n   - database_schema.md: ER diagram, table definitions\n3. Check Maintenance section\n\n### Phase 4: Return Status\n```json\n{\n  \"created\": [\"docs\u002Fproject\u002Fapi_spec.md\"],\n  \"skipped\": [\"docs\u002Fproject\u002Fdatabase_schema.md\"],\n  \"tbd_count\": 2,\n  \"validation\": \"OK\"\n}\n```\n\n## Critical Notes\n- **Conditional:** Skip entirely if no backend\u002Fdatabase detected\n- **OpenAPI compliant:** api_spec.md follows OpenAPI 3.0 structure\n- **ER diagrams:** Generated in Mermaid erDiagram format\n- **Idempotent:** Never overwrite existing files\n\n### NO_CODE_EXAMPLES Rule (MANDATORY)\nAPI spec documents **contracts**, NOT implementations:\n- **ALLOWED in api_spec.md:** JSON request\u002Fresponse schemas (this IS the API contract), endpoint tables\n- **FORBIDDEN:** Controller implementations, validation classes, service code, middleware examples\n- **TEMPLATE RULE:** api_spec_template.md includes `\u003C!-- NO_CODE_EXAMPLES: ... -->` tag - FOLLOW IT\n\n### Stack Adaptation Rule (MANDATORY)\n- Links must reference stack-appropriate docs (Microsoft for .NET, MDN for JS)\n- API examples must match project stack (Express for Node.js, FastAPI for Python)\n\n### Format Priority (MANDATORY)\nTables (endpoints, schemas) > Mermaid (ER diagrams) > Lists > Text\n\n## Definition of Done\n- Conditions checked (hasBackend, hasDatabase)\n- Applicable documents created\n- ER diagram generated (if database_schema.md created)\n- Self-validation passed\n- **Actuality verified:** all document facts match current code (paths, functions, APIs, configs exist and are accurate)\n- Status returned to coordinator\n\n## Reference Files\n- Templates: `references\u002Ftemplates\u002Fapi_spec_template.md`, `database_schema_template.md`\n- Questions: `references\u002Fquestions_backend.md` (Q39-Q42)\n\n---\n**Version:** 1.2.0\n**Last Updated:** 2025-01-12\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# Backend Documentation Creator\n\nL3 Worker that creates 2 backend documentation files. CONDITIONAL - only invoked when project has backend or database.\n\n## Purpose & Scope\n- Creates api_spec.md (if hasBackend)\n- Creates database_schema.md (if hasDatabase)\n- Receives Context Store from ln-110-project-docs-coordinator\n- OpenAPI 3.0 compliant API specification\n- ER diagrams in Mermaid for database schema\n- Never gathers context itself; uses coordinator input\n\n## Invocation (who\u002Fwhen)\n- **ln-110-project-docs-coordinator:** CONDITIONALLY invoked when:\n  - `hasBackend=true` (express, fastify, nestjs, fastapi detected)\n  - `hasDatabase=true` (pg, mongoose, prisma, sequelize detected)\n- Never called directly by users\n\n## Inputs\nFrom coordinator:\n- `contextStore`: Context Store with backend-specific data\n  - API_TYPE (REST, GraphQL, gRPC)\n  - API_ENDPOINTS (from route scan)\n  - AUTH_SCHEME (JWT, OAuth2, API keys)\n  - DATABASE_TYPE (PostgreSQL, MongoDB, MySQL)\n  - SCHEMA_OVERVIEW (from migrations\u002Fmodels)\n  - ER_DIAGRAM (generated from schema)\n- `targetDir`: Project root directory\n- `flags`: { hasBackend, hasDatabase }\n\n## Documents Created (2, conditional)\n\n| File | Condition | Questions | Auto-Discovery |\n|------|-----------|-----------|----------------|\n| docs\u002Fproject\u002Fapi_spec.md | hasBackend | Q39-Q40 | Medium |\n| docs\u002Fproject\u002Fdatabase_schema.md | hasDatabase | Q41-Q42 | High |\n\n## Workflow\n\n### Phase 1: Check Conditions\n1. Parse flags from coordinator\n2. If `!hasBackend && !hasDatabase`: return early with empty result\n3. Determine which documents to create\n\n### Phase 2: Create Documents\nFor each applicable document:\n1. Check if file exists (idempotent)\n2. If exists: skip with log\n3. If not exists:\n   - Copy template\n   - Replace placeholders with Context Store values\n   - Generate ER diagram for database_schema.md\n   - Mark `[TBD: X]` for missing data\n\n### Phase 3: Self-Validate\n1. Check SCOPE tag\n2. Validate format:\n   - api_spec.md: endpoint table, request\u002Fresponse examples\n   - database_schema.md: ER diagram, table definitions\n3. Check Maintenance section\n\n### Phase 4: Return Status\n```json\n{\n  \"created\": [\"docs\u002Fproject\u002Fapi_spec.md\"],\n  \"skipped\": [\"docs\u002Fproject\u002Fdatabase_schema.md\"],\n  \"tbd_count\": 2,\n  \"validation\": \"OK\"\n}\n```\n\n## Critical Notes\n- **Conditional:** Skip entirely if no backend\u002Fdatabase detected\n- **OpenAPI compliant:** api_spec.md follows OpenAPI 3.0 structure\n- **ER diagrams:** Generated in Mermaid erDiagram format\n- **Idempotent:** Never overwrite existing files\n\n### NO_CODE_EXAMPLES Rule (MANDATORY)\nAPI spec documents **contracts**, NOT implementations:\n- **ALLOWED in api_spec.md:** JSON request\u002Fresponse schemas (this IS the API contract), endpoint tables\n- **FORBIDDEN:** Controller implementations, validation classes, service code, middleware examples\n- **TEMPLATE RULE:** api_spec_template.md includes `\u003C!-- NO_CODE_EXAMPLES: ... -->` tag - FOLLOW IT\n\n### Stack Adaptation Rule (MANDATORY)\n- Links must reference stack-appropriate docs (Microsoft for .NET, MDN for JS)\n- API examples must match project stack (Express for Node.js, FastAPI for Python)\n\n### Format Priority (MANDATORY)\nTables (endpoints, schemas) > Mermaid (ER diagrams) > Lists > Text\n\n## Definition of Done\n- Conditions checked (hasBackend, hasDatabase)\n- Applicable documents created\n- ER diagram generated (if database_schema.md created)\n- Self-validation passed\n- **Actuality verified:** all document facts match current code (paths, functions, APIs, configs exist and are accurate)\n- Status returned to coordinator\n\n## Reference Files\n- Templates: `references\u002Ftemplates\u002Fapi_spec_template.md`, `database_schema_template.md`\n- Questions: `references\u002Fquestions_backend.md` (Q39-Q42)\n\n---\n**Version:** 1.2.0\n**Last Updated:** 2025-01-12\n",{"name":5,"license":15,"description":7},"main","fa638b97a18ff6d9f26cf0eaf3dfa123531bcc87","organized-skills\u002Fln-113-backend-docs-creator",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":46,"prompt":56,"zipAvailable":57},[47,50,53],{"tool":48,"command":49},"npx","npx skills add levalencia\u002Fagent-god-mode --skill ln-113-backend-docs-creator",{"tool":51,"command":52},"bunx","bunx skills add levalencia\u002Fagent-god-mode --skill ln-113-backend-docs-creator",{"tool":54,"command":55},"pnpm","pnpm dlx skills add levalencia\u002Fagent-god-mode --skill ln-113-backend-docs-creator","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Flevalencia\u002Fagent-god-mode\u002Fblob\u002Fmain\u002Forganized-skills\u002Fln-113-backend-docs-creator\u002FSKILL.md",true,[59,65,69],{"path":60,"resourceType":61,"resourceTypeDesc":62,"sizeBytes":63,"sourceHtmlUrl":64},"references\u002Fquestions_backend.md","REFERENCE","参考文档",3635,"https:\u002F\u002Fgithub.com\u002Flevalencia\u002Fagent-god-mode\u002Fblob\u002Fmain\u002Forganized-skills\u002Fln-113-backend-docs-creator\u002Freferences\u002Fquestions_backend.md",{"path":66,"resourceType":61,"resourceTypeDesc":62,"sizeBytes":67,"sourceHtmlUrl":68},"references\u002Ftemplates\u002Fapi_spec_template.md",9924,"https:\u002F\u002Fgithub.com\u002Flevalencia\u002Fagent-god-mode\u002Fblob\u002Fmain\u002Forganized-skills\u002Fln-113-backend-docs-creator\u002Freferences\u002Ftemplates\u002Fapi_spec_template.md",{"path":70,"resourceType":61,"resourceTypeDesc":62,"sizeBytes":71,"sourceHtmlUrl":72},"references\u002Ftemplates\u002Fdatabase_schema_template.md",9657,"https:\u002F\u002Fgithub.com\u002Flevalencia\u002Fagent-god-mode\u002Fblob\u002Fmain\u002Forganized-skills\u002Fln-113-backend-docs-creator\u002Freferences\u002Ftemplates\u002Fdatabase_schema_template.md",[74,96,129,156,182,210],{"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":31},"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",[],[81,82,83,84,85,86,87,88,89,90,91,92,93,94,95],"python","zarr python","storage","integration","s3","gcs","cloud","dask","parallel","pipelines","arrays","numpy","scientific computing","scale","scientific",{"skillNo":97,"name":98,"nameZh":6,"description":99,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":100,"categories":101,"keywords":111,"publishedAt":31},"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",[102,103,106],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":104,"categoryName":105,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":107,"categoryName":108,"taxonomyType":109,"taxonomyTypeDesc":110},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[98,81,112,113,114,115,116,29,117,118,119,120,121,122,123,124,125,126,127,128],"automation","window management","monitoring","data","templates","system","operations","use","maintenance","objects","permission","bulk operations","triggers","host","events","via","bulk",{"skillNo":130,"name":131,"nameZh":6,"description":132,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":133,"categories":134,"keywords":135,"publishedAt":31},"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",[],[136,137,138,139,140,141,142,143,144,145,146,147,148,149,150,151,152,153,154,155],"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":157,"name":158,"nameZh":6,"description":159,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":160,"categories":161,"keywords":162,"publishedAt":31},"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",[],[163,164,165,166,167,168,169,170,171,172,173,174,119,175,176,177,178,179,180,181],"oracle","what if oracle","test","planning","ux","futures","risk","analysis","explore","decision","branch","question","exploration","options","stress-test","strategies","trigger","case","multi",{"skillNo":183,"name":184,"nameZh":6,"description":185,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":186,"categories":187,"keywords":191,"publishedAt":31},"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",[188],{"categoryNo":189,"categoryName":190,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000009","前端开发",[192,193,194,195,196,197,198,199,200,201,202,203,204,115,205,206,207,208,209,124],"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":211,"name":212,"nameZh":6,"description":213,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":214,"categories":215,"keywords":226,"publishedAt":31},"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",[216,219,222,223],{"categoryNo":217,"categoryName":218,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":220,"categoryName":221,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000021","资料检索与研究",{"categoryNo":104,"categoryName":105,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":224,"categoryName":225,"taxonomyType":109,"taxonomyTypeDesc":110},"01JBSEEDCAT000000000000036","内容创作者",[116,227,228,201,229,230,231,232,233,234,235,147,236,237,238,239,240,241,95,242],"venue templates","research","NeurIPS","ICML","LaTeX","science","Bash","access","read","edit","proposals","Academic","requirements","formatting","journal","chi"]