[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6MEZAWTT87SXM6H284RFQY8":3,"skill-same:01M6MEZAWTT87SXM6H284RFQY8":72},{"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":39,"linkOnly":40,"markdownContent":41,"markdownBody":42,"frontMatter":43,"refName":51,"commitSha":52,"skillDirectory":53,"forksCount":54,"repositoryHtmlUrl":55,"repositoryHomepageUrl":6,"ownerHtmlUrl":56,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":57,"install":58,"resources":71},"01M6MEZAWTT87SXM6H284RFQY8","one-three-one-rule",null,"Structured decision-making framework for technical proposals and trade-off analysis. When the user faces a choice between multiple approaches (architecture decisions, tool selection, refactoring strategies, migration paths), this skill produces a 1-3-1 format: one clear problem statement, three distinct options with pros\u002Fcons, and one concrete recommendation with definition of done and implementation plan. Use when the user asks for a \"1-3-1\", says \"give me options\", or needs help choosing between competing approaches.","ibragimov-oasis\u002Fvibe-coder","ibragimov-oasis","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F240665573?v=4","01M6DF78Y45R8228FHAZ7G6JXM","IBRAGIMOV MUKHAMMADJON","01M6K5ZYR8TDPAFG4R6693E2A6",3,"MIT","https:\u002F\u002Fgithub.com\u002Fibragimov-oasis\u002Fvibe-coder\u002Fblob\u002Fmain\u002Fvc-kit\u002Fcontent\u002FCOMBINED\u002FCOMBINED\u002FREPO_DOCS\u002F02-hermes-agent\u002Foptional-skills\u002Fcommunication\u002Fone-three-one-rule\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38],"rule","three","one three one rule","decision-making","implementation plan","definition","trade-offs","for","problem statement","recommendation","problem","definition of done","done","selection","use","proposals","technical","choice","decision","tool","2026-11-10 10:12:30",false,"---\nname: one-three-one-rule\ndescription: >\n  Structured decision-making framework for technical proposals and trade-off analysis.\n  When the user faces a choice between multiple approaches (architecture decisions,\n  tool selection, refactoring strategies, migration paths), this skill produces a\n  1-3-1 format: one clear problem statement, three distinct options with pros\u002Fcons,\n  and one concrete recommendation with definition of done and implementation plan.\n  Use when the user asks for a \"1-3-1\", says \"give me options\", or needs help\n  choosing between competing approaches.\nversion: 1.0.0\nauthor: Willard Moore\nlicense: MIT\ncategory: communication\nmetadata:\n  hermes:\n    tags: [communication, decision-making, proposals, trade-offs]\n---\n\n# 1-3-1 Communication Rule\n\nStructured decision-making format for when a task has multiple viable approaches and the user needs a clear recommendation. Produces a concise problem framing, three options with trade-offs, and an actionable plan for the recommended path.\n\n## When to Use\n\n- The user explicitly asks for a \"1-3-1\" response.\n- The user says \"give me options\" or \"what are my choices\" for a technical decision.\n- A task has multiple viable approaches with meaningful trade-offs (architecture, tooling, migration strategy).\n- The user needs a proposal they can forward to a team or stakeholder.\n\nDo NOT use for simple questions with one obvious answer, debugging sessions, or tasks where the user has already decided on an approach.\n\n## Procedure\n\n1. **Problem** (one sentence)\n   - State the core decision or desired outcome in a single concise sentence.\n   - Focus on the *what*, not the *how* — no implementation details, tool names, or specific technologies.\n   - Keep it tight. If you need \"and\", you're describing two problems.\n\n2. **Options** (exactly three)\n   - Present three distinct, viable approaches labeled A, B, C.\n   - Each option gets a brief description, pros, and cons.\n   - Options should represent genuinely different strategies, not minor variations of the same approach.\n\n3. **Recommendation** (one option)\n   - State which option you recommend and why, based on the user's context and priorities.\n   - Be direct — this is your professional judgment, not a hedge.\n\n4. **Definition of Done**\n   - List the specific success criteria for the recommended option.\n   - These are concrete, verifiable outcomes — not vague aspirations.\n   - If the user picks a different option, revise this section to match.\n\n5. **Implementation Plan**\n   - Concrete steps to execute the recommended option.\n   - Include specific commands, tools, or actions where applicable.\n   - If the user picks a different option, revise this section to match.\n\n## Verification\n\n- Response has exactly one Problem sentence.\n- Response has exactly three Options (A, B, C) with pros and cons for each.\n- Response has a single Recommendation that picks one option with reasoning.\n- Definition of Done and Implementation Plan align with the recommended option.\n- If the user selects a different option, Recommendation, DoD, and Implementation Plan update accordingly.\n\n## Example\n\nUser: \"Give me a 1-3-1 for adding retry logic to our API client.\"\n\nAgent:\n\n**Problem:** API calls to external services fail intermittently under load and need graceful retry handling.\n\n**Options:**\n\n- **Option A: Exponential backoff with jitter in a shared utility.**\n  Pros: Simple, well-understood pattern; single implementation shared across all callers.\n  Cons: No circuit-breaking; callers still block during retries.\n\n- **Option B: Retry library (tenacity) as a decorator on each endpoint call.**\n  Pros: Configurable per-endpoint; built-in support for circuit breakers and rate limits.\n  Cons: Adds a dependency; decorator pattern can obscure control flow.\n\n- **Option C: Queue-based async retry with dead letter handling.**\n  Pros: Non-blocking; failed calls are tracked and replayable; scales well.\n  Cons: Significant complexity increase; requires a queue backend; overkill for low-volume services.\n\n**Recommendation:** Option A. The call volume doesn't justify queue infrastructure, and a shared utility with exponential backoff + jitter covers the failure mode cleanly without new dependencies.\n\n**Definition of Done:**\n- `api_retry()` utility handles transient HTTP errors (429, 502, 503, 504).\n- Retries up to 3 times with exponential backoff and jitter.\n- All external API calls route through the retry utility.\n- Logs each retry attempt with endpoint and attempt number.\n- Tests cover retry exhaustion, immediate success, and transient-then-success scenarios.\n\n**Implementation Plan:**\n1. Create `utils\u002Fapi_retry.py` with configurable max retries, base delay, and retryable status codes.\n2. Add jitter using `random.uniform(0, base_delay)` to prevent thundering herd.\n3. Wrap existing API calls in `api_client.py` with the retry utility.\n4. Add unit tests mocking HTTP responses for each retry scenario.\n5. Verify under load with a simple stress test against a flaky endpoint mock.\n\n## ? Связи\n\n- [[000 - Map of Maps]] — REPO_DOCS\n- [[000 - Map of Maps]] — Map of Maps\n\n","# 1-3-1 Communication Rule\n\nStructured decision-making format for when a task has multiple viable approaches and the user needs a clear recommendation. Produces a concise problem framing, three options with trade-offs, and an actionable plan for the recommended path.\n\n## When to Use\n\n- The user explicitly asks for a \"1-3-1\" response.\n- The user says \"give me options\" or \"what are my choices\" for a technical decision.\n- A task has multiple viable approaches with meaningful trade-offs (architecture, tooling, migration strategy).\n- The user needs a proposal they can forward to a team or stakeholder.\n\nDo NOT use for simple questions with one obvious answer, debugging sessions, or tasks where the user has already decided on an approach.\n\n## Procedure\n\n1. **Problem** (one sentence)\n   - State the core decision or desired outcome in a single concise sentence.\n   - Focus on the *what*, not the *how* — no implementation details, tool names, or specific technologies.\n   - Keep it tight. If you need \"and\", you're describing two problems.\n\n2. **Options** (exactly three)\n   - Present three distinct, viable approaches labeled A, B, C.\n   - Each option gets a brief description, pros, and cons.\n   - Options should represent genuinely different strategies, not minor variations of the same approach.\n\n3. **Recommendation** (one option)\n   - State which option you recommend and why, based on the user's context and priorities.\n   - Be direct — this is your professional judgment, not a hedge.\n\n4. **Definition of Done**\n   - List the specific success criteria for the recommended option.\n   - These are concrete, verifiable outcomes — not vague aspirations.\n   - If the user picks a different option, revise this section to match.\n\n5. **Implementation Plan**\n   - Concrete steps to execute the recommended option.\n   - Include specific commands, tools, or actions where applicable.\n   - If the user picks a different option, revise this section to match.\n\n## Verification\n\n- Response has exactly one Problem sentence.\n- Response has exactly three Options (A, B, C) with pros and cons for each.\n- Response has a single Recommendation that picks one option with reasoning.\n- Definition of Done and Implementation Plan align with the recommended option.\n- If the user selects a different option, Recommendation, DoD, and Implementation Plan update accordingly.\n\n## Example\n\nUser: \"Give me a 1-3-1 for adding retry logic to our API client.\"\n\nAgent:\n\n**Problem:** API calls to external services fail intermittently under load and need graceful retry handling.\n\n**Options:**\n\n- **Option A: Exponential backoff with jitter in a shared utility.**\n  Pros: Simple, well-understood pattern; single implementation shared across all callers.\n  Cons: No circuit-breaking; callers still block during retries.\n\n- **Option B: Retry library (tenacity) as a decorator on each endpoint call.**\n  Pros: Configurable per-endpoint; built-in support for circuit breakers and rate limits.\n  Cons: Adds a dependency; decorator pattern can obscure control flow.\n\n- **Option C: Queue-based async retry with dead letter handling.**\n  Pros: Non-blocking; failed calls are tracked and replayable; scales well.\n  Cons: Significant complexity increase; requires a queue backend; overkill for low-volume services.\n\n**Recommendation:** Option A. The call volume doesn't justify queue infrastructure, and a shared utility with exponential backoff + jitter covers the failure mode cleanly without new dependencies.\n\n**Definition of Done:**\n- `api_retry()` utility handles transient HTTP errors (429, 502, 503, 504).\n- Retries up to 3 times with exponential backoff and jitter.\n- All external API calls route through the retry utility.\n- Logs each retry attempt with endpoint and attempt number.\n- Tests cover retry exhaustion, immediate success, and transient-then-success scenarios.\n\n**Implementation Plan:**\n1. Create `utils\u002Fapi_retry.py` with configurable max retries, base delay, and retryable status codes.\n2. Add jitter using `random.uniform(0, base_delay)` to prevent thundering herd.\n3. Wrap existing API calls in `api_client.py` with the retry utility.\n4. Add unit tests mocking HTTP responses for each retry scenario.\n5. Verify under load with a simple stress test against a flaky endpoint mock.\n\n## ? Связи\n\n- [[000 - Map of Maps]] — REPO_DOCS\n- [[000 - Map of Maps]] — Map of Maps\n\n",{"name":5,"author":44,"license":15,"version":45,"category":46,"metadata":47,"description":50},"Willard Moore","1.0.0","communication",{"hermes":48},{"tags":49},[46,22,34,25],"Structured decision-making framework for technical proposals and trade-off analysis. When the user faces a choice between multiple approaches (architecture decisions, tool selection, refactoring strategies, migration paths), this skill produces a 1-3-1 format: one clear problem statement, three distinct options with pros\u002Fcons, and one concrete recommendation with definition of done and implementation plan. Use when the user asks for a \"1-3-1\", says \"give me options\", or needs help choosing between competing approaches.\n","main","bdd9f958d7bb1a0f19b8ad8da020b0bab0f53eb1","vc-kit\u002Fcontent\u002FCOMBINED\u002FCOMBINED\u002FREPO_DOCS\u002F02-hermes-agent\u002Foptional-skills\u002Fcommunication\u002Fone-three-one-rule",1,"https:\u002F\u002Fgithub.com\u002Fibragimov-oasis\u002Fvibe-coder","https:\u002F\u002Fgithub.com\u002Fibragimov-oasis","2026-06-24 16:31:18",{"source":8,"skillName":5,"commands":59,"prompt":69,"zipAvailable":70},[60,63,66],{"tool":61,"command":62},"npx","npx skills add ibragimov-oasis\u002Fvibe-coder --skill one-three-one-rule",{"tool":64,"command":65},"bunx","bunx skills add ibragimov-oasis\u002Fvibe-coder --skill one-three-one-rule",{"tool":67,"command":68},"pnpm","pnpm dlx skills add ibragimov-oasis\u002Fvibe-coder --skill one-three-one-rule","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fibragimov-oasis\u002Fvibe-coder\u002Fblob\u002Fmain\u002Fvc-kit\u002Fcontent\u002FCOMBINED\u002FCOMBINED\u002FREPO_DOCS\u002F02-hermes-agent\u002Foptional-skills\u002Fcommunication\u002Fone-three-one-rule\u002FSKILL.md",true,[],[73,110,137,157,183,214],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":89,"publishedAt":39},"01M6Q4Q22KKKVMJJYA411DQ4ER","ckm:ui-styling","Create beautiful, accessible user interfaces with shadcn\u002Fui components (built on Radix UI + Tailwind), Tailwind CSS utility-first styling, and canvas-based visual designs. Use when building user interfaces, implementing design systems, creating responsive layouts, adding accessible components (dialogs, dropdowns, forms, tables), customizing themes and colors, implementing dark mode, generating visual designs and posters, or establishing consistent styling patterns across applications.","https:\u002F\u002Fgithub.com\u002Fibragimov-oasis\u002Fvibe-coder\u002Fblob\u002Fmain\u002Fvc-kit\u002Fcontent\u002FCOMBINED\u002FCOMBINED\u002Fui-design\u002Fui-rules\u002Fui-ux-pro-max\u002Fclaude\u002Fskills\u002Fui-styling\u002FSKILL.md",[79,84],{"categoryNo":80,"categoryName":81,"taxonomyType":82,"taxonomyTypeDesc":83},"01JBSEEDCAT000000000000015","视觉设计","SCENARIO","使用场景",{"categoryNo":85,"categoryName":86,"taxonomyType":87,"taxonomyTypeDesc":88},"01JBSEEDCAT000000000000032","设计师","PROFESSION","适用职业",[90,91,92,93,94,95,96,97,98,99,100,101,102,103,104,105,106,107,108,109],"ui styling","ui","styling","ckm:ui styling","ckm","design","css","canvas","components","component","create","design systems","Tailwind","across","themes","utility","mode","implementing","artifact\u002Fui-component","source\u002Fui-design",{"skillNo":111,"name":112,"nameZh":6,"description":113,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":114,"categories":115,"keywords":124,"publishedAt":39},"01M6Q4PQ2NX4NDVWTEHA3MQ2R0","ckm:design","Comprehensive design skill: brand identity, design tokens, UI styling, logo generation (55 styles, Gemini AI), corporate identity program (50 deliverables, CIP mockups), HTML presentations (Chart.js), banner design (22 styles, social\u002Fads\u002Fweb\u002Fprint), icon design (15 styles, SVG, Gemini 3.1 Pro), social photos (HTML→screenshot, multi-platform). Actions: design logo, create CIP, generate mockups, build slides, design banner, generate icon, create social photos, social media images, brand identity, design system. Platforms: Facebook, Twitter, LinkedIn, YouTube, Instagram, Pinterest, TikTok, Threads, Google Ads.","https:\u002F\u002Fgithub.com\u002Fibragimov-oasis\u002Fvibe-coder\u002Fblob\u002Fmain\u002Fvc-kit\u002Fcontent\u002FCOMBINED\u002FCOMBINED\u002Fui-design\u002Fui-rules\u002Fui-ux-pro-max\u002Fclaude\u002Fskills\u002Fdesign\u002FSKILL.md",[116,119,120,123],{"categoryNo":117,"categoryName":118,"taxonomyType":82,"taxonomyTypeDesc":83},"01JBSEEDCAT000000000000003","演示文稿",{"categoryNo":80,"categoryName":81,"taxonomyType":82,"taxonomyTypeDesc":83},{"categoryNo":121,"categoryName":122,"taxonomyType":82,"taxonomyTypeDesc":83},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":85,"categoryName":86,"taxonomyType":87,"taxonomyTypeDesc":88},[95,112,94,125,99,90,126,100,127,128,129,130,131,132,133,134,135,136,108,109],"google","presentations","generate","screenshot","actions","Media","logo","ads","youtube","tiktok","artifact","chart",{"skillNo":138,"name":139,"nameZh":6,"description":140,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":141,"categories":142,"keywords":145,"publishedAt":39},"01M6Q4PJE27GEA3M0CECEBCZKS","ckm:design-system","Token architecture, component specifications, and slide generation. Three-layer tokens (primitive→semantic→component), CSS variables, spacing\u002Ftypography scales, component specs, strategic slide creation. Use for design tokens, systematic design, brand-compliant presentations.","https:\u002F\u002Fgithub.com\u002Fibragimov-oasis\u002Fvibe-coder\u002Fblob\u002Fmain\u002Fvc-kit\u002Fcontent\u002FCOMBINED\u002FCOMBINED\u002Fui-design\u002Fui-rules\u002Fui-ux-pro-max\u002Fclaude\u002Fskills\u002Fdesign-system\u002FSKILL.md",[143,144],{"categoryNo":80,"categoryName":81,"taxonomyType":82,"taxonomyTypeDesc":83},{"categoryNo":85,"categoryName":86,"taxonomyType":87,"taxonomyTypeDesc":88},[95,146,147,148,112,94,96,99,149,126,135,150,151,152,153,154,155,156,108,109],"design system","system","ckm:design system","architecture","token","creation","systematic","css variables","Variables","spacing","layer",{"skillNo":158,"name":159,"nameZh":6,"description":160,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":161,"categories":162,"keywords":168,"publishedAt":39},"01M6Q4P90JXFYMH2S634QM6SQJ","ckm:banner-design","Design banners for social media, ads, website heroes, creative assets, and print. Multiple art direction options with AI-generated visuals. Actions: design, create, generate banner. Platforms: Facebook, Twitter\u002FX, LinkedIn, YouTube, Instagram, Google Display, website hero, print. Styles: minimalist, gradient, bold typography, photo-based, illustrated, geometric, retro, glassmorphism, 3D, neon, duotone, editorial, collage. Uses ui-ux-pro-max, frontend-design, ai-artist, ai-multimodal skills.","https:\u002F\u002Fgithub.com\u002Fibragimov-oasis\u002Fvibe-coder\u002Fblob\u002Fmain\u002Fvc-kit\u002Fcontent\u002FCOMBINED\u002FCOMBINED\u002Fui-design\u002Fui-rules\u002Fui-ux-pro-max\u002Fclaude\u002Fskills\u002Fbanner-design\u002FSKILL.md",[163,166,167],{"categoryNo":164,"categoryName":165,"taxonomyType":82,"taxonomyTypeDesc":83},"01JBSEEDCAT000000000000009","前端开发",{"categoryNo":80,"categoryName":81,"taxonomyType":82,"taxonomyTypeDesc":83},{"categoryNo":85,"categoryName":86,"taxonomyType":87,"taxonomyTypeDesc":88},[95,169,170,171,94,172,129,130,173,174,175,176,177,178,179,180,108,109,181,182],"banner design","ckm:banner design","banner","frontend","3D","generated","Art","social","dimensions","neon","direction","display","frontend-design","hero",{"skillNo":184,"name":185,"nameZh":6,"description":186,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":187,"categories":188,"keywords":195,"publishedAt":39},"01M6Q2RZXBJ9TBE413GXCYQNDB","seo","Comprehensive SEO analysis for any website or business type. Performs full site audits, single-page deep analysis, technical SEO checks (crawlability, indexability, Core Web Vitals with INP), schema markup detection\u002Fvalidation\u002Fgeneration, content quality assessment (E-E-A-T framework per Dec 2025 update extending to all competitive queries), image optimization, sitemap analysis, and Generative Engine Optimization (GEO) for AI Overviews, ChatGPT, and Perplexity citations. Analyzes AI crawler accessibility (GPTBot, ClaudeBot, PerplexityBot), llms.txt compliance, brand mention signals, and passage-level citability. Industry detection for SaaS, e-commerce, local business, publishers, agencies. Triggers on: \"SEO\", \"audit\", \"schema\", \"Core Web Vitals\", \"sitemap\", \"E-E-A-T\", \"AI Overviews\", \"GEO\", \"technical SEO\", \"content quality\", \"page speed\", \"structured data\".","https:\u002F\u002Fgithub.com\u002Fibragimov-oasis\u002Fvibe-coder\u002Fblob\u002Fmain\u002Fvc-kit\u002Fcontent\u002FCOMBINED\u002FCOMBINED\u002Fskills\u002Fskills-seo\u002Fseo\u002Fclaude-seo\u002Fskills\u002Fseo\u002FSKILL.md",[189,192],{"categoryNo":190,"categoryName":191,"taxonomyType":82,"taxonomyTypeDesc":83},"01JBSEEDCAT000000000000019","营销推广",{"categoryNo":193,"categoryName":194,"taxonomyType":87,"taxonomyTypeDesc":88},"01JBSEEDCAT000000000000035","市场营销",[185,196,197,198,199,200,201,135,202,203,204,205,206,207,208,209,210,211,212,213],"image","llms","assessment","deep analysis","Citations","analysis","local","deep","crawlability","seo analysis","2025","commerce","URL","domain\u002Fseo","source\u002Fskills-seo","vitals","generative","publishers",{"skillNo":215,"name":216,"nameZh":6,"description":217,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":218,"categories":219,"keywords":222,"publishedAt":39},"01M6Q2RVE7VGFCFQKBK468NHVY","seo-technical","Technical SEO audit across 9 categories: crawlability, indexability, security, URL structure, mobile, Core Web Vitals, structured data, JavaScript rendering, and IndexNow protocol. Use when user says \"technical SEO\", \"crawl issues\", \"robots.txt\", \"Core Web Vitals\", \"site speed\", or \"security headers\".","https:\u002F\u002Fgithub.com\u002Fibragimov-oasis\u002Fvibe-coder\u002Fblob\u002Fmain\u002Fvc-kit\u002Fcontent\u002FCOMBINED\u002FCOMBINED\u002Fskills\u002Fskills-seo\u002Fseo\u002Fclaude-seo\u002Fskills\u002Fseo-technical\u002FSKILL.md",[220,221],{"categoryNo":190,"categoryName":191,"taxonomyType":82,"taxonomyTypeDesc":83},{"categoryNo":193,"categoryName":194,"taxonomyType":87,"taxonomyTypeDesc":88},[185,35,223,224,225,226,227,228,229,135,103,204,230,231,208,232,233,209,210,211],"seo technical","issues","audit","data","mobile","crawl","structure","rendering","technical seo audit","headers","categories"]