[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6JD1KT66FNTPF7MYM3148GJ":3,"skill-same:01M6JD1KT66FNTPF7MYM3148GJ":72},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":22,"publishedAt":43,"linkOnly":44,"markdownContent":45,"markdownBody":46,"frontMatter":47,"refName":50,"commitSha":51,"skillDirectory":52,"forksCount":53,"repositoryHtmlUrl":54,"repositoryHomepageUrl":55,"ownerHtmlUrl":56,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":57,"install":58,"resources":71},"01M6JD1KT66FNTPF7MYM3148GJ","healthcare-emr-patterns",null,"EMR\u002FEHR development patterns for healthcare applications. Clinical safety, encounter workflows, prescription generation, clinical decision support integration, and accessibility-first UI for medical data entry.","S3YED\u002Fappie-kit","S3YED","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F62743867?v=4","01M6JBKBRRVP6KMS0VWZ27T3R6","01M6JBKBX0KG30284PW1DBYJT1",14,"MIT","https:\u002F\u002Fgithub.com\u002FS3YED\u002Fappie-kit\u002Fblob\u002Fmaster\u002Fskills\u002Fecc\u002Fhealthcare-emr-patterns\u002FSKILL.md",[17],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42],"healthcare emr patterns","EMR","patterns","healthcare","for","support","clinical","medical","generation","decision support","decision","clinical decision support","first","applications","Safety","data","integration","ui","development","workflows","2026-11-10 10:12:30",false,"---\nname: healthcare-emr-patterns\ndescription: EMR\u002FEHR development patterns for healthcare applications. Clinical safety, encounter workflows, prescription generation, clinical decision support integration, and accessibility-first UI for medical data entry.\norigin: Health1 Super Speciality Hospitals — contributed by Dr. Keyur Patel\nversion: \"1.0.0\"\n---\n\n# Healthcare EMR Development Patterns\n\nPatterns for building Electronic Medical Record (EMR) and Electronic Health Record (EHR) systems. Prioritizes patient safety, clinical accuracy, and practitioner efficiency.\n\n## When to Use\n\n- Building patient encounter workflows (complaint, exam, diagnosis, prescription)\n- Implementing clinical note-taking (structured + free text + voice-to-text)\n- Designing prescription\u002Fmedication modules with drug interaction checking\n- Integrating Clinical Decision Support Systems (CDSS)\n- Building lab result displays with reference range highlighting\n- Implementing audit trails for clinical data\n- Designing healthcare-accessible UIs for clinical data entry\n\n## How It Works\n\n### Patient Safety First\n\nEvery design decision must be evaluated against: \"Could this harm a patient?\"\n\n- Drug interactions MUST alert, not silently pass\n- Abnormal lab values MUST be visually flagged\n- Critical vitals MUST trigger escalation workflows\n- No clinical data modification without audit trail\n\n### Single-Page Encounter Flow\n\nClinical encounters should flow vertically on a single page — no tab switching:\n\n```\nPatient Header (sticky — always visible)\n├── Demographics, allergies, active medications\n│\nEncounter Flow (vertical scroll)\n├── 1. Chief Complaint (structured templates + free text)\n├── 2. History of Present Illness\n├── 3. Physical Examination (system-wise)\n├── 4. Vitals (auto-trigger clinical scoring)\n├── 5. Diagnosis (ICD-10\u002FSNOMED search)\n├── 6. Medications (drug DB + interaction check)\n├── 7. Investigations (lab\u002Fradiology orders)\n├── 8. Plan & Follow-up\n└── 9. Sign \u002F Lock \u002F Print\n```\n\n### Smart Template System\n\n```typescript\ninterface ClinicalTemplate {\n  id: string;\n  name: string;             \u002F\u002F e.g., \"Chest Pain\"\n  chips: string[];          \u002F\u002F clickable symptom chips\n  requiredFields: string[]; \u002F\u002F mandatory data points\n  redFlags: string[];       \u002F\u002F triggers non-dismissable alert\n  icdSuggestions: string[]; \u002F\u002F pre-mapped diagnosis codes\n}\n```\n\nRed flags in any template must trigger a visible, non-dismissable alert — NOT a toast notification.\n\n### Medication Safety Pattern\n\n```\nUser selects drug\n  → Check current medications for interactions\n  → Check encounter medications for interactions\n  → Check patient allergies\n  → Validate dose against weight\u002Fage\u002Frenal function\n  → If CRITICAL interaction: BLOCK prescribing entirely\n  → Clinician must document override reason to proceed past a block\n  → If MAJOR interaction: display warning, require acknowledgment\n  → Log all alerts and override reasons in audit trail\n```\n\nCritical interactions **block prescribing by default**. The clinician must explicitly override with a documented reason stored in the audit trail. The system never silently allows a critical interaction.\n\n### Locked Encounter Pattern\n\nOnce a clinical encounter is signed:\n- No edits allowed — only an addendum (a separate linked record)\n- Both original and addendum appear in the patient timeline\n- Audit trail captures who signed, when, and any addendum records\n\n### UI Patterns for Clinical Data\n\n**Vitals Display:** Current values with normal range highlighting (green\u002Fyellow\u002Fred), trend arrows vs previous, clinical scoring auto-calculated (NEWS2, qSOFA), escalation guidance inline.\n\n**Lab Results Display:** Normal range highlighting, previous value comparison, critical values with non-dismissable alert, collection\u002Fanalysis timestamps, pending orders with expected turnaround.\n\n**Prescription PDF:** One-click generation with patient demographics, allergies, diagnosis, drug details (generic + brand, dose, route, frequency, duration), clinician signature block.\n\n### Accessibility for Healthcare\n\nHealthcare UIs have stricter requirements than typical web apps:\n- 4.5:1 minimum contrast (WCAG AA) — clinicians work in varied lighting\n- Large touch targets (44x44px minimum) — for gloved\u002Frushed interaction\n- Keyboard navigation — for power users entering data rapidly\n- No color-only indicators — always pair color with text\u002Ficon (colorblind clinicians)\n- Screen reader labels on all form fields\n- No auto-dismissing toasts for clinical alerts — clinician must actively acknowledge\n\n### Anti-Patterns\n\n- Storing clinical data in browser localStorage\n- Silent failures in drug interaction checking\n- Dismissable toasts for critical clinical alerts\n- Tab-based encounter UIs that fragment the clinical workflow\n- Allowing edits to signed\u002Flocked encounters\n- Displaying clinical data without audit trail\n- Using `any` type for clinical data structures\n\n## Examples\n\n### Example 1: Patient Encounter Flow\n\n```\nDoctor opens encounter for Patient #4521\n  → Sticky header shows: \"Rajesh M, 58M, Allergies: Penicillin, Active Meds: Metformin 500mg\"\n  → Chief Complaint: selects \"Chest Pain\" template\n    → Clicks chips: \"substernal\", \"radiating to left arm\", \"crushing\"\n    → Red flag \"crushing substernal chest pain\" triggers non-dismissable alert\n  → Examination: CVS system — \"S1 S2 normal, no murmur\"\n  → Vitals: HR 110, BP 90\u002F60, SpO2 94%\n    → NEWS2 auto-calculates: score 8, risk HIGH, escalation alert shown\n  → Diagnosis: searches \"ACS\" → selects ICD-10 I21.9\n  → Medications: selects Aspirin 300mg\n    → CDSS checks against Metformin: no interaction\n  → Signs encounter → locked, addendum-only from this point\n```\n\n### Example 2: Medication Safety Workflow\n\n```\nDoctor prescribes Warfarin for Patient #4521\n  → CDSS detects: Warfarin + Aspirin = CRITICAL interaction\n  → UI: red non-dismissable modal blocks prescribing\n  → Doctor clicks \"Override with reason\"\n  → Types: \"Benefits outweigh risks — monitored INR protocol\"\n  → Override reason + alert stored in audit trail\n  → Prescription proceeds with documented override\n```\n\n### Example 3: Locked Encounter + Addendum\n\n```\nEncounter #E-2024-0891 signed by Dr. Shah at 14:30\n  → All fields locked — no edit buttons visible\n  → \"Add Addendum\" button available\n  → Dr. Shah clicks addendum, adds: \"Lab results received — Troponin elevated\"\n  → New record E-2024-0891-A1 linked to original\n  → Timeline shows both: original encounter + addendum with timestamps\n```\n","# Healthcare EMR Development Patterns\n\nPatterns for building Electronic Medical Record (EMR) and Electronic Health Record (EHR) systems. Prioritizes patient safety, clinical accuracy, and practitioner efficiency.\n\n## When to Use\n\n- Building patient encounter workflows (complaint, exam, diagnosis, prescription)\n- Implementing clinical note-taking (structured + free text + voice-to-text)\n- Designing prescription\u002Fmedication modules with drug interaction checking\n- Integrating Clinical Decision Support Systems (CDSS)\n- Building lab result displays with reference range highlighting\n- Implementing audit trails for clinical data\n- Designing healthcare-accessible UIs for clinical data entry\n\n## How It Works\n\n### Patient Safety First\n\nEvery design decision must be evaluated against: \"Could this harm a patient?\"\n\n- Drug interactions MUST alert, not silently pass\n- Abnormal lab values MUST be visually flagged\n- Critical vitals MUST trigger escalation workflows\n- No clinical data modification without audit trail\n\n### Single-Page Encounter Flow\n\nClinical encounters should flow vertically on a single page — no tab switching:\n\n```\nPatient Header (sticky — always visible)\n├── Demographics, allergies, active medications\n│\nEncounter Flow (vertical scroll)\n├── 1. Chief Complaint (structured templates + free text)\n├── 2. History of Present Illness\n├── 3. Physical Examination (system-wise)\n├── 4. Vitals (auto-trigger clinical scoring)\n├── 5. Diagnosis (ICD-10\u002FSNOMED search)\n├── 6. Medications (drug DB + interaction check)\n├── 7. Investigations (lab\u002Fradiology orders)\n├── 8. Plan & Follow-up\n└── 9. Sign \u002F Lock \u002F Print\n```\n\n### Smart Template System\n\n```typescript\ninterface ClinicalTemplate {\n  id: string;\n  name: string;             \u002F\u002F e.g., \"Chest Pain\"\n  chips: string[];          \u002F\u002F clickable symptom chips\n  requiredFields: string[]; \u002F\u002F mandatory data points\n  redFlags: string[];       \u002F\u002F triggers non-dismissable alert\n  icdSuggestions: string[]; \u002F\u002F pre-mapped diagnosis codes\n}\n```\n\nRed flags in any template must trigger a visible, non-dismissable alert — NOT a toast notification.\n\n### Medication Safety Pattern\n\n```\nUser selects drug\n  → Check current medications for interactions\n  → Check encounter medications for interactions\n  → Check patient allergies\n  → Validate dose against weight\u002Fage\u002Frenal function\n  → If CRITICAL interaction: BLOCK prescribing entirely\n  → Clinician must document override reason to proceed past a block\n  → If MAJOR interaction: display warning, require acknowledgment\n  → Log all alerts and override reasons in audit trail\n```\n\nCritical interactions **block prescribing by default**. The clinician must explicitly override with a documented reason stored in the audit trail. The system never silently allows a critical interaction.\n\n### Locked Encounter Pattern\n\nOnce a clinical encounter is signed:\n- No edits allowed — only an addendum (a separate linked record)\n- Both original and addendum appear in the patient timeline\n- Audit trail captures who signed, when, and any addendum records\n\n### UI Patterns for Clinical Data\n\n**Vitals Display:** Current values with normal range highlighting (green\u002Fyellow\u002Fred), trend arrows vs previous, clinical scoring auto-calculated (NEWS2, qSOFA), escalation guidance inline.\n\n**Lab Results Display:** Normal range highlighting, previous value comparison, critical values with non-dismissable alert, collection\u002Fanalysis timestamps, pending orders with expected turnaround.\n\n**Prescription PDF:** One-click generation with patient demographics, allergies, diagnosis, drug details (generic + brand, dose, route, frequency, duration), clinician signature block.\n\n### Accessibility for Healthcare\n\nHealthcare UIs have stricter requirements than typical web apps:\n- 4.5:1 minimum contrast (WCAG AA) — clinicians work in varied lighting\n- Large touch targets (44x44px minimum) — for gloved\u002Frushed interaction\n- Keyboard navigation — for power users entering data rapidly\n- No color-only indicators — always pair color with text\u002Ficon (colorblind clinicians)\n- Screen reader labels on all form fields\n- No auto-dismissing toasts for clinical alerts — clinician must actively acknowledge\n\n### Anti-Patterns\n\n- Storing clinical data in browser localStorage\n- Silent failures in drug interaction checking\n- Dismissable toasts for critical clinical alerts\n- Tab-based encounter UIs that fragment the clinical workflow\n- Allowing edits to signed\u002Flocked encounters\n- Displaying clinical data without audit trail\n- Using `any` type for clinical data structures\n\n## Examples\n\n### Example 1: Patient Encounter Flow\n\n```\nDoctor opens encounter for Patient #4521\n  → Sticky header shows: \"Rajesh M, 58M, Allergies: Penicillin, Active Meds: Metformin 500mg\"\n  → Chief Complaint: selects \"Chest Pain\" template\n    → Clicks chips: \"substernal\", \"radiating to left arm\", \"crushing\"\n    → Red flag \"crushing substernal chest pain\" triggers non-dismissable alert\n  → Examination: CVS system — \"S1 S2 normal, no murmur\"\n  → Vitals: HR 110, BP 90\u002F60, SpO2 94%\n    → NEWS2 auto-calculates: score 8, risk HIGH, escalation alert shown\n  → Diagnosis: searches \"ACS\" → selects ICD-10 I21.9\n  → Medications: selects Aspirin 300mg\n    → CDSS checks against Metformin: no interaction\n  → Signs encounter → locked, addendum-only from this point\n```\n\n### Example 2: Medication Safety Workflow\n\n```\nDoctor prescribes Warfarin for Patient #4521\n  → CDSS detects: Warfarin + Aspirin = CRITICAL interaction\n  → UI: red non-dismissable modal blocks prescribing\n  → Doctor clicks \"Override with reason\"\n  → Types: \"Benefits outweigh risks — monitored INR protocol\"\n  → Override reason + alert stored in audit trail\n  → Prescription proceeds with documented override\n```\n\n### Example 3: Locked Encounter + Addendum\n\n```\nEncounter #E-2024-0891 signed by Dr. Shah at 14:30\n  → All fields locked — no edit buttons visible\n  → \"Add Addendum\" button available\n  → Dr. Shah clicks addendum, adds: \"Lab results received — Troponin elevated\"\n  → New record E-2024-0891-A1 linked to original\n  → Timeline shows both: original encounter + addendum with timestamps\n```\n",{"name":5,"origin":48,"version":49,"description":7},"Health1 Super Speciality Hospitals — contributed by Dr. Keyur Patel","1.0.0","master","8ec37df6d71fb664ea19d32c079e7d3ff931a8e0","skills\u002Fecc\u002Fhealthcare-emr-patterns",3,"https:\u002F\u002Fgithub.com\u002FS3YED\u002Fappie-kit","https:\u002F\u002Fweblyfe.ai","https:\u002F\u002Fgithub.com\u002FS3YED","2026-08-27 01:54:02",{"source":8,"skillName":5,"commands":59,"prompt":69,"zipAvailable":70},[60,63,66],{"tool":61,"command":62},"npx","npx skills add S3YED\u002Fappie-kit --skill healthcare-emr-patterns",{"tool":64,"command":65},"bunx","bunx skills add S3YED\u002Fappie-kit --skill healthcare-emr-patterns",{"tool":67,"command":68},"pnpm","pnpm dlx skills add S3YED\u002Fappie-kit --skill healthcare-emr-patterns","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FS3YED\u002Fappie-kit\u002Fblob\u002Fmaster\u002Fskills\u002Fecc\u002Fhealthcare-emr-patterns\u002FSKILL.md",true,[],[73,104,138,164,195,218],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":86,"publishedAt":43},"01M6JFD4M6N4DSGC7TXEJ5R3J2","ai-music","AI music generation and audio tools: HeartMuLa lyrics-to-music generation, songwriting craft (+ Suno prompts), and audio spectrogram\u002Ffeature visualization.","https:\u002F\u002Fgithub.com\u002FS3YED\u002Fappie-kit\u002Fblob\u002Fmaster\u002Fskills\u002Fwethlete\u002Fai-music\u002FSKILL.md",[79,82,85],{"categoryNo":80,"categoryName":81,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000013","分析与可视化",{"categoryNo":83,"categoryName":84,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000016","图像与多媒体",{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},[87,88,89,90,91,92,93,94,95,96,97,98,99,100,31,101,102,103],"music","ai music","humanizer","visualization","Tools","Audio","hermes","hermes agent","songwriting","suno","lyrics","prompts","heartmula","craft","feature","ai music generation","music generation",{"skillNo":105,"name":106,"nameZh":6,"description":107,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":108,"categories":109,"keywords":118,"publishedAt":43},"01M6JFCZE4XNFQFMNZDHKHT5V5","agentic-webdesign-design-system-ingestion","Use v0 Design Systems 2.0, Bolt Design System Agents, or Lovable to generate production UI from a client's real design system components — not generic Tailwind. Use when building a client website where brand consistency matters.","https:\u002F\u002Fgithub.com\u002FS3YED\u002Fappie-kit\u002Fblob\u002Fmaster\u002Fskills\u002Fweb-design\u002Fagentic-webdesign-design-system-ingestion\u002FSKILL.md",[110,113],{"categoryNo":111,"categoryName":112,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000015","视觉设计",{"categoryNo":114,"categoryName":115,"taxonomyType":116,"taxonomyTypeDesc":117},"01JBSEEDCAT000000000000032","设计师","PROFESSION","适用职业",[119,120,121,122,123,124,125,126,127,128,129,40,130,131,132,133,134,135,136,137],"design","agentic","design system","system","ingestion","webdesign","agentic webdesign design system ingestion","components","generate","design systems","website","Tailwind","bolt","lovable","v0","design-system","wed","design system components","appie",{"skillNo":139,"name":140,"nameZh":6,"description":141,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":142,"categories":143,"keywords":146,"publishedAt":43},"01M6JFCVPX3913CFAS6QQJ33ZB","agentic-webdesign-agent-elements","Use 21st.dev Agent Elements — 25 shadcn\u002Fui components purpose-built for AI agent UIs. Tool cards (Bash, Edit, Search, Plan, Subagent, MCP), chat, input, streaming. Open source, shadcn-registry install, no runtime lock-in.","https:\u002F\u002Fgithub.com\u002FS3YED\u002Fappie-kit\u002Fblob\u002Fmaster\u002Fskills\u002Fweb-design\u002Fagentic-webdesign-agent-elements\u002FSKILL.md",[144,145],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},{"categoryNo":114,"categoryName":115,"taxonomyType":116,"taxonomyTypeDesc":117},[120,147,124,148,149,150,126,151,152,153,154,155,156,157,158,159,160,161,162,163],"elements","agentic webdesign agent elements","MCP","ai agent","registry","search","streaming","open source","open","Bash","plan","subagent","edit","install","input","lock","source",{"skillNo":165,"name":166,"nameZh":6,"description":167,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":168,"categories":169,"keywords":174,"publishedAt":43},"01M6JFCQC7H65M9QJ6TRE71BS1","vercel-deployment","Deploy static sites and frontends to Vercel — handles both CLI and REST API paths, including the CLI token sanitization workaround.","https:\u002F\u002Fgithub.com\u002FS3YED\u002Fappie-kit\u002Fblob\u002Fmaster\u002Fskills\u002Fsoftware-development\u002Fvercel-deployment\u002FSKILL.md",[170,173],{"categoryNo":171,"categoryName":172,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000011","运维与部署",{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},[175,176,177,178,179,180,181,182,183,184,185,186,187,188,189,190,191,192,193,194],"deployment","vercel deployment","vercel","macos","cli","linux","windows","deploy","vercel deploy","REST","api","site","deploy to vercel","token","rest api","host","sites","paths","sanitization","static site",{"skillNo":196,"name":197,"nameZh":6,"description":198,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":199,"categories":200,"keywords":202,"publishedAt":43},"01M6JFCM4SMTXBM5A01BK2YQG1","software-quality-workflows","Umbrella workflow for TDD, debugging, code simplification, spikes, pre-commit review, and debugger-assisted investigation.","https:\u002F\u002Fgithub.com\u002FS3YED\u002Fappie-kit\u002Fblob\u002Fmaster\u002Fskills\u002Fsoftware-development\u002Fsoftware-quality-workflows\u002FSKILL.md",[201],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},[42,203,204,205,206,207,208,209,210,211,212,213,214,215,216,217,27],"quality","software","software quality workflows","review","tdd","workflow","commit","debugging","code","debugger","pre-commit","investigation","code simplification","user","simplification",{"skillNo":219,"name":220,"nameZh":6,"description":221,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":222,"categories":223,"keywords":231,"publishedAt":43},"01M6JFCGD0M6CEATY01W7YN6DB","react-component-refactoring","Safely refactor large React components into smaller, maintainable pieces using proven patterns","https:\u002F\u002Fgithub.com\u002FS3YED\u002Fappie-kit\u002Fblob\u002Fmaster\u002Fskills\u002Fsoftware-development\u002Freact-component-refactoring\u002FSKILL.md",[224,227,230],{"categoryNo":225,"categoryName":226,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000007","代码审查",{"categoryNo":228,"categoryName":229,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000009","前端开发",{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},[232,233,234,235,236,237,238,239,178,240,241,126,242,181,243,211,244,245,25,246],"react","component","refactoring","component refactoring","react component","react component refactoring","frontend","writing","safe","typescript","react components","modular","refactor","simplify","test-driven-development"]