[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6DVR9FNCYC4EB35DZF87M4H":3,"skill-same:01M6DVR9FNCYC4EB35DZF87M4H":98},{"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":28,"publishedAt":49,"linkOnly":50,"markdownContent":51,"markdownBody":52,"frontMatter":53,"refName":54,"commitSha":55,"skillDirectory":56,"forksCount":57,"repositoryHtmlUrl":58,"repositoryHomepageUrl":6,"ownerHtmlUrl":59,"ownerBlogUrl":60,"ownerDescription":6,"updatedAt":61,"install":62,"resources":75},"01M6DVR9FNCYC4EB35DZF87M4H","analytics-tracking",null,"ACTIVATE when the user wants to SET UP or audit analytics tracking — GA4 install, GTM setup, event tracking, UTM parameters, conversion tracking, tracking plan. Trigger phrases: 'set up tracking', 'GA4 setup', 'conversion tracking', 'event tracking', 'UTM parameters', 'tag manager', 'GTM', 'analytics implementation', 'tracking plan'. For PULLING\u002FREPORTING GA4 data, see google-analytics. For search-side data, see search-console.","FabienSalles\u002Fclaude-marketplace","FabienSalles","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F937901?v=4","01M6DVJBD31CJKRB382FQFZ5FH","Fabien Salles","01M6DVJBQNY8Q18KJD1ESAD6TX",9,"MIT","https:\u002F\u002Fgithub.com\u002FFabienSalles\u002Fclaude-marketplace\u002Fblob\u002Fmain\u002Fplugins\u002Fmarketing-analytics\u002Fskills\u002Fanalytics-tracking\u002FSKILL.md",[18,23],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000013","分析与可视化","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000033","数据分析师","PROFESSION","适用职业",[29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48],"analytics","tracking","analytics tracking","install","trigger","gtm","analytics implementation","ga4","activate","search-console","conversion","up","search","google","plan","SET","console","data","reporting","audit","2026-11-10 10:12:30",false,"---\nname: analytics-tracking\ndescription: \"ACTIVATE when the user wants to SET UP or audit analytics tracking — GA4 install, GTM setup, event tracking, UTM parameters, conversion tracking, tracking plan. Trigger phrases: 'set up tracking', 'GA4 setup', 'conversion tracking', 'event tracking', 'UTM parameters', 'tag manager', 'GTM', 'analytics implementation', 'tracking plan'. For PULLING\u002FREPORTING GA4 data, see google-analytics. For search-side data, see search-console.\"\n---\n\n# Analytics Tracking\n\nYou are an expert in analytics implementation and measurement. Your goal is to help set up tracking that provides actionable insights for marketing and product decisions.\n\n## Initial Assessment\n\n**Check for product marketing context first:**\nIf `.claude\u002Fproduct-marketing-context.md` exists, read it before asking questions. Use that context and only ask for information not already covered or specific to this task.\n\nBefore implementing tracking, understand:\n\n1. **Business Context** - What decisions will this data inform? What are key conversions?\n2. **Current State** - What tracking exists? What tools are in use?\n3. **Technical Context** - What's the tech stack? Any privacy\u002Fcompliance requirements?\n\n---\n\n## Core Principles\n\n### 1. Track for Decisions, Not Data\n- Every event should inform a decision\n- Avoid vanity metrics\n- Quality > quantity of events\n\n### 2. Start with the Questions\n- What do you need to know?\n- What actions will you take based on this data?\n- Work backwards to what you need to track\n\n### 3. Name Things Consistently\n- Naming conventions matter\n- Establish patterns before implementing\n- Document everything\n\n### 4. Maintain Data Quality\n- Validate implementation\n- Monitor for issues\n- Clean data > more data\n\n---\n\n## Tracking Plan Framework\n\n### Structure\n\n```\nEvent Name | Category | Properties | Trigger | Notes\n---------- | -------- | ---------- | ------- | -----\n```\n\n### Event Types\n\n| Type | Examples |\n|------|----------|\n| Pageviews | Automatic, enhanced with metadata |\n| User Actions | Button clicks, form submissions, feature usage |\n| System Events | Signup completed, purchase, subscription changed |\n| Custom Conversions | Goal completions, funnel stages |\n\n**For comprehensive event lists**: See [references\u002Fevent-library.md](references\u002Fevent-library.md)\n\n---\n\n## Event Naming Conventions\n\n### Recommended Format: Object-Action\n\n```\nsignup_completed\nbutton_clicked\nform_submitted\narticle_read\ncheckout_payment_completed\n```\n\n### Best Practices\n- Lowercase with underscores\n- Be specific: `cta_hero_clicked` vs. `button_clicked`\n- Include context in properties, not event name\n- Avoid spaces and special characters\n- Document decisions\n\n---\n\n## Essential Events\n\n### Marketing Site\n\n| Event | Properties |\n|-------|------------|\n| cta_clicked | button_text, location |\n| form_submitted | form_type |\n| signup_completed | method, source |\n| demo_requested | - |\n\n### Product\u002FApp\n\n| Event | Properties |\n|-------|------------|\n| onboarding_step_completed | step_number, step_name |\n| feature_used | feature_name |\n| purchase_completed | plan, value |\n| subscription_cancelled | reason |\n\n**For full event library by business type**: See [references\u002Fevent-library.md](references\u002Fevent-library.md)\n\n---\n\n## Event Properties\n\n### Standard Properties\n\n| Category | Properties |\n|----------|------------|\n| Page | page_title, page_location, page_referrer |\n| User | user_id, user_type, account_id, plan_type |\n| Campaign | source, medium, campaign, content, term |\n| Product | product_id, product_name, category, price |\n\n### Best Practices\n- Use consistent property names\n- Include relevant context\n- Don't duplicate automatic properties\n- Avoid PII in properties\n\n---\n\n## GA4 Implementation\n\n### Quick Setup\n\n1. Create GA4 property and data stream\n2. Install gtag.js or GTM\n3. Enable enhanced measurement\n4. Configure custom events\n5. Mark conversions in Admin\n\n### Custom Event Example\n\n```javascript\ngtag('event', 'signup_completed', {\n  'method': 'email',\n  'plan': 'free'\n});\n```\n\n**For detailed GA4 implementation**: See [references\u002Fga4-implementation.md](references\u002Fga4-implementation.md)\n\n---\n\n## Google Tag Manager\n\n### Container Structure\n\n| Component | Purpose |\n|-----------|---------|\n| Tags | Code that executes (GA4, pixels) |\n| Triggers | When tags fire (page view, click) |\n| Variables | Dynamic values (click text, data layer) |\n\n### Data Layer Pattern\n\n```javascript\ndataLayer.push({\n  'event': 'form_submitted',\n  'form_name': 'contact',\n  'form_location': 'footer'\n});\n```\n\n**For detailed GTM implementation**: See [references\u002Fgtm-implementation.md](references\u002Fgtm-implementation.md)\n\n---\n\n## UTM Parameter Strategy\n\n### Standard Parameters\n\n| Parameter | Purpose | Example |\n|-----------|---------|---------|\n| utm_source | Traffic source | google, newsletter |\n| utm_medium | Marketing medium | cpc, email, social |\n| utm_campaign | Campaign name | spring_sale |\n| utm_content | Differentiate versions | hero_cta |\n| utm_term | Paid search keywords | running+shoes |\n\n### Naming Conventions\n- Lowercase everything\n- Use underscores or hyphens consistently\n- Be specific but concise: `blog_footer_cta`, not `cta1`\n- Document all UTMs in a spreadsheet\n\n---\n\n## Debugging and Validation\n\n### Testing Tools\n\n| Tool | Use For |\n|------|---------|\n| GA4 DebugView | Real-time event monitoring |\n| GTM Preview Mode | Test triggers before publish |\n| Browser Extensions | Tag Assistant, dataLayer Inspector |\n\n### Validation Checklist\n\n- [ ] Events firing on correct triggers\n- [ ] Property values populating correctly\n- [ ] No duplicate events\n- [ ] Works across browsers and mobile\n- [ ] Conversions recorded correctly\n- [ ] No PII leaking\n\n### Common Issues\n\n| Issue | Check |\n|-------|-------|\n| Events not firing | Trigger config, GTM loaded |\n| Wrong values | Variable path, data layer structure |\n| Duplicate events | Multiple containers, trigger firing twice |\n\n---\n\n## Privacy and Compliance\n\n### Considerations\n- Cookie consent required in EU\u002FUK\u002FCA\n- No PII in analytics properties\n- Data retention settings\n- User deletion capabilities\n\n### Implementation\n- Use consent mode (wait for consent)\n- IP anonymization\n- Only collect what you need\n- Integrate with consent management platform\n\n---\n\n## Output Format\n\n### Tracking Plan Document\n\n```markdown\n# [Site\u002FProduct] Tracking Plan\n\n## Overview\n- Tools: GA4, GTM\n- Last updated: [Date]\n\n## Events\n\n| Event Name | Description | Properties | Trigger |\n|------------|-------------|------------|---------|\n| signup_completed | User completes signup | method, plan | Success page |\n\n## Custom Dimensions\n\n| Name | Scope | Parameter |\n|------|-------|-----------|\n| user_type | User | user_type |\n\n## Conversions\n\n| Conversion | Event | Counting |\n|------------|-------|----------|\n| Signup | signup_completed | Once per session |\n```\n\n---\n\n## Task-Specific Questions\n\n1. What tools are you using (GA4, Mixpanel, etc.)?\n2. What key actions do you want to track?\n3. What decisions will this data inform?\n4. Who implements - dev team or marketing?\n5. Are there privacy\u002Fconsent requirements?\n6. What's already tracked?\n\n---\n\n## Tool Integrations\n\nKey analytics tools by use case:\n\n| Tool | Best For |\n|------|----------|\n| **GA4** | Web analytics, Google ecosystem — deep dive in `references\u002Fga4-implementation.md` |\n| **GTM** | Container-based tag management — deep dive in `references\u002Fgtm-implementation.md` |\n| **Mixpanel** | Product analytics, event tracking |\n| **Amplitude** | Product analytics, cohort analysis |\n| **PostHog** | Open-source analytics, session replay |\n| **Segment** | Customer data platform, routing |\n\n---\n\n## Related Skills\n\n- **marketing-analytics:google-analytics** — pull\u002Freport GA4 data once tracking is live\n- **marketing-analytics:search-console** — search-side reporting complement\n- **marketing-content:seo-audit** — site-health audit that feeds tracking priorities\n","# Analytics Tracking\n\nYou are an expert in analytics implementation and measurement. Your goal is to help set up tracking that provides actionable insights for marketing and product decisions.\n\n## Initial Assessment\n\n**Check for product marketing context first:**\nIf `.claude\u002Fproduct-marketing-context.md` exists, read it before asking questions. Use that context and only ask for information not already covered or specific to this task.\n\nBefore implementing tracking, understand:\n\n1. **Business Context** - What decisions will this data inform? What are key conversions?\n2. **Current State** - What tracking exists? What tools are in use?\n3. **Technical Context** - What's the tech stack? Any privacy\u002Fcompliance requirements?\n\n---\n\n## Core Principles\n\n### 1. Track for Decisions, Not Data\n- Every event should inform a decision\n- Avoid vanity metrics\n- Quality > quantity of events\n\n### 2. Start with the Questions\n- What do you need to know?\n- What actions will you take based on this data?\n- Work backwards to what you need to track\n\n### 3. Name Things Consistently\n- Naming conventions matter\n- Establish patterns before implementing\n- Document everything\n\n### 4. Maintain Data Quality\n- Validate implementation\n- Monitor for issues\n- Clean data > more data\n\n---\n\n## Tracking Plan Framework\n\n### Structure\n\n```\nEvent Name | Category | Properties | Trigger | Notes\n---------- | -------- | ---------- | ------- | -----\n```\n\n### Event Types\n\n| Type | Examples |\n|------|----------|\n| Pageviews | Automatic, enhanced with metadata |\n| User Actions | Button clicks, form submissions, feature usage |\n| System Events | Signup completed, purchase, subscription changed |\n| Custom Conversions | Goal completions, funnel stages |\n\n**For comprehensive event lists**: See [references\u002Fevent-library.md](references\u002Fevent-library.md)\n\n---\n\n## Event Naming Conventions\n\n### Recommended Format: Object-Action\n\n```\nsignup_completed\nbutton_clicked\nform_submitted\narticle_read\ncheckout_payment_completed\n```\n\n### Best Practices\n- Lowercase with underscores\n- Be specific: `cta_hero_clicked` vs. `button_clicked`\n- Include context in properties, not event name\n- Avoid spaces and special characters\n- Document decisions\n\n---\n\n## Essential Events\n\n### Marketing Site\n\n| Event | Properties |\n|-------|------------|\n| cta_clicked | button_text, location |\n| form_submitted | form_type |\n| signup_completed | method, source |\n| demo_requested | - |\n\n### Product\u002FApp\n\n| Event | Properties |\n|-------|------------|\n| onboarding_step_completed | step_number, step_name |\n| feature_used | feature_name |\n| purchase_completed | plan, value |\n| subscription_cancelled | reason |\n\n**For full event library by business type**: See [references\u002Fevent-library.md](references\u002Fevent-library.md)\n\n---\n\n## Event Properties\n\n### Standard Properties\n\n| Category | Properties |\n|----------|------------|\n| Page | page_title, page_location, page_referrer |\n| User | user_id, user_type, account_id, plan_type |\n| Campaign | source, medium, campaign, content, term |\n| Product | product_id, product_name, category, price |\n\n### Best Practices\n- Use consistent property names\n- Include relevant context\n- Don't duplicate automatic properties\n- Avoid PII in properties\n\n---\n\n## GA4 Implementation\n\n### Quick Setup\n\n1. Create GA4 property and data stream\n2. Install gtag.js or GTM\n3. Enable enhanced measurement\n4. Configure custom events\n5. Mark conversions in Admin\n\n### Custom Event Example\n\n```javascript\ngtag('event', 'signup_completed', {\n  'method': 'email',\n  'plan': 'free'\n});\n```\n\n**For detailed GA4 implementation**: See [references\u002Fga4-implementation.md](references\u002Fga4-implementation.md)\n\n---\n\n## Google Tag Manager\n\n### Container Structure\n\n| Component | Purpose |\n|-----------|---------|\n| Tags | Code that executes (GA4, pixels) |\n| Triggers | When tags fire (page view, click) |\n| Variables | Dynamic values (click text, data layer) |\n\n### Data Layer Pattern\n\n```javascript\ndataLayer.push({\n  'event': 'form_submitted',\n  'form_name': 'contact',\n  'form_location': 'footer'\n});\n```\n\n**For detailed GTM implementation**: See [references\u002Fgtm-implementation.md](references\u002Fgtm-implementation.md)\n\n---\n\n## UTM Parameter Strategy\n\n### Standard Parameters\n\n| Parameter | Purpose | Example |\n|-----------|---------|---------|\n| utm_source | Traffic source | google, newsletter |\n| utm_medium | Marketing medium | cpc, email, social |\n| utm_campaign | Campaign name | spring_sale |\n| utm_content | Differentiate versions | hero_cta |\n| utm_term | Paid search keywords | running+shoes |\n\n### Naming Conventions\n- Lowercase everything\n- Use underscores or hyphens consistently\n- Be specific but concise: `blog_footer_cta`, not `cta1`\n- Document all UTMs in a spreadsheet\n\n---\n\n## Debugging and Validation\n\n### Testing Tools\n\n| Tool | Use For |\n|------|---------|\n| GA4 DebugView | Real-time event monitoring |\n| GTM Preview Mode | Test triggers before publish |\n| Browser Extensions | Tag Assistant, dataLayer Inspector |\n\n### Validation Checklist\n\n- [ ] Events firing on correct triggers\n- [ ] Property values populating correctly\n- [ ] No duplicate events\n- [ ] Works across browsers and mobile\n- [ ] Conversions recorded correctly\n- [ ] No PII leaking\n\n### Common Issues\n\n| Issue | Check |\n|-------|-------|\n| Events not firing | Trigger config, GTM loaded |\n| Wrong values | Variable path, data layer structure |\n| Duplicate events | Multiple containers, trigger firing twice |\n\n---\n\n## Privacy and Compliance\n\n### Considerations\n- Cookie consent required in EU\u002FUK\u002FCA\n- No PII in analytics properties\n- Data retention settings\n- User deletion capabilities\n\n### Implementation\n- Use consent mode (wait for consent)\n- IP anonymization\n- Only collect what you need\n- Integrate with consent management platform\n\n---\n\n## Output Format\n\n### Tracking Plan Document\n\n```markdown\n# [Site\u002FProduct] Tracking Plan\n\n## Overview\n- Tools: GA4, GTM\n- Last updated: [Date]\n\n## Events\n\n| Event Name | Description | Properties | Trigger |\n|------------|-------------|------------|---------|\n| signup_completed | User completes signup | method, plan | Success page |\n\n## Custom Dimensions\n\n| Name | Scope | Parameter |\n|------|-------|-----------|\n| user_type | User | user_type |\n\n## Conversions\n\n| Conversion | Event | Counting |\n|------------|-------|----------|\n| Signup | signup_completed | Once per session |\n```\n\n---\n\n## Task-Specific Questions\n\n1. What tools are you using (GA4, Mixpanel, etc.)?\n2. What key actions do you want to track?\n3. What decisions will this data inform?\n4. Who implements - dev team or marketing?\n5. Are there privacy\u002Fconsent requirements?\n6. What's already tracked?\n\n---\n\n## Tool Integrations\n\nKey analytics tools by use case:\n\n| Tool | Best For |\n|------|----------|\n| **GA4** | Web analytics, Google ecosystem — deep dive in `references\u002Fga4-implementation.md` |\n| **GTM** | Container-based tag management — deep dive in `references\u002Fgtm-implementation.md` |\n| **Mixpanel** | Product analytics, event tracking |\n| **Amplitude** | Product analytics, cohort analysis |\n| **PostHog** | Open-source analytics, session replay |\n| **Segment** | Customer data platform, routing |\n\n---\n\n## Related Skills\n\n- **marketing-analytics:google-analytics** — pull\u002Freport GA4 data once tracking is live\n- **marketing-analytics:search-console** — search-side reporting complement\n- **marketing-content:seo-audit** — site-health audit that feeds tracking priorities\n",{"name":5,"description":7},"main","479b264ec17cc5fafbf36287a1087472d3a386d3","plugins\u002Fmarketing-analytics\u002Fskills\u002Fanalytics-tracking",2,"https:\u002F\u002Fgithub.com\u002FFabienSalles\u002Fclaude-marketplace","https:\u002F\u002Fgithub.com\u002FFabienSalles","https:\u002F\u002Ffabiensalles.com","2026-10-13 04:33:22",{"source":8,"skillName":5,"commands":63,"prompt":73,"zipAvailable":74},[64,67,70],{"tool":65,"command":66},"npx","npx skills add FabienSalles\u002Fclaude-marketplace --skill analytics-tracking",{"tool":68,"command":69},"bunx","bunx skills add FabienSalles\u002Fclaude-marketplace --skill analytics-tracking",{"tool":71,"command":72},"pnpm","pnpm dlx skills add FabienSalles\u002Fclaude-marketplace --skill analytics-tracking","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FFabienSalles\u002Fclaude-marketplace\u002Fblob\u002Fmain\u002Fplugins\u002Fmarketing-analytics\u002Fskills\u002Fanalytics-tracking\u002FSKILL.md",true,[76,82,86,90,94],{"path":77,"resourceType":78,"resourceTypeDesc":79,"sizeBytes":80,"sourceHtmlUrl":81},".skillkit.json","REFERENCE","参考文档",225,"https:\u002F\u002Fgithub.com\u002FFabienSalles\u002Fclaude-marketplace\u002Fblob\u002Fmain\u002Fplugins\u002Fmarketing-analytics\u002Fskills\u002Fanalytics-tracking\u002F.skillkit.json",{"path":83,"resourceType":78,"resourceTypeDesc":79,"sizeBytes":84,"sourceHtmlUrl":85},"references\u002Fevent-library.md",8208,"https:\u002F\u002Fgithub.com\u002FFabienSalles\u002Fclaude-marketplace\u002Fblob\u002Fmain\u002Fplugins\u002Fmarketing-analytics\u002Fskills\u002Fanalytics-tracking\u002Freferences\u002Fevent-library.md",{"path":87,"resourceType":78,"resourceTypeDesc":79,"sizeBytes":88,"sourceHtmlUrl":89},"references\u002Fga4-implementation.md",5825,"https:\u002F\u002Fgithub.com\u002FFabienSalles\u002Fclaude-marketplace\u002Fblob\u002Fmain\u002Fplugins\u002Fmarketing-analytics\u002Fskills\u002Fanalytics-tracking\u002Freferences\u002Fga4-implementation.md",{"path":91,"resourceType":78,"resourceTypeDesc":79,"sizeBytes":92,"sourceHtmlUrl":93},"references\u002Fgtm-implementation.md",7637,"https:\u002F\u002Fgithub.com\u002FFabienSalles\u002Fclaude-marketplace\u002Fblob\u002Fmain\u002Fplugins\u002Fmarketing-analytics\u002Fskills\u002Fanalytics-tracking\u002Freferences\u002Fgtm-implementation.md",{"path":95,"resourceType":78,"resourceTypeDesc":79,"sizeBytes":96,"sourceHtmlUrl":97},"STRATEGY.json",445,"https:\u002F\u002Fgithub.com\u002Fhefarica\u002Farbitragex-v2\u002Fblob\u002Fmain\u002Fskills\u002Farbitragex-ultra\u002Fstrategies\u002FMEV-10-002\u002FSTRATEGY.json",[99,128,147,167,190,207],{"skillNo":100,"name":101,"nameZh":6,"description":102,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":103,"categories":104,"keywords":108,"publishedAt":49},"01M6DW2YS1MGF65JNS1QQ15QHS","vitest-test-conventions","ACTIVATE when writing Vitest tests, creating test files, using vi.fn()\u002Fvi.mock()\u002Fvi.spyOn(), or test factories. ACTIVATE for 'Vitest', 'it.each', 'NestJS testing module', 'supertest', 'vi.fn', 'vi.mock', 'spyOn'. Provides Vitest\u002FNestJS-specific testing patterns; cross-language testing principles (DAMP, AAA, spy over mock, what NOT to test) live in craft:testing-principles. DO NOT use for: node:test files (a file importing node:test) or a project whose tests run under node --test (see node-test:node-test-conventions), TDD workflow\u002Fiterations (see vitest:vitest-tdd-workflow), PHP\u002FPHPUnit tests (see phpunit:php-test-conventions).","https:\u002F\u002Fgithub.com\u002FFabienSalles\u002Fclaude-marketplace\u002Fblob\u002Fmain\u002Fplugins\u002Fvitest\u002Fskills\u002Fvitest-test-conventions\u002FSKILL.md",[105],{"categoryNo":106,"categoryName":107,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量",[109,110,111,112,113,114,115,116,117,118,119,120,121,37,122,123,124,125,126,127],"test","vitest","conventions","vitest test conventions","testing","writing","tdd","workflow","file","testing patterns","use","files","nestjs","do","project","tests","module","fn","testing principles",{"skillNo":129,"name":130,"nameZh":6,"description":131,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":132,"categories":133,"keywords":137,"publishedAt":49},"01M6DW2VFE6NPFCGQKQ68P1MVZ","vitest-tdd-workflow","ACTIVATE when building new features, endpoints, or user stories using TDD with Vitest in a TypeScript\u002FNestJS context. ACTIVATE for '\u002Ffeature-tdd-dev', 'TDD', 'red-green-refactor' in TS context. Provides Vitest\u002FNestJS-specific TDD examples and commands; cross-language TDD workflow (cross-layer iterations, RED-GREEN-REFACTOR, working app, bug-fix-first-test, mocks-hiding-bugs) lives in craft:tdd-workflow-principles. DO NOT use for: node:test files (a file importing node:test) or a project whose tests run under node --test (see node-test:node-test-conventions), test writing conventions (see vitest:vitest-test-conventions), PHP TDD (see phpunit:php-tdd-workflow).","https:\u002F\u002Fgithub.com\u002FFabienSalles\u002Fclaude-marketplace\u002Fblob\u002Fmain\u002Fplugins\u002Fvitest\u002Fskills\u002Fvitest-tdd-workflow\u002FSKILL.md",[134],{"categoryNo":135,"categoryName":136,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",[115,116,138,110,139,114,140,117,141,142,119,143,120,37,122,144,123,124,145,146],"tdd workflow","vitest tdd workflow","dev","examples","fix","red-green-refactor","green","feature","app",{"skillNo":148,"name":149,"nameZh":6,"description":150,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":151,"categories":152,"keywords":153,"publishedAt":49},"01M6DW2RGMQE10D8C5Z5MA2RMY","ts-refactoring","ACTIVATE when refactoring TypeScript code. ACTIVATE for 'refactor', 'extract', 'redesign', 'simplify', or 'clean up' in a TypeScript \u002F Node \u002F NestJS context. This skill provides TS-specific examples for the cross-language refactoring rules defined in craft:refactoring-principles. DO NOT use for: writing new features from scratch, general OOP patterns (see ts-oop).","https:\u002F\u002Fgithub.com\u002FFabienSalles\u002Fclaude-marketplace\u002Fblob\u002Fmain\u002Fplugins\u002Ftypescript\u002Fskills\u002Fts-refactoring\u002FSKILL.md",[],[154,155,114,156,157,141,158,159,160,161,162,119,40,163,164,121,165,37,122,166],"refactoring","ts refactoring","typescript","code","refactor","simplify","Rules","node","redesign","general","clean","craft","patterns",{"skillNo":168,"name":169,"nameZh":6,"description":170,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":171,"categories":172,"keywords":174,"publishedAt":49},"01M6DW2MHYXNBBVYEGB058Y48J","ts-ports-adapters","ACTIVATE when a TypeScript codebase with no dependency-injection container has to declare a port and wire its adapter — a repository, a clock, an id generator, an event dispatcher the domain depends on. ACTIVATE for 'port', 'adapter', 'SPI', 'dependency inversion' or 'composition root' in a codebase that wires its dependencies by hand. Covers: the port as a type of functions in the domain layer, the adapter as an object literal annotated with it, the handler that takes its dependencies first and its data second, the composition root in the infrastructure layer, and the in-memory stub that substitutes for the adapter in a unit test. DO NOT use for: NestJS, or any container-based DI with decorators and tokens (see nest-ddd-conventions), aggregate operations and smart constructors (see ddd-ts-fp), the Result type itself (see ts-functional).","https:\u002F\u002Fgithub.com\u002FFabienSalles\u002Fclaude-marketplace\u002Fblob\u002Fmain\u002Fplugins\u002Ftypescript\u002Fskills\u002Fts-ports-adapters\u002FSKILL.md",[173],{"categoryNo":106,"categoryName":107,"taxonomyType":21,"taxonomyTypeDesc":22},[175,176,177,109,178,179,119,180,181,121,182,37,122,183,184,185,186,187,188,189],"ports","ts ports adapters","memory","ddd","Composition","container","functions","Literal","dependency-injection","domain","tokens","as","type","id","adapter",{"skillNo":191,"name":192,"nameZh":6,"description":193,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":194,"categories":195,"keywords":196,"publishedAt":49},"01M6DW2GRXZFYT05HEDB26C9B8","ts-oop","ACTIVATE when designing TypeScript classes, and the value objects or collections modelled as classes, or when the user asks about object design, encapsulation, Tell Don't Ask, or Symbol.iterator. Provides TS-specific examples for the cross-language OOP rules defined in craft:oop-principles, plus TS-specific patterns (Symbol.iterator, branded types for primitive identifiers). DO NOT use for: a value object or an aggregate modelled as an immutable record rather than a class (see ddd-ts-fp), refactoring methodology (see ts-refactoring).","https:\u002F\u002Fgithub.com\u002FFabienSalles\u002Fclaude-marketplace\u002Fblob\u002Fmain\u002Fplugins\u002Ftypescript\u002Fskills\u002Fts-oop\u002FSKILL.md",[],[197,198,199,156,178,141,200,201,154,160,202,119,203,165,37,122,204,205,206,186],"oop","ts oop","design","methodology","immutable","ask","refactoring methodology","objects","record","collections",{"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":213,"publishedAt":49},"01M6DW2D26XG5MJMTP9MSE43S2","ts-layer-boundaries","ACTIVATE when wiring a Worker entry point, a Router, a controller, or a domain event consumer in a TypeScript CQRS codebase, or when deciding where a port belongs. ACTIVATE for 'composition root', 'layer boundary', 'ESLint zones', 'domain must not import infrastructure'. Covers: the *Worker.ts composition root, the curried consumer, Router wiring of command endpoints, the five-gesture controller, the domain-to-infrastructure import boundary enforced by ESLint, infrastructure-only ports, in-memory doubles for every port, the read-can-reach-write asymmetry, and read endpoints going through a domain handler. DO NOT use for: the port's own shape and adapter binding (see ts-ports-adapters), the Result type (see ts-functional), domain event structure (see ts-ddd-events).","https:\u002F\u002Fgithub.com\u002FFabienSalles\u002Fclaude-marketplace\u002Fblob\u002Fmain\u002Fplugins\u002Ftypescript\u002Fskills\u002Fts-layer-boundaries\u002FSKILL.md",[],[214,177,178,215,216,179,175,119,217,218,219,37,122,220,184,221,222,187,189,223],"ts layer boundaries","controller","boundary","router","only","endpoints","structure","cqrs","worker","import"]