[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7EVAB0DDEWMMMS4XV15T81C":3,"skill-same:01M7EVAB0DDEWMMMS4XV15T81C":47},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":25,"commitSha":26,"skillDirectory":27,"forksCount":28,"repositoryHtmlUrl":29,"repositoryHomepageUrl":6,"ownerHtmlUrl":30,"ownerBlogUrl":31,"ownerDescription":6,"updatedAt":32,"install":33,"resources":46},"01M7EVAB0DDEWMMMS4XV15T81C","pharmacogenomics-basics",null,"Pharmacogenomics in practice — key gene-drug pairs, phenotype translation, and clinical implementation.","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-pharmacogenomics-basics\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: pharmacogenomics-basics\ndescription: Pharmacogenomics in practice — key gene-drug pairs, phenotype translation, and clinical implementation.\ncategory: scientific\n---\n\n## Overview\n\npharmacogenomics-basics covers using genetic variation to guide drug therapy: the high-evidence\ngene-drug pairs, translating genotypes to metabolizer phenotypes, and implementing testing in\nclinical workflows. It focuses on what's actionable now — a small set of well-validated pairs —\nrather than the polygenic future.\n\n## When to use\n\n- Learning the actionable gene-drug pairs (CPIC\u002FDPWG guidelines).\n- Translating genotypes to phenotypes: CYP2D6, CYP2C19, TPMT, DPYD activity scores.\n- Preemptive vs reactive testing strategies.\n- Interpreting pharmacogenomic test reports.\n- Implementing: CDS alerts, EHR integration, result portability.\n- Counseling patients on pharmacogenomic results.\n\n## Core concepts\n\n- **The high-value pairs.** CYP2C19-clopidogrel (poor metabolizers: reduced activation, more\n  events — use alternative antiplatelet), CYP2D6-codeine\u002Ftramadol (ultrarapid: toxicity;\n  poor: no analgesia), TPMT\u002FNUDT15-thiopurines (poor metabolizers: severe myelosuppression),\n  DPYD-fluoropyrimidines (poor metabolizers: severe toxicity), HLA-B*57:01-abacavir\n  (hypersensitivity — test required), HLA-B*15:02-carbamazepine (SJS\u002FTEN in Asian ancestry),\n  SLCO1B1-simvastatin (myopathy risk), CYP2C9\u002FVKORC1-warfarin (dosing). CPIC and DPWG\n  guidelines give the actionable recommendations — follow them, not marketing.\n- **Genotype → phenotype.** Star alleles (*1 = normal function, *2\u002F*3... = defined variants);\n  activity scores sum allele activities; phenotype bins: poor, intermediate, normal, rapid,\n  ultrarapid metabolizer. Phenoconversion (drug interactions overriding genetics — e.g. a CYP2D6\n  normal metabolizer on paroxetine functions as poor) must be considered alongside genotype.\n- **CPIC levels.** CPIC assigns evidence levels; focus on level A\u002FB pairs for clinical action.\n  Most gene-drug associations in the literature are not actionable — actionability requires\n  replicated evidence plus a viable alternative therapy.\n- **Preemptive vs reactive.** Preemptive panel testing (genotype once, use for life) is\n  cost-effective where prescribing volume is high; reactive testing (order when prescribing a\n  high-risk drug) fits low-volume settings. Either way, results must live in the EHR\n  discretely (not as PDF scans) to fire clinical decision support.\n- **Implementation.** CDS alerts at prescribing (interruptive for high-risk, passive otherwise);\n  pharmacist review workflows; result portability across encounters and systems. The genetics\n  is the easy part — workflow integration determines whether testing changes prescribing.\n- **Ancestry matters.** Allele frequencies differ by ancestry (HLA-B*15:02 relevant in Southeast\n  Asian ancestry; CYP2D6 duplications in North African\u002FMiddle Eastern populations). Panels must\n  cover population-relevant alleles; \"normal\" results from incomplete panels are misleading.\n- **Limits.** Pharmacogenomics explains a fraction of response variability — age, organ\n  function, interactions, and adherence usually dominate. Don't let a normal genotype provide\n  false reassurance, or an abnormal one deny effective therapy without alternatives.\n- **Counseling.** Results are probabilistic, not deterministic; most findings have implications\n  for relatives (germline); GINA-type protections vary by jurisdiction — know the local legal\n  context before testing.\n\n## Practical workflow\n\n1. **Select pairs.** Start with CPIC level-A pairs relevant to your prescribing volume.\n2. **Choose strategy.** Preemptive panel vs reactive single-gene, based on volume and\n   infrastructure.\n3. **Test.** Validated panel covering ancestry-appropriate alleles; clear phenotype translation\n   in the report.\n4. **Integrate.** Discrete EHR results + CDS alerts + pharmacist workflow; portability across\n   encounters.\n5. **Act.** Follow CPIC\u002FDPWG recommendations; document the genotype-guided decision;\n   consider phenoconversion from interacting drugs.\n6. **Counsel.** Explain what the result means and doesn't mean; discuss familial implications.\n7. **Monitor.** Track alert override rates, prescribing changes, and outcomes; update as\n   guidelines evolve.\n\n## Common pitfalls\n\n- Acting on low-evidence associations without CPIC\u002FDPWG backing.\n- Incomplete panels missing ancestry-relevant alleles (\"normal\" by omission).\n- PDF-only results that can't drive CDS (testing without implementation).\n- Ignoring phenoconversion (genotype overridden by interacting drugs).\n- Alert fatigue from poorly tuned pharmacogenomic CDS.\n- Overpromising: genetics as a small piece of response variability.\n- No plan for result portability (re-testing at every institution).\n- Copy-number variants (CYP2D6 duplications\u002Fdeletions) missed by SNP-only panels.\n","## Overview\n\npharmacogenomics-basics covers using genetic variation to guide drug therapy: the high-evidence\ngene-drug pairs, translating genotypes to metabolizer phenotypes, and implementing testing in\nclinical workflows. It focuses on what's actionable now — a small set of well-validated pairs —\nrather than the polygenic future.\n\n## When to use\n\n- Learning the actionable gene-drug pairs (CPIC\u002FDPWG guidelines).\n- Translating genotypes to phenotypes: CYP2D6, CYP2C19, TPMT, DPYD activity scores.\n- Preemptive vs reactive testing strategies.\n- Interpreting pharmacogenomic test reports.\n- Implementing: CDS alerts, EHR integration, result portability.\n- Counseling patients on pharmacogenomic results.\n\n## Core concepts\n\n- **The high-value pairs.** CYP2C19-clopidogrel (poor metabolizers: reduced activation, more\n  events — use alternative antiplatelet), CYP2D6-codeine\u002Ftramadol (ultrarapid: toxicity;\n  poor: no analgesia), TPMT\u002FNUDT15-thiopurines (poor metabolizers: severe myelosuppression),\n  DPYD-fluoropyrimidines (poor metabolizers: severe toxicity), HLA-B*57:01-abacavir\n  (hypersensitivity — test required), HLA-B*15:02-carbamazepine (SJS\u002FTEN in Asian ancestry),\n  SLCO1B1-simvastatin (myopathy risk), CYP2C9\u002FVKORC1-warfarin (dosing). CPIC and DPWG\n  guidelines give the actionable recommendations — follow them, not marketing.\n- **Genotype → phenotype.** Star alleles (*1 = normal function, *2\u002F*3... = defined variants);\n  activity scores sum allele activities; phenotype bins: poor, intermediate, normal, rapid,\n  ultrarapid metabolizer. Phenoconversion (drug interactions overriding genetics — e.g. a CYP2D6\n  normal metabolizer on paroxetine functions as poor) must be considered alongside genotype.\n- **CPIC levels.** CPIC assigns evidence levels; focus on level A\u002FB pairs for clinical action.\n  Most gene-drug associations in the literature are not actionable — actionability requires\n  replicated evidence plus a viable alternative therapy.\n- **Preemptive vs reactive.** Preemptive panel testing (genotype once, use for life) is\n  cost-effective where prescribing volume is high; reactive testing (order when prescribing a\n  high-risk drug) fits low-volume settings. Either way, results must live in the EHR\n  discretely (not as PDF scans) to fire clinical decision support.\n- **Implementation.** CDS alerts at prescribing (interruptive for high-risk, passive otherwise);\n  pharmacist review workflows; result portability across encounters and systems. The genetics\n  is the easy part — workflow integration determines whether testing changes prescribing.\n- **Ancestry matters.** Allele frequencies differ by ancestry (HLA-B*15:02 relevant in Southeast\n  Asian ancestry; CYP2D6 duplications in North African\u002FMiddle Eastern populations). Panels must\n  cover population-relevant alleles; \"normal\" results from incomplete panels are misleading.\n- **Limits.** Pharmacogenomics explains a fraction of response variability — age, organ\n  function, interactions, and adherence usually dominate. Don't let a normal genotype provide\n  false reassurance, or an abnormal one deny effective therapy without alternatives.\n- **Counseling.** Results are probabilistic, not deterministic; most findings have implications\n  for relatives (germline); GINA-type protections vary by jurisdiction — know the local legal\n  context before testing.\n\n## Practical workflow\n\n1. **Select pairs.** Start with CPIC level-A pairs relevant to your prescribing volume.\n2. **Choose strategy.** Preemptive panel vs reactive single-gene, based on volume and\n   infrastructure.\n3. **Test.** Validated panel covering ancestry-appropriate alleles; clear phenotype translation\n   in the report.\n4. **Integrate.** Discrete EHR results + CDS alerts + pharmacist workflow; portability across\n   encounters.\n5. **Act.** Follow CPIC\u002FDPWG recommendations; document the genotype-guided decision;\n   consider phenoconversion from interacting drugs.\n6. **Counsel.** Explain what the result means and doesn't mean; discuss familial implications.\n7. **Monitor.** Track alert override rates, prescribing changes, and outcomes; update as\n   guidelines evolve.\n\n## Common pitfalls\n\n- Acting on low-evidence associations without CPIC\u002FDPWG backing.\n- Incomplete panels missing ancestry-relevant alleles (\"normal\" by omission).\n- PDF-only results that can't drive CDS (testing without implementation).\n- Ignoring phenoconversion (genotype overridden by interacting drugs).\n- Alert fatigue from poorly tuned pharmacogenomic CDS.\n- Overpromising: genetics as a small piece of response variability.\n- No plan for result portability (re-testing at every institution).\n- Copy-number variants (CYP2D6 duplications\u002Fdeletions) missed by SNP-only panels.\n",{"name":5,"category":24,"description":7},"scientific","main","af388a77c2fe5e0b4fd879cca4300a0ffa9a6579","skills\u002Fams-pharmacogenomics-basics",1,"https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis","https:\u002F\u002Fgithub.com\u002FTanNhatCMS","https:\u002F\u002Fmrkiet.name.vn","2026-11-07 14:23:08",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add TanNhatCMS\u002Fjarvis --skill pharmacogenomics-basics",{"tool":39,"command":40},"bunx","bunx skills add TanNhatCMS\u002Fjarvis --skill pharmacogenomics-basics",{"tool":42,"command":43},"pnpm","pnpm dlx skills add TanNhatCMS\u002Fjarvis --skill pharmacogenomics-basics","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fams-pharmacogenomics-basics\u002FSKILL.md",true,[],[48,55,63,70,77,84],{"skillNo":49,"name":50,"nameZh":6,"description":51,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":52,"categories":53,"keywords":54,"publishedAt":19},"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":56,"name":57,"nameZh":6,"description":58,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":59,"sourceHtmlUrl":60,"categories":61,"keywords":62,"publishedAt":19},"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":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":19},"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":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":19},"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":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":19},"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":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":19},"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",[],[]]