[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7DMXYKGCQWJ5KGXVMHACP64":3,"skill-same:01M7DMXYKGCQWJ5KGXVMHACP64":62},{"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":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":29,"ownerHtmlUrl":30,"ownerBlogUrl":31,"ownerDescription":32,"updatedAt":33,"install":34,"resources":47},"01M7DMXYKGCQWJ5KGXVMHACP64","setup-design-system",null,"Curate a studio design system for a prototype, or assess and import an existing React system with its theme and assets. Use document-component for one component.","itspatmorgan\u002Fdesign-studio","itspatmorgan","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F5795564?v=4","01M7DMV13S3S8TFBGHQPFWTQ2E","Patrick Morgan","01M7DMV14EW8AYDS9F3B33FH6K",161,"MIT","https:\u002F\u002Fgithub.com\u002Fitspatmorgan\u002Fdesign-studio\u002Fblob\u002Fmain\u002Fsrc\u002Fplatform\u002Fmodules\u002Fsystems\u002Fskills\u002Fsetup-design-system\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: setup-design-system\ndescription: \"Curate a studio design system for a prototype, or assess and import an existing React system with its theme and assets. Use document-component for one component.\"\n---\n\n## Scope and input\n\nRead the [system authoring context](..\u002F..\u002Fcontext\u002Fauthoring.md) and the contract sections it selects. Use [manage-modules](..\u002F..\u002F..\u002F..\u002Fskills\u002Fmanage-modules\u002FSKILL.md) when creation, registration, default changes, or retirement are needed.\n\nInspect the target system, configuration, component destinations, and packages. For replacement or retirement, inspect all consumers, including disabled module content.\n\nRead [System curation](..\u002F..\u002Fcontext\u002Fcuration.md) when establishing or resuming setup. Overview provides the initial prompt builder and the system's metrics. Keep agreed direction, sources, and next action in the saved curation record, and guide reviews in chat using system navigation and prototype links. Inspect existing records before asking the person to repeat decisions.\n\nOverview prompts carry the person's source choice, preset, context, and requested next step. This skill owns the setup procedure and technical constraints. Resolve the target by its supplied system key. Preserve other systems, existing prototypes, and the default unless the person requests changes. A continuation of an assessment remains assessment-only until import is authorized.\n\nEstablish whether the person wants to curate a toolkit or bring an existing React system. For curation, start with what they want to prototype. A designer may name components and visual choices. For a product manager, decompose the intended flow into screens, states, and the smallest supporting kit. For an existing system, start with its source, inventory, and dependencies. Do not require a prototype idea to audit it and propose an import plan. Ask only for decisions needed for the next step.\n\nCollect missing system ID, component source or package, tokens, assets, and usage guidance. If only design files exist, inspect available material and report gaps.\n\nUse supplied decisions. Do not present the placeholder's styles as the person's product system.\n\n## Choose the path\n\n- Keep the starter while exploring, adapt it, or create a separate system according to the person's choice. Sample removal is a separate decision.\n- For a curated library kit, follow [Curate from libraries](references\u002Fcurated-libraries.md). Use shadcn as the curated starting point. Other React libraries can be assessed through the existing-system path.\n- For existing React code, follow [Assess an existing system](references\u002Fexisting-react-system.md) before importing. An assessment request alone does not authorize migration.\n\nDescribe the proposed components, theme, assets, dependencies, and known gaps in plain language. Apply already-authorized choices. Ask about unresolved scope or fidelity compromises before dependent work.\n\nContext and skills are separate curation decisions. Save supplied product knowledge; do not invent personas or product context to fill folders. Add a skill only for a demonstrated recurring task. Do not install a skills catalog during setup.\n\nFor an assessment-only request, report evidence, an import plan, adaptations, and unresolved questions. Cover the reusable system in stages when useful. No new system or prototype is required.\n\nWhen the person selects an existing target system, save the assessment summary there with stage `assessment` and link its detailed record. Open Overview for review. Missing production material can block one import stage without blocking a portable theme or asset stage. Do not create a system just to hold an assessment unless requested.\n\n## Establish the kit\n\n1. Adapt the chosen installed system in place if requested. Otherwise, preview `pnpm studio create-system` and apply authorized creation.\n2. Import components or connect the package. Avoid unnecessary copies of package code.\n3. Adapt aliases, dependencies, themes, and portals to the system contract. Place fonts, logos, and imagery using the [static asset convention](..\u002F..\u002F..\u002F..\u002Fcontext\u002Fassets.md).\n   Install packages in the target system's workspace, following [System libraries and dependencies](..\u002F..\u002Fcontext\u002Flibraries.md). Expose library APIs deliberately when prototypes need capabilities beyond the documented components. Record the selected component sources, foundations, icon sets, fonts, and other meaningful libraries in the library inventory. Omit implementation helpers and transitive dependencies. Listing a source does not expose its package API.\n4. Follow [document-component](..\u002Fdocument-component\u002FSKILL.md) for component pages and examples.\n5. Create or reuse one representative prototype in the person's folder. Verify the kit there and on its Systems pages.\n\nAdd shadcn components only for demonstrated gaps. Use the target system's configuration through isolated preparation; consult [shadcn configuration and DESIGN.md guidance](references\u002Fshadcn.md). Save reviewed resolved configuration separately from runtime integration. Never treat a CLI destination override as isolation of all writes.\n\n## Change the default and retire placeholders\n\nRun `pnpm build` before switching the default. Preview `pnpm studio configure --system \u003Cid>`, then apply confirmed choices with `--yes`.\n\nThe command preserves existing system choices. Migrate retained prototypes by updating imports and metadata together.\n\nIf cleanup is authorized, inspect all dependencies of each system being retired, including Product or Marketing. Include sample content and disabled modules.\n\nPreserve recoverable copies when replacing content. Use the [system lifecycle](..\u002F..\u002FREADME.md#system-lifecycle) to archive or permanently delete a retired system. Shadcn configuration belongs to each system; preserve the retained system's choices when retiring another. Preview changes and resolve dependencies instead of using `--force`.\n\nDo not remove another person's work merely because a contributor joined. Explain proposed starter cleanup and obtain unresolved choices.\n\n## Completion\n\nLocal creation registers the system and maintainer entry; external source is integrated into that scaffold. Set the intended [system declarations](..\u002F..\u002FREADME.md#structure) and [theme inventory](..\u002F..\u002FREADME.md#theme); validators check their structure. Adjust components and examples to those choices.\n\nReview representative components and pop-ups in every supported color mode. Verify that a single-mode system keeps its mode when Studio toggles. Follow the Working in Studio section of `AGENTS.md` for build and save requirements after migration.\n\nAfter completing the person's requested customization of an example system, set `overview.starter: false` in its `intro.tsx` and revise the summary to describe the customized system. This clears the example banner for everyone. Do not clear it just because the person opened or copied a setup prompt, or while assessment or customization is incomplete. Preserve any curation summary and saved decisions.\n\nReport source provenance, adaptations, the default system, verified prototype URL, and missing input. Return that prototype to initialization for reuse.\n\nFor imported product code, distinguish verified API, theme, and behavior fidelity from unresolved differences. A passing build alone does not establish equivalence with production.\n","## Scope and input\n\nRead the [system authoring context](..\u002F..\u002Fcontext\u002Fauthoring.md) and the contract sections it selects. Use [manage-modules](..\u002F..\u002F..\u002F..\u002Fskills\u002Fmanage-modules\u002FSKILL.md) when creation, registration, default changes, or retirement are needed.\n\nInspect the target system, configuration, component destinations, and packages. For replacement or retirement, inspect all consumers, including disabled module content.\n\nRead [System curation](..\u002F..\u002Fcontext\u002Fcuration.md) when establishing or resuming setup. Overview provides the initial prompt builder and the system's metrics. Keep agreed direction, sources, and next action in the saved curation record, and guide reviews in chat using system navigation and prototype links. Inspect existing records before asking the person to repeat decisions.\n\nOverview prompts carry the person's source choice, preset, context, and requested next step. This skill owns the setup procedure and technical constraints. Resolve the target by its supplied system key. Preserve other systems, existing prototypes, and the default unless the person requests changes. A continuation of an assessment remains assessment-only until import is authorized.\n\nEstablish whether the person wants to curate a toolkit or bring an existing React system. For curation, start with what they want to prototype. A designer may name components and visual choices. For a product manager, decompose the intended flow into screens, states, and the smallest supporting kit. For an existing system, start with its source, inventory, and dependencies. Do not require a prototype idea to audit it and propose an import plan. Ask only for decisions needed for the next step.\n\nCollect missing system ID, component source or package, tokens, assets, and usage guidance. If only design files exist, inspect available material and report gaps.\n\nUse supplied decisions. Do not present the placeholder's styles as the person's product system.\n\n## Choose the path\n\n- Keep the starter while exploring, adapt it, or create a separate system according to the person's choice. Sample removal is a separate decision.\n- For a curated library kit, follow [Curate from libraries](references\u002Fcurated-libraries.md). Use shadcn as the curated starting point. Other React libraries can be assessed through the existing-system path.\n- For existing React code, follow [Assess an existing system](references\u002Fexisting-react-system.md) before importing. An assessment request alone does not authorize migration.\n\nDescribe the proposed components, theme, assets, dependencies, and known gaps in plain language. Apply already-authorized choices. Ask about unresolved scope or fidelity compromises before dependent work.\n\nContext and skills are separate curation decisions. Save supplied product knowledge; do not invent personas or product context to fill folders. Add a skill only for a demonstrated recurring task. Do not install a skills catalog during setup.\n\nFor an assessment-only request, report evidence, an import plan, adaptations, and unresolved questions. Cover the reusable system in stages when useful. No new system or prototype is required.\n\nWhen the person selects an existing target system, save the assessment summary there with stage `assessment` and link its detailed record. Open Overview for review. Missing production material can block one import stage without blocking a portable theme or asset stage. Do not create a system just to hold an assessment unless requested.\n\n## Establish the kit\n\n1. Adapt the chosen installed system in place if requested. Otherwise, preview `pnpm studio create-system` and apply authorized creation.\n2. Import components or connect the package. Avoid unnecessary copies of package code.\n3. Adapt aliases, dependencies, themes, and portals to the system contract. Place fonts, logos, and imagery using the [static asset convention](..\u002F..\u002F..\u002F..\u002Fcontext\u002Fassets.md).\n   Install packages in the target system's workspace, following [System libraries and dependencies](..\u002F..\u002Fcontext\u002Flibraries.md). Expose library APIs deliberately when prototypes need capabilities beyond the documented components. Record the selected component sources, foundations, icon sets, fonts, and other meaningful libraries in the library inventory. Omit implementation helpers and transitive dependencies. Listing a source does not expose its package API.\n4. Follow [document-component](..\u002Fdocument-component\u002FSKILL.md) for component pages and examples.\n5. Create or reuse one representative prototype in the person's folder. Verify the kit there and on its Systems pages.\n\nAdd shadcn components only for demonstrated gaps. Use the target system's configuration through isolated preparation; consult [shadcn configuration and DESIGN.md guidance](references\u002Fshadcn.md). Save reviewed resolved configuration separately from runtime integration. Never treat a CLI destination override as isolation of all writes.\n\n## Change the default and retire placeholders\n\nRun `pnpm build` before switching the default. Preview `pnpm studio configure --system \u003Cid>`, then apply confirmed choices with `--yes`.\n\nThe command preserves existing system choices. Migrate retained prototypes by updating imports and metadata together.\n\nIf cleanup is authorized, inspect all dependencies of each system being retired, including Product or Marketing. Include sample content and disabled modules.\n\nPreserve recoverable copies when replacing content. Use the [system lifecycle](..\u002F..\u002FREADME.md#system-lifecycle) to archive or permanently delete a retired system. Shadcn configuration belongs to each system; preserve the retained system's choices when retiring another. Preview changes and resolve dependencies instead of using `--force`.\n\nDo not remove another person's work merely because a contributor joined. Explain proposed starter cleanup and obtain unresolved choices.\n\n## Completion\n\nLocal creation registers the system and maintainer entry; external source is integrated into that scaffold. Set the intended [system declarations](..\u002F..\u002FREADME.md#structure) and [theme inventory](..\u002F..\u002FREADME.md#theme); validators check their structure. Adjust components and examples to those choices.\n\nReview representative components and pop-ups in every supported color mode. Verify that a single-mode system keeps its mode when Studio toggles. Follow the Working in Studio section of `AGENTS.md` for build and save requirements after migration.\n\nAfter completing the person's requested customization of an example system, set `overview.starter: false` in its `intro.tsx` and revise the summary to describe the customized system. This clears the example banner for everyone. Do not clear it just because the person opened or copied a setup prompt, or while assessment or customization is incomplete. Preserve any curation summary and saved decisions.\n\nReport source provenance, adaptations, the default system, verified prototype URL, and missing input. Return that prototype to initialization for reuse.\n\nFor imported product code, distinguish verified API, theme, and behavior fidelity from unresolved differences. A passing build alone does not establish equivalence with production.\n",{"name":5,"description":7},"main","8c6d1ebd043e77207e105ab59db08e02f1e3552b","src\u002Fplatform\u002Fmodules\u002Fsystems\u002Fskills\u002Fsetup-design-system",25,"https:\u002F\u002Fgithub.com\u002Fitspatmorgan\u002Fdesign-studio","https:\u002F\u002Fitspatmorgan.com\u002Fdesign-studio","https:\u002F\u002Fgithub.com\u002Fitspatmorgan","https:\u002F\u002Fitspatmorgan.com\u002F","Product Design @ Sublime Security. Creator of Unknown Arts (7k+ Readers).","2026-11-14 05:07:11",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add itspatmorgan\u002Fdesign-studio --skill setup-design-system",{"tool":40,"command":41},"bunx","bunx skills add itspatmorgan\u002Fdesign-studio --skill setup-design-system",{"tool":43,"command":44},"pnpm","pnpm dlx skills add itspatmorgan\u002Fdesign-studio --skill setup-design-system","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fitspatmorgan\u002Fdesign-studio\u002Fblob\u002Fmain\u002Fsrc\u002Fplatform\u002Fmodules\u002Fsystems\u002Fskills\u002Fsetup-design-system\u002FSKILL.md",true,[48,54,58],{"path":49,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":52,"sourceHtmlUrl":53},"references\u002Fcurated-libraries.md","REFERENCE","参考文档",4433,"https:\u002F\u002Fgithub.com\u002Fitspatmorgan\u002Fdesign-studio\u002Fblob\u002Fmain\u002Fsrc\u002Fplatform\u002Fmodules\u002Fsystems\u002Fskills\u002Fsetup-design-system\u002Freferences\u002Fcurated-libraries.md",{"path":55,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":56,"sourceHtmlUrl":57},"references\u002Fexisting-react-system.md",3075,"https:\u002F\u002Fgithub.com\u002Fitspatmorgan\u002Fdesign-studio\u002Fblob\u002Fmain\u002Fsrc\u002Fplatform\u002Fmodules\u002Fsystems\u002Fskills\u002Fsetup-design-system\u002Freferences\u002Fexisting-react-system.md",{"path":59,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":60,"sourceHtmlUrl":61},"references\u002Fshadcn.md",6181,"https:\u002F\u002Fgithub.com\u002Fitspatmorgan\u002Fdesign-studio\u002Fblob\u002Fmain\u002Fsrc\u002Fplatform\u002Fmodules\u002Fsystems\u002Fskills\u002Fsetup-design-system\u002Freferences\u002Fshadcn.md",[63,70,77,84,91,98],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":19},"01M7DMYK2KD32X2C11P8X6PRN1","setup-contributor","Register someone joining an existing studio and verify local access. Use configure-studio for a new studio.","https:\u002F\u002Fgithub.com\u002Fitspatmorgan\u002Fdesign-studio\u002Fblob\u002Fmain\u002Fsrc\u002Fplatform\u002Fskills\u002Fsetup-contributor\u002FSKILL.md",[],[],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":19},"01M7DMYH3JTA5HQF5G6PVB56B6","manage-modules","Create, install, enable, disable, or remove modules; create, rename, archive, restore, or delete systems through the Studio CLI.","https:\u002F\u002Fgithub.com\u002Fitspatmorgan\u002Fdesign-studio\u002Fblob\u002Fmain\u002Fsrc\u002Fplatform\u002Fskills\u002Fmanage-modules\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":19},"01M7DMYDT4YRZY6B4WQFE0AYGQ","maintain-documentation","Author or audit READMEs, context, and task skills for the platform, modules, and systems; coordinate human Manual updates.","https:\u002F\u002Fgithub.com\u002Fitspatmorgan\u002Fdesign-studio\u002Fblob\u002Fmain\u002Fsrc\u002Fplatform\u002Fskills\u002Fmaintain-documentation\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":19},"01M7DMYA8AZ6XQ8JKJB50SSSER","configure-studio","Configure a running studio for the first time, update requested studio settings, or update the studio to a newer Design Studio release. Use setup-contributor for someone joining; installation has its own workflow.","https:\u002F\u002Fgithub.com\u002Fitspatmorgan\u002Fdesign-studio\u002Fblob\u002Fmain\u002Fsrc\u002Fplatform\u002Fskills\u002Fconfigure-studio\u002FSKILL.md",[],[],{"skillNo":92,"name":93,"nameZh":6,"description":94,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":95,"categories":96,"keywords":97,"publishedAt":19},"01M7DMY5RG5KA0Q1RCKZV5GSRM","check-design-system","Audit a Design Studio surface against its applicable design system and report findings for human review before any fixes. Use for an explicit design-system review of Studio UI, prototypes, or system previews.","https:\u002F\u002Fgithub.com\u002Fitspatmorgan\u002Fdesign-studio\u002Fblob\u002Fmain\u002Fsrc\u002Fplatform\u002Fskills\u002Fcheck-design-system\u002FSKILL.md",[],[],{"skillNo":99,"name":100,"nameZh":6,"description":101,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":102,"categories":103,"keywords":104,"publishedAt":19},"01M7DMY2EW25PTR3VVZS5JE8Q0","use-__ID__","Use __LABEL__ in Design Studio when the capability is enabled.","https:\u002F\u002Fgithub.com\u002Fitspatmorgan\u002Fdesign-studio\u002Fblob\u002Fmain\u002Fsrc\u002Fplatform\u002Fnode\u002Ftemplates\u002Fmodule\u002Finstructions\u002Fskills\u002Fuse-__ID__\u002FSKILL.md",[],[]]