[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M755Y26PS6M20SWDZVMJWNT1":3,"skill-same:01M755Y26PS6M20SWDZVMJWNT1":55},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":29,"commitSha":30,"skillDirectory":31,"forksCount":13,"repositoryHtmlUrl":32,"repositoryHomepageUrl":6,"ownerHtmlUrl":33,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":34,"install":35,"resources":48},"01M755Y26PS6M20SWDZVMJWNT1","drift-detector",null,"Detect infrastructure drift between Terraform state and actual cloud resources. Identifies\nunmanaged resources, manual changes, and configuration drift. Use when:\n- User asks to check for infrastructure drift\n- User wants to find unmanaged cloud resources\n- User mentions \"drift detection\" or \"Terraform drift\"\n- User asks to compare cloud state to IaC\n- User wants to audit infrastructure changes","ASoudy\u002FAGS","ASoudy","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F40639702?v=4","01M74G5NTCW8MWDNRTAF303PA1","01M74G5NTZXSE6T0GZR5BCB6V0",0,"Apache-2.0","https:\u002F\u002Fgithub.com\u002FASoudy\u002FAGS\u002Fblob\u002Fmain\u002Fclaude_skills_libraries\u002Fsnyk-fix\u002Fcommand_directives\u002Fsynchronous_remediation\u002Fskills\u002Fdrift-detector\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: drift-detector\ndescription: |\n  Detect infrastructure drift between Terraform state and actual cloud resources. Identifies\n  unmanaged resources, manual changes, and configuration drift. Use when:\n  - User asks to check for infrastructure drift\n  - User wants to find unmanaged cloud resources\n  - User mentions \"drift detection\" or \"Terraform drift\"\n  - User asks to compare cloud state to IaC\n  - User wants to audit infrastructure changes\nallowed-tools: \"Bash Read Write Grep\"\nlicense: Apache-2.0\ncompatibility: |\n  Requires Snyk CLI installed and authenticated. Uses `snyk iac describe` CLI command\n  (shell execution). Cloud provider credentials must be configured (AWS, Azure, or GCP).\n  Terraform state file (local or remote) required.\nmetadata:\n  author: Snyk\n  version: 1.0.0\n---\n\n# Infrastructure Drift Detector\n\nDetect, track, and resolve infrastructure drift between Terraform state and actual cloud resources to maintain Infrastructure as Code integrity.\n\n**Core Principle**: Your cloud should match your code.\n\n**Note**: This skill uses `snyk iac describe` CLI command (requires shell execution).\n\n---\n\n## Quick Start\n\n```bash\n# Basic drift scan against a local Terraform state file\nsnyk iac describe --from=tfstate:\u002F\u002Fterraform.tfstate\n\n# Output as JSON for further analysis\nsnyk iac describe --from=tfstate:\u002F\u002Fterraform.tfstate --json > drift-report.json\n```\n\n---\n\n## Prerequisites\n\n- Terraform project with state file (local or remote)\n- Cloud provider credentials configured\n- `snyk` CLI installed\n- Network access to cloud APIs\n\n### Supported Cloud Providers\n\n| Provider | Setup |\n|----------|-------|\n| **AWS** | AWS credentials (profile, env vars, or IAM role) |\n| **Azure** | Azure CLI login or service principal |\n| **GCP** | Application default credentials or service account |\n\nFor a full list of supported resource types per provider, see `SERVICES.md`.\n\n---\n\n## Phase 1: Setup\n\n**Goal**: Configure drift detection environment.\n\n### Step 1.1: Verify Terraform State\n\nCheck for Terraform state:\n\n**Local state**:\n```bash\nls terraform.tfstate\n```\n\n**Remote state** (S3 backend):\n```hcl\nterraform {\n  backend \"s3\" {\n    bucket = \"my-terraform-state\"\n    key    = \"state\u002Fterraform.tfstate\"\n    region = \"us-east-1\"\n  }\n}\n```\n\n### Step 1.2: Verify Cloud Credentials\n\n**AWS**:\n```bash\naws sts get-caller-identity\n```\n\n**Azure**:\n```bash\naz account show\n```\n\n**GCP**:\n```bash\ngcloud auth application-default print-access-token\n```\n\n---\n\n## Phase 2: Run Drift Detection\n\n**Goal**: Identify differences between IaC and actual cloud state.\n\n### Step 2.1: Basic Drift Scan\n\n```bash\nsnyk iac describe --from=tfstate:\u002F\u002Fterraform.tfstate\n```\n\n### Step 2.2: Remote State Scan\n\nFor S3 backend:\n```bash\nsnyk iac describe --from=tfstate+s3:\u002F\u002Fmy-bucket\u002Fstate.tfstate\n```\n\nFor Terraform Cloud:\n```bash\nsnyk iac describe \\\n  --from=tfstate+tfcloud:\u002F\u002Forganization\u002Fworkspace \\\n  --tfc-token=$TFC_TOKEN\n```\n\n### Step 2.3: Specific Service Scan\n\nTo focus on specific AWS services:\n```bash\nsnyk iac describe \\\n  --from=tfstate:\u002F\u002Fterraform.tfstate \\\n  --service=aws_s3,aws_ec2,aws_rds\n```\n\n### Step 2.4: JSON Output for Analysis\n\n```bash\nsnyk iac describe \\\n  --from=tfstate:\u002F\u002Fterraform.tfstate \\\n  --json > drift-report.json\n```\n\n---\n\n## Phase 3: Analyze Results\n\n**Goal**: Understand and categorize drift.\n\n### Step 3.1: Drift Categories\n\n| Category | Description | Risk Level |\n|----------|-------------|------------|\n| **Unmanaged** | Resources not in Terraform | High - shadow IT |\n| **Changed** | Resources modified outside Terraform | Medium - config drift |\n| **Missing** | Resources in state but deleted | Low - usually intentional |\n\n### Step 3.2: Generate Report\n\n```\n## Infrastructure Drift Report\n\nScan Date: 2024-01-15\nTerraform State: s3:\u002F\u002Fmy-bucket\u002Fprod.tfstate\nCloud Provider: AWS (us-east-1)\n\n### Summary\n- Unmanaged Resources: 12 (High)\n- Changed Resources:    5  (Medium)\n- Missing Resources:    2  (Low)\n- Total Drift:         19\n\n### Unmanaged Resources (Not in Terraform)\n- aws_s3_bucket      | prod-logs-manual   | High     | Import or delete\n- aws_security_group | sg-temp-access     | Critical | Review and remove\n\n### Changed Resources (Modified Outside Terraform)\n- aws_security_group.web | ingress: [443]   → ingress: [443, 22]  | High\n- aws_rds_instance.main  | multi_az: true   → multi_az: false      | Critical\n```\n\n### Step 3.3: Risk Assessment\n\nPrioritize **Critical** issues first (e.g. SSH opened to 0.0.0.0\u002F0, production HA disabled), then **High** risk issues (e.g. unmanaged IAM users or security groups). Document the affected resource, the risk, and the intended remediation action for each finding.\n\n---\n\n## Phase 4: Remediation\n\n**Goal**: Resolve drift and restore IaC integrity.\n\n### Step 4.1: Import Unmanaged Resources\n\nFor resources that should be in Terraform:\n\n```bash\n# Generate import block\nterraform import aws_s3_bucket.manual_bucket prod-logs-manual\n\n# Or use import block (Terraform 1.5+)\n```\n\n```hcl\nimport {\n  to = aws_s3_bucket.manual_bucket\n  id = \"prod-logs-manual\"\n}\n```\n\n### Step 4.2: Remove Unauthorized Resources\n\nFor resources that shouldn't exist:\n\n```bash\n# After verification, delete unmanaged resources\naws s3 rb s3:\u002F\u002Funauthorized-bucket --force\naws ec2 terminate-instances --instance-ids i-temp-server\n```\n\n### Step 4.3: Revert Changes\n\nFor resources modified outside Terraform:\n\n```bash\n# Re-apply Terraform to restore intended state\nterraform apply\n```\n\n### Step 4.4: Update Terraform (Adopt Changes)\n\nIf the manual change should be kept:\n\n```hcl\n# Update Terraform to match new reality\nresource \"aws_security_group\" \"web\" {\n  # Add the new rule\n  ingress {\n    from_port   = 22\n    to_port     = 22\n    protocol    = \"tcp\"\n    cidr_blocks = [\"10.0.0.0\u002F8\"]  # Restrict if keeping\n  }\n}\n```\n\n---\n\n## Phase 5: Prevention\n\n**Goal**: Prevent future drift.\n\n### Step 5.1: Generate Exclude Policy\n\nFor expected drift (auto-scaling, etc.):\n\n```bash\nsnyk iac update-exclude-policy \\\n  --exclude-unmanaged \\\n  --exclude-changed\n```\n\nThis creates a `.snyk` policy file:\n\n```yaml\nexclude:\n  iac-drift:\n    - aws_autoscaling_group.*\n    - aws_ecs_service.*:desiredCount\n```\n\n### Step 5.2: CI\u002FCD Integration\n\nAdd drift detection to CI\u002FCD:\n\n```yaml\n# GitHub Actions example\n- name: Check for Infrastructure Drift\n  run: |\n    snyk iac describe \\\n      --from=tfstate+s3:\u002F\u002Fmy-bucket\u002Fprod.tfstate \\\n      --json > drift.json\n    \n    # Fail if unmanaged resources found\n    if [ $(jq '.summary.total_unmanaged' drift.json) -gt 0 ]; then\n      echo \"Drift detected!\"\n      exit 1\n    fi\n```\n\n### Step 5.3: Regular Audits\n\nSchedule regular drift audits:\n\n| Frequency | Scope | Purpose |\n|-----------|-------|---------|\n| Daily | Critical resources | Security monitoring |\n| Weekly | All production | Configuration audit |\n| Monthly | All environments | Comprehensive review |\n\n---\n\n## Common Scenarios\n\nFor detailed worked examples, see `EXAMPLES.md`. Brief references:\n\n- **Post-Incident Audit**: Run drift detection with JSON output, filter for security-related resources, identify unauthorized changes, generate incident report, remediate and document.\n- **Pre-Deployment Check**: Run drift detection, fail deployment if drift exists, resolve drift first, then proceed with deployment.\n- **Shadow IT Discovery**: Run drift detection, filter to unmanaged resources, categorize by owner\u002Fpurpose, import or remove as appropriate.\n\n---\n\n## Error Handling\n\n### State Access Error\n\n```\nError: Could not read Terraform state\n\nSolutions:\n1. Verify state file path\n2. Check S3\u002Fbackend permissions\n3. Ensure terraform init has been run\n```\n\n### Cloud Credential Error\n\n```\nError: Authentication failed\n\nSolutions:\n1. Verify cloud credentials\n2. Check IAM permissions for describe\u002Flist\n3. Ensure credentials not expired\n```\n\n### Service Not Supported\n\n```\nWarning: Service X not supported\n\nSolutions:\n1. Check supported services list\n2. Use Terraform plan comparison instead\n3. Report to Snyk for feature request\n```\n\n---\n\n## Constraints\n\n1. **Read-only**: This skill only detects drift, doesn't modify resources\n2. **Credentials required**: Needs cloud provider access\n3. **Service coverage**: Not all resource types supported\n4. **State required**: Must have Terraform state to compare\n5. **Network required**: Needs access to cloud APIs\n","# Infrastructure Drift Detector\n\nDetect, track, and resolve infrastructure drift between Terraform state and actual cloud resources to maintain Infrastructure as Code integrity.\n\n**Core Principle**: Your cloud should match your code.\n\n**Note**: This skill uses `snyk iac describe` CLI command (requires shell execution).\n\n---\n\n## Quick Start\n\n```bash\n# Basic drift scan against a local Terraform state file\nsnyk iac describe --from=tfstate:\u002F\u002Fterraform.tfstate\n\n# Output as JSON for further analysis\nsnyk iac describe --from=tfstate:\u002F\u002Fterraform.tfstate --json > drift-report.json\n```\n\n---\n\n## Prerequisites\n\n- Terraform project with state file (local or remote)\n- Cloud provider credentials configured\n- `snyk` CLI installed\n- Network access to cloud APIs\n\n### Supported Cloud Providers\n\n| Provider | Setup |\n|----------|-------|\n| **AWS** | AWS credentials (profile, env vars, or IAM role) |\n| **Azure** | Azure CLI login or service principal |\n| **GCP** | Application default credentials or service account |\n\nFor a full list of supported resource types per provider, see `SERVICES.md`.\n\n---\n\n## Phase 1: Setup\n\n**Goal**: Configure drift detection environment.\n\n### Step 1.1: Verify Terraform State\n\nCheck for Terraform state:\n\n**Local state**:\n```bash\nls terraform.tfstate\n```\n\n**Remote state** (S3 backend):\n```hcl\nterraform {\n  backend \"s3\" {\n    bucket = \"my-terraform-state\"\n    key    = \"state\u002Fterraform.tfstate\"\n    region = \"us-east-1\"\n  }\n}\n```\n\n### Step 1.2: Verify Cloud Credentials\n\n**AWS**:\n```bash\naws sts get-caller-identity\n```\n\n**Azure**:\n```bash\naz account show\n```\n\n**GCP**:\n```bash\ngcloud auth application-default print-access-token\n```\n\n---\n\n## Phase 2: Run Drift Detection\n\n**Goal**: Identify differences between IaC and actual cloud state.\n\n### Step 2.1: Basic Drift Scan\n\n```bash\nsnyk iac describe --from=tfstate:\u002F\u002Fterraform.tfstate\n```\n\n### Step 2.2: Remote State Scan\n\nFor S3 backend:\n```bash\nsnyk iac describe --from=tfstate+s3:\u002F\u002Fmy-bucket\u002Fstate.tfstate\n```\n\nFor Terraform Cloud:\n```bash\nsnyk iac describe \\\n  --from=tfstate+tfcloud:\u002F\u002Forganization\u002Fworkspace \\\n  --tfc-token=$TFC_TOKEN\n```\n\n### Step 2.3: Specific Service Scan\n\nTo focus on specific AWS services:\n```bash\nsnyk iac describe \\\n  --from=tfstate:\u002F\u002Fterraform.tfstate \\\n  --service=aws_s3,aws_ec2,aws_rds\n```\n\n### Step 2.4: JSON Output for Analysis\n\n```bash\nsnyk iac describe \\\n  --from=tfstate:\u002F\u002Fterraform.tfstate \\\n  --json > drift-report.json\n```\n\n---\n\n## Phase 3: Analyze Results\n\n**Goal**: Understand and categorize drift.\n\n### Step 3.1: Drift Categories\n\n| Category | Description | Risk Level |\n|----------|-------------|------------|\n| **Unmanaged** | Resources not in Terraform | High - shadow IT |\n| **Changed** | Resources modified outside Terraform | Medium - config drift |\n| **Missing** | Resources in state but deleted | Low - usually intentional |\n\n### Step 3.2: Generate Report\n\n```\n## Infrastructure Drift Report\n\nScan Date: 2024-01-15\nTerraform State: s3:\u002F\u002Fmy-bucket\u002Fprod.tfstate\nCloud Provider: AWS (us-east-1)\n\n### Summary\n- Unmanaged Resources: 12 (High)\n- Changed Resources:    5  (Medium)\n- Missing Resources:    2  (Low)\n- Total Drift:         19\n\n### Unmanaged Resources (Not in Terraform)\n- aws_s3_bucket      | prod-logs-manual   | High     | Import or delete\n- aws_security_group | sg-temp-access     | Critical | Review and remove\n\n### Changed Resources (Modified Outside Terraform)\n- aws_security_group.web | ingress: [443]   → ingress: [443, 22]  | High\n- aws_rds_instance.main  | multi_az: true   → multi_az: false      | Critical\n```\n\n### Step 3.3: Risk Assessment\n\nPrioritize **Critical** issues first (e.g. SSH opened to 0.0.0.0\u002F0, production HA disabled), then **High** risk issues (e.g. unmanaged IAM users or security groups). Document the affected resource, the risk, and the intended remediation action for each finding.\n\n---\n\n## Phase 4: Remediation\n\n**Goal**: Resolve drift and restore IaC integrity.\n\n### Step 4.1: Import Unmanaged Resources\n\nFor resources that should be in Terraform:\n\n```bash\n# Generate import block\nterraform import aws_s3_bucket.manual_bucket prod-logs-manual\n\n# Or use import block (Terraform 1.5+)\n```\n\n```hcl\nimport {\n  to = aws_s3_bucket.manual_bucket\n  id = \"prod-logs-manual\"\n}\n```\n\n### Step 4.2: Remove Unauthorized Resources\n\nFor resources that shouldn't exist:\n\n```bash\n# After verification, delete unmanaged resources\naws s3 rb s3:\u002F\u002Funauthorized-bucket --force\naws ec2 terminate-instances --instance-ids i-temp-server\n```\n\n### Step 4.3: Revert Changes\n\nFor resources modified outside Terraform:\n\n```bash\n# Re-apply Terraform to restore intended state\nterraform apply\n```\n\n### Step 4.4: Update Terraform (Adopt Changes)\n\nIf the manual change should be kept:\n\n```hcl\n# Update Terraform to match new reality\nresource \"aws_security_group\" \"web\" {\n  # Add the new rule\n  ingress {\n    from_port   = 22\n    to_port     = 22\n    protocol    = \"tcp\"\n    cidr_blocks = [\"10.0.0.0\u002F8\"]  # Restrict if keeping\n  }\n}\n```\n\n---\n\n## Phase 5: Prevention\n\n**Goal**: Prevent future drift.\n\n### Step 5.1: Generate Exclude Policy\n\nFor expected drift (auto-scaling, etc.):\n\n```bash\nsnyk iac update-exclude-policy \\\n  --exclude-unmanaged \\\n  --exclude-changed\n```\n\nThis creates a `.snyk` policy file:\n\n```yaml\nexclude:\n  iac-drift:\n    - aws_autoscaling_group.*\n    - aws_ecs_service.*:desiredCount\n```\n\n### Step 5.2: CI\u002FCD Integration\n\nAdd drift detection to CI\u002FCD:\n\n```yaml\n# GitHub Actions example\n- name: Check for Infrastructure Drift\n  run: |\n    snyk iac describe \\\n      --from=tfstate+s3:\u002F\u002Fmy-bucket\u002Fprod.tfstate \\\n      --json > drift.json\n    \n    # Fail if unmanaged resources found\n    if [ $(jq '.summary.total_unmanaged' drift.json) -gt 0 ]; then\n      echo \"Drift detected!\"\n      exit 1\n    fi\n```\n\n### Step 5.3: Regular Audits\n\nSchedule regular drift audits:\n\n| Frequency | Scope | Purpose |\n|-----------|-------|---------|\n| Daily | Critical resources | Security monitoring |\n| Weekly | All production | Configuration audit |\n| Monthly | All environments | Comprehensive review |\n\n---\n\n## Common Scenarios\n\nFor detailed worked examples, see `EXAMPLES.md`. Brief references:\n\n- **Post-Incident Audit**: Run drift detection with JSON output, filter for security-related resources, identify unauthorized changes, generate incident report, remediate and document.\n- **Pre-Deployment Check**: Run drift detection, fail deployment if drift exists, resolve drift first, then proceed with deployment.\n- **Shadow IT Discovery**: Run drift detection, filter to unmanaged resources, categorize by owner\u002Fpurpose, import or remove as appropriate.\n\n---\n\n## Error Handling\n\n### State Access Error\n\n```\nError: Could not read Terraform state\n\nSolutions:\n1. Verify state file path\n2. Check S3\u002Fbackend permissions\n3. Ensure terraform init has been run\n```\n\n### Cloud Credential Error\n\n```\nError: Authentication failed\n\nSolutions:\n1. Verify cloud credentials\n2. Check IAM permissions for describe\u002Flist\n3. Ensure credentials not expired\n```\n\n### Service Not Supported\n\n```\nWarning: Service X not supported\n\nSolutions:\n1. Check supported services list\n2. Use Terraform plan comparison instead\n3. Report to Snyk for feature request\n```\n\n---\n\n## Constraints\n\n1. **Read-only**: This skill only detects drift, doesn't modify resources\n2. **Credentials required**: Needs cloud provider access\n3. **Service coverage**: Not all resource types supported\n4. **State required**: Must have Terraform state to compare\n5. **Network required**: Needs access to cloud APIs\n",{"name":5,"license":14,"metadata":23,"description":26,"allowed-tools":27,"compatibility":28},{"author":24,"version":25},"Snyk","1.0.0","Detect infrastructure drift between Terraform state and actual cloud resources. Identifies\nunmanaged resources, manual changes, and configuration drift. Use when:\n- User asks to check for infrastructure drift\n- User wants to find unmanaged cloud resources\n- User mentions \"drift detection\" or \"Terraform drift\"\n- User asks to compare cloud state to IaC\n- User wants to audit infrastructure changes\n","Bash Read Write Grep","Requires Snyk CLI installed and authenticated. Uses `snyk iac describe` CLI command\n(shell execution). Cloud provider credentials must be configured (AWS, Azure, or GCP).\nTerraform state file (local or remote) required.\n","main","cd1d94757d590093507ef8ac26299eab8bc20478","claude_skills_libraries\u002Fsnyk-fix\u002Fcommand_directives\u002Fsynchronous_remediation\u002Fskills\u002Fdrift-detector","https:\u002F\u002Fgithub.com\u002FASoudy\u002FAGS","https:\u002F\u002Fgithub.com\u002FASoudy","2026-05-23 09:43:12",{"source":8,"skillName":5,"commands":36,"prompt":46,"zipAvailable":47},[37,40,43],{"tool":38,"command":39},"npx","npx skills add ASoudy\u002FAGS --skill drift-detector",{"tool":41,"command":42},"bunx","bunx skills add ASoudy\u002FAGS --skill drift-detector",{"tool":44,"command":45},"pnpm","pnpm dlx skills add ASoudy\u002FAGS --skill drift-detector","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FASoudy\u002FAGS\u002Fblob\u002Fmain\u002Fclaude_skills_libraries\u002Fsnyk-fix\u002Fcommand_directives\u002Fsynchronous_remediation\u002Fskills\u002Fdrift-detector\u002FSKILL.md",true,[49],{"path":50,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":53,"sourceHtmlUrl":54},"references\u002Fdrift-remediation.md","REFERENCE","参考文档",7504,"https:\u002F\u002Fgithub.com\u002FASoudy\u002FAGS\u002Fblob\u002Fmain\u002Fclaude_skills_libraries\u002Fsnyk-fix\u002Fcommand_directives\u002Fsynchronous_remediation\u002Fskills\u002Fdrift-detector\u002Freferences\u002Fdrift-remediation.md",[56,64,71,78,85,92],{"skillNo":57,"name":58,"nameZh":6,"description":59,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":60,"licenseFileUrl":6,"sourceHtmlUrl":61,"categories":62,"keywords":63,"publishedAt":18},"01M756BTEVC407T0QR8S420JWD","web-typography","Select, pair, and implement typefaces for web projects. Use when the user mentions \"font pairing\", \"which typeface\", \"line height\", \"responsive typography\", \"web font loading\", \"type hierarchy\", \"variable fonts\", \"FOUT\u002FFOIT\", or \"typographic scale\". Also trigger when choosing between system fonts and web fonts, optimizing font loading performance, or designing readable long-form content layouts. Covers readability evaluation, CSS implementation, and performance optimization. For overall UI design systems, see refactoring-ui. For dramatic typographic experiences, see top-design.","MIT","https:\u002F\u002Fgithub.com\u002FASoudy\u002FAGS\u002Fblob\u002Fmain\u002Fclaude_skills_libraries\u002Fwondelai-product-strategy\u002Fweb-typography\u002FSKILL.md",[],[],{"skillNo":65,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":60,"licenseFileUrl":6,"sourceHtmlUrl":68,"categories":69,"keywords":70,"publishedAt":18},"01M756B4RYF2CB17C33X6ZJQT5","ux-heuristics","Evaluate and improve interface usability using heuristic analysis. Use when the user mentions \"usability audit\", \"UX review\", \"users are confused\", \"heuristic evaluation\", \"form usability\", \"navigation problems\", \"Nielsen heuristics\", \"cognitive walkthrough\", or \"usability testing\". Also trigger when reviewing a design for usability issues, improving form completion rates, or evaluating information architecture and navigation. Covers Nielsens 10 heuristics, severity ratings, and information architecture. For visual design fixes, see refactoring-ui. For conversion-focused audits, see cro-methodology.","https:\u002F\u002Fgithub.com\u002FASoudy\u002FAGS\u002Fblob\u002Fmain\u002Fclaude_skills_libraries\u002Fwondelai-product-strategy\u002Fux-heuristics\u002FSKILL.md",[],[],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":60,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"publishedAt":18},"01M756ANVFT0T6BAPV6Y93EPR6","traction-eos","Implement the Entrepreneurial Operating System (EOS) to align vision and execution across a company. Use when the user mentions \"EOS\", \"V\u002FTO\", \"quarterly rocks\", \"Level 10 meetings\", \"accountability chart\", \"IDS process\", \"Entrepreneurial Operating System\", or \"business operating system\". Also trigger when a growing company needs meeting structure, goal-setting frameworks, or a systematic approach to solving recurring organizational issues. Covers the six EOS components: Vision, People, Data, Issues, Process, Traction. For team motivation design, see drive-motivation. For lean experimentation, see lean-startup.","https:\u002F\u002Fgithub.com\u002FASoudy\u002FAGS\u002Fblob\u002Fmain\u002Fclaude_skills_libraries\u002Fwondelai-product-strategy\u002Ftraction-eos\u002FSKILL.md",[],[],{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":60,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":18},"01M756A7NZZMNJN9KZ33QGFHV6","top-design","Create award-winning, immersive web experiences at the level of Awwwards-featured agencies. Use when the user mentions \"premium website\", \"portfolio site\", \"scroll animations\", \"Awwwards quality\", \"brand experience\", \"cinematic web design\", \"parallax storytelling\", or \"agency-quality site\". Also trigger when building landing pages that need to impress, designing creative portfolios, or elevating a standard website to a memorable digital experience. Covers dramatic typography, purposeful motion, scroll-based composition, and performance-optimized animation. For foundational UI, see refactoring-ui. For type selection, see web-typography.","https:\u002F\u002Fgithub.com\u002FASoudy\u002FAGS\u002Fblob\u002Fmain\u002Fclaude_skills_libraries\u002Fwondelai-product-strategy\u002Ftop-design\u002FSKILL.md",[],[],{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":60,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":18},"01M7569J5G1NXM3RR194D52SGB","system-design","Design scalable distributed systems using structured approaches for load balancing, caching, database scaling, and message queues. Use when the user mentions \"system design\", \"scale this\", \"high availability\", \"rate limiter\", \"design a URL shortener\", \"system design interview\", \"capacity planning\", or \"distributed architecture\". Also trigger when estimating infrastructure requirements, choosing between microservices and monoliths, or designing for millions of concurrent users. Covers common system designs and back-of-the-envelope estimation. For data fundamentals, see ddia-systems. For resilience, see release-it.","https:\u002F\u002Fgithub.com\u002FASoudy\u002FAGS\u002Fblob\u002Fmain\u002Fclaude_skills_libraries\u002Fwondelai-product-strategy\u002Fsystem-design\u002FSKILL.md",[],[],{"skillNo":93,"name":94,"nameZh":6,"description":95,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":60,"licenseFileUrl":6,"sourceHtmlUrl":96,"categories":97,"keywords":98,"publishedAt":18},"01M75691MJKE6PBA1EC398EKQT","storybrand-messaging","Clarify brand messaging using narrative structure that positions the customer as hero. Use when the user mentions \"brand message\", \"website copy\", \"elevator pitch\", \"one-liner\", \"messaging isnt resonating\", \"brand script\", \"StoryBrand framework\", or \"customer as hero\". Also trigger when rewriting homepage copy, crafting email nurture sequences, or creating consistent messaging across sales collateral and marketing materials. Covers landing page copy, marketing collateral, and consistent communication. For memorable messaging, see made-to-stick. For product positioning, see obviously-awesome.","https:\u002F\u002Fgithub.com\u002FASoudy\u002FAGS\u002Fblob\u002Fmain\u002Fclaude_skills_libraries\u002Fwondelai-product-strategy\u002Fstorybrand-messaging\u002FSKILL.md",[],[]]