[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7C8GF13MPD855ZDMVSE06MT":3,"skill-same:01M7C8GF13MPD855ZDMVSE06MT":50},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":27,"commitSha":28,"skillDirectory":29,"forksCount":30,"repositoryHtmlUrl":31,"repositoryHomepageUrl":32,"ownerHtmlUrl":33,"ownerBlogUrl":6,"ownerDescription":34,"updatedAt":35,"install":36,"resources":49},"01M7C8GF13MPD855ZDMVSE06MT","c4-context",null,"Expert C4 Context-level documentation specialist. Creates high-level system context diagrams, documents personas, user journeys, system features, and external dependencies.","YYC-Cube\u002FYYC3-Knowledge-Base","YYC-Cube","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F235006543?v=4","01M79J2PH4SWD2X0825X6PN748","yyc3","01M79J2PHVK3F6ZBYT8K2SCZCW",1,"MIT","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-Skills-技能包\u002FYYC3-Skills-技能包-antigravity-awesome-skills\u002Fplugins\u002Fantigravity-awesome-skills\u002Fskills\u002Fc4-context\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: c4-context\ndescription: Expert C4 Context-level documentation specialist. Creates high-level system context diagrams, documents personas, user journeys, system features, and external dependencies.\nrisk: unknown\nsource: community\ndate_added: '2026-02-27'\n---\n\n# C4 Context Level: System Context\n\n## Use this skill when\n\n- Working on c4 context level: system context tasks or workflows\n- Needing guidance, best practices, or checklists for c4 context level: system context\n\n## Do not use this skill when\n\n- The task is unrelated to c4 context level: system context\n- You need a different domain or tool outside this scope\n\n## Instructions\n\n- Clarify goals, constraints, and required inputs.\n- Apply relevant best practices and validate outcomes.\n- Provide actionable steps and verification.\n- If detailed examples are required, open `resources\u002Fimplementation-playbook.md`.\n\n## System Overview\n\n### Short Description\n\n[One-sentence description of what the system does]\n\n### Long Description\n\n[Detailed description of the system's purpose, capabilities, and the problems it solves]\n\n## Personas\n\n### [Persona Name]\n\n- **Type**: [Human User \u002F Programmatic User \u002F External System]\n- **Description**: [Who this persona is and what they need]\n- **Goals**: [What this persona wants to achieve]\n- **Key Features Used**: [List of features this persona uses]\n\n## System Features\n\n### [Feature Name]\n\n- **Description**: [What this feature does]\n- **Users**: [Which personas use this feature]\n- **User Journey**: [Link to user journey map]\n\n## User Journeys\n\n### [Feature Name] - [Persona Name] Journey\n\n1. [Step 1]: [Description]\n2. [Step 2]: [Description]\n3. [Step 3]: [Description]\n   ...\n\n### [External System] Integration Journey\n\n1. [Step 1]: [Description]\n2. [Step 2]: [Description]\n   ...\n\n## External Systems and Dependencies\n\n### [External System Name]\n\n- **Type**: [Database, API, Service, Message Queue, etc.]\n- **Description**: [What this external system provides]\n- **Integration Type**: [API, Events, File Transfer, etc.]\n- **Purpose**: [Why the system depends on this]\n\n## System Context Diagram\n\n[Mermaid diagram showing system, users, and external systems]\n\n## Related Documentation\n\n- Container Documentation\n- Component Documentation\n```\n\n## Context Diagram Template\n\nAccording to the [C4 model](https:\u002F\u002Fc4model.com\u002Fdiagrams\u002Fsystem-context), a System Context diagram shows the system as a box in the center, surrounded by its users and the other systems that it interacts with. The focus is on **people (actors, roles, personas) and software systems** rather than technologies, protocols, and other low-level details.\n\nUse proper Mermaid C4 syntax:\n\n```mermaid\nC4Context\n    title System Context Diagram\n\n    Person(user, \"User\", \"Uses the system to accomplish their goals\")\n    System(system, \"System Name\", \"Provides features X, Y, and Z\")\n    System_Ext(external1, \"External System 1\", \"Provides service A\")\n    System_Ext(external2, \"External System 2\", \"Provides service B\")\n    SystemDb(externalDb, \"External Database\", \"Stores data\")\n\n    Rel(user, system, \"Uses\")\n    Rel(system, external1, \"Uses\", \"API\")\n    Rel(system, external2, \"Sends events to\")\n    Rel(system, externalDb, \"Reads from and writes to\")\n```\n\n**Key Principles** (from [c4model.com](https:\u002F\u002Fc4model.com\u002Fdiagrams\u002Fsystem-context)):\n\n- Focus on **people and software systems**, not technologies\n- Show the **system boundary** clearly\n- Include all **users** (human and programmatic)\n- Include all **external systems** the system interacts with\n- Keep it **stakeholder-friendly** - understandable by non-technical audiences\n- Avoid showing technologies, protocols, or low-level details\n\n## Example Interactions\n\n- \"Create C4 Context-level documentation for the system\"\n- \"Identify all personas and create user journey maps for key features\"\n- \"Document external systems and create a system context diagram\"\n- \"Analyze system documentation and create comprehensive context documentation\"\n- \"Map user journeys for all key features including programmatic users\"\n\n## Key Distinctions\n\n- **vs C4-Container agent**: Provides high-level system view; Container agent focuses on deployment architecture\n- **vs C4-Component agent**: Focuses on system context; Component agent focuses on logical component structure\n- **vs C4-Code agent**: Provides stakeholder-friendly overview; Code agent provides technical code details\n\n## Output Examples\n\nWhen creating context documentation, provide:\n\n- Clear system descriptions (short and long)\n- Comprehensive persona documentation (human and programmatic)\n- Complete feature lists with descriptions\n- Detailed user journey maps for all key features\n- Complete external system and dependency documentation\n- Mermaid context diagram showing system, users, and external systems\n- Links to container and component documentation\n- Stakeholder-friendly documentation understandable by non-technical audiences\n- Consistent documentation format\n\n## Limitations\n- Use this skill only when the task clearly matches the scope described above.\n- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.\n- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.\n","# C4 Context Level: System Context\n\n## Use this skill when\n\n- Working on c4 context level: system context tasks or workflows\n- Needing guidance, best practices, or checklists for c4 context level: system context\n\n## Do not use this skill when\n\n- The task is unrelated to c4 context level: system context\n- You need a different domain or tool outside this scope\n\n## Instructions\n\n- Clarify goals, constraints, and required inputs.\n- Apply relevant best practices and validate outcomes.\n- Provide actionable steps and verification.\n- If detailed examples are required, open `resources\u002Fimplementation-playbook.md`.\n\n## System Overview\n\n### Short Description\n\n[One-sentence description of what the system does]\n\n### Long Description\n\n[Detailed description of the system's purpose, capabilities, and the problems it solves]\n\n## Personas\n\n### [Persona Name]\n\n- **Type**: [Human User \u002F Programmatic User \u002F External System]\n- **Description**: [Who this persona is and what they need]\n- **Goals**: [What this persona wants to achieve]\n- **Key Features Used**: [List of features this persona uses]\n\n## System Features\n\n### [Feature Name]\n\n- **Description**: [What this feature does]\n- **Users**: [Which personas use this feature]\n- **User Journey**: [Link to user journey map]\n\n## User Journeys\n\n### [Feature Name] - [Persona Name] Journey\n\n1. [Step 1]: [Description]\n2. [Step 2]: [Description]\n3. [Step 3]: [Description]\n   ...\n\n### [External System] Integration Journey\n\n1. [Step 1]: [Description]\n2. [Step 2]: [Description]\n   ...\n\n## External Systems and Dependencies\n\n### [External System Name]\n\n- **Type**: [Database, API, Service, Message Queue, etc.]\n- **Description**: [What this external system provides]\n- **Integration Type**: [API, Events, File Transfer, etc.]\n- **Purpose**: [Why the system depends on this]\n\n## System Context Diagram\n\n[Mermaid diagram showing system, users, and external systems]\n\n## Related Documentation\n\n- Container Documentation\n- Component Documentation\n```\n\n## Context Diagram Template\n\nAccording to the [C4 model](https:\u002F\u002Fc4model.com\u002Fdiagrams\u002Fsystem-context), a System Context diagram shows the system as a box in the center, surrounded by its users and the other systems that it interacts with. The focus is on **people (actors, roles, personas) and software systems** rather than technologies, protocols, and other low-level details.\n\nUse proper Mermaid C4 syntax:\n\n```mermaid\nC4Context\n    title System Context Diagram\n\n    Person(user, \"User\", \"Uses the system to accomplish their goals\")\n    System(system, \"System Name\", \"Provides features X, Y, and Z\")\n    System_Ext(external1, \"External System 1\", \"Provides service A\")\n    System_Ext(external2, \"External System 2\", \"Provides service B\")\n    SystemDb(externalDb, \"External Database\", \"Stores data\")\n\n    Rel(user, system, \"Uses\")\n    Rel(system, external1, \"Uses\", \"API\")\n    Rel(system, external2, \"Sends events to\")\n    Rel(system, externalDb, \"Reads from and writes to\")\n```\n\n**Key Principles** (from [c4model.com](https:\u002F\u002Fc4model.com\u002Fdiagrams\u002Fsystem-context)):\n\n- Focus on **people and software systems**, not technologies\n- Show the **system boundary** clearly\n- Include all **users** (human and programmatic)\n- Include all **external systems** the system interacts with\n- Keep it **stakeholder-friendly** - understandable by non-technical audiences\n- Avoid showing technologies, protocols, or low-level details\n\n## Example Interactions\n\n- \"Create C4 Context-level documentation for the system\"\n- \"Identify all personas and create user journey maps for key features\"\n- \"Document external systems and create a system context diagram\"\n- \"Analyze system documentation and create comprehensive context documentation\"\n- \"Map user journeys for all key features including programmatic users\"\n\n## Key Distinctions\n\n- **vs C4-Container agent**: Provides high-level system view; Container agent focuses on deployment architecture\n- **vs C4-Component agent**: Focuses on system context; Component agent focuses on logical component structure\n- **vs C4-Code agent**: Provides stakeholder-friendly overview; Code agent provides technical code details\n\n## Output Examples\n\nWhen creating context documentation, provide:\n\n- Clear system descriptions (short and long)\n- Comprehensive persona documentation (human and programmatic)\n- Complete feature lists with descriptions\n- Detailed user journey maps for all key features\n- Complete external system and dependency documentation\n- Mermaid context diagram showing system, users, and external systems\n- Links to container and component documentation\n- Stakeholder-friendly documentation understandable by non-technical audiences\n- Consistent documentation format\n\n## Limitations\n- Use this skill only when the task clearly matches the scope described above.\n- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.\n- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.\n",{"name":5,"risk":24,"source":25,"date_added":26,"description":7},"unknown","community","2026-02-27","main","87afe6ce96220accf50a345dea46784c8c9f210e","YYC3-Skills-技能包\u002FYYC3-Skills-技能包-antigravity-awesome-skills\u002Fplugins\u002Fantigravity-awesome-skills\u002Fskills\u002Fc4-context",0,"https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base","https:\u002F\u002Fkb.yyc3.top\u002F","https:\u002F\u002Fgithub.com\u002FYYC-Cube","万象归元于云枢 | 深栈智启新纪元","2026-11-10 10:37:32",{"source":8,"skillName":5,"commands":37,"prompt":47,"zipAvailable":48},[38,41,44],{"tool":39,"command":40},"npx","npx skills add YYC-Cube\u002FYYC3-Knowledge-Base --skill c4-context",{"tool":42,"command":43},"bunx","bunx skills add YYC-Cube\u002FYYC3-Knowledge-Base --skill c4-context",{"tool":45,"command":46},"pnpm","pnpm dlx skills add YYC-Cube\u002FYYC3-Knowledge-Base --skill c4-context","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-Skills-技能包\u002FYYC3-Skills-技能包-antigravity-awesome-skills\u002Fplugins\u002Fantigravity-awesome-skills\u002Fskills\u002Fc4-context\u002FSKILL.md",true,[],[51,58,65,72,79,86],{"skillNo":52,"name":53,"nameZh":6,"description":54,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":55,"categories":56,"keywords":57,"publishedAt":19},"01M7CTDWHERCXPQCP0K03A86AS","vercel-sandbox","Run agent-browser + Chrome inside Vercel Sandbox microVMs for browser automation from any Vercel-deployed app. Use when the user needs browser automation in a Vercel app (Next.js, SvelteKit, Nuxt, Remix, Astro, etc.), wants to run headless Chrome without binary size limits, needs persistent browser sessions across commands, or wants ephemeral isolated browser environments. Triggers include \"Vercel Sandbox browser\", \"microVM Chrome\", \"agent-browser in sandbox\", \"browser automation on Vercel\", or any task requiring Chrome in a Vercel Sandbox.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-WebSpec-Web标准\u002FYYC3-WebSpec-Web标准-standards\u002Fbrowser-agent\u002Fskills\u002Fvercel-sandbox\u002FSKILL.md",[],[],{"skillNo":59,"name":60,"nameZh":6,"description":61,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":62,"categories":63,"keywords":64,"publishedAt":19},"01M7CTD8D2BNJY54S65M47HEJA","slack","Interact with Slack workspaces using browser automation. Use when the user needs to check unread channels, navigate Slack, send messages, extract data, find information, search conversations, or automate any Slack task. Triggers include \"check my Slack\", \"what channels have unreads\", \"send a message to\", \"search Slack for\", \"extract from Slack\", \"find who said\", or any task requiring programmatic Slack interaction.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-WebSpec-Web标准\u002FYYC3-WebSpec-Web标准-standards\u002Fbrowser-agent\u002Fskills\u002Fslack\u002FSKILL.md",[],[],{"skillNo":66,"name":67,"nameZh":6,"description":68,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":69,"categories":70,"keywords":71,"publishedAt":19},"01M7CTCSSB8ZP3Q58C3YZDZK1W","electron","Automate Electron desktop apps (VS Code, Slack, Discord, Figma, Notion, Spotify, etc.) using agent-browser via Chrome DevTools Protocol. Use when the user needs to interact with an Electron app, automate a desktop app, connect to a running app, control a native app, or test an Electron application. Triggers include \"automate Slack app\", \"control VS Code\", \"interact with Discord app\", \"test this Electron app\", \"connect to desktop app\", or any task requiring automation of a native Electron application.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-WebSpec-Web标准\u002FYYC3-WebSpec-Web标准-standards\u002Fbrowser-agent\u002Fskills\u002Felectron\u002FSKILL.md",[],[],{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":19},"01M7CTCBJY76688V4DCZGWFHGQ","dogfood","Systematically explore and test a web application to find bugs, UX issues, and other problems. Use when asked to \"dogfood\", \"QA\", \"exploratory test\", \"find issues\", \"bug hunt\", \"test this app\u002Fsite\u002Fplatform\", or review the quality of a web application. Produces a structured report with full reproduction evidence -- step-by-step screenshots, repro videos, and detailed repro steps for every issue -- so findings can be handed directly to the responsible teams.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-WebSpec-Web标准\u002FYYC3-WebSpec-Web标准-standards\u002Fbrowser-agent\u002Fskills\u002Fdogfood\u002FSKILL.md",[],[],{"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":85,"publishedAt":19},"01M7CTC4H0FFGVEAQR9PA4GA1A","agent-browser","Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to \"open a website\", \"fill out a form\", \"click a button\", \"take a screenshot\", \"scrape data from a page\", \"test this web app\", \"login to a site\", \"automate browser actions\", or any task requiring programmatic web interaction.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-WebSpec-Web标准\u002FYYC3-WebSpec-Web标准-standards\u002Fbrowser-agent\u002Fskills\u002Fagent-browser\u002FSKILL.md",[],[],{"skillNo":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":19},"01M7CTBKVFYBG78FDSABSDJTTQ","shadcn","Manages shadcn components and projects — adding, searching, fixing, debugging, styling, and composing UI, including chat interfaces. Provides project context, component docs, and usage examples. Applies when working with shadcn\u002Fui, component registries, presets, --preset codes, or any project with a components.json file. Also triggers for \"shadcn init\", \"create an app with --preset\", \"switch to --preset\", and for building a design system or applying a DESIGN.md or brand spec to shadcn\u002Fui.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-UI-界面组件\u002FYYC3-UI-界面组件-ui\u002Fskills\u002Fshadcn\u002FSKILL.md",[],[]]