[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6H7VR9P7ZP2BMG6ZMPDD6HT":3,"skill-same:01M6H7VR9P7ZP2BMG6ZMPDD6HT":79},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":38,"linkOnly":39,"markdownContent":40,"markdownBody":41,"frontMatter":42,"refName":48,"commitSha":49,"skillDirectory":50,"forksCount":51,"repositoryHtmlUrl":52,"repositoryHomepageUrl":6,"ownerHtmlUrl":53,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":54,"install":55,"resources":68},"01M6H7VR9P7ZP2BMG6ZMPDD6HT","lokalise-multi-env-setup",null,"Configure Lokalise across development, staging, and production environments.\nUse when setting up multi-environment deployments, configuring per-environment secrets,\nor implementing environment-specific Lokalise configurations.\nTrigger with phrases like \"lokalise environments\", \"lokalise staging\",\n\"lokalise dev prod\", \"lokalise environment setup\", \"lokalise config by env\".","micsapp\u002Fmicstec-skills","micsapp","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F82411001?v=4","01M6GWCFQ6D3PV8EHNY62NN5VW","01M6GWCFVE1PA5HG0DKC7AMFJ3",4,"MIT","https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills\u002Fblob\u002Fmaster\u002Fclaude-code\u002Fplugins-plus-skills\u002Fplugins\u002Fsaas-packs\u002Flokalise-pack\u002Fskills\u002Flokalise-multi-env-setup\u002FSKILL.md",[],[18,19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37],"setup","lokalise multi env setup","multi","env setup","env","implementing","gcloud","environment setup","trigger","io","across","deployments","up","use","environment","configure","Bash","dev","code","development","2026-11-10 10:12:30",false,"---\nname: lokalise-multi-env-setup\ndescription: |\n  Configure Lokalise across development, staging, and production environments.\n  Use when setting up multi-environment deployments, configuring per-environment secrets,\n  or implementing environment-specific Lokalise configurations.\n  Trigger with phrases like \"lokalise environments\", \"lokalise staging\",\n  \"lokalise dev prod\", \"lokalise environment setup\", \"lokalise config by env\".\nallowed-tools: Read, Write, Edit, Bash(aws:*), Bash(gcloud:*), Bash(vault:*)\nversion: 1.0.0\nlicense: MIT\nauthor: Jeremy Longshore \u003Cjeremy@intentsolutions.io>\ncompatible-with: claude-code, codex, openclaw\n---\n# Lokalise Multi Env Setup\n\n## Overview\nConfigure Lokalise across development, staging, and production environments with isolated API keys, environment-specific settings, and proper secret management. Each environment gets its own credentials and configuration to prevent cross-environment data leakage.\n\n## Prerequisites\n- Separate Lokalise API keys per environment\n- Secret management solution (environment variables, Vault, or cloud secrets)\n- CI\u002FCD pipeline with environment-aware deployment\n- Application with environment detection logic\n\n## Instructions\n1. **Environment Strategy**\n2. **Instructions**\n\nFor full implementation details, load: `Read(${CLAUDE_SKILL_DIR}\u002Freferences\u002Fimplementation-guide.md)`\n\n## Error Handling\n| Issue | Cause | Solution |\n|-------|-------|----------|\n| Wrong environment | Missing NODE_ENV | Set environment variable in deployment |\n| Secret not found | Wrong secret path | Verify secret manager configuration |\n| Cross-env data leak | Shared API key | Use separate keys per environment |\n| Config validation fail | Missing field | Add startup validation with Zod schema |\n\n## Examples\n### Quick Environment Check\n```typescript\nconst config = getLokaliseConfig();\nconsole.log(`Running in ${config.environment}`);\nconsole.log(`Cache enabled: ${config.cache.enabled}`);\n```\n\n### Startup Validation\n```typescript\nimport { z } from \"zod\";\n\nconst configSchema = z.object({\n  apiKey: z.string().min(1, \"LOKALISE_API_TOKEN is required\"),\n  environment: z.enum([\"development\", \"staging\", \"production\"]),\n  timeout: z.number().positive(),\n});\n\nconst config = configSchema.parse(getLokaliseConfig());\n```\n\n## Resources\n- [Lokalise API](https:\u002F\u002Fdevelopers.lokalise.com)\n- [12-Factor Config](https:\u002F\u002F12factor.net\u002Fconfig)\n\n## Next Steps\nFor deployment, see `lokalise-deploy-integration`.\n\n## Output\n\n- Configuration files or code changes applied to the project\n- Validation report confirming correct implementation\n- Summary of changes made and their rationale\n\nSee [deployment implementation details](${CLAUDE_SKILL_DIR}\u002Freferences\u002Fimplementation.md) for output format specifications.","# Lokalise Multi Env Setup\n\n## Overview\nConfigure Lokalise across development, staging, and production environments with isolated API keys, environment-specific settings, and proper secret management. Each environment gets its own credentials and configuration to prevent cross-environment data leakage.\n\n## Prerequisites\n- Separate Lokalise API keys per environment\n- Secret management solution (environment variables, Vault, or cloud secrets)\n- CI\u002FCD pipeline with environment-aware deployment\n- Application with environment detection logic\n\n## Instructions\n1. **Environment Strategy**\n2. **Instructions**\n\nFor full implementation details, load: `Read(${CLAUDE_SKILL_DIR}\u002Freferences\u002Fimplementation-guide.md)`\n\n## Error Handling\n| Issue | Cause | Solution |\n|-------|-------|----------|\n| Wrong environment | Missing NODE_ENV | Set environment variable in deployment |\n| Secret not found | Wrong secret path | Verify secret manager configuration |\n| Cross-env data leak | Shared API key | Use separate keys per environment |\n| Config validation fail | Missing field | Add startup validation with Zod schema |\n\n## Examples\n### Quick Environment Check\n```typescript\nconst config = getLokaliseConfig();\nconsole.log(`Running in ${config.environment}`);\nconsole.log(`Cache enabled: ${config.cache.enabled}`);\n```\n\n### Startup Validation\n```typescript\nimport { z } from \"zod\";\n\nconst configSchema = z.object({\n  apiKey: z.string().min(1, \"LOKALISE_API_TOKEN is required\"),\n  environment: z.enum([\"development\", \"staging\", \"production\"]),\n  timeout: z.number().positive(),\n});\n\nconst config = configSchema.parse(getLokaliseConfig());\n```\n\n## Resources\n- [Lokalise API](https:\u002F\u002Fdevelopers.lokalise.com)\n- [12-Factor Config](https:\u002F\u002F12factor.net\u002Fconfig)\n\n## Next Steps\nFor deployment, see `lokalise-deploy-integration`.\n\n## Output\n\n- Configuration files or code changes applied to the project\n- Validation report confirming correct implementation\n- Summary of changes made and their rationale\n\nSee [deployment implementation details](${CLAUDE_SKILL_DIR}\u002Freferences\u002Fimplementation.md) for output format specifications.",{"name":5,"author":43,"license":14,"version":44,"description":45,"allowed-tools":46,"compatible-with":47},"Jeremy Longshore \u003Cjeremy@intentsolutions.io>","1.0.0","Configure Lokalise across development, staging, and production environments.\nUse when setting up multi-environment deployments, configuring per-environment secrets,\nor implementing environment-specific Lokalise configurations.\nTrigger with phrases like \"lokalise environments\", \"lokalise staging\",\n\"lokalise dev prod\", \"lokalise environment setup\", \"lokalise config by env\".\n","Read, Write, Edit, Bash(aws:*), Bash(gcloud:*), Bash(vault:*)","claude-code, codex, openclaw","master","3f5d983eb4ef375b749adcd6b07ec03bd82ae8a8","claude-code\u002Fplugins-plus-skills\u002Fplugins\u002Fsaas-packs\u002Flokalise-pack\u002Fskills\u002Flokalise-multi-env-setup",0,"https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills","https:\u002F\u002Fgithub.com\u002Fmicsapp","2026-03-20 11:24:18",{"source":8,"skillName":5,"commands":56,"prompt":66,"zipAvailable":67},[57,60,63],{"tool":58,"command":59},"npx","npx skills add micsapp\u002Fmicstec-skills --skill lokalise-multi-env-setup",{"tool":61,"command":62},"bunx","bunx skills add micsapp\u002Fmicstec-skills --skill lokalise-multi-env-setup",{"tool":64,"command":65},"pnpm","pnpm dlx skills add micsapp\u002Fmicstec-skills --skill lokalise-multi-env-setup","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills\u002Fblob\u002Fmaster\u002Fclaude-code\u002Fplugins-plus-skills\u002Fplugins\u002Fsaas-packs\u002Flokalise-pack\u002Fskills\u002Flokalise-multi-env-setup\u002FSKILL.md",true,[69,75],{"path":70,"resourceType":71,"resourceTypeDesc":72,"sizeBytes":73,"sourceHtmlUrl":74},"references\u002Fimplementation-guide.md","REFERENCE","参考文档",3447,"https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills\u002Fblob\u002Fmaster\u002Fclaude-code\u002Fplugins-plus-skills\u002Fplugins\u002Fsaas-packs\u002Flokalise-pack\u002Fskills\u002Flokalise-multi-env-setup\u002Freferences\u002Fimplementation-guide.md",{"path":76,"resourceType":71,"resourceTypeDesc":72,"sizeBytes":77,"sourceHtmlUrl":78},"references\u002Fimplementation.md",6650,"https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills\u002Fblob\u002Fmaster\u002Fclaude-code\u002Fplugins-plus-skills\u002Fplugins\u002Fsaas-packs\u002Flokalise-pack\u002Fskills\u002Flokalise-multi-env-setup\u002Freferences\u002Fimplementation.md",[80,116,144,164,184,209],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":96,"publishedAt":38},"01M6HBTJ02FXBFG9NYEHHYAP52","azure-apim-architecture","Analyzes and explains Azure API Management architecture decisions for enterprise API marketplace implementations using VNet Internal mode, Front Door, hybrid authentication, and multi-environment strategies. Use when discussing APIM component selection, network topology, cost optimization, or comparing alternatives like workspaces vs instances, VNet Internal vs External mode, or Front Door vs Application Gateway.","https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills\u002Fblob\u002Fmaster\u002Fcopilot-cli\u002Fcopilot-agent-skills\u002F.github\u002Fskills\u002Fazure-apim-architecture\u002FSKILL.md",[86,91],{"categoryNo":87,"categoryName":88,"taxonomyType":89,"taxonomyTypeDesc":90},"01JBSEEDCAT000000000000010","后端与接口","SCENARIO","使用场景",{"categoryNo":92,"categoryName":93,"taxonomyType":94,"taxonomyTypeDesc":95},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[97,98,99,100,101,102,103,104,105,106,107,32,108,109,110,111,112,113,114,115],"architecture","azure","azure apim architecture","component","authentication","gateway","topology","Optimization","network","api","team","multi-environment","workspaces","instances","selection","strategies","azure api management","mode","for",{"skillNo":117,"name":118,"nameZh":6,"description":119,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":120,"categories":121,"keywords":130,"publishedAt":38},"01M6HBT7J4H082JEEA670B3EQ9","apiops-deployment","Guides deployment of Azure API Management infrastructure using Infrastructure as Code (Bicep\u002FTerraform), CI\u002FCD pipelines (GitHub Actions\u002FAzure DevOps), and APIOps workflows. Use when deploying APIM, creating pipelines, or implementing dev→test→prod promotion strategies.","https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills\u002Fblob\u002Fmaster\u002Fcopilot-cli\u002Fcopilot-agent-skills\u002F.github\u002Fskills\u002Fapiops-deployment\u002FSKILL.md",[122,123,126,129],{"categoryNo":87,"categoryName":88,"taxonomyType":89,"taxonomyTypeDesc":90},{"categoryNo":124,"categoryName":125,"taxonomyType":89,"taxonomyTypeDesc":90},"01JBSEEDCAT000000000000011","运维与部署",{"categoryNo":127,"categoryName":128,"taxonomyType":89,"taxonomyTypeDesc":90},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":92,"categoryName":93,"taxonomyType":94,"taxonomyTypeDesc":95},[131,132,133,134,98,135,36,136,137,138,139,140,106,107,112,141,142,113,143,23],"deployment","apiops deployment","workflows","azure devops","infrastructure","infrastructure as code","actions","ci","github actions","github-actions","as","guides","CI\u002FCD",{"skillNo":145,"name":146,"nameZh":6,"description":147,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":148,"categories":149,"keywords":151,"publishedAt":38},"01M6HBT2HEA23THNE9E00GYQBE","apim-policy-authoring","Creates production-ready Azure API Management policy XML for authentication (OAuth 2.0, JWT validation, subscription keys), rate limiting, CORS configuration, error handling, and API transformations. Use when implementing API security, access control, or request\u002Fresponse processing logic.","https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills\u002Fblob\u002Fmaster\u002Fcopilot-cli\u002Fcopilot-agent-skills\u002F.github\u002Fskills\u002Fapim-policy-authoring\u002FSKILL.md",[150],{"categoryNo":87,"categoryName":88,"taxonomyType":89,"taxonomyTypeDesc":90},[152,153,154,155,98,101,106,107,156,31,157,158,159,160,161,113,162,163,23,115],"policy","authoring","apim policy authoring","security","access","ready","api security","Access Control","error","processing","cors configuration","production-ready",{"skillNo":165,"name":166,"nameZh":6,"description":167,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":168,"categories":169,"keywords":172,"publishedAt":38},"01M6HBSY65SB29J9WE9KYD0K6T","api-security-review","Reviews Azure API Management configurations for security vulnerabilities, OWASP API Security Top 10 compliance, VNet Internal mode validation, Private Link verification, and Azure Security Benchmark alignment. Use when performing security audits, pre-deployment validation, or compliance reviews.","https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills\u002Fblob\u002Fmaster\u002Fcopilot-cli\u002Fcopilot-agent-skills\u002F.github\u002Fskills\u002Fapi-security-review\u002FSKILL.md",[170,171],{"categoryNo":87,"categoryName":88,"taxonomyType":89,"taxonomyTypeDesc":90},{"categoryNo":92,"categoryName":93,"taxonomyType":94,"taxonomyTypeDesc":95},[173,155,174,106,158,175,98,131,176,177,178,179,107,180,113,181,182,183,114,115],"review","security review","api security review","benchmark","verification","owasp","owasp-api","alignment","azure security","reviews","top",{"skillNo":185,"name":186,"nameZh":6,"description":187,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":188,"categories":189,"keywords":190,"publishedAt":38},"01M6HBSRW4PDFE6K4F8JYPZQ05","jira-cli","Interact with Jira from the command line to create, list, view, edit, and transition issues, manage sprints and epics, and perform common Jira workflows. Use when the user asks about Jira tasks, tickets, issues, sprints, or needs to manage project work items.","https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills\u002Fblob\u002Fmaster\u002Fcopilot-cli\u002Fawesome-copilot-agents\u002Fskills\u002Fjira-cli\u002FSKILL.md",[],[191,192,193,133,194,195,196,197,106,198,199,200,201,202,203,204,205,206,207,208],"cli","jira","jira cli","init","tasks","create","issues","common","work","command","edit","list","view","project","project work","token","line","sprints",{"skillNo":210,"name":211,"nameZh":6,"description":212,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":213,"categories":214,"keywords":215,"publishedAt":38},"01M6HBSNS3JHMW603G47TWE31H","calculator","Performs arbitrary-precision arithmetic calculations including addition, subtraction, multiplication, division, and exponents. Use when the user asks to calculate, compute, or evaluate math expressions, or when precise decimal arithmetic is needed to avoid floating-point errors.","https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills\u002Fblob\u002Fmaster\u002Fcopilot-cli\u002Fawesome-copilot-agents\u002Fskills\u002Fcalculator\u002FSKILL.md",[],[211,216,217,218,219,220,221,31,222,223],"npm","js","calculate","node","math","user","compute","errors"]