[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7ESTR2TWM6JJJPHW309M1TP":3,"skill-same:01M7ESTR2TWM6JJJPHW309M1TP":45},{"skillNo":4,"name":5,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"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":23,"commitSha":24,"skillDirectory":25,"forksCount":26,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":29,"ownerDescription":6,"updatedAt":30,"install":31,"resources":44},"01M7ESTR2TWM6JJJPHW309M1TP","ams-linear-pro-dev",null,"TanNhatCMS\u002Fjarvis","TanNhatCMS","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F113796420?v=4","01M753MV17KG5CD3152G3WQEQY","KietNT","01M7EKEDYVYQ6PWVJJMZ911VMX",0,"MIT","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fams-linear-pro-dev\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: linear-pro-dev\ndescription: Run Linear effectively: issue workflow, cycles, triage, integrations, and team habits. Use when configuring Linear or improving team process around it.\ncategory: development\n---\n\n# Linear Pro (Dev)\n\n## Overview\n\nLinear's appeal — **speed, opinionated workflow, and GitHub-native integration** — works best when\nteams embrace its opinions instead of rebuilding Jira inside it. Professional Linear usage means\nlean issue hygiene, cycles for cadence, triage as a habit, and integrations (GitHub, Slack) doing\nthe status-syncing automatically.\n\nThe through-line: Linear rewards lightness — keep process minimal, issues current, and let the\nintegrations carry the coordination.\n\n## When to use\n\n- Setting up Linear for a software team.\n- Establishing issue, cycle, and triage habits.\n- Integrating Linear with GitHub and Slack.\n- Improving backlog hygiene or planning cadence.\n- Migrating from Jira (or heavier tools) to Linear.\n\n## Core concepts\n\n- **Issues, lightweight.** Title + description (with template: context, proposal\u002Foutcome,\n  acceptance criteria), priority (Urgent\u002FHigh\u002FMedium\u002FLow — use honestly), labels for areas,\n  estimate (points or t-shirt — pick one, keep it rough). Creation friction near zero is the\n  feature — don't add required-field ceremony.\n- **Cycles for cadence.** Time-boxed iterations (1–2 weeks) with planned scope; Linear tracks\n  progress automatically from issue states. Don't over-plan cycles — they're a heartbeat, not a\n  contract. Carry-over is data, not failure.\n- **Triage inbox.** New issues land in Triage; someone (rotating duty) routes daily: accept\n  (prioritize + label), decline (with reason — decisions are progress), or ask for clarification.\n  An untriaged inbox becomes a black hole; daily triage keeps it a queue.\n- **Workflow states, minimal.** Backlog → Todo → In Progress → In Review → Done (+ Canceled).\n  Resist adding statuses — Linear's power is the default workflow; customize only with real need.\n- **GitHub integration.** Branch names (`feat\u002Fabc-123-short-desc`) auto-link; PRs closing issues\n  (`Fixes ABC-123`) transition automatically; commit\u002FPR activity appears on the issue. The issue\n  becomes the source of truth without manual status updates.\n- **Projects for initiatives.** Cross-cutting efforts (launches, migrations) as Linear Projects\n  with milestones and documents — the layer above issues for stakeholder visibility without\n  polluting the backlog.\n\n## Practical workflow\n\n1. **Set up the team simply.** Default workflow states, a few labels (area: frontend\u002Fbackend,\n   type: bug\u002Ffeature\u002Fchore), one estimate scale, issue templates for bugs and features.\n2. **Establish triage.** Daily 10-minute triage rotation: every new issue gets a decision within\n   24h. Backlog stays a queue, not a graveyard.\n3. **Wire integrations.** GitHub (auto-link branches\u002FPRs, auto-close on merge), Slack (cycle\n   updates, mentions), and CI status on issues. Manual status syncing should approach zero.\n4. **Run cycles lightly.** Plan the cycle from a triaged backlog (capacity-aware, not\n   wishful); daily async check-ins over meetings; end-of-cycle: demo what shipped, note\n   carry-over honestly.\n5. **Keep hygiene automatic.** Stale-issue nudges (automation or triage habit), done-issues\n   linked to PRs, canceled-with-reason instead of silent deletion.\n6. **Review the system monthly.** Are estimates roughly right? Is triage keeping up? Are cycles\n   too full? Adjust the *process*, not just the issues — Linear's simplicity makes process\n   problems visible fast.\n\nTeam habits checklist:\n\n```text\n[ ] Issue template used: context, acceptance criteria, priority set honestly\n[ ] Triage inbox cleared daily (rotating duty)\n[ ] Branches\u002FPRs reference issue IDs — status flows automatically\n[ ] Cycle scope fits capacity; carry-over reviewed, not hidden\n[ ] Labels consistent; no label sprawl\n[ ] Canceled issues have a reason (one line — future archaeology)\n[ ] Monthly: review estimates, cycle health, and process friction\n```\n\n## Common pitfalls\n\n- **Rebuilding Jira in Linear.** 20 custom statuses, 15 required fields, 6 issue types —\n  defeats the entire point. Embrace the opinions; customize only with evidence of need.\n- **No triage habit.** Issues pile in Triage for weeks; reporters stop filing. Daily triage is\n  the cheapest high-value Linear habit.\n- **Priority inflation.** Everything \"Urgent\" means nothing is. Urgent = drop everything;\n  enforce the semantics or the scale is decorative.\n- **Cycle over-planning.** Treating cycles as commitments with 100% allocation — no slack for\n  bugs, reviews, or reality. Plan to ~70%; protect the buffer.\n- **Manual status syncing.** Updating Linear by hand when the GitHub integration does it free.\n  Wire the integration; trust the automation.\n- **Dead backlog.** Hundreds of untouched backlog issues — close or icebox them. A backlog is a\n  set of *options*, curated; a graveyard is just guilt.\n- **Skipping retros.** Linear makes process friction visible (carry-over, stale issues) — but\n  visibility without retros is just dashboard decoration. Review and adjust monthly.\n","# Linear Pro (Dev)\n\n## Overview\n\nLinear's appeal — **speed, opinionated workflow, and GitHub-native integration** — works best when\nteams embrace its opinions instead of rebuilding Jira inside it. Professional Linear usage means\nlean issue hygiene, cycles for cadence, triage as a habit, and integrations (GitHub, Slack) doing\nthe status-syncing automatically.\n\nThe through-line: Linear rewards lightness — keep process minimal, issues current, and let the\nintegrations carry the coordination.\n\n## When to use\n\n- Setting up Linear for a software team.\n- Establishing issue, cycle, and triage habits.\n- Integrating Linear with GitHub and Slack.\n- Improving backlog hygiene or planning cadence.\n- Migrating from Jira (or heavier tools) to Linear.\n\n## Core concepts\n\n- **Issues, lightweight.** Title + description (with template: context, proposal\u002Foutcome,\n  acceptance criteria), priority (Urgent\u002FHigh\u002FMedium\u002FLow — use honestly), labels for areas,\n  estimate (points or t-shirt — pick one, keep it rough). Creation friction near zero is the\n  feature — don't add required-field ceremony.\n- **Cycles for cadence.** Time-boxed iterations (1–2 weeks) with planned scope; Linear tracks\n  progress automatically from issue states. Don't over-plan cycles — they're a heartbeat, not a\n  contract. Carry-over is data, not failure.\n- **Triage inbox.** New issues land in Triage; someone (rotating duty) routes daily: accept\n  (prioritize + label), decline (with reason — decisions are progress), or ask for clarification.\n  An untriaged inbox becomes a black hole; daily triage keeps it a queue.\n- **Workflow states, minimal.** Backlog → Todo → In Progress → In Review → Done (+ Canceled).\n  Resist adding statuses — Linear's power is the default workflow; customize only with real need.\n- **GitHub integration.** Branch names (`feat\u002Fabc-123-short-desc`) auto-link; PRs closing issues\n  (`Fixes ABC-123`) transition automatically; commit\u002FPR activity appears on the issue. The issue\n  becomes the source of truth without manual status updates.\n- **Projects for initiatives.** Cross-cutting efforts (launches, migrations) as Linear Projects\n  with milestones and documents — the layer above issues for stakeholder visibility without\n  polluting the backlog.\n\n## Practical workflow\n\n1. **Set up the team simply.** Default workflow states, a few labels (area: frontend\u002Fbackend,\n   type: bug\u002Ffeature\u002Fchore), one estimate scale, issue templates for bugs and features.\n2. **Establish triage.** Daily 10-minute triage rotation: every new issue gets a decision within\n   24h. Backlog stays a queue, not a graveyard.\n3. **Wire integrations.** GitHub (auto-link branches\u002FPRs, auto-close on merge), Slack (cycle\n   updates, mentions), and CI status on issues. Manual status syncing should approach zero.\n4. **Run cycles lightly.** Plan the cycle from a triaged backlog (capacity-aware, not\n   wishful); daily async check-ins over meetings; end-of-cycle: demo what shipped, note\n   carry-over honestly.\n5. **Keep hygiene automatic.** Stale-issue nudges (automation or triage habit), done-issues\n   linked to PRs, canceled-with-reason instead of silent deletion.\n6. **Review the system monthly.** Are estimates roughly right? Is triage keeping up? Are cycles\n   too full? Adjust the *process*, not just the issues — Linear's simplicity makes process\n   problems visible fast.\n\nTeam habits checklist:\n\n```text\n[ ] Issue template used: context, acceptance criteria, priority set honestly\n[ ] Triage inbox cleared daily (rotating duty)\n[ ] Branches\u002FPRs reference issue IDs — status flows automatically\n[ ] Cycle scope fits capacity; carry-over reviewed, not hidden\n[ ] Labels consistent; no label sprawl\n[ ] Canceled issues have a reason (one line — future archaeology)\n[ ] Monthly: review estimates, cycle health, and process friction\n```\n\n## Common pitfalls\n\n- **Rebuilding Jira in Linear.** 20 custom statuses, 15 required fields, 6 issue types —\n  defeats the entire point. Embrace the opinions; customize only with evidence of need.\n- **No triage habit.** Issues pile in Triage for weeks; reporters stop filing. Daily triage is\n  the cheapest high-value Linear habit.\n- **Priority inflation.** Everything \"Urgent\" means nothing is. Urgent = drop everything;\n  enforce the semantics or the scale is decorative.\n- **Cycle over-planning.** Treating cycles as commitments with 100% allocation — no slack for\n  bugs, reviews, or reality. Plan to ~70%; protect the buffer.\n- **Manual status syncing.** Updating Linear by hand when the GitHub integration does it free.\n  Wire the integration; trust the automation.\n- **Dead backlog.** Hundreds of untouched backlog issues — close or icebox them. A backlog is a\n  set of *options*, curated; a graveyard is just guilt.\n- **Skipping retros.** Linear makes process friction visible (carry-over, stale issues) — but\n  visibility without retros is just dashboard decoration. Review and adjust monthly.\n",{},"main","af388a77c2fe5e0b4fd879cca4300a0ffa9a6579","skills\u002Fams-linear-pro-dev",1,"https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis","https:\u002F\u002Fgithub.com\u002FTanNhatCMS","https:\u002F\u002Fmrkiet.name.vn","2026-11-07 14:23:08",{"source":7,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add TanNhatCMS\u002Fjarvis --skill ams-linear-pro-dev",{"tool":37,"command":38},"bunx","bunx skills add TanNhatCMS\u002Fjarvis --skill ams-linear-pro-dev",{"tool":40,"command":41},"pnpm","pnpm dlx skills add TanNhatCMS\u002Fjarvis --skill ams-linear-pro-dev","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fams-linear-pro-dev\u002FSKILL.md",true,[],[46,53,61,68,75,82],{"skillNo":47,"name":48,"nameZh":6,"description":49,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":50,"categories":51,"keywords":52,"publishedAt":18},"01M7EWYJR0J8DARY7E59Z6Y9MV","web-scrape","Turn web pages into LLM-ready markdown via the Firecrawl API (renders JS, anti-bot handling). Use when browser_open\u002Ffetch fails on JS-heavy pages, or when you need clean markdown\u002Fstructured extraction from a site. Requires FIRECRAWL_API_KEY.","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fweb-scrape\u002FSKILL.md",[],[],{"skillNo":54,"name":55,"nameZh":6,"description":56,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":57,"sourceHtmlUrl":58,"categories":59,"keywords":60,"publishedAt":18},"01M7EWYBN5P6F2AJG3FR24T9BP","design-taste-frontend","tasteskill v2, the anti-slop frontend skill. Art direction for websites, distilled from a study of 247 curated gallery sites (One Page Love, Awwwards Sites of the Day). Deals researched directions (idea, composition, type, palette, photographs, section blueprints) from a library, enforces a strict no-slop house style with a real-browser inspector, and runs a look-and-fix loop on screenshots. Use this whenever you build, design, redesign, restyle, polish or review a landing page, marketing site, portfolio, product page, one-pager, hero or any public-facing web page, in any stack (HTML\u002FCSS, React, Next.js, Vue, Svelte, Astro, Tailwind) — also when the user says a page looks generic, templated, \"AI-made\", sloppy, or asks to make it look designed, premium, award-level or less like every other site. Not for dashboards or app screens.","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Ftaste-design\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Ftaste-design\u002FSKILL.md",[],[],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":18},"01M7EWY8FQFNQ2GB7NZZWGSSDX","test-driven-development","Use when implementing any feature or bugfix, before writing implementation code","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fsuperpowers-tdd\u002FSKILL.md",[],[],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":18},"01M7EWY5SHBFRH1HDHVWM9K7TV","systematic-debugging","Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fsuperpowers-debugging\u002FSKILL.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":18},"01M7EWY3NM0Z0JAKS7HDZ24K66","requesting-code-review","Use when completing tasks, implementing major features, or before merging to verify work meets requirements","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fsuperpowers-code-review\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":18},"01M7EWY0WRMWX4M9ZFY0WKC593","brainstorming","You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation).","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fsuperpowers-brainstorming\u002FSKILL.md",[],[]]