[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7C4H2YZ5TH9EDARGWRYAPGZ":3,"skill-same:01M7C4H2YZ5TH9EDARGWRYAPGZ":45},{"skillNo":4,"name":5,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":20,"frontMatter":21,"refName":22,"commitSha":23,"skillDirectory":24,"forksCount":25,"repositoryHtmlUrl":26,"repositoryHomepageUrl":6,"ownerHtmlUrl":27,"ownerBlogUrl":28,"ownerDescription":29,"updatedAt":30,"install":31,"resources":44},"01M7C4H2YZ5TH9EDARGWRYAPGZ","incremental-implementation",null,"QuinntyneBrown\u002Fquinntyne-brown-studio","QuinntyneBrown","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F1749159?v=4","01M7C4DEMVW0A87TDN8PMZTNFG","Quinntyne Brown","01M7C4DENDYX1QYZDN3F0A5ZX0",1,"MIT","https:\u002F\u002Fgithub.com\u002FQuinntyneBrown\u002Fquinntyne-brown-studio\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fincremental-implementation\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"@..\u002F..\u002F..\u002F.agents\u002Fskills\u002Fincremental-implementation\u002FSKILL.md\n",{},"main","0dbacec4955ea8b75622a8b16233d9bd2618e7ed",".claude\u002Fskills\u002Fincremental-implementation",0,"https:\u002F\u002Fgithub.com\u002FQuinntyneBrown\u002Fquinntyne-brown-studio","https:\u002F\u002Fgithub.com\u002FQuinntyneBrown","https:\u002F\u002Fquinntynebrown.com","Microsoft Certified Solutions Developer specializing in C#, ASP.NET Core, TypeScript, Azure, Angular, Web Components, RxJS, SignalR Core & Entity Framework Core","2026-10-19 10:28:28",{"source":7,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add QuinntyneBrown\u002Fquinntyne-brown-studio --skill incremental-implementation",{"tool":37,"command":38},"bunx","bunx skills add QuinntyneBrown\u002Fquinntyne-brown-studio --skill incremental-implementation",{"tool":40,"command":41},"pnpm","pnpm dlx skills add QuinntyneBrown\u002Fquinntyne-brown-studio --skill incremental-implementation","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FQuinntyneBrown\u002Fquinntyne-brown-studio\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fincremental-implementation\u002FSKILL.md",true,[],[46,53,60,67,74,81],{"skillNo":47,"name":48,"nameZh":6,"description":49,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":50,"categories":51,"keywords":52,"publishedAt":18},"01M7C4JA8SJ18P9JERCKVN799X","writing-screen-composition","Create or update docs\u002Fscreen-composition.md, a document that itemizes every page, dialog, notification and shell part from the HTML mocks and lists, for each, the component-library components it shall be composed of plus the UI that must be built locally. Also ensures AGENTS.md has the \"Components library is mandatory (CRITICAL)\" section. Use when the user mentions screen composition, which components a page uses, mapping mocks to a component library, local vs library UI, or before implementing an application against a component library; and whenever docs\u002Fmocks and a component catalogue exist but docs\u002Fscreen-composition.md does not or is out of date.","https:\u002F\u002Fgithub.com\u002FQuinntyneBrown\u002Fquinntyne-brown-studio\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fwriting-screen-composition\u002FSKILL.md",[],[],{"skillNo":54,"name":55,"nameZh":6,"description":56,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":57,"categories":58,"keywords":59,"publishedAt":18},"01M7C4J46A36085AMSCEKZX3GG","writing-requirements","Create and manage software requirements documents (L1 high-level and L2 detailed with acceptance criteria) in docs\u002Fspecs\u002F. Use this skill whenever the user mentions requirements, specs, specifications, user stories, features to build, acceptance criteria, ATDD, or wants to define what a system should do before coding. Also use when the user says things like 'what should we build', 'let's plan the feature', 'write up what this needs to do', 'define the behavior', or describes functionality they want implemented -- even if they don't explicitly say 'requirements'. If the user is about to start coding a feature and there are no requirements yet, proactively suggest using this skill first. Requirements come before code. Always.","https:\u002F\u002Fgithub.com\u002FQuinntyneBrown\u002Fquinntyne-brown-studio\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fwriting-requirements\u002FSKILL.md",[],[],{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":18},"01M7C4HWSMCNEE8H922B4W4BT7","writing-html-mocks","Write static HTML mocks in docs\u002Fmocks\u002F for EVERY page, dialog and notification of a product in EVERY state (default, loading, empty, error, invalid, busy, success, no-results, forbidden, stacked...), responsive, light and dark, keyboard-accessible, with real copy and a coverage matrix. Use this skill BEFORE writing any frontend code, component, template, view or page; whenever the user says mock, mockup, wireframe, prototype, UI, UX, screen, layout, dialog, modal, toast, banner, empty\u002Ferror\u002Floading state, \"what should this look like\", \"show me the UI\", or describes a feature with a visible result; and whenever docs\u002Fspecs or docs\u002Fdetailed-designs exist but docs\u002Fmocks does not. Also use it to add missing states to existing mocks. Mocks come before implementation: if asked for frontend code with no mocks, say so and offer this first. Pair with extracting-design-systems to turn finished mocks into docs\u002Fdesign-system\u002F.","https:\u002F\u002Fgithub.com\u002FQuinntyneBrown\u002Fquinntyne-brown-studio\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fwriting-html-mocks\u002FSKILL.md",[],[],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":18},"01M7C4HQZ8AM15WF2PHH3G2BGN","writing-feature-prompts","Write a ready-to-run implementation prompt for a feature request or a bug fix in the current repository, save it outside the repository and open it in a text editor (Notepad on Windows). A feature prompt drives mocks, design system, requirements, detailed design, estimate update and incremental acceptance-test-driven implementation end to end without stopping; a bug-fix prompt drives reproduce, root cause, fix and documentation alignment. Use whenever the user asks to \"create a prompt\", \"write a prompt for this feature\" or \"for this bug\", wants a \"prompt to build X\" or \"prompt to fix Y\", or asks to open a prompt in Notepad.","https:\u002F\u002Fgithub.com\u002FQuinntyneBrown\u002Fquinntyne-brown-studio\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fwriting-feature-prompts\u002FSKILL.md",[],[],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":18},"01M7C4HJHMY4ESK2M82BXXJNT9","writing-design-documents","Create software design documents and architecture write-ups from existing L1\u002FL2 requirements in docs\u002Fspecs\u002F. Use for detailed designs organized by subsystem and feature, with requirement traceability and rendered PlantUML C4, class, and sequence diagrams in docs\u002Fdetailed-designs\u002F.","https:\u002F\u002Fgithub.com\u002FQuinntyneBrown\u002Fquinntyne-brown-studio\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fwriting-design-documents\u002FSKILL.md",[],[],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":18},"01M7C4HAJZ2JQKS09VASR3XM4T","writing-agent-instructions","Writes the agent instruction files a repository needs so coding agents know how to work in it - AGENTS.md plus the CLAUDE.md, GEMINI.md, and .github\u002Fcopilot-instructions.md pointers - generated from a description of what the project shall be, for a project that does not exist yet. Use this whenever someone mentions AGENTS.md, CLAUDE.md, GEMINI.md, copilot-instructions, \"agent instructions\", \"agent context files\", \"coding agent guidance\", or asks to set up, scaffold, bootstrap, or initialise the conventions for a new project or repository. Use it too when someone describes a project they are about to start and wants an agent to follow its conventions, even if they never name any of these files - if they are standing at an empty directory describing what they intend to build, this is the skill.","https:\u002F\u002Fgithub.com\u002FQuinntyneBrown\u002Fquinntyne-brown-studio\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fwriting-agent-instructions\u002FSKILL.md",[],[]]