[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71HFHAWHCXJEWDMMPTWTHZ1":3,"skill-same:01M71HFHAWHCXJEWDMMPTWTHZ1":78},{"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":38,"linkOnly":39,"markdownContent":40,"markdownBody":41,"frontMatter":42,"refName":49,"commitSha":50,"skillDirectory":51,"forksCount":52,"repositoryHtmlUrl":53,"repositoryHomepageUrl":6,"ownerHtmlUrl":54,"ownerBlogUrl":55,"ownerDescription":56,"updatedAt":57,"install":58,"resources":71},"01M71HFHAWHCXJEWDMMPTWTHZ1","context-engine",null,"Loads and manages company context for all C-suite advisor skills. Reads ~\u002F.claude\u002Fcompany-context.md, detects stale context (>90 days), enriches context during conversations, and enforces privacy\u002Fanonymization rules before external API calls.","iDorgham\u002FWorkspace-Factory","iDorgham","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F136521493?v=4","01M6CNGBDAHE4ARW3YJEF4X2FD","Dorgham","01M71E8H3CXZ7DJX59MTM9JEB2",1,"MIT","https:\u002F\u002Fgithub.com\u002FiDorgham\u002FWorkspace-Factory\u002Fblob\u002Fmaster\u002Ffactory\u002Flibrary\u002Fskills\u002Fgithub_imports\u002Fc-level-advisor\u002Fcontext-engine\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37],"context engine","context","engine","suite","stale","privacy","2026","advisor","enrichment","external api","api","orchestration","Rules","loads","calls","company","loading","for","conversations","2026-11-10 10:12:30",false,"---\nname: \"context-engine\"\ndescription: \"Loads and manages company context for all C-suite advisor skills. Reads ~\u002F.claude\u002Fcompany-context.md, detects stale context (>90 days), enriches context during conversations, and enforces privacy\u002Fanonymization rules before external API calls.\"\nlicense: MIT\nmetadata:\n  version: 1.0.0\n  author: Alireza Rezvani\n  category: c-level\n  domain: orchestration\n  updated: 2026-03-05\n  frameworks: context-loading, anonymization, context-enrichment\n---\n\n# Company Context Engine\n\nThe memory layer for C-suite advisors. Every advisor skill loads this first. Context is what turns generic advice into specific insight.\n\n## Keywords\ncompany context, context loading, context engine, company profile, advisor context, stale context, context refresh, privacy, anonymization\n\n---\n\n## Load Protocol (Run at Start of Every C-Suite Session)\n\n**Step 1 — Check for context file:** `~\u002F.claude\u002Fcompany-context.md`\n- Exists → proceed to Step 2\n- Missing → prompt: *\"Run \u002Fcs:setup to build your company context — it makes every advisor conversation significantly more useful.\"*\n\n**Step 2 — Check staleness:** Read `Last updated` field.\n- **\u003C 90 days:** Load and proceed.\n- **≥ 90 days:** Prompt: *\"Your context is [N] days old. Quick 15-min refresh (\u002Fcs:update), or continue with what I have?\"*\n  - If continue: load with `[STALE — last updated DATE]` noted internally.\n\n**Step 3 — Parse into working memory.** Always active:\n- Company stage (pre-PMF \u002F scaling \u002F optimizing)\n- Founder archetype (product \u002F sales \u002F technical \u002F operator)\n- Current #1 challenge\n- Runway (as risk signal — never share externally)\n- Team size\n- Unfair advantage\n- 12-month target\n\n---\n\n## Context Quality Signals\n\n| Condition | Confidence | Action |\n|-----------|-----------|--------|\n| \u003C 30 days, full interview | High | Use directly |\n| 30–90 days, update done | Medium | Use, flag what may have changed |\n| > 90 days | Low | Flag stale, prompt refresh |\n| Key fields missing | Low | Ask in-session |\n| No file | None | Prompt \u002Fcs:setup |\n\nIf Low: *\"My context is [stale\u002Fincomplete] — I'm assuming [X]. Correct me if I'm wrong.\"*\n\n---\n\n## Context Enrichment\n\nDuring conversations, you'll learn things not in the file. Capture them.\n\n**Triggers:** New number or timeline revealed, key person mentioned, priority shift, constraint surfaces.\n\n**Protocol:**\n1. Note internally: `[CONTEXT UPDATE: {what was learned}]`\n2. At session end: *\"I picked up a few things to add to your context. Want me to update the file?\"*\n3. If yes: append to the relevant dimension, update timestamp.\n\n**Never silently overwrite.** Always confirm before modifying the context file.\n\n---\n\n## Privacy Rules\n\n### Never send externally\n- Specific revenue or burn figures\n- Customer names\n- Employee names (unless publicly known)\n- Investor names (unless public)\n- Specific runway months\n- Watch List contents\n\n### Safe to use externally (with anonymization)\n- Stage label\n- Team size ranges (1–10, 10–50, 50–200+)\n- Industry vertical\n- Challenge category\n- Market position descriptor\n\n### Before any external API call or web search\nApply `references\u002Fanonymization-protocol.md`:\n- Numbers → ranges or stage-relative descriptors\n- Names → roles\n- Revenue → percentages or stage labels\n- Customers → \"Customer A, B, C\"\n\n---\n\n## Missing or Partial Context\n\nHandle gracefully — never block the conversation.\n\n- **Missing stage:** \"Just to calibrate — are you still finding PMF or scaling what works?\"\n- **Missing financials:** Use stage + team size to infer. Note the gap.\n- **Missing founder profile:** Infer from conversation style. Mark as inferred.\n- **Multiple founders:** Context reflects the interviewee. Note co-founder perspective may differ.\n\n---\n\n## Required Context Fields\n\n```\nRequired:\n  - Last updated (date)\n  - Company Identity → What we do\n  - Stage & Scale → Stage\n  - Founder Profile → Founder archetype\n  - Current Challenges → Priority #1\n  - Goals & Ambition → 12-month target\n\nHigh-value optional:\n  - Unfair advantage\n  - Kill-shot risk\n  - Avoided decision\n  - Watch list\n```\n\nMissing required fields: note gaps, work around in session, ask in-session only when critical.\n\n---\n\n## References\n- `references\u002Fanonymization-protocol.md` — detailed rules for stripping sensitive data before external calls\n","# Company Context Engine\n\nThe memory layer for C-suite advisors. Every advisor skill loads this first. Context is what turns generic advice into specific insight.\n\n## Keywords\ncompany context, context loading, context engine, company profile, advisor context, stale context, context refresh, privacy, anonymization\n\n---\n\n## Load Protocol (Run at Start of Every C-Suite Session)\n\n**Step 1 — Check for context file:** `~\u002F.claude\u002Fcompany-context.md`\n- Exists → proceed to Step 2\n- Missing → prompt: *\"Run \u002Fcs:setup to build your company context — it makes every advisor conversation significantly more useful.\"*\n\n**Step 2 — Check staleness:** Read `Last updated` field.\n- **\u003C 90 days:** Load and proceed.\n- **≥ 90 days:** Prompt: *\"Your context is [N] days old. Quick 15-min refresh (\u002Fcs:update), or continue with what I have?\"*\n  - If continue: load with `[STALE — last updated DATE]` noted internally.\n\n**Step 3 — Parse into working memory.** Always active:\n- Company stage (pre-PMF \u002F scaling \u002F optimizing)\n- Founder archetype (product \u002F sales \u002F technical \u002F operator)\n- Current #1 challenge\n- Runway (as risk signal — never share externally)\n- Team size\n- Unfair advantage\n- 12-month target\n\n---\n\n## Context Quality Signals\n\n| Condition | Confidence | Action |\n|-----------|-----------|--------|\n| \u003C 30 days, full interview | High | Use directly |\n| 30–90 days, update done | Medium | Use, flag what may have changed |\n| > 90 days | Low | Flag stale, prompt refresh |\n| Key fields missing | Low | Ask in-session |\n| No file | None | Prompt \u002Fcs:setup |\n\nIf Low: *\"My context is [stale\u002Fincomplete] — I'm assuming [X]. Correct me if I'm wrong.\"*\n\n---\n\n## Context Enrichment\n\nDuring conversations, you'll learn things not in the file. Capture them.\n\n**Triggers:** New number or timeline revealed, key person mentioned, priority shift, constraint surfaces.\n\n**Protocol:**\n1. Note internally: `[CONTEXT UPDATE: {what was learned}]`\n2. At session end: *\"I picked up a few things to add to your context. Want me to update the file?\"*\n3. If yes: append to the relevant dimension, update timestamp.\n\n**Never silently overwrite.** Always confirm before modifying the context file.\n\n---\n\n## Privacy Rules\n\n### Never send externally\n- Specific revenue or burn figures\n- Customer names\n- Employee names (unless publicly known)\n- Investor names (unless public)\n- Specific runway months\n- Watch List contents\n\n### Safe to use externally (with anonymization)\n- Stage label\n- Team size ranges (1–10, 10–50, 50–200+)\n- Industry vertical\n- Challenge category\n- Market position descriptor\n\n### Before any external API call or web search\nApply `references\u002Fanonymization-protocol.md`:\n- Numbers → ranges or stage-relative descriptors\n- Names → roles\n- Revenue → percentages or stage labels\n- Customers → \"Customer A, B, C\"\n\n---\n\n## Missing or Partial Context\n\nHandle gracefully — never block the conversation.\n\n- **Missing stage:** \"Just to calibrate — are you still finding PMF or scaling what works?\"\n- **Missing financials:** Use stage + team size to infer. Note the gap.\n- **Missing founder profile:** Infer from conversation style. Mark as inferred.\n- **Multiple founders:** Context reflects the interviewee. Note co-founder perspective may differ.\n\n---\n\n## Required Context Fields\n\n```\nRequired:\n  - Last updated (date)\n  - Company Identity → What we do\n  - Stage & Scale → Stage\n  - Founder Profile → Founder archetype\n  - Current Challenges → Priority #1\n  - Goals & Ambition → 12-month target\n\nHigh-value optional:\n  - Unfair advantage\n  - Kill-shot risk\n  - Avoided decision\n  - Watch list\n```\n\nMissing required fields: note gaps, work around in session, ask in-session only when critical.\n\n---\n\n## References\n- `references\u002Fanonymization-protocol.md` — detailed rules for stripping sensitive data before external calls\n",{"name":5,"license":15,"metadata":43,"description":7},{"author":44,"domain":30,"updated":45,"version":46,"category":47,"frameworks":48},"Alireza Rezvani",1772668800000,"1.0.0","c-level","context-loading, anonymization, context-enrichment","master","c2e410e11df4d80d885e0ecf0583ef3c926df736","factory\u002Flibrary\u002Fskills\u002Fgithub_imports\u002Fc-level-advisor\u002Fcontext-engine",0,"https:\u002F\u002Fgithub.com\u002FiDorgham\u002FWorkspace-Factory","https:\u002F\u002Fgithub.com\u002FiDorgham","Dorgham.me","hey I'm Dorgham \r\nI code, I create, and AI codes back. \r\nMaybe we can give AI the chance!! now we begin. 🚀🤖\r\n... . . . git commit -m \"Hello, Future\" ","2026-05-04 18:39:09",{"source":8,"skillName":5,"commands":59,"prompt":69,"zipAvailable":70},[60,63,66],{"tool":61,"command":62},"npx","npx skills add iDorgham\u002FWorkspace-Factory --skill context-engine",{"tool":64,"command":65},"bunx","bunx skills add iDorgham\u002FWorkspace-Factory --skill context-engine",{"tool":67,"command":68},"pnpm","pnpm dlx skills add iDorgham\u002FWorkspace-Factory --skill context-engine","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FiDorgham\u002FWorkspace-Factory\u002Fblob\u002Fmaster\u002Ffactory\u002Flibrary\u002Fskills\u002Fgithub_imports\u002Fc-level-advisor\u002Fcontext-engine\u002FSKILL.md",true,[72],{"path":73,"resourceType":74,"resourceTypeDesc":75,"sizeBytes":76,"sourceHtmlUrl":77},"references\u002Fanonymization-protocol.md","REFERENCE","参考文档",5766,"https:\u002F\u002Fgithub.com\u002FiDorgham\u002FWorkspace-Factory\u002Fblob\u002Fmaster\u002Ffactory\u002Flibrary\u002Fskills\u002Fgithub_imports\u002Fc-level-advisor\u002Fcontext-engine\u002Freferences\u002Fanonymization-protocol.md",[79,111,133,155,175,197],{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":90,"publishedAt":110},"01M71P8WVBMB2X3D24R0YT0B0E","vercel-react-view-transitions","Guide for implementing smooth, native-feeling animations using React's View Transition API (`\u003CViewTransition>` component, `addTransitionType`, and CSS view transition pseudo-elements). Use this skill whenever the user wants to add page transitions, animate route changes, create shared element animations, animate enter\u002Fexit of components, animate list reorder, implement directional (forward\u002Fback) navigation animations, or integrate view transitions in Next.js. Also use when the user mentions view transitions, `startViewTransition`, `ViewTransition`, transition types, or asks about animating between UI states in React without third-party animation libraries.","https:\u002F\u002Fgithub.com\u002FiDorgham\u002FWorkspace-Factory\u002Fblob\u002Fmaster\u002Ffactory\u002Flibrary\u002Fskills\u002Fofficial_vercel_labs_react_view_transitions\u002Fskill.md",[85],{"categoryNo":86,"categoryName":87,"taxonomyType":88,"taxonomyTypeDesc":89},"01JBSEEDCAT000000000000009","前端开发","SCENARIO","使用场景",[91,92,93,94,95,96,97,98,99,100,101,102,103,104,105,106,29,107,108,109],"react","vercel react view transitions","view","react view transitions","vercel","transitions","shared","back","Animation","css","types","states","element","implementing","when","components","route","create","libraries","2026-11-10 13:02:02",{"skillNo":112,"name":113,"nameZh":6,"description":114,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":115,"categories":116,"keywords":118,"publishedAt":110},"01M71P8TDGHZ289TSAC5VTG2EW","vercel-react-native-skills","React Native and Expo best practices for building performant mobile apps. Use when building React Native components, optimizing list performance, implementing animations, or working with native modules. Triggers on tasks involving React Native, Expo, mobile performance, or native platform APIs.","https:\u002F\u002Fgithub.com\u002FiDorgham\u002FWorkspace-Factory\u002Fblob\u002Fmaster\u002Ffactory\u002Flibrary\u002Fskills\u002Fofficial_vercel_labs_react_native_skills\u002Fskill.md",[117],{"categoryNo":86,"categoryName":87,"taxonomyType":88,"taxonomyTypeDesc":89},[91,119,120,95,121,122,123,124,104,125,105,126,106,127,128,129,130,131,132,36],"react native","native","vercel react native skills","react native skills","modules","performance","apps","tasks","mobile","expo","list","mobile performance","platform","animations",{"skillNo":134,"name":135,"nameZh":6,"description":136,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":137,"categories":138,"keywords":140,"publishedAt":110},"01M71P8QK4JF5BYRGYDDGPZQG9","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\u002FiDorgham\u002FWorkspace-Factory\u002Fblob\u002Fmaster\u002Ffactory\u002Flibrary\u002Fskills\u002Fofficial_vercel_labs_react_best_practices\u002Fskill.md",[139],{"categoryNo":86,"categoryName":87,"taxonomyType":88,"taxonomyTypeDesc":89},[91,141,142,95,143,124,144,105,145,126,106,146,147,148,149,150,151,152,153,154],"react best practices","vercel react best practices","best practices","writing","code","data fetching","react components","next","refactoring","data","patterns","Optimization","guidelines","triggers",{"skillNo":156,"name":157,"nameZh":6,"description":158,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":159,"categories":160,"keywords":162,"publishedAt":110},"01M71P8HVEA70K5N6ZVJCG2ED3","vercel-composition-patterns","React composition patterns that scale. Use when refactoring components with boolean prop proliferation, building flexible component libraries, or designing reusable APIs. Triggers on tasks involving compound components, render props, context providers, or component architecture. Includes React 19 API changes.","https:\u002F\u002Fgithub.com\u002FiDorgham\u002FWorkspace-Factory\u002Fblob\u002Fmaster\u002Ffactory\u002Flibrary\u002Fskills\u002Fofficial_vercel_labs_composition_patterns\u002Fskill.md",[161],{"categoryNo":86,"categoryName":87,"taxonomyType":88,"taxonomyTypeDesc":89},[163,95,164,151,165,166,167,168,154,169,170,171,105,172,126,106,173,174,29,91],"Composition","composition patterns","vercel composition patterns","react composition patterns","react 19","render","boolean","component architecture","use","reusable","architecture","react composition",{"skillNo":176,"name":177,"nameZh":6,"description":178,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":179,"categories":180,"keywords":184,"publishedAt":110},"01M71P60XXKKP222ZFJRG7R373","supabase-postgres-best-practices","Postgres performance optimization and best practices from Supabase. Use this skill when writing, reviewing, or optimizing Postgres queries, schema designs, or database configurations.","https:\u002F\u002Fgithub.com\u002FiDorgham\u002FWorkspace-Factory\u002Fblob\u002Fmaster\u002Ffactory\u002Flibrary\u002Fskills\u002Fofficial_supabase_supabase_postgres_best_practices\u002Fskill.md",[181],{"categoryNo":182,"categoryName":183,"taxonomyType":88,"taxonomyTypeDesc":89},"01JBSEEDCAT000000000000010","后端与接口",[185,186,187,188,143,189,190,191,36,152,124,192,193,144,194,171,31,195,196,105],"postgres best practices","supabase","postgres","supabase postgres best practices","categories","postgres performance","advanced","correct","schema","impact","critical","database",{"skillNo":198,"name":199,"nameZh":6,"description":200,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":201,"categories":202,"keywords":204,"publishedAt":220},"01M71P2ZCEJD0PKC458YTP1FJW","portable-text-serialization","Render and serialize Portable Text to React, Svelte, Vue, Astro, HTML, Markdown, and plain text. Use when implementing Portable Text rendering in any frontend framework, building custom serializers for non-standard block types, converting Portable Text to HTML strings server-side, converting Portable Text to Markdown, extracting plain text from Portable Text, or troubleshooting rendering issues with marks, blocks, lists, or custom types.","https:\u002F\u002Fgithub.com\u002FiDorgham\u002FWorkspace-Factory\u002Fblob\u002Fmaster\u002Ffactory\u002Flibrary\u002Fskills\u002Fofficial_sanity_io_portable_text_serialization\u002Fskill.md",[203],{"categoryNo":86,"categoryName":87,"taxonomyType":88,"taxonomyTypeDesc":89},[205,206,207,208,209,101,210,168,211,104,212,213,105,91,214,215,216,217,218,219],"text","portable text serialization","portable","serialization","extracting","strings","issues","frontend","svelte","sanity","astro","server","markdown","rendering","vue","2026-11-10 10:56:23"]