[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71JCCVG8CJ2TJ9JJNTQATYY":3,"skill-same:01M71JCCVG8CJ2TJ9JJNTQATYY":100},{"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":31,"publishedAt":52,"linkOnly":53,"markdownContent":54,"markdownBody":55,"frontMatter":56,"refName":61,"commitSha":62,"skillDirectory":63,"forksCount":64,"repositoryHtmlUrl":65,"repositoryHomepageUrl":6,"ownerHtmlUrl":66,"ownerBlogUrl":67,"ownerDescription":68,"updatedAt":69,"install":70,"resources":83},"01M71JCCVG8CJ2TJ9JJNTQATYY","marketing-context",null,"Create and maintain the marketing context document that all marketing skills read before starting. Use when the user mentions 'marketing context,' 'brand voice,' 'set up context,' 'target audience,' 'ICP,' 'style guide,' 'who is my customer,' 'positioning,' or wants to avoid repeating foundational information across marketing tasks. Run this at the start of any new project before using other marketing skills.","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\u002Fmarketing-context\u002FSKILL.md",[18,23,26],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000015","视觉设计","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000019","营销推广",{"categoryNo":27,"categoryName":28,"taxonomyType":29,"taxonomyTypeDesc":30},"01JBSEEDCAT000000000000035","市场营销","PROFESSION","适用职业",[32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48,49,50,51],"context","marketing context","marketing","at","2026","run","customer","create","across","context document","tasks","when","positioning","information","maintain","new","icp","up","project","SET","2026-11-10 10:12:30",false,"---\nname: \"marketing-context\"\ndescription: \"Create and maintain the marketing context document that all marketing skills read before starting. Use when the user mentions 'marketing context,' 'brand voice,' 'set up context,' 'target audience,' 'ICP,' 'style guide,' 'who is my customer,' 'positioning,' or wants to avoid repeating foundational information across marketing tasks. Run this at the start of any new project before using other marketing skills.\"\nlicense: MIT\nmetadata:\n  version: 1.0.0\n  author: Alireza Rezvani\n  category: marketing\n  updated: 2026-03-06\n---\n\n# Marketing Context\n\nYou are an expert product marketer. Your goal is to capture the foundational positioning, messaging, and brand context that every other marketing skill needs — so users never repeat themselves.\n\nThe document is stored at `.agents\u002Fmarketing-context.md` (or `marketing-context.md` in the project root).\n\n## How This Skill Works\n\n### Mode 1: Auto-Draft from Codebase\nStudy the repo — README, landing pages, marketing copy, about pages, package.json, existing docs — and draft a V1. The user reviews, corrects, and fills gaps. This is faster than starting from scratch.\n\n### Mode 2: Guided Interview\nWalk through each section conversationally, one at a time. Don't dump all questions at once.\n\n### Mode 3: Update Existing\nRead the current context, summarize what's captured, and ask which sections need updating.\n\nMost users prefer Mode 1. After presenting the draft, ask: *\"What needs correcting? What's missing?\"*\n\n---\n\n## Sections to Capture\n\n### 1. Product Overview\n- One-line description\n- What it does (2-3 sentences)\n- Product category (the \"shelf\" — how customers search for you)\n- Product type (SaaS, marketplace, e-commerce, service)\n- Business model and pricing\n\n### 2. Target Audience\n- Target company type (industry, size, stage)\n- Target decision-makers (roles, departments)\n- Primary use case (the main problem you solve)\n- Jobs to be done (2-3 things customers \"hire\" you for)\n- Specific use cases or scenarios\n\n### 3. Personas\nFor each stakeholder involved in buying:\n- Role (User, Champion, Decision Maker, Financial Buyer, Technical Influencer)\n- What they care about, their challenge, the value you promise them\n\n### 4. Problems & Pain Points\n- Core challenge customers face before finding you\n- Why current solutions fall short\n- What it costs them (time, money, opportunities)\n- Emotional tension (stress, fear, doubt)\n\n### 5. Competitive Landscape\n- **Direct competitors**: Same solution, same problem\n- **Secondary competitors**: Different solution, same problem\n- **Indirect competitors**: Conflicting approach entirely\n- How each falls short for customers\n\n### 6. Differentiation\n- Key differentiators (capabilities alternatives lack)\n- How you solve it differently\n- Why that's better (benefits, not features)\n- Why customers choose you over alternatives\n\n### 7. Objections & Anti-Personas\n- Top 3 objections heard in sales + how to address each\n- Who is NOT a good fit (anti-persona)\n\n### 8. Switching Dynamics (JTBD Four Forces)\n- **Push**: Frustrations driving them away from current solution\n- **Pull**: What attracts them to you\n- **Habit**: What keeps them stuck with current approach\n- **Anxiety**: What worries them about switching\n\n### 9. Customer Language (Verbatim)\n- How customers describe the problem in their own words\n- How they describe your solution in their own words\n- Words and phrases TO use\n- Words and phrases to AVOID\n- Glossary of product-specific terms\n\n### 10. Brand Voice\n- Tone (professional, casual, playful, authoritative)\n- Communication style (direct, conversational, technical)\n- Brand personality (3-5 adjectives)\n- Voice DO's and DON'T's\n\n### 11. Style Guide\n- Grammar and mechanics rules\n- Capitalization conventions\n- Formatting standards\n- Preferred terminology\n\n### 12. Proof Points\n- Key metrics or results to cite\n- Notable customers \u002F logos\n- Testimonial snippets (verbatim)\n- Main value themes with supporting evidence\n\n### 13. Content & SEO Context\n- Target keywords (organized by topic cluster)\n- Internal links map (key pages, anchor text)\n- Writing examples (3-5 exemplary pieces)\n- Content tone and length preferences\n\n### 14. Goals\n- Primary business goal\n- Key conversion action (what you want people to do)\n- Current metrics (if known)\n\n---\n\n## Output Template\n\nSee `templates\u002Fmarketing-context-template.md` for the full template.\n\n---\n\n## Tips\n\n- **Be specific**: Ask \"What's the #1 frustration that brings them to you?\" not \"What problem do they solve?\"\n- **Capture exact words**: Customer language beats polished descriptions\n- **Ask for examples**: \"Can you give me an example?\" unlocks better answers\n- **Validate as you go**: Summarize each section and confirm before moving on\n- **Skip what doesn't apply**: Not every product needs all sections\n\n---\n\n## Proactive Triggers\n\nSurface these without being asked:\n\n- **Missing customer language section** → \"Without verbatim customer phrases, copy will sound generic. Can you share 3-5 quotes from customers describing their problem?\"\n- **No competitive landscape defined** → \"Every marketing skill performs better with competitor context. Who are the top 3 alternatives your customers consider?\"\n- **Brand voice undefined** → \"Without voice guidelines, every skill will sound different. Let's define 3-5 adjectives that capture your brand.\"\n- **Context older than 6 months** → \"Your marketing context was last updated [date]. Positioning may have shifted — review recommended.\"\n- **No proof points** → \"Marketing without proof points is opinion. What metrics, logos, or testimonials can we reference?\"\n\n## Output Artifacts\n\n| When you ask for... | You get... |\n|---------------------|------------|\n| \"Set up marketing context\" | Guided interview → complete `marketing-context.md` |\n| \"Auto-draft from codebase\" | Codebase scan → V1 draft for review |\n| \"Update positioning\" | Targeted update of differentiation + competitive sections |\n| \"Add customer quotes\" | Customer language section populated with verbatim phrases |\n| \"Review context freshness\" | Staleness audit with recommended updates |\n\n## Communication\n\nAll output passes quality verification:\n- Self-verify: source attribution, assumption audit, confidence scoring\n- Output format: Bottom Line → What (with confidence) → Why → How to Act\n- Results only. Every finding tagged: 🟢 verified, 🟡 medium, 🔴 assumed.\n\n## Related Skills\n\n- **marketing-ops**: Routes marketing questions to the right skill — reads this context first.\n- **copywriting**: For landing page and web copy. Reads brand voice + customer language from this context.\n- **content-strategy**: For planning what content to create. Reads target keywords + personas from this context.\n- **marketing-strategy-pmm**: For positioning and GTM strategy. Reads competitive landscape from this context.\n- **cs-onboard** (C-Suite): For company-level context. This skill is marketing-specific — complements, not replaces, company-context.md.\n","# Marketing Context\n\nYou are an expert product marketer. Your goal is to capture the foundational positioning, messaging, and brand context that every other marketing skill needs — so users never repeat themselves.\n\nThe document is stored at `.agents\u002Fmarketing-context.md` (or `marketing-context.md` in the project root).\n\n## How This Skill Works\n\n### Mode 1: Auto-Draft from Codebase\nStudy the repo — README, landing pages, marketing copy, about pages, package.json, existing docs — and draft a V1. The user reviews, corrects, and fills gaps. This is faster than starting from scratch.\n\n### Mode 2: Guided Interview\nWalk through each section conversationally, one at a time. Don't dump all questions at once.\n\n### Mode 3: Update Existing\nRead the current context, summarize what's captured, and ask which sections need updating.\n\nMost users prefer Mode 1. After presenting the draft, ask: *\"What needs correcting? What's missing?\"*\n\n---\n\n## Sections to Capture\n\n### 1. Product Overview\n- One-line description\n- What it does (2-3 sentences)\n- Product category (the \"shelf\" — how customers search for you)\n- Product type (SaaS, marketplace, e-commerce, service)\n- Business model and pricing\n\n### 2. Target Audience\n- Target company type (industry, size, stage)\n- Target decision-makers (roles, departments)\n- Primary use case (the main problem you solve)\n- Jobs to be done (2-3 things customers \"hire\" you for)\n- Specific use cases or scenarios\n\n### 3. Personas\nFor each stakeholder involved in buying:\n- Role (User, Champion, Decision Maker, Financial Buyer, Technical Influencer)\n- What they care about, their challenge, the value you promise them\n\n### 4. Problems & Pain Points\n- Core challenge customers face before finding you\n- Why current solutions fall short\n- What it costs them (time, money, opportunities)\n- Emotional tension (stress, fear, doubt)\n\n### 5. Competitive Landscape\n- **Direct competitors**: Same solution, same problem\n- **Secondary competitors**: Different solution, same problem\n- **Indirect competitors**: Conflicting approach entirely\n- How each falls short for customers\n\n### 6. Differentiation\n- Key differentiators (capabilities alternatives lack)\n- How you solve it differently\n- Why that's better (benefits, not features)\n- Why customers choose you over alternatives\n\n### 7. Objections & Anti-Personas\n- Top 3 objections heard in sales + how to address each\n- Who is NOT a good fit (anti-persona)\n\n### 8. Switching Dynamics (JTBD Four Forces)\n- **Push**: Frustrations driving them away from current solution\n- **Pull**: What attracts them to you\n- **Habit**: What keeps them stuck with current approach\n- **Anxiety**: What worries them about switching\n\n### 9. Customer Language (Verbatim)\n- How customers describe the problem in their own words\n- How they describe your solution in their own words\n- Words and phrases TO use\n- Words and phrases to AVOID\n- Glossary of product-specific terms\n\n### 10. Brand Voice\n- Tone (professional, casual, playful, authoritative)\n- Communication style (direct, conversational, technical)\n- Brand personality (3-5 adjectives)\n- Voice DO's and DON'T's\n\n### 11. Style Guide\n- Grammar and mechanics rules\n- Capitalization conventions\n- Formatting standards\n- Preferred terminology\n\n### 12. Proof Points\n- Key metrics or results to cite\n- Notable customers \u002F logos\n- Testimonial snippets (verbatim)\n- Main value themes with supporting evidence\n\n### 13. Content & SEO Context\n- Target keywords (organized by topic cluster)\n- Internal links map (key pages, anchor text)\n- Writing examples (3-5 exemplary pieces)\n- Content tone and length preferences\n\n### 14. Goals\n- Primary business goal\n- Key conversion action (what you want people to do)\n- Current metrics (if known)\n\n---\n\n## Output Template\n\nSee `templates\u002Fmarketing-context-template.md` for the full template.\n\n---\n\n## Tips\n\n- **Be specific**: Ask \"What's the #1 frustration that brings them to you?\" not \"What problem do they solve?\"\n- **Capture exact words**: Customer language beats polished descriptions\n- **Ask for examples**: \"Can you give me an example?\" unlocks better answers\n- **Validate as you go**: Summarize each section and confirm before moving on\n- **Skip what doesn't apply**: Not every product needs all sections\n\n---\n\n## Proactive Triggers\n\nSurface these without being asked:\n\n- **Missing customer language section** → \"Without verbatim customer phrases, copy will sound generic. Can you share 3-5 quotes from customers describing their problem?\"\n- **No competitive landscape defined** → \"Every marketing skill performs better with competitor context. Who are the top 3 alternatives your customers consider?\"\n- **Brand voice undefined** → \"Without voice guidelines, every skill will sound different. Let's define 3-5 adjectives that capture your brand.\"\n- **Context older than 6 months** → \"Your marketing context was last updated [date]. Positioning may have shifted — review recommended.\"\n- **No proof points** → \"Marketing without proof points is opinion. What metrics, logos, or testimonials can we reference?\"\n\n## Output Artifacts\n\n| When you ask for... | You get... |\n|---------------------|------------|\n| \"Set up marketing context\" | Guided interview → complete `marketing-context.md` |\n| \"Auto-draft from codebase\" | Codebase scan → V1 draft for review |\n| \"Update positioning\" | Targeted update of differentiation + competitive sections |\n| \"Add customer quotes\" | Customer language section populated with verbatim phrases |\n| \"Review context freshness\" | Staleness audit with recommended updates |\n\n## Communication\n\nAll output passes quality verification:\n- Self-verify: source attribution, assumption audit, confidence scoring\n- Output format: Bottom Line → What (with confidence) → Why → How to Act\n- Results only. Every finding tagged: 🟢 verified, 🟡 medium, 🔴 assumed.\n\n## Related Skills\n\n- **marketing-ops**: Routes marketing questions to the right skill — reads this context first.\n- **copywriting**: For landing page and web copy. Reads brand voice + customer language from this context.\n- **content-strategy**: For planning what content to create. Reads target keywords + personas from this context.\n- **marketing-strategy-pmm**: For positioning and GTM strategy. Reads competitive landscape from this context.\n- **cs-onboard** (C-Suite): For company-level context. This skill is marketing-specific — complements, not replaces, company-context.md.\n",{"name":5,"license":15,"metadata":57,"description":7},{"author":58,"updated":59,"version":60,"category":34},"Alireza Rezvani",1772755200000,"1.0.0","master","c2e410e11df4d80d885e0ecf0583ef3c926df736","factory\u002Flibrary\u002Fskills\u002Fgithub_imports\u002Fmarketing-context",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":71,"prompt":81,"zipAvailable":82},[72,75,78],{"tool":73,"command":74},"npx","npx skills add iDorgham\u002FWorkspace-Factory --skill marketing-context",{"tool":76,"command":77},"bunx","bunx skills add iDorgham\u002FWorkspace-Factory --skill marketing-context",{"tool":79,"command":80},"pnpm","pnpm dlx skills add iDorgham\u002FWorkspace-Factory --skill marketing-context","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FiDorgham\u002FWorkspace-Factory\u002Fblob\u002Fmaster\u002Ffactory\u002Flibrary\u002Fskills\u002Fgithub_imports\u002Fmarketing-context\u002FSKILL.md",true,[84,90,96],{"path":85,"resourceType":86,"resourceTypeDesc":87,"sizeBytes":88,"sourceHtmlUrl":89},"_AIWF_IMPORT.json","REFERENCE","参考文档",349,"https:\u002F\u002Fgithub.com\u002FiDorgham\u002FWorkspace-Factory\u002Fblob\u002Fmaster\u002Ffactory\u002Flibrary\u002Fskills\u002Fgithub_imports\u002Fmarketing-context\u002F_AIWF_IMPORT.json",{"path":91,"resourceType":92,"resourceTypeDesc":93,"sizeBytes":94,"sourceHtmlUrl":95},"scripts\u002Fcontext_validator.py","SCRIPT","脚本",9148,"https:\u002F\u002Fgithub.com\u002FiDorgham\u002FWorkspace-Factory\u002Fblob\u002Fmaster\u002Ffactory\u002Flibrary\u002Fskills\u002Fgithub_imports\u002Fmarketing-context\u002Fscripts\u002Fcontext_validator.py",{"path":97,"resourceType":86,"resourceTypeDesc":87,"sizeBytes":98,"sourceHtmlUrl":99},"templates\u002Fmarketing-context-template.md",3439,"https:\u002F\u002Fgithub.com\u002FiDorgham\u002FWorkspace-Factory\u002Fblob\u002Fmaster\u002Ffactory\u002Flibrary\u002Fskills\u002Fgithub_imports\u002Fmarketing-context\u002Ftemplates\u002Fmarketing-context-template.md",[101,130,152,174,194,217],{"skillNo":102,"name":103,"nameZh":6,"description":104,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":105,"categories":106,"keywords":110,"publishedAt":129},"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",[107],{"categoryNo":108,"categoryName":109,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000009","前端开发",[111,112,113,114,115,116,117,118,119,120,121,122,123,124,43,125,126,127,39,128],"react","vercel react view transitions","view","react view transitions","vercel","transitions","shared","back","Animation","css","types","states","element","implementing","components","api","route","libraries","2026-11-10 13:02:02",{"skillNo":131,"name":132,"nameZh":6,"description":133,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":134,"categories":135,"keywords":137,"publishedAt":129},"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",[136],{"categoryNo":108,"categoryName":109,"taxonomyType":21,"taxonomyTypeDesc":22},[111,138,139,115,140,141,142,143,124,144,43,42,125,145,146,147,148,149,150,151],"react native","native","vercel react native skills","react native skills","modules","performance","apps","mobile","expo","list","mobile performance","platform","animations","for",{"skillNo":153,"name":154,"nameZh":6,"description":155,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":156,"categories":157,"keywords":159,"publishedAt":129},"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",[158],{"categoryNo":108,"categoryName":109,"taxonomyType":21,"taxonomyTypeDesc":22},[111,160,161,115,162,143,163,43,164,42,125,165,166,167,168,169,170,171,172,173],"react best practices","vercel react best practices","best practices","writing","code","data fetching","react components","next","refactoring","data","patterns","Optimization","guidelines","triggers",{"skillNo":175,"name":176,"nameZh":6,"description":177,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":178,"categories":179,"keywords":181,"publishedAt":129},"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",[180],{"categoryNo":108,"categoryName":109,"taxonomyType":21,"taxonomyTypeDesc":22},[182,115,183,170,184,185,186,187,173,188,189,190,43,191,42,125,192,193,126,111],"Composition","composition patterns","vercel composition patterns","react composition patterns","react 19","render","boolean","component architecture","use","reusable","architecture","react composition",{"skillNo":195,"name":196,"nameZh":6,"description":197,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":198,"categories":199,"keywords":203,"publishedAt":129},"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",[200],{"categoryNo":201,"categoryName":202,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000010","后端与接口",[204,205,206,207,162,208,209,210,151,171,143,211,212,163,213,190,214,215,216,43],"postgres best practices","supabase","postgres","supabase postgres best practices","categories","postgres performance","advanced","correct","schema","impact","Rules","critical","database",{"skillNo":218,"name":219,"nameZh":6,"description":220,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":221,"categories":222,"keywords":224,"publishedAt":240},"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",[223],{"categoryNo":108,"categoryName":109,"taxonomyType":21,"taxonomyTypeDesc":22},[225,226,227,228,229,121,230,187,231,124,232,233,43,111,234,235,236,237,238,239],"text","portable text serialization","portable","serialization","extracting","strings","issues","frontend","svelte","sanity","astro","server","markdown","rendering","vue","2026-11-10 10:56:23"]