[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6P00Q8BZCFBWS93BAHBHQR3":3,"skill-same:01M6P00Q8BZCFBWS93BAHBHQR3":73},{"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":26,"publishedAt":47,"linkOnly":48,"markdownContent":49,"markdownBody":50,"frontMatter":51,"refName":52,"commitSha":53,"skillDirectory":54,"forksCount":55,"repositoryHtmlUrl":56,"repositoryHomepageUrl":6,"ownerHtmlUrl":57,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":58,"install":59,"resources":72},"01M6P00Q8BZCFBWS93BAHBHQR3","readme-blueprint-generator",null,"Intelligent README.md generation prompt that analyzes project documentation structure and creates comprehensive repository documentation. Scans .github\u002Fcopilot directory files and copilot-instructions.md to extract project information, technology stack, architecture, development workflow, coding standards, and testing approaches while generating well-structured markdown documentation with proper formatting, cross-references, and developer-focused content.","mattonweb\u002Fai-assistant-foundry","mattonweb","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F2309734?v=4","01M6NQYCY846TKYN2ZCRS71WQ7","Matt Johnson","01M6NQYD2NPAQEFVD8TW9W0SVX",1,"MIT","https:\u002F\u002Fgithub.com\u002Fmattonweb\u002Fai-assistant-foundry\u002Fblob\u002Fmain\u002Fwrite-technical\u002Fgithub\u002Freadme-blueprint-generator\u002FSKILL.md",[18,23],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",[27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46],"generator","readme blueprint generator","README","Blueprint","development workflow","project documentation","with","information","project","technology","references","files","testing","standards","prompt","development","documentation","copilot","architecture","workflow","2026-11-10 10:12:30",false,"---\nname: readme-blueprint-generator\ndescription: 'Intelligent README.md generation prompt that analyzes project documentation structure and creates comprehensive repository documentation. Scans .github\u002Fcopilot directory files and copilot-instructions.md to extract project information, technology stack, architecture, development workflow, coding standards, and testing approaches while generating well-structured markdown documentation with proper formatting, cross-references, and developer-focused content.'\n---\n\n# README Generator Prompt\n\nGenerate a comprehensive README.md for this repository by analyzing the documentation files in the .github\u002Fcopilot directory and the copilot-instructions.md file. Follow these steps:\n\n1. Scan all the files in the .github\u002Fcopilot folder, like:\n   - Architecture\n   - Code_Exemplars\n   - Coding_Standards\n   - Project_Folder_Structure\n   - Technology_Stack\n   - Unit_Tests\n   - Workflow_Analysis\n\n2. Also review the copilot-instructions.md file in the .github folder\n\n3. Create a README.md with the following sections:\n\n## Project Name and Description\n- Extract the project name and primary purpose from the documentation\n- Include a concise description of what the project does\n\n## Technology Stack\n- List the primary technologies, languages, and frameworks used\n- Include version information when available\n- Source this information primarily from the Technology_Stack file\n\n## Project Architecture\n- Provide a high-level overview of the architecture\n- Consider including a simple diagram if described in the documentation\n- Source from the Architecture file\n\n## Getting Started\n- Include installation instructions based on the technology stack\n- Add setup and configuration steps\n- Include any prerequisites\n\n## Project Structure\n- Brief overview of the folder organization\n- Source from Project_Folder_Structure file\n\n## Key Features\n- List main functionality and features of the project\n- Extract from various documentation files\n\n## Development Workflow\n- Summarize the development process\n- Include information about branching strategy if available\n- Source from Workflow_Analysis file\n\n## Coding Standards\n- Summarize key coding standards and conventions\n- Source from the Coding_Standards file\n\n## Testing\n- Explain testing approach and tools\n- Source from Unit_Tests file\n\n## Contributing\n- Guidelines for contributing to the project\n- Reference any code exemplars for guidance\n- Source from Code_Exemplars and copilot-instructions\n\n## License\n- Include license information if available\n\nFormat the README with proper Markdown, including:\n- Clear headings and subheadings\n- Code blocks where appropriate\n- Lists for better readability\n- Links to other documentation files\n- Badges for build status, version, etc. if information is available\n\nKeep the README concise yet informative, focusing on what new developers or users would need to know about the project.\n","# README Generator Prompt\n\nGenerate a comprehensive README.md for this repository by analyzing the documentation files in the .github\u002Fcopilot directory and the copilot-instructions.md file. Follow these steps:\n\n1. Scan all the files in the .github\u002Fcopilot folder, like:\n   - Architecture\n   - Code_Exemplars\n   - Coding_Standards\n   - Project_Folder_Structure\n   - Technology_Stack\n   - Unit_Tests\n   - Workflow_Analysis\n\n2. Also review the copilot-instructions.md file in the .github folder\n\n3. Create a README.md with the following sections:\n\n## Project Name and Description\n- Extract the project name and primary purpose from the documentation\n- Include a concise description of what the project does\n\n## Technology Stack\n- List the primary technologies, languages, and frameworks used\n- Include version information when available\n- Source this information primarily from the Technology_Stack file\n\n## Project Architecture\n- Provide a high-level overview of the architecture\n- Consider including a simple diagram if described in the documentation\n- Source from the Architecture file\n\n## Getting Started\n- Include installation instructions based on the technology stack\n- Add setup and configuration steps\n- Include any prerequisites\n\n## Project Structure\n- Brief overview of the folder organization\n- Source from Project_Folder_Structure file\n\n## Key Features\n- List main functionality and features of the project\n- Extract from various documentation files\n\n## Development Workflow\n- Summarize the development process\n- Include information about branching strategy if available\n- Source from Workflow_Analysis file\n\n## Coding Standards\n- Summarize key coding standards and conventions\n- Source from the Coding_Standards file\n\n## Testing\n- Explain testing approach and tools\n- Source from Unit_Tests file\n\n## Contributing\n- Guidelines for contributing to the project\n- Reference any code exemplars for guidance\n- Source from Code_Exemplars and copilot-instructions\n\n## License\n- Include license information if available\n\nFormat the README with proper Markdown, including:\n- Clear headings and subheadings\n- Code blocks where appropriate\n- Lists for better readability\n- Links to other documentation files\n- Badges for build status, version, etc. if information is available\n\nKeep the README concise yet informative, focusing on what new developers or users would need to know about the project.\n",{"name":5,"description":7},"main","d8518247cb8ab8b2dac57a6be33543ffd23b97c5","write-technical\u002Fgithub\u002Freadme-blueprint-generator",0,"https:\u002F\u002Fgithub.com\u002Fmattonweb\u002Fai-assistant-foundry","https:\u002F\u002Fgithub.com\u002Fmattonweb","2026-05-29 08:42:23",{"source":8,"skillName":5,"commands":60,"prompt":70,"zipAvailable":71},[61,64,67],{"tool":62,"command":63},"npx","npx skills add mattonweb\u002Fai-assistant-foundry --skill readme-blueprint-generator",{"tool":65,"command":66},"bunx","bunx skills add mattonweb\u002Fai-assistant-foundry --skill readme-blueprint-generator",{"tool":68,"command":69},"pnpm","pnpm dlx skills add mattonweb\u002Fai-assistant-foundry --skill readme-blueprint-generator","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmattonweb\u002Fai-assistant-foundry\u002Fblob\u002Fmain\u002Fwrite-technical\u002Fgithub\u002Freadme-blueprint-generator\u002FSKILL.md",true,[],[74,108,119,139,159,185],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":88,"publishedAt":47},"01M6P02DENRHN6KVGYC55FKASJ","writing-clearly-and-concisely","Use when writing prose humans will read—documentation, commit messages, error messages, explanations, reports, or UI text. Applies Strunk's timeless rules for clearer, stronger, more professional writing.","https:\u002F\u002Fgithub.com\u002Fmattonweb\u002Fai-assistant-foundry\u002Fblob\u002Fmain\u002Fwrite-technical\u002Fsoftaworks\u002Fwriting-clearly-and-concisely\u002FSKILL.md",[80,83],{"categoryNo":81,"categoryName":82,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":84,"categoryName":85,"taxonomyType":86,"taxonomyTypeDesc":87},"01JBSEEDCAT000000000000036","内容创作者","PROFESSION","适用职业",[89,90,91,92,93,94,95,96,97,98,99,100,101,102,103,104,105,106,43,107],"writing clearly and concisely","writing","concisely","text","for","more","timeless","error","professional","prose","reports","use","read","Rules","commit messages","messages","error messages","ui","commit",{"skillNo":109,"name":110,"nameZh":6,"description":111,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":112,"categories":113,"keywords":114,"publishedAt":47},"01M6P0286HZ8RWMFCCPC8HF7SC","crafting-effective-readmes","Use when writing or improving README files. Not all READMEs are the same — provides templates and guidance matched to your audience and project type.","https:\u002F\u002Fgithub.com\u002Fmattonweb\u002Fai-assistant-foundry\u002Fblob\u002Fmain\u002Fwrite-technical\u002Fsoftaworks\u002Fcrafting-effective-readmes\u002FSKILL.md",[],[115,29,90,116,117,100,35,118,38],"crafting effective readmes","templates","type","guidance",{"skillNo":120,"name":121,"nameZh":6,"description":122,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":123,"categories":124,"keywords":128,"publishedAt":47},"01M6P025A41BBTPWVTZ3GFQVG6","wiki-architect","You are a documentation architect that produces structured wiki catalogues and onboarding guides from codebases.","https:\u002F\u002Fgithub.com\u002Fmattonweb\u002Fai-assistant-foundry\u002Fblob\u002Fmain\u002Fwrite-technical\u002Fsickn33\u002Fwiki-architect\u002FSKILL.md",[125],{"categoryNo":126,"categoryName":127,"taxonomyType":86,"taxonomyTypeDesc":87},"01JBSEEDCAT000000000000038","人力资源",[129,130,131,132,133,134,135,136,137,138,43],"wiki","architect","wiki architect","unknown","you","documentation architect","guides","structured","community","onboarding",{"skillNo":140,"name":141,"nameZh":6,"description":142,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":143,"categories":144,"keywords":145,"publishedAt":47},"01M6P01NSKPXP77NWB4K0PXRK5","readme","You are an expert technical writer creating comprehensive project documentation. Your goal is to write a README.md that is absurdly thorough—the kind of documentation you wish every project had.","https:\u002F\u002Fgithub.com\u002Fmattonweb\u002Fai-assistant-foundry\u002Fblob\u002Fmain\u002Fwrite-technical\u002Fsickn33\u002Freadme\u002FSKILL.md",[],[29,32,146,147,133,148,149,35,150,151,52,152,153,154,155,156,43,157,158],"tree","kind","expert","github","wish","writer","goal","write","technical writer","technical","https","write a readme","safe",{"skillNo":160,"name":161,"nameZh":6,"description":162,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":163,"categories":164,"keywords":165,"publishedAt":47},"01M6P01GP0NEN8KT3A3SA6ZFVE","ubiquitous-language","Extract a DDD-style ubiquitous language glossary from the current conversation, flagging ambiguities and proposing canonical terms. Saves to UBIQUITOUS_LANGUAGE.md. Use when user wants to define domain terms, build a glossary, harden terminology, create a ubiquitous language, or mentions \"domain model\" or \"DDD\".","https:\u002F\u002Fgithub.com\u002Fmattonweb\u002Fai-assistant-foundry\u002Fblob\u002Fmain\u002Fwrite-technical\u002Fmattpocock\u002Fubiquitous-language\u002FSKILL.md",[],[166,167,100,168,169,170,171,172,173,174,175,176,177,178,179,180,181,182,183,184],"ubiquitous language","language","extract","user","glossary","model","terms","ddd","create","build","true","canonical","style","define","harden","domain model","domain","terminology","conversation",{"skillNo":186,"name":187,"nameZh":6,"description":188,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":189,"categories":190,"keywords":193,"publishedAt":47},"01M6P01BJBP9XP4TDRT7QD1ZVA","technical-writing-style","Enforce clear, direct writing in software development documents including OKRs, PRDs, tech specs, architecture decision records (ADRs), git commit messages, PR descriptions, READMEs, changelogs, runbooks, incident postmortems, API docs, and onboarding guides. Trigger whenever a user asks to write, edit, revise, or review any of these document types. Also trigger when the user says writing \"sounds like AI\", \"feels robotic\", \"needs polish\", or asks to \"make it sound more natural\" in the context of technical or professional prose. Do not trigger for fiction, poetry, creative writing, academic papers, or legal documents unless the user explicitly asks for a more natural tone.","https:\u002F\u002Fgithub.com\u002Fmattonweb\u002Fai-assistant-foundry\u002Fblob\u002Fmain\u002Fwrite-technical\u002Fmattnebr\u002Ftechnical-writing-style\u002FSKILL.md",[191,192],{"categoryNo":81,"categoryName":82,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":84,"categoryName":85,"taxonomyType":86,"taxonomyTypeDesc":87},[194,195,178,155,90,196,97,197,198,199,200,201,202,203,204,104,205,45,107,206],"writing style","technical writing style","technical writing","papers","types","runbooks","software development","incident","Poetry","decision","api","documents","review"]