[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M788CAC31HTXGW48HD6X2BRE":3,"skill-same:01M788CAC31HTXGW48HD6X2BRE":80},{"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":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":42,"commitSha":43,"skillDirectory":44,"forksCount":13,"repositoryHtmlUrl":45,"repositoryHomepageUrl":46,"ownerHtmlUrl":47,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":48,"install":49,"resources":62},"01M788CAC31HTXGW48HD6X2BRE","clinical-case-report",null,"Structured medical case presentation for clinical rounds, conferences,\nand documentation. Generates SOAP-format or narrative case reports\nwith physiologically accurate vitals, labs, and evidence-based plans.\nUse when the brief mentions \"case report\", \"case presentation\", \"SOAP note\",\n\"clinical case\", \"ward rounds\", \"case summary\", or \"patient presentation\".","bluesman1971\u002Fopen-design","bluesman1971","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F96430007?v=4","01M788AK0TR13JE8ART2WNQZV6","01M788AK1PVB085AS9SP38WWGK",0,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fbluesman1971\u002Fopen-design\u002Fblob\u002Fmain\u002Fdesign-templates\u002Fclinical-case-report\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: clinical-case-report\ndescription: |\n  Structured medical case presentation for clinical rounds, conferences,\n  and documentation. Generates SOAP-format or narrative case reports\n  with physiologically accurate vitals, labs, and evidence-based plans.\n  Use when the brief mentions \"case report\", \"case presentation\", \"SOAP note\",\n  \"clinical case\", \"ward rounds\", \"case summary\", or \"patient presentation\".\ntriggers:\n  - \"case report\"\n  - \"case presentation\"\n  - \"soap note\"\n  - \"clinical case\"\n  - \"ward rounds\"\n  - \"patient presentation\"\n  - \"case summary\"\n  - \"medical case\"\nod:\n  mode: prototype\n  platform: desktop\n  scenario: healthcare\n  preview:\n    type: html\n    entry: index.html\n  fidelity: high-fidelity\n  example_prompt: \"58-year-old male with 2 hours of substernal chest pain radiating to the left arm, diaphoresis, and ST elevation in leads II, III, aVF. Generate a full emergency cardiology case presentation.\"\n---\n\n# Clinical Case Report Skill\n\nGenerate a structured medical case presentation for clinical rounds,\nconferences, or documentation. The output follows standard medical\nformatting conventions used in hospital settings worldwide.\n\n## What you will produce\n\nA single-page HTML case report (`index.html`). Content varies by format\n(see `references\u002Fcase-formats.md` — selected in Step 0):\n\n**SOAP \u002F Conference format:**\n- **Patient identification** — age, sex, chief complaint\n- **History of Present Illness (HPI)** — chronological narrative with\n  pertinent positives and negatives\n- **Past Medical History, Medications, Allergies**\n- **Review of Systems**\n- **Physical Examination** — systematic findings by system\n- **Vital Signs** — formatted table with reference ranges and flags\n- **Investigations** — laboratory results and imaging findings\n- **Assessment** — primary diagnosis and differential (3–5 items)\n  with clinical reasoning for each\n- **Management Plan** — evidence-based, organised by problem\n\n**Brief Rounds format** (daily review, ward round, handover, ICU, post-call):\n- **ID line** — age, sex, day of admission, primary problem\n- **Interval events \u002F current status** — what has changed since last review\n- **Active problems** — numbered list\n- **Plan-by-problem** — concise actions for each active problem\n- Full HPI and systematic physical examination are **not** included\n\n---\n\n## Step-by-step workflow\n\n### Step 0 — Load reference files\n\nBefore starting, read both reference files:\n\n1. `references\u002Fcase-formats.md` — use this to choose the correct output\n   format (SOAP, Conference, or Brief Rounds) based on the user's context\n2. `references\u002Fchecklist.md` — keep P0 gates in mind throughout; you\n   must pass all P0 items before emitting the final artifact\n\n### Step 1 — Parse the brief\n\nRead the user's prompt and extract:\n\n- Patient age and sex\n- Chief complaint or presenting problem\n- Any vitals, labs, or imaging the user has provided\n- Clinical context: ED, ward rounds, conference case, outpatient, etc.\n- Specialty context: cardiology, emergency, internal medicine, etc.\n\nIf the chief complaint or presenting problem is missing:\n- **SOAP \u002F Conference**: ask one clarifying question before proceeding. Do not proceed without it.\n- **Brief Rounds**: if the admission problem or ID line is already available (e.g. \"day-3 ICU review for septic shock\"), proceed directly — a separate chief complaint is not required.\n\n### Step 2 — Build the clinical narrative\n\n**For SOAP \u002F Conference outputs:** write the HPI as a continuous prose\nnarrative in standard clinical style:\n\n> \"This is a [age]-year-old [sex] with a history of [relevant PMH] who\n> presents with [chief complaint]. Symptoms began [timeline] and are\n> characterised by [quality, severity, radiation]. Associated symptoms\n> include [list]. Pertinent negatives include [list].\"\n\nThe HPI must be chronological. Include timeline markers\n(\"2 hours prior to presentation\", \"onset yesterday morning\").\n\n**For Brief Rounds outputs** (daily review, ward round, handover, ICU,\npost-call): skip the full HPI and examination. Instead produce:\n\n- **ID line**: \"[Age][sex], Day [N] of admission, [primary problem]\"\n- **Interval events \u002F current status**: what has changed since last review\n- **Active problems**: numbered list\n- **Plan-by-problem**: concise action for each active problem\n\n### Step 3 — Generate physiologically consistent clinical data\n\nIf the user has not provided specific values, generate values that are\ninternally consistent with the diagnosis:\n\n**Consistency checks (typical patterns):**\n\n- A patient in shock **typically** has: HR >100, SBP \u003C90, raised lactate,\n  impaired capillary refill — but medications (beta-blockers), age, or\n  shock type (neurogenic, spinal) can alter this pattern\n- Pneumonia **typically** presents with raised WBC, raised CRP,\n  temperature >38°C — but afebrile pneumonia exists, especially in\n  the elderly or immunocompromised\n- A STEMI **typically** shows ST elevation in contiguous leads and raised\n  high-sensitivity troponin — but early presentations may have initially\n  normal troponin; CK-MB is not universally required\n- Sepsis **typically** shows raised or low WBC, raised lactate >2,\n  temperature abnormality — but compensated early sepsis may present\n  with normal vitals\n- Lab units must match convention: creatinine in µmol\u002FL or mg\u002FdL\n  (state which), glucose in mmol\u002FL, haemoglobin in g\u002FdL\n\n**Critical rule — preserve user-provided data:**\n- Never overwrite a value the user has explicitly stated\n- If a user-provided value is atypical for the diagnosis, keep it and\n  note the atypical presentation in the assessment rather than\n  forcing canonical numbers\n- Never generate a value that contradicts the stated diagnosis\n\n### Step 4 — Write the assessment\n\nThe assessment section must contain:\n\n1. **Primary diagnosis** stated clearly on the first line\n2. **Clinical reasoning** — one sentence explaining why this is the\n   most likely diagnosis\n3. **Differential diagnosis** — exactly 3 to 5 items, each with one\n   sentence of supporting or refuting evidence\n4. **Risk stratification** — include a validated clinical score where\n   applicable (TIMI for ACS, GRACE for ACS, Killip class + Shock Index\n   for STEMI\u002Fcardiogenic shock, CURB-65 for pneumonia, qSOFA for sepsis,\n   Wells for PE, etc.). Killip class and Shock Index together are\n   accepted as sufficient risk stratification for STEMI\u002Fcardiogenic shock cases.\n\n### Step 5 — Write the management plan\n\nThe plan must be:\n\n- **Specific**: write drug names, doses, routes, and frequencies.\n  Do not write \"start antibiotics\" — write\n  \"Piperacillin-Tazobactam 4.5g IV q8h for 5 days\"\n- **Organised by problem** using numbered headers\n- **Evidence-based**: management must reflect current standard of care\n  for the diagnosis\n- **Complete**: include investigations to order, monitoring parameters,\n  consults to request, and disposition\n\nIf you are uncertain about a specific dose, write\n\"[drug name] — dose per local formulary\u002Fprotocol\" rather than\ninventing a dose.\n\n### Important — Prescribing Safety\n\nGenerated plans must:\n- Be marked as educational\u002Fsimulated, not a substitute for clinician judgment\n- Use \"per local formulary\u002Fprotocol\" language when required patient variables\n  (weight, renal function, allergies) are missing from the brief\n- List key contraindications and unknowns before medication recommendations\n  when relevant patient data has not been provided\n- Never claim a plan is \"definitive\" or \"standard of care\" without full\n  patient context (allergy status, renal\u002Fhepatic function, pregnancy\n  status, weight, anticoagulation\u002Fbleeding risk)\n- Include a disclaimer footer in the HTML output stating the case is for\n  educational and documentation purposes only\n\n### Step 6 — Write `index.html`\n\nRequirements for the HTML output:\n\n- Professional medical document typography\n  (Georgia or system serif font preferred)\n- White background, dark text — suitable for printing\n- Vital signs and lab results in HTML `\u003Ctable>` elements\n- Critical findings (ST elevation, raised troponin, low BP, etc.)\n  highlighted in a visually distinct callout box with red left border\n- @media print CSS rules so the document prints cleanly on A4\u002FLetter\n- Tag every major section with `data-od-id` for comment-mode targeting:\n\n```html\n\u003Csection data-od-id=\"hpi\">...\u003C\u002Fsection>\n\u003Csection data-od-id=\"vitals\">...\u003C\u002Fsection>\n\u003Csection data-od-id=\"pmh\">...\u003C\u002Fsection>\n\u003Csection data-od-id=\"examination\">...\u003C\u002Fsection>\n\u003Csection data-od-id=\"investigations\">...\u003C\u002Fsection>\n\u003Csection data-od-id=\"assessment\">...\u003C\u002Fsection>\n\u003Csection data-od-id=\"plan\">...\u003C\u002Fsection>\n```\n\n### Step 7 — Self-check against `references\u002Fchecklist.md`\n\nBefore emitting `\u003Cartifact>`, run every P0 item in `references\u002Fchecklist.md`.\nAll P0 items must pass. Fix any failures before emitting.","# Clinical Case Report Skill\n\nGenerate a structured medical case presentation for clinical rounds,\nconferences, or documentation. The output follows standard medical\nformatting conventions used in hospital settings worldwide.\n\n## What you will produce\n\nA single-page HTML case report (`index.html`). Content varies by format\n(see `references\u002Fcase-formats.md` — selected in Step 0):\n\n**SOAP \u002F Conference format:**\n- **Patient identification** — age, sex, chief complaint\n- **History of Present Illness (HPI)** — chronological narrative with\n  pertinent positives and negatives\n- **Past Medical History, Medications, Allergies**\n- **Review of Systems**\n- **Physical Examination** — systematic findings by system\n- **Vital Signs** — formatted table with reference ranges and flags\n- **Investigations** — laboratory results and imaging findings\n- **Assessment** — primary diagnosis and differential (3–5 items)\n  with clinical reasoning for each\n- **Management Plan** — evidence-based, organised by problem\n\n**Brief Rounds format** (daily review, ward round, handover, ICU, post-call):\n- **ID line** — age, sex, day of admission, primary problem\n- **Interval events \u002F current status** — what has changed since last review\n- **Active problems** — numbered list\n- **Plan-by-problem** — concise actions for each active problem\n- Full HPI and systematic physical examination are **not** included\n\n---\n\n## Step-by-step workflow\n\n### Step 0 — Load reference files\n\nBefore starting, read both reference files:\n\n1. `references\u002Fcase-formats.md` — use this to choose the correct output\n   format (SOAP, Conference, or Brief Rounds) based on the user's context\n2. `references\u002Fchecklist.md` — keep P0 gates in mind throughout; you\n   must pass all P0 items before emitting the final artifact\n\n### Step 1 — Parse the brief\n\nRead the user's prompt and extract:\n\n- Patient age and sex\n- Chief complaint or presenting problem\n- Any vitals, labs, or imaging the user has provided\n- Clinical context: ED, ward rounds, conference case, outpatient, etc.\n- Specialty context: cardiology, emergency, internal medicine, etc.\n\nIf the chief complaint or presenting problem is missing:\n- **SOAP \u002F Conference**: ask one clarifying question before proceeding. Do not proceed without it.\n- **Brief Rounds**: if the admission problem or ID line is already available (e.g. \"day-3 ICU review for septic shock\"), proceed directly — a separate chief complaint is not required.\n\n### Step 2 — Build the clinical narrative\n\n**For SOAP \u002F Conference outputs:** write the HPI as a continuous prose\nnarrative in standard clinical style:\n\n> \"This is a [age]-year-old [sex] with a history of [relevant PMH] who\n> presents with [chief complaint]. Symptoms began [timeline] and are\n> characterised by [quality, severity, radiation]. Associated symptoms\n> include [list]. Pertinent negatives include [list].\"\n\nThe HPI must be chronological. Include timeline markers\n(\"2 hours prior to presentation\", \"onset yesterday morning\").\n\n**For Brief Rounds outputs** (daily review, ward round, handover, ICU,\npost-call): skip the full HPI and examination. Instead produce:\n\n- **ID line**: \"[Age][sex], Day [N] of admission, [primary problem]\"\n- **Interval events \u002F current status**: what has changed since last review\n- **Active problems**: numbered list\n- **Plan-by-problem**: concise action for each active problem\n\n### Step 3 — Generate physiologically consistent clinical data\n\nIf the user has not provided specific values, generate values that are\ninternally consistent with the diagnosis:\n\n**Consistency checks (typical patterns):**\n\n- A patient in shock **typically** has: HR >100, SBP \u003C90, raised lactate,\n  impaired capillary refill — but medications (beta-blockers), age, or\n  shock type (neurogenic, spinal) can alter this pattern\n- Pneumonia **typically** presents with raised WBC, raised CRP,\n  temperature >38°C — but afebrile pneumonia exists, especially in\n  the elderly or immunocompromised\n- A STEMI **typically** shows ST elevation in contiguous leads and raised\n  high-sensitivity troponin — but early presentations may have initially\n  normal troponin; CK-MB is not universally required\n- Sepsis **typically** shows raised or low WBC, raised lactate >2,\n  temperature abnormality — but compensated early sepsis may present\n  with normal vitals\n- Lab units must match convention: creatinine in µmol\u002FL or mg\u002FdL\n  (state which), glucose in mmol\u002FL, haemoglobin in g\u002FdL\n\n**Critical rule — preserve user-provided data:**\n- Never overwrite a value the user has explicitly stated\n- If a user-provided value is atypical for the diagnosis, keep it and\n  note the atypical presentation in the assessment rather than\n  forcing canonical numbers\n- Never generate a value that contradicts the stated diagnosis\n\n### Step 4 — Write the assessment\n\nThe assessment section must contain:\n\n1. **Primary diagnosis** stated clearly on the first line\n2. **Clinical reasoning** — one sentence explaining why this is the\n   most likely diagnosis\n3. **Differential diagnosis** — exactly 3 to 5 items, each with one\n   sentence of supporting or refuting evidence\n4. **Risk stratification** — include a validated clinical score where\n   applicable (TIMI for ACS, GRACE for ACS, Killip class + Shock Index\n   for STEMI\u002Fcardiogenic shock, CURB-65 for pneumonia, qSOFA for sepsis,\n   Wells for PE, etc.). Killip class and Shock Index together are\n   accepted as sufficient risk stratification for STEMI\u002Fcardiogenic shock cases.\n\n### Step 5 — Write the management plan\n\nThe plan must be:\n\n- **Specific**: write drug names, doses, routes, and frequencies.\n  Do not write \"start antibiotics\" — write\n  \"Piperacillin-Tazobactam 4.5g IV q8h for 5 days\"\n- **Organised by problem** using numbered headers\n- **Evidence-based**: management must reflect current standard of care\n  for the diagnosis\n- **Complete**: include investigations to order, monitoring parameters,\n  consults to request, and disposition\n\nIf you are uncertain about a specific dose, write\n\"[drug name] — dose per local formulary\u002Fprotocol\" rather than\ninventing a dose.\n\n### Important — Prescribing Safety\n\nGenerated plans must:\n- Be marked as educational\u002Fsimulated, not a substitute for clinician judgment\n- Use \"per local formulary\u002Fprotocol\" language when required patient variables\n  (weight, renal function, allergies) are missing from the brief\n- List key contraindications and unknowns before medication recommendations\n  when relevant patient data has not been provided\n- Never claim a plan is \"definitive\" or \"standard of care\" without full\n  patient context (allergy status, renal\u002Fhepatic function, pregnancy\n  status, weight, anticoagulation\u002Fbleeding risk)\n- Include a disclaimer footer in the HTML output stating the case is for\n  educational and documentation purposes only\n\n### Step 6 — Write `index.html`\n\nRequirements for the HTML output:\n\n- Professional medical document typography\n  (Georgia or system serif font preferred)\n- White background, dark text — suitable for printing\n- Vital signs and lab results in HTML `\u003Ctable>` elements\n- Critical findings (ST elevation, raised troponin, low BP, etc.)\n  highlighted in a visually distinct callout box with red left border\n- @media print CSS rules so the document prints cleanly on A4\u002FLetter\n- Tag every major section with `data-od-id` for comment-mode targeting:\n\n```html\n\u003Csection data-od-id=\"hpi\">...\u003C\u002Fsection>\n\u003Csection data-od-id=\"vitals\">...\u003C\u002Fsection>\n\u003Csection data-od-id=\"pmh\">...\u003C\u002Fsection>\n\u003Csection data-od-id=\"examination\">...\u003C\u002Fsection>\n\u003Csection data-od-id=\"investigations\">...\u003C\u002Fsection>\n\u003Csection data-od-id=\"assessment\">...\u003C\u002Fsection>\n\u003Csection data-od-id=\"plan\">...\u003C\u002Fsection>\n```\n\n### Step 7 — Self-check against `references\u002Fchecklist.md`\n\nBefore emitting `\u003Cartifact>`, run every P0 item in `references\u002Fchecklist.md`.\nAll P0 items must pass. Fix any failures before emitting.",{"od":23,"name":5,"triggers":32,"description":41},{"mode":24,"preview":25,"fidelity":28,"platform":29,"scenario":30,"example_prompt":31},"prototype",{"type":26,"entry":27},"html","index.html","high-fidelity","desktop","healthcare","58-year-old male with 2 hours of substernal chest pain radiating to the left arm, diaphoresis, and ST elevation in leads II, III, aVF. Generate a full emergency cardiology case presentation.",[33,34,35,36,37,38,39,40],"case report","case presentation","soap note","clinical case","ward rounds","patient presentation","case summary","medical case","Structured medical case presentation for clinical rounds, conferences,\nand documentation. Generates SOAP-format or narrative case reports\nwith physiologically accurate vitals, labs, and evidence-based plans.\nUse when the brief mentions \"case report\", \"case presentation\", \"SOAP note\",\n\"clinical case\", \"ward rounds\", \"case summary\", or \"patient presentation\".\n","main","0467f0e19df12a6994ec7fb20ff6e9e23cd704e7","design-templates\u002Fclinical-case-report","https:\u002F\u002Fgithub.com\u002Fbluesman1971\u002Fopen-design","https:\u002F\u002Fopen-design.ai","https:\u002F\u002Fgithub.com\u002Fbluesman1971","2026-07-09 04:08:20",{"source":8,"skillName":5,"commands":50,"prompt":60,"zipAvailable":61},[51,54,57],{"tool":52,"command":53},"npx","npx skills add bluesman1971\u002Fopen-design --skill clinical-case-report",{"tool":55,"command":56},"bunx","bunx skills add bluesman1971\u002Fopen-design --skill clinical-case-report",{"tool":58,"command":59},"pnpm","pnpm dlx skills add bluesman1971\u002Fopen-design --skill clinical-case-report","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fbluesman1971\u002Fopen-design\u002Fblob\u002Fmain\u002Fdesign-templates\u002Fclinical-case-report\u002FSKILL.md",true,[63,69,72,76],{"path":64,"resourceType":65,"resourceTypeDesc":66,"sizeBytes":67,"sourceHtmlUrl":68},"example.html","REFERENCE","参考文档",27680,"https:\u002F\u002Fgithub.com\u002Fbluesman1971\u002Fopen-design\u002Fblob\u002Fmain\u002Fdesign-templates\u002Fclinical-case-report\u002Fexample.html",{"path":70,"resourceType":65,"resourceTypeDesc":66,"sizeBytes":67,"sourceHtmlUrl":71},"examples\u002Fexample-stemi.html","https:\u002F\u002Fgithub.com\u002Fbluesman1971\u002Fopen-design\u002Fblob\u002Fmain\u002Fdesign-templates\u002Fclinical-case-report\u002Fexamples\u002Fexample-stemi.html",{"path":73,"resourceType":65,"resourceTypeDesc":66,"sizeBytes":74,"sourceHtmlUrl":75},"references\u002Fcase-formats.md",2878,"https:\u002F\u002Fgithub.com\u002Fbluesman1971\u002Fopen-design\u002Fblob\u002Fmain\u002Fdesign-templates\u002Fclinical-case-report\u002Freferences\u002Fcase-formats.md",{"path":77,"resourceType":65,"resourceTypeDesc":66,"sizeBytes":78,"sourceHtmlUrl":79},"references\u002Fchecklist.md",3137,"https:\u002F\u002Fgithub.com\u002Fbluesman1971\u002Fopen-design\u002Fblob\u002Fmain\u002Fdesign-templates\u002Fclinical-case-report\u002Freferences\u002Fchecklist.md",[81,90,98,105,112,119],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":85,"licenseFileUrl":86,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":18},"01M78AMRG8NAGKWKNDQE39ZZFQ","web-design-guidelines","Review UI code for Web Interface Guidelines compliance by the Vercel engineering team. Covers layout, typography, color, motion, and accessibility for product UI.","MIT","https:\u002F\u002Fgithub.com\u002Fbluesman1971\u002Fopen-design\u002Fblob\u002Fmain\u002Fskills\u002Fweb-design-guidelines\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fbluesman1971\u002Fopen-design\u002Fblob\u002Fmain\u002Fskills\u002Fweb-design-guidelines\u002FSKILL.md",[],[],{"skillNo":91,"name":92,"nameZh":6,"description":93,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":85,"licenseFileUrl":94,"sourceHtmlUrl":95,"categories":96,"keywords":97,"publishedAt":18},"01M78AMKHTFS149JGEYNQM5AXR","web-clone","网站复刻 \u002F 克隆方法论。USE WHEN 用户说 复刻网站、克隆网站、clone website、抄个站、仿站、 照着这个站做一个、reproduce site、还原某个网页效果、把这个站搬下来改成我的、 复刻某个交互\u002FWebGL\u002FCanvas\u002FThree.js 效果。提供「先拿真源码 → 判路径 → 逆向拆解 → 搭工程 → 替换内容」的可移植决策树，覆盖静态站 \u002F React-Vue-Next 内容站 \u002F WebGL-Canvas 重前端站三大分支，并强制核对任何 AI 二手分析里的可执行代码。","https:\u002F\u002Fgithub.com\u002Fbluesman1971\u002Fopen-design\u002Fblob\u002Fmain\u002Fskills\u002Fweb-clone\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fbluesman1971\u002Fopen-design\u002Fblob\u002Fmain\u002Fskills\u002Fweb-clone\u002FSKILL.md",[],[],{"skillNo":99,"name":100,"nameZh":6,"description":101,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":102,"categories":103,"keywords":104,"publishedAt":18},"01M78AMH25JH2SH3AWTRSDCM9F","venice-video","Video generation and transcription workflows via the Venice.ai API.","https:\u002F\u002Fgithub.com\u002Fbluesman1971\u002Fopen-design\u002Fblob\u002Fmain\u002Fskills\u002Fvenice-video\u002FSKILL.md",[],[],{"skillNo":106,"name":107,"nameZh":6,"description":108,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":109,"categories":110,"keywords":111,"publishedAt":18},"01M78AMF0M4FFKFWXFJ9NHTF5M","venice-image-generate","Image generation endpoints and available styles via the Venice.ai API.","https:\u002F\u002Fgithub.com\u002Fbluesman1971\u002Fopen-design\u002Fblob\u002Fmain\u002Fskills\u002Fvenice-image-generate\u002FSKILL.md",[],[],{"skillNo":113,"name":114,"nameZh":6,"description":115,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":116,"categories":117,"keywords":118,"publishedAt":18},"01M78AMCH68X46SHNZVD284KXS","threejs","Three.js skills for creating 3D elements and interactive experiences in the browser — scenes, materials, controls, and post-processing.","https:\u002F\u002Fgithub.com\u002Fbluesman1971\u002Fopen-design\u002Fblob\u002Fmain\u002Fskills\u002Fthreejs\u002FSKILL.md",[],[],{"skillNo":120,"name":121,"nameZh":6,"description":122,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":123,"categories":124,"keywords":125,"publishedAt":18},"01M78AM7P8WSBZDNZZ42BQHGK7","taste","Brief-time anti-AI-slop taste checklist — read the room and set the\ndesign dials BEFORE generating a landing page, portfolio, or redesign,\nso the first draft doesn't need a post-generation rescue. Use at the\nstart of a visual\u002Fcreative brief, not after the artifact exists.","https:\u002F\u002Fgithub.com\u002Fbluesman1971\u002Fopen-design\u002Fblob\u002Fmain\u002Fskills\u002Ftaste\u002FSKILL.md",[],[]]