[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6JFV717AKESPNETYCBY0RT0":3,"skill-same:01M6JFV717AKESPNETYCBY0RT0":74},{"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":38,"linkOnly":39,"markdownContent":40,"markdownBody":41,"frontMatter":42,"refName":47,"commitSha":48,"skillDirectory":49,"forksCount":13,"repositoryHtmlUrl":50,"repositoryHomepageUrl":6,"ownerHtmlUrl":51,"ownerBlogUrl":6,"ownerDescription":52,"updatedAt":53,"install":54,"resources":67},"01M6JFV717AKESPNETYCBY0RT0","jira-cli",null,"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.","superhealth\u002Fskills-hub","superhealth","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F6292112?v=4","01M6JA6E7F21BYK5W3E4P270TT","01M6JA6EC0W8MPHKDJVBZDSEZ0",0,"MIT","https:\u002F\u002Fgithub.com\u002Fsuperhealth\u002Fskills-hub\u002Fblob\u002Fmaster\u002Fskills\u002Fcode-and-sorts\u002Fjira-cli\u002FSKILL.md",[],[18,19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37],"jira","jira cli","cli","work","sprints","line","token","project work","project","view","list","edit","command","common","api","issues","create","tasks","init","workflows","2026-11-10 10:12:30",false,"---\nname: jira-cli\ndescription: 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.\nlicense: MIT\ncompatibility: Requires jira-cli installed (https:\u002F\u002Fgithub.com\u002Fankitpokhrel\u002Fjira-cli) and configured with `jira init`. Requires JIRA_API_TOKEN environment variable.\nmetadata:\n  author: Colby Timm\n  version: \"1.0\"\n---\n\n# Jira CLI\n\nInteract with Atlassian Jira from the command line using [jira-cli](https:\u002F\u002Fgithub.com\u002Fankitpokhrel\u002Fjira-cli).\n\n## When to Use\n\n- User asks to create, view, edit, or search Jira issues\u002Ftickets\n- User needs to transition issues through workflow states (To Do → In Progress → Done)\n- User wants to manage sprints, epics, or boards\n- User needs to assign issues, add comments, or log work time\n- User asks about their current tasks or sprint progress\n\n## Prerequisites\n\n1. Install jira-cli: `brew install ankitpokhrel\u002Fjira-cli\u002Fjira-cli` (macOS) or download from [releases](https:\u002F\u002Fgithub.com\u002Fankitpokhrel\u002Fjira-cli\u002Freleases)\n2. Set API token: `export JIRA_API_TOKEN=\"your-token\"`\n3. Initialize: `jira init` and follow prompts\n\n## Issue Commands\n\n### List Issues\n\n```bash\n# List issues in current project\njira issue list\n\n# List my assigned issues\njira issue list -a$(jira me)\n\n# List issues by status\njira issue list -s\"In Progress\"\n\n# List high priority issues\njira issue list -yHigh\n\n# List issues with multiple filters\njira issue list -a$(jira me) -s\"To Do\" -yHigh --created week\n\n# List issues with raw JQL\njira issue list -q \"project = PROJ AND status = 'In Progress'\"\n\n# Plain text output for scripting\njira issue list --plain --columns key,summary,status --no-headers\n```\n\n### Create Issues\n\n```bash\n# Interactive issue creation\njira issue create\n\n# Create with all options specified\njira issue create -tBug -s\"Login button not working\" -b\"Description here\" -yHigh --no-input\n\n# Create a story\njira issue create -tStory -s\"Add user authentication\" -yMedium\n\n# Create with labels and components\njira issue create -tTask -s\"Update dependencies\" -lmaintenance -l\"tech-debt\" -Cbackend\n\n# Create and assign to self\njira issue create -tBug -s\"Fix crash on startup\" -a$(jira me) --no-input\n```\n\n### View Issues\n\n```bash\n# View issue details\njira issue view ISSUE-123\n\n# View with comments\njira issue view ISSUE-123 --comments 10\n\n# View in plain text\njira issue view ISSUE-123 --plain\n\n# Open issue in browser\njira open ISSUE-123\n```\n\n### Edit Issues\n\n```bash\n# Edit summary\njira issue edit ISSUE-123 -s\"Updated summary\"\n\n# Edit description\njira issue edit ISSUE-123 -b\"New description\"\n\n# Edit priority\njira issue edit ISSUE-123 -yHigh\n\n# Add labels\njira issue edit ISSUE-123 -lnew-label\n```\n\n### Transition Issues\n\n```bash\n# Move issue to a new status\njira issue move ISSUE-123 \"In Progress\"\n\n# Move with comment\njira issue move ISSUE-123 \"Done\" --comment \"Completed the task\"\n\n# Move and set resolution\njira issue move ISSUE-123 \"Done\" -RFixed\n```\n\n### Assign Issues\n\n```bash\n# Assign to self\njira issue assign ISSUE-123 $(jira me)\n\n# Assign to specific user\njira issue assign ISSUE-123 username\n\n# Unassign\njira issue assign ISSUE-123 x\n```\n\n### Comments\n\n```bash\n# Add a comment\njira issue comment add ISSUE-123 \"This is my comment\"\n\n# Add comment from editor\njira issue comment add ISSUE-123\n```\n\n### Work Logging\n\n```bash\n# Log time\njira issue worklog add ISSUE-123 \"2h 30m\"\n\n# Log time with comment\njira issue worklog add ISSUE-123 \"1d 4h\" --comment \"Completed feature implementation\" --no-input\n```\n\n### Link & Clone Issues\n\n```bash\n# Link two issues\njira issue link ISSUE-123 ISSUE-456 Blocks\n\n# Unlink issues\njira issue unlink ISSUE-123 ISSUE-456\n\n# Clone an issue\njira issue clone ISSUE-123 -s\"Cloned: New summary\"\n\n# Delete an issue\njira issue delete ISSUE-123\n```\n\n## Epic Commands\n\n```bash\n# List epics\njira epic list\n\n# List epics in table format\njira epic list --table\n\n# Create an epic\njira epic create -n\"Q1 Features\" -s\"Epic summary\" -b\"Epic description\"\n\n# Add issues to epic\njira epic add EPIC-1 ISSUE-123 ISSUE-456\n\n# Remove issues from epic\njira epic remove ISSUE-123 ISSUE-456\n```\n\n## Sprint Commands\n\n```bash\n# List sprints\njira sprint list\n\n# List current\u002Factive sprint\njira sprint list --current\n\n# List my issues in current sprint\njira sprint list --current -a$(jira me)\n\n# Add issues to sprint\njira sprint add SPRINT_ID ISSUE-123 ISSUE-456\n```\n\n## Project & Board Commands\n\n```bash\n# List projects\njira project list\n\n# List boards\njira board list\n\n# List releases\u002Fversions\njira release list\n\n# Open project in browser\njira open\n```\n\n## Utility Commands\n\n```bash\n# Get current username\njira me\n\n# Show help\njira --help\njira issue --help\n\n# Setup shell completion\njira completion bash  # or zsh, fish, powershell\n```\n\n## Common Flags\n\n| Flag | Description |\n| ---- | ----------- |\n| `--plain` | Plain text output (no interactive UI) |\n| `--raw` | Raw JSON output |\n| `--csv` | CSV output |\n| `--no-input` | Skip interactive prompts |\n| `-t, --type` | Issue type (Bug, Story, Task, Epic) |\n| `-s, --summary` | Issue summary\u002Ftitle |\n| `-b, --body` | Issue description |\n| `-y, --priority` | Priority (Highest, High, Medium, Low, Lowest) |\n| `-l, --label` | Labels (repeatable) |\n| `-a, --assignee` | Assignee username |\n| `-r, --reporter` | Reporter username |\n| `-C, --component` | Component name |\n| `-P, --parent` | Parent issue\u002Fepic key |\n| `-q, --jql` | Raw JQL query |\n| `--created` | Filter by creation date (-7d, week, month) |\n| `--order-by` | Sort field |\n| `--reverse` | Reverse sort order |\n\n## Common Workflows\n\n### Start Working on an Issue\n\n```bash\n# Assign to self and move to In Progress\njira issue assign ISSUE-123 $(jira me)\njira issue move ISSUE-123 \"In Progress\"\n```\n\n### Complete an Issue\n\n```bash\n# Log work and close\njira issue worklog add ISSUE-123 \"4h\" --no-input\njira issue move ISSUE-123 \"Done\" --comment \"Completed\" -RFixed\n```\n\n### Daily Standup Review\n\n```bash\n# View my current sprint tasks\njira sprint list --current -a$(jira me)\n```\n\n### Create and Track a Bug\n\n```bash\n# Create bug\njira issue create -tBug -s\"App crashes on login\" -yHigh -lbug --no-input\n# Note the returned issue key, then assign\njira issue assign BUG-123 $(jira me)\njira issue move BUG-123 \"In Progress\"\n```\n\n## Output Examples\n\n| Command | Use Case |\n| ------- | -------- |\n| `jira issue list --plain` | Script-friendly output |\n| `jira issue list --raw` | JSON for parsing |\n| `jira issue list --csv` | Export to spreadsheet |\n\n## Limitations\n\n- Requires prior `jira init` configuration\n- Some features may vary between Jira Cloud and Server\n- Complex custom fields may require `--custom` flag with field IDs\n- Rate limits apply based on Jira instance configuration\n","# Jira CLI\n\nInteract with Atlassian Jira from the command line using [jira-cli](https:\u002F\u002Fgithub.com\u002Fankitpokhrel\u002Fjira-cli).\n\n## When to Use\n\n- User asks to create, view, edit, or search Jira issues\u002Ftickets\n- User needs to transition issues through workflow states (To Do → In Progress → Done)\n- User wants to manage sprints, epics, or boards\n- User needs to assign issues, add comments, or log work time\n- User asks about their current tasks or sprint progress\n\n## Prerequisites\n\n1. Install jira-cli: `brew install ankitpokhrel\u002Fjira-cli\u002Fjira-cli` (macOS) or download from [releases](https:\u002F\u002Fgithub.com\u002Fankitpokhrel\u002Fjira-cli\u002Freleases)\n2. Set API token: `export JIRA_API_TOKEN=\"your-token\"`\n3. Initialize: `jira init` and follow prompts\n\n## Issue Commands\n\n### List Issues\n\n```bash\n# List issues in current project\njira issue list\n\n# List my assigned issues\njira issue list -a$(jira me)\n\n# List issues by status\njira issue list -s\"In Progress\"\n\n# List high priority issues\njira issue list -yHigh\n\n# List issues with multiple filters\njira issue list -a$(jira me) -s\"To Do\" -yHigh --created week\n\n# List issues with raw JQL\njira issue list -q \"project = PROJ AND status = 'In Progress'\"\n\n# Plain text output for scripting\njira issue list --plain --columns key,summary,status --no-headers\n```\n\n### Create Issues\n\n```bash\n# Interactive issue creation\njira issue create\n\n# Create with all options specified\njira issue create -tBug -s\"Login button not working\" -b\"Description here\" -yHigh --no-input\n\n# Create a story\njira issue create -tStory -s\"Add user authentication\" -yMedium\n\n# Create with labels and components\njira issue create -tTask -s\"Update dependencies\" -lmaintenance -l\"tech-debt\" -Cbackend\n\n# Create and assign to self\njira issue create -tBug -s\"Fix crash on startup\" -a$(jira me) --no-input\n```\n\n### View Issues\n\n```bash\n# View issue details\njira issue view ISSUE-123\n\n# View with comments\njira issue view ISSUE-123 --comments 10\n\n# View in plain text\njira issue view ISSUE-123 --plain\n\n# Open issue in browser\njira open ISSUE-123\n```\n\n### Edit Issues\n\n```bash\n# Edit summary\njira issue edit ISSUE-123 -s\"Updated summary\"\n\n# Edit description\njira issue edit ISSUE-123 -b\"New description\"\n\n# Edit priority\njira issue edit ISSUE-123 -yHigh\n\n# Add labels\njira issue edit ISSUE-123 -lnew-label\n```\n\n### Transition Issues\n\n```bash\n# Move issue to a new status\njira issue move ISSUE-123 \"In Progress\"\n\n# Move with comment\njira issue move ISSUE-123 \"Done\" --comment \"Completed the task\"\n\n# Move and set resolution\njira issue move ISSUE-123 \"Done\" -RFixed\n```\n\n### Assign Issues\n\n```bash\n# Assign to self\njira issue assign ISSUE-123 $(jira me)\n\n# Assign to specific user\njira issue assign ISSUE-123 username\n\n# Unassign\njira issue assign ISSUE-123 x\n```\n\n### Comments\n\n```bash\n# Add a comment\njira issue comment add ISSUE-123 \"This is my comment\"\n\n# Add comment from editor\njira issue comment add ISSUE-123\n```\n\n### Work Logging\n\n```bash\n# Log time\njira issue worklog add ISSUE-123 \"2h 30m\"\n\n# Log time with comment\njira issue worklog add ISSUE-123 \"1d 4h\" --comment \"Completed feature implementation\" --no-input\n```\n\n### Link & Clone Issues\n\n```bash\n# Link two issues\njira issue link ISSUE-123 ISSUE-456 Blocks\n\n# Unlink issues\njira issue unlink ISSUE-123 ISSUE-456\n\n# Clone an issue\njira issue clone ISSUE-123 -s\"Cloned: New summary\"\n\n# Delete an issue\njira issue delete ISSUE-123\n```\n\n## Epic Commands\n\n```bash\n# List epics\njira epic list\n\n# List epics in table format\njira epic list --table\n\n# Create an epic\njira epic create -n\"Q1 Features\" -s\"Epic summary\" -b\"Epic description\"\n\n# Add issues to epic\njira epic add EPIC-1 ISSUE-123 ISSUE-456\n\n# Remove issues from epic\njira epic remove ISSUE-123 ISSUE-456\n```\n\n## Sprint Commands\n\n```bash\n# List sprints\njira sprint list\n\n# List current\u002Factive sprint\njira sprint list --current\n\n# List my issues in current sprint\njira sprint list --current -a$(jira me)\n\n# Add issues to sprint\njira sprint add SPRINT_ID ISSUE-123 ISSUE-456\n```\n\n## Project & Board Commands\n\n```bash\n# List projects\njira project list\n\n# List boards\njira board list\n\n# List releases\u002Fversions\njira release list\n\n# Open project in browser\njira open\n```\n\n## Utility Commands\n\n```bash\n# Get current username\njira me\n\n# Show help\njira --help\njira issue --help\n\n# Setup shell completion\njira completion bash  # or zsh, fish, powershell\n```\n\n## Common Flags\n\n| Flag | Description |\n| ---- | ----------- |\n| `--plain` | Plain text output (no interactive UI) |\n| `--raw` | Raw JSON output |\n| `--csv` | CSV output |\n| `--no-input` | Skip interactive prompts |\n| `-t, --type` | Issue type (Bug, Story, Task, Epic) |\n| `-s, --summary` | Issue summary\u002Ftitle |\n| `-b, --body` | Issue description |\n| `-y, --priority` | Priority (Highest, High, Medium, Low, Lowest) |\n| `-l, --label` | Labels (repeatable) |\n| `-a, --assignee` | Assignee username |\n| `-r, --reporter` | Reporter username |\n| `-C, --component` | Component name |\n| `-P, --parent` | Parent issue\u002Fepic key |\n| `-q, --jql` | Raw JQL query |\n| `--created` | Filter by creation date (-7d, week, month) |\n| `--order-by` | Sort field |\n| `--reverse` | Reverse sort order |\n\n## Common Workflows\n\n### Start Working on an Issue\n\n```bash\n# Assign to self and move to In Progress\njira issue assign ISSUE-123 $(jira me)\njira issue move ISSUE-123 \"In Progress\"\n```\n\n### Complete an Issue\n\n```bash\n# Log work and close\njira issue worklog add ISSUE-123 \"4h\" --no-input\njira issue move ISSUE-123 \"Done\" --comment \"Completed\" -RFixed\n```\n\n### Daily Standup Review\n\n```bash\n# View my current sprint tasks\njira sprint list --current -a$(jira me)\n```\n\n### Create and Track a Bug\n\n```bash\n# Create bug\njira issue create -tBug -s\"App crashes on login\" -yHigh -lbug --no-input\n# Note the returned issue key, then assign\njira issue assign BUG-123 $(jira me)\njira issue move BUG-123 \"In Progress\"\n```\n\n## Output Examples\n\n| Command | Use Case |\n| ------- | -------- |\n| `jira issue list --plain` | Script-friendly output |\n| `jira issue list --raw` | JSON for parsing |\n| `jira issue list --csv` | Export to spreadsheet |\n\n## Limitations\n\n- Requires prior `jira init` configuration\n- Some features may vary between Jira Cloud and Server\n- Complex custom fields may require `--custom` flag with field IDs\n- Rate limits apply based on Jira instance configuration\n",{"name":5,"license":14,"metadata":43,"description":7,"compatibility":46},{"author":44,"version":45},"Colby Timm","1.0","Requires jira-cli installed (https:\u002F\u002Fgithub.com\u002Fankitpokhrel\u002Fjira-cli) and configured with `jira init`. Requires JIRA_API_TOKEN environment variable.","master","08cc2532077058aa50e6e18f54695bc256c88152","skills\u002Fcode-and-sorts\u002Fjira-cli","https:\u002F\u002Fgithub.com\u002Fsuperhealth\u002Fskills-hub","https:\u002F\u002Fgithub.com\u002Fsuperhealth","java engineer","2026-04-06 22:07:23",{"source":8,"skillName":5,"commands":55,"prompt":65,"zipAvailable":66},[56,59,62],{"tool":57,"command":58},"npx","npx skills add superhealth\u002Fskills-hub --skill jira-cli",{"tool":60,"command":61},"bunx","bunx skills add superhealth\u002Fskills-hub --skill jira-cli",{"tool":63,"command":64},"pnpm","pnpm dlx skills add superhealth\u002Fskills-hub --skill jira-cli","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fsuperhealth\u002Fskills-hub\u002Fblob\u002Fmaster\u002Fskills\u002Fcode-and-sorts\u002Fjira-cli\u002FSKILL.md",true,[68],{"path":69,"resourceType":70,"resourceTypeDesc":71,"sizeBytes":72,"sourceHtmlUrl":73},"skill-report.json","REFERENCE","参考文档",16961,"https:\u002F\u002Fgithub.com\u002Fsuperhealth\u002Fskills-hub\u002Fblob\u002Fmaster\u002Fskills\u002Fcode-and-sorts\u002Fjira-cli\u002Fskill-report.json",[75,106,134,147,163,186],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":86,"publishedAt":38},"01M6MC9F3WHV8S8FZ2W4TRB0FE","vercel-react-best-practices","React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React\u002FNext.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.","https:\u002F\u002Fgithub.com\u002Fsuperhealth\u002Fskills-hub\u002Fblob\u002Fmaster\u002Fskills\u002Fzhanlincui\u002Fvercel-react-best-practices\u002FSKILL.md",[81],{"categoryNo":82,"categoryName":83,"taxonomyType":84,"taxonomyTypeDesc":85},"01JBSEEDCAT000000000000009","前端开发","SCENARIO","使用场景",[87,88,89,90,91,92,93,94,95,96,97,98,99,100,35,101,102,103,104,105],"react","vercel react best practices","best practices","vercel","react best practices","data fetching","code","triggers","pages","next","patterns","refactoring","data","Optimization","guidelines","react components","components","performance","writing",{"skillNo":107,"name":108,"nameZh":6,"description":109,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":110,"categories":111,"keywords":116,"publishedAt":38},"01M6MB8KWE1Q5A5KERR7RFTQWP","vue-testing-best-practices","Use for Vue.js testing. Covers Vitest, Vue Test Utils, component testing, mocking, testing patterns, and Playwright for E2E testing.","https:\u002F\u002Fgithub.com\u002Fsuperhealth\u002Fskills-hub\u002Fblob\u002Fmaster\u002Fskills\u002Fvuejs-ai\u002Fvue-testing-best-practices\u002FSKILL.md",[112,115],{"categoryNo":113,"categoryName":114,"taxonomyType":84,"taxonomyTypeDesc":85},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":82,"categoryName":83,"taxonomyType":84,"taxonomyTypeDesc":85},[117,118,119,89,120,121,122,123,124,125,126,97,127,128,129,130,131,132,133],"vue testing best practices","testing best practices","vue","testing","testing patterns","js","e2e","vitest","use","component","test","mocking","for","utils","e2e testing","github","playwright",{"skillNo":135,"name":136,"nameZh":6,"description":137,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":138,"categories":139,"keywords":141,"publishedAt":38},"01M6MB8GK06M6GA4KVYNDV1BZP","vue-router-best-practices","Vue Router 4 patterns, navigation guards, route params, and route-component lifecycle interactions.","https:\u002F\u002Fgithub.com\u002Fsuperhealth\u002Fskills-hub\u002Fblob\u002Fmaster\u002Fskills\u002Fvuejs-ai\u002Fvue-router-best-practices\u002FSKILL.md",[140],{"categoryNo":82,"categoryName":83,"taxonomyType":84,"taxonomyTypeDesc":85},[89,119,142,143,144,97,145,146,126,132],"router","vue router best practices","route","navigation","lifecycle",{"skillNo":148,"name":149,"nameZh":6,"description":150,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":151,"categories":152,"keywords":154,"publishedAt":38},"01M6MB8DQF21TZMQ9XC3745ERW","vue-pinia-best-practices","Pinia stores, state management patterns, store setup, and reactivity with stores.","https:\u002F\u002Fgithub.com\u002Fsuperhealth\u002Fskills-hub\u002Fblob\u002Fmaster\u002Fskills\u002Fvuejs-ai\u002Fvue-pinia-best-practices\u002FSKILL.md",[153],{"categoryNo":82,"categoryName":83,"taxonomyType":84,"taxonomyTypeDesc":85},[155,156,119,89,157,158,97,159,160,161,162,132],"vue pinia best practices","pinia","with","store","management","state","state management","setup",{"skillNo":164,"name":165,"nameZh":6,"description":166,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":167,"categories":168,"keywords":178,"publishedAt":38},"01M6MB8A7MC08747J9TV4GWQ9A","vue-options-api-best-practices","Vue 3 Options API style (data(), methods, this context). Each reference shows Options API solution only.","https:\u002F\u002Fgithub.com\u002Fsuperhealth\u002Fskills-hub\u002Fblob\u002Fmaster\u002Fskills\u002Fvuejs-ai\u002Fvue-options-api-best-practices\u002FSKILL.md",[169,170,173],{"categoryNo":82,"categoryName":83,"taxonomyType":84,"taxonomyTypeDesc":85},{"categoryNo":171,"categoryName":172,"taxonomyType":84,"taxonomyTypeDesc":85},"01JBSEEDCAT000000000000010","后端与接口",{"categoryNo":174,"categoryName":175,"taxonomyType":176,"taxonomyTypeDesc":177},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[119,179,180,32,89,181,182,183,184,99,132,185],"options","vue options api best practices","methods","reference","only","context","style",{"skillNo":187,"name":188,"nameZh":6,"description":189,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":190,"categories":191,"keywords":193,"publishedAt":38},"01M6MB85ZTQC24Q04X49MM4YXN","vue-development-guides","A collection of best practices and tips for developing applications using Vue.js. This skill MUST be apply when developing, refactoring or reviewing Vue.js or Nuxt projects.","https:\u002F\u002Fgithub.com\u002Fsuperhealth\u002Fskills-hub\u002Fblob\u002Fmaster\u002Fskills\u002Fvuejs-ai\u002Fvue-development-guides\u002FSKILL.md",[192],{"categoryNo":82,"categoryName":83,"taxonomyType":84,"taxonomyTypeDesc":85},[194,119,195,196,132,197,198,129,26,199,200,122,98,201,202,89],"development","guides","vue development guides","tips","apply","nuxt","projects","collection","applications"]