[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6H7SC9RKBKRRE5FCPSMN54Q":3,"skill-same:01M6H7SC9RKBKRRE5FCPSMN54Q":75},{"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},"01M6H7SC9RKBKRRE5FCPSMN54Q","linear-reference-architecture",null,"Production-grade Linear integration architecture patterns.\nUse when designing system architecture, planning integrations,\nor reviewing architectural decisions.\nTrigger with phrases like \"linear architecture\", \"linear system design\",\n\"linear integration patterns\", \"linear best practices architecture\".","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\u002Flinear-pack\u002Fskills\u002Flinear-reference-architecture\u002FSKILL.md",[],[18,19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37],"linear reference architecture","architecture","linear","reference","decisions","with","trigger","io","system design","use","write","read","design","integrations","system","integration","best practices","planning","code","codex","2026-11-10 10:12:30",false,"---\nname: linear-reference-architecture\ndescription: |\n  Production-grade Linear integration architecture patterns.\n  Use when designing system architecture, planning integrations,\n  or reviewing architectural decisions.\n  Trigger with phrases like \"linear architecture\", \"linear system design\",\n  \"linear integration patterns\", \"linear best practices architecture\".\nallowed-tools: Read, Write, Edit, Grep\nversion: 1.0.0\nlicense: MIT\nauthor: Jeremy Longshore \u003Cjeremy@intentsolutions.io>\ncompatible-with: claude-code, codex, openclaw\n---\n# Linear Reference Architecture\n\n## Contents\n- [Overview](#overview)\n- [Prerequisites](#prerequisites)\n- [Instructions](#instructions)\n- [Output](#output)\n- [Error Handling](#error-handling)\n- [Examples](#examples)\n- [Resources](#resources)\n\n## Overview\nProduction-grade architectural patterns for Linear integrations. Covers simple, service-oriented, event-driven, and CQRS architectures.\n\n## Prerequisites\n- Understanding of distributed systems\n- Experience with cloud infrastructure\n- Familiarity with event-driven architecture\n\n## Instructions\n\n### Step 1: Choose Architecture Pattern\n| Pattern | Best For | Complexity |\n|---------|----------|------------|\n| Simple Integration | Small teams, single app | Low |\n| Service-Oriented | Medium teams, multiple apps | Medium |\n| Event-Driven | Large teams, real-time needs | High |\n| CQRS + Event Sourcing | Complex domains, audit needs | Very High |\n\n### Step 2: Implement Core Components\n1. **Linear Gateway** - Centralized API access with rate limiting and caching\n2. **Webhook Ingester** - Receive and validate Linear webhook events\n3. **Event Processor** - Apply business logic to incoming events\n4. **State Store** - Persist synchronized data locally\n\n### Step 3: Configure Infrastructure\n- Set up caching layer (Redis for multi-service, in-memory for simple)\n- Configure rate limiting (stay under 1500 req\u002Fmin Linear limit)\n- Deploy webhook endpoint with signature verification\n- Set up monitoring and health checks\n\nSee [detailed implementation](${CLAUDE_SKILL_DIR}\u002Freferences\u002Fimplementation.md) for full code examples of all four architecture patterns plus project structure.\n\n## Output\n- Architecture pattern selected and justified\n- Core infrastructure components configured\n- Rate limiting and caching in place\n- Webhook handling operational\n\n## Error Handling\n| Error | Cause | Solution |\n|-------|-------|----------|\n| Rate limit exceeded | Too many API calls | Implement gateway with rate limiter |\n| Stale cache | TTL too long | Invalidate on webhook events |\n| Event loss | Webhook failures | Use message queue with retries |\n| Schema drift | API version changes | Pin SDK version, test upgrades |\n\n## Examples\n\n### Quick Start: Simple Integration\n```typescript\nimport { LinearClient } from \"@linear\u002Fsdk\";\n\nconst client = new LinearClient({ apiKey: process.env.LINEAR_API_KEY! });\nconst teams = await client.teams();\nconsole.log(teams.nodes.map(t => t.name));\n```\n\n## Resources\n- [Linear API Best Practices](https:\u002F\u002Fdevelopers.linear.app\u002Fdocs\u002Fgraphql\u002Fbest-practices)\n- [Event-Driven Architecture](https:\u002F\u002Fmartinfowler.com\u002Farticles\u002F201701-event-driven.html)\n- [CQRS Pattern](https:\u002F\u002Fmartinfowler.com\u002Fbliki\u002FCQRS.html)\n\n## Next Steps\nConfigure multi-environment setup with `linear-multi-env-setup`.","# Linear Reference Architecture\n\n## Contents\n- [Overview](#overview)\n- [Prerequisites](#prerequisites)\n- [Instructions](#instructions)\n- [Output](#output)\n- [Error Handling](#error-handling)\n- [Examples](#examples)\n- [Resources](#resources)\n\n## Overview\nProduction-grade architectural patterns for Linear integrations. Covers simple, service-oriented, event-driven, and CQRS architectures.\n\n## Prerequisites\n- Understanding of distributed systems\n- Experience with cloud infrastructure\n- Familiarity with event-driven architecture\n\n## Instructions\n\n### Step 1: Choose Architecture Pattern\n| Pattern | Best For | Complexity |\n|---------|----------|------------|\n| Simple Integration | Small teams, single app | Low |\n| Service-Oriented | Medium teams, multiple apps | Medium |\n| Event-Driven | Large teams, real-time needs | High |\n| CQRS + Event Sourcing | Complex domains, audit needs | Very High |\n\n### Step 2: Implement Core Components\n1. **Linear Gateway** - Centralized API access with rate limiting and caching\n2. **Webhook Ingester** - Receive and validate Linear webhook events\n3. **Event Processor** - Apply business logic to incoming events\n4. **State Store** - Persist synchronized data locally\n\n### Step 3: Configure Infrastructure\n- Set up caching layer (Redis for multi-service, in-memory for simple)\n- Configure rate limiting (stay under 1500 req\u002Fmin Linear limit)\n- Deploy webhook endpoint with signature verification\n- Set up monitoring and health checks\n\nSee [detailed implementation](${CLAUDE_SKILL_DIR}\u002Freferences\u002Fimplementation.md) for full code examples of all four architecture patterns plus project structure.\n\n## Output\n- Architecture pattern selected and justified\n- Core infrastructure components configured\n- Rate limiting and caching in place\n- Webhook handling operational\n\n## Error Handling\n| Error | Cause | Solution |\n|-------|-------|----------|\n| Rate limit exceeded | Too many API calls | Implement gateway with rate limiter |\n| Stale cache | TTL too long | Invalidate on webhook events |\n| Event loss | Webhook failures | Use message queue with retries |\n| Schema drift | API version changes | Pin SDK version, test upgrades |\n\n## Examples\n\n### Quick Start: Simple Integration\n```typescript\nimport { LinearClient } from \"@linear\u002Fsdk\";\n\nconst client = new LinearClient({ apiKey: process.env.LINEAR_API_KEY! });\nconst teams = await client.teams();\nconsole.log(teams.nodes.map(t => t.name));\n```\n\n## Resources\n- [Linear API Best Practices](https:\u002F\u002Fdevelopers.linear.app\u002Fdocs\u002Fgraphql\u002Fbest-practices)\n- [Event-Driven Architecture](https:\u002F\u002Fmartinfowler.com\u002Farticles\u002F201701-event-driven.html)\n- [CQRS Pattern](https:\u002F\u002Fmartinfowler.com\u002Fbliki\u002FCQRS.html)\n\n## Next Steps\nConfigure multi-environment setup with `linear-multi-env-setup`.",{"name":5,"author":43,"license":14,"version":44,"description":45,"allowed-tools":46,"compatible-with":47},"Jeremy Longshore \u003Cjeremy@intentsolutions.io>","1.0.0","Production-grade Linear integration architecture patterns.\nUse when designing system architecture, planning integrations,\nor reviewing architectural decisions.\nTrigger with phrases like \"linear architecture\", \"linear system design\",\n\"linear integration patterns\", \"linear best practices architecture\".\n","Read, Write, Edit, Grep","claude-code, codex, openclaw","master","3f5d983eb4ef375b749adcd6b07ec03bd82ae8a8","claude-code\u002Fplugins-plus-skills\u002Fplugins\u002Fsaas-packs\u002Flinear-pack\u002Fskills\u002Flinear-reference-architecture",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 linear-reference-architecture",{"tool":61,"command":62},"bunx","bunx skills add micsapp\u002Fmicstec-skills --skill linear-reference-architecture",{"tool":64,"command":65},"pnpm","pnpm dlx skills add micsapp\u002Fmicstec-skills --skill linear-reference-architecture","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills\u002Fblob\u002Fmaster\u002Fclaude-code\u002Fplugins-plus-skills\u002Fplugins\u002Fsaas-packs\u002Flinear-pack\u002Fskills\u002Flinear-reference-architecture\u002FSKILL.md",true,[69],{"path":70,"resourceType":71,"resourceTypeDesc":72,"sizeBytes":73,"sourceHtmlUrl":74},"references\u002Fimplementation.md","REFERENCE","参考文档",10623,"https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills\u002Fblob\u002Fmaster\u002Fclaude-code\u002Fplugins-plus-skills\u002Fplugins\u002Fsaas-packs\u002Flinear-pack\u002Fskills\u002Flinear-reference-architecture\u002Freferences\u002Fimplementation.md",[76,112,141,161,181,206],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":92,"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",[82,87],{"categoryNo":83,"categoryName":84,"taxonomyType":85,"taxonomyTypeDesc":86},"01JBSEEDCAT000000000000010","后端与接口","SCENARIO","使用场景",{"categoryNo":88,"categoryName":89,"taxonomyType":90,"taxonomyTypeDesc":91},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[19,93,94,95,96,97,98,99,100,101,102,103,104,105,106,107,108,109,110,111],"azure","azure apim architecture","component","authentication","gateway","topology","Optimization","network","api","team","environment","multi-environment","workspaces","instances","selection","strategies","azure api management","mode","for",{"skillNo":113,"name":114,"nameZh":6,"description":115,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":116,"categories":117,"keywords":126,"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",[118,119,122,125],{"categoryNo":83,"categoryName":84,"taxonomyType":85,"taxonomyTypeDesc":86},{"categoryNo":120,"categoryName":121,"taxonomyType":85,"taxonomyTypeDesc":86},"01JBSEEDCAT000000000000011","运维与部署",{"categoryNo":123,"categoryName":124,"taxonomyType":85,"taxonomyTypeDesc":86},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":88,"categoryName":89,"taxonomyType":90,"taxonomyTypeDesc":91},[127,128,129,130,93,131,36,132,133,134,135,136,101,102,108,137,138,109,139,140],"deployment","apiops deployment","workflows","azure devops","infrastructure","infrastructure as code","actions","ci","github actions","github-actions","as","guides","CI\u002FCD","implementing",{"skillNo":142,"name":143,"nameZh":6,"description":144,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":145,"categories":146,"keywords":148,"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",[147],{"categoryNo":83,"categoryName":84,"taxonomyType":85,"taxonomyTypeDesc":86},[149,150,151,152,93,96,101,102,153,27,154,155,156,157,158,109,159,160,140,111],"policy","authoring","apim policy authoring","security","access","ready","api security","Access Control","error","processing","cors configuration","production-ready",{"skillNo":162,"name":163,"nameZh":6,"description":164,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":165,"categories":166,"keywords":169,"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",[167,168],{"categoryNo":83,"categoryName":84,"taxonomyType":85,"taxonomyTypeDesc":86},{"categoryNo":88,"categoryName":89,"taxonomyType":90,"taxonomyTypeDesc":91},[170,152,171,101,155,172,93,127,173,174,175,176,102,177,109,178,179,180,110,111],"review","security review","api security review","benchmark","verification","owasp","owasp-api","alignment","azure security","reviews","top",{"skillNo":182,"name":183,"nameZh":6,"description":184,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":185,"categories":186,"keywords":187,"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",[],[188,189,190,129,191,192,193,194,101,195,196,197,198,199,200,201,202,203,204,205],"cli","jira","jira cli","init","tasks","create","issues","common","work","command","edit","list","view","project","project work","token","line","sprints",{"skillNo":207,"name":208,"nameZh":6,"description":209,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":210,"categories":211,"keywords":212,"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",[],[208,213,214,215,216,217,218,27,219,220],"npm","js","calculate","node","math","user","compute","errors"]