[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6NS965Y4FAMTTDVXMA8ABNJ":3,"skill-same:01M6NS965Y4FAMTTDVXMA8ABNJ":137},{"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},"01M6NS965Y4FAMTTDVXMA8ABNJ","marp-slide",null,"Create professional Marp presentation slides with 7 beautiful themes (default, minimal, colorful, dark, gradient, tech, business). Use when users request slide creation, presentations, or Marp documents. Supports custom themes, image layouts, and \"make it look good\" requests with automatic quality improvements.","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\u002Fbuild-pptx\u002Fsoftaworks\u002Fmarp-slide\u002FSKILL.md",[18,23],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000003","演示文稿","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000016","图像与多媒体",[27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46],"marp slide","marp","tech","dark","automatic","request","gradient","presentation","make","themes","professional","image","creation","default","minimal","good","slides","create","presentations","documents","2026-11-10 10:12:30",false,"---\nname: marp-slide\ndescription: Create professional Marp presentation slides with 7 beautiful themes (default, minimal, colorful, dark, gradient, tech, business). Use when users request slide creation, presentations, or Marp documents. Supports custom themes, image layouts, and \"make it look good\" requests with automatic quality improvements.\n---\n\n# Marp Slide Creator\n\nCreate professional, visually appealing Marp presentation slides with 7 pre-designed themes and built-in best practices.\n\n## When to Use This Skill\n\nUse this skill when the user:\n- Requests to create presentation slides or Marp documents\n- Asks to \"make slides look good\" or \"improve slide design\"\n- Provides vague instructions like \"良い感じにして\" (make it nice) or \"かっこよく\" (make it cool)\n- Wants to create lecture or seminar materials\n- Needs bullet-point focused slides with occasional images\n\n## Quick Start\n\n### Step 1: Select Theme\n\nFirst, determine the appropriate theme based on the user's request and content.\n\n**Quick theme selection:**\n- **Technical\u002FDeveloper content** → tech theme\n- **Business\u002FCorporate** → business theme\n- **Creative\u002FEvent** → colorful or gradient theme\n- **Academic\u002FSimple** → minimal theme\n- **General\u002FUnsure** → default theme\n- **Dark background preferred** → dark or tech theme\n\nFor detailed theme selection guidance, read `references\u002Ftheme-selection.md`.\n\n### Step 2: Create Slides\n\n1. **Read relevant references first**:\n   - Always start by reading `references\u002Fmarp-syntax.md` for basic syntax\n   - For images: `references\u002Fimage-patterns.md` (official Marpit image syntax)\n   - For advanced features (math, emoji): `references\u002Fadvanced-features.md`\n   - For custom themes: `references\u002Ftheme-css-guide.md`\n\n2. Copy content from the appropriate template file:\n   - `assets\u002Ftemplate-basic.md` - Default theme (most common)\n   - `assets\u002Ftemplate-minimal.md` - Minimal theme\n   - `assets\u002Ftemplate-colorful.md` - Colorful theme\n   - `assets\u002Ftemplate-dark.md` - Dark mode theme\n   - `assets\u002Ftemplate-gradient.md` - Gradient theme\n   - `assets\u002Ftemplate-tech.md` - Tech\u002Fcode theme\n   - `assets\u002Ftemplate-business.md` - Business theme\n\n3. Read `references\u002Fbest-practices.md` for quality guidelines\n\n4. Structure content following best practices:\n   - Title slide with `\u003C!-- _class: lead -->`\n   - Concise h2 titles (5-7 characters in Japanese)\n   - 3-5 bullet points per slide\n   - Adequate whitespace\n\n5. Add images if needed using patterns from `references\u002Fimage-patterns.md`\n\n6. Save to `\u002Fmnt\u002Fuser-data\u002Foutputs\u002F` with `.md` extension\n\n## Available Themes\n\n### 1. Default Theme\n**Colors**: Beige background, navy text, blue headings\n**Style**: Clean, sophisticated with decorative lines\n**Use for**: General seminars, lectures, presentations\n**Template**: `template-basic.md`\n\n### 2. Minimal Theme\n**Colors**: White background, gray text, black headings\n**Style**: Minimal decoration, wide margins, light fonts\n**Use for**: Content-focused presentations, academic talks\n**Template**: `template-minimal.md`\n\n### 3. Colorful & Pop Theme\n**Colors**: Pink gradient background, multi-color accents\n**Style**: Vibrant gradients, bold fonts, rainbow accents\n**Use for**: Youth-oriented events, creative projects\n**Template**: `template-colorful.md`\n\n### 4. Dark Mode Theme\n**Colors**: Black background, cyan\u002Fpurple accents\n**Style**: Dark theme with glow effects, eye-friendly\n**Use for**: Tech presentations, evening talks, modern look\n**Template**: `template-dark.md`\n\n### 5. Gradient Background Theme\n**Colors**: Purple\u002Fpink\u002Fblue\u002Fgreen gradients (varies per slide)\n**Style**: Different gradient per slide, white text, shadows\n**Use for**: Visual-focused, creative presentations\n**Template**: `template-gradient.md`\n\n### 6. Tech\u002FCode Theme\n**Colors**: GitHub-style dark background, blue\u002Fgreen accents\n**Style**: Code fonts, Markdown-style headers with # symbols\n**Use for**: Programming tutorials, tech meetups, developer content\n**Template**: `template-tech.md`\n\n### 7. Business Theme\n**Colors**: White background, navy headings, blue accents\n**Style**: Corporate presentation style, top border, table support\n**Use for**: Business presentations, proposals, reports\n**Template**: `template-business.md`\n\n## Creating Slides Process\n\n### Basic Workflow\n\n1. **Understand requirements**\n   - Identify content: title, topics, key points\n   - Determine target audience\n   - Assess formality level\n\n2. **Select theme**\n   - Use quick selection rules above\n   - If uncertain, consult `references\u002Ftheme-selection.md`\n   - Default to default theme if still unsure\n\n3. **Apply template**\n   - Load appropriate template from `assets\u002F`\n   - CSS is already embedded - no external files needed\n   - Maintain template structure\n\n4. **Structure content**\n   - Title slide: `\u003C!-- _class: lead -->` + h1\n   - Content slides: h2 title + bullet points\n   - Keep titles to 5-7 characters (Japanese)\n   - Use 3-5 bullet points per slide\n\n5. **Refine quality**\n   - Read `references\u002Fbest-practices.md`\n   - Ensure adequate whitespace\n   - Maintain consistency\n   - Keep text concise (15-25 chars per line)\n\n6. **Add images**\n   - If needed, consult `references\u002Fimage-patterns.md`\n   - Common: `![bg right:40%](image.png)` for side images\n   - Use proper Marp image syntax\n\n7. **Output file**\n   - Save to `\u002Fmnt\u002Fuser-data\u002Foutputs\u002F`\n   - Use descriptive filename like `presentation.md`\n\n## Handling \"Make It Look Good\" Requests\n\nWhen users give vague instructions like \"良い感じにして\", \"かっこよく\", or \"make it cool\":\n\n1. **Infer theme from content**:\n   - Business content → business theme\n   - Technical content → tech or dark theme\n   - Creative content → gradient or colorful theme\n   - General → default theme\n\n2. **Apply best practices automatically**:\n   - Shorten titles to 5-7 characters\n   - Limit bullet points to 3-5 items\n   - Add adequate whitespace\n   - Use consistent structure\n\n3. **Enhance visual hierarchy**:\n   - Use h3 for sub-sections when appropriate\n   - Break up dense text into multiple slides\n   - Ensure logical flow (intro → body → conclusion)\n\n4. **Maintain professional tone**:\n   - Match formality to content\n   - Use parallel structure in lists\n   - Keep technical terms consistent\n\n## Image Integration\n\nFor slides with images, consult `references\u002Fimage-patterns.md` for detailed syntax.\n\nCommon patterns:\n- **Side image**: `![bg right:40%](image.png)` - Image on right, text on left\n- **Centered**: `![w:600px](image.png)` - Centered with specific width\n- **Full background**: `![bg](image.png)` - Full-screen background\n- **Multiple images**: Multiple `![bg]` declarations\n\nExample lecture pattern:\n```markdown\n\n## Slide Title\n\n![bg right:40%](diagram.png)\n\n- Explanation point 1\n- Explanation point 2\n- Explanation point 3\n```\n\n## File Output\n\nAlways save the final Marp file to `\u002Fmnt\u002Fuser-data\u002Foutputs\u002F` with `.md` extension:\n- `presentation.md`\n- `seminar-slides.md`\n- `lecture-materials.md`\n\n## Quality Checklist\n\nBefore delivering slides, verify:\n- [ ] Theme selected appropriately for content\n- [ ] CSS theme is embedded in the file\n- [ ] Title slide uses `\u003C!-- _class: lead -->`\n- [ ] All h2 titles are concise (5-7 chars)\n- [ ] Bullet points are 3-5 items per slide\n- [ ] Images use proper Marp syntax\n- [ ] File saved to outputs directory\n- [ ] Content follows best practices\n\n## References\n\n### Core Documentation\n- **Marp syntax**: `references\u002Fmarp-syntax.md` - Basic Marp\u002FMarpit syntax (directives, frontmatter, pagination, etc.)\n- **Image patterns**: `references\u002Fimage-patterns.md` - Official image syntax (bg, filters, split backgrounds)\n- **Theme CSS guide**: `references\u002Ftheme-css-guide.md` - How to create custom themes based on Marpit specification\n- **Advanced features**: `references\u002Fadvanced-features.md` - Math, emoji, fragmented lists, Marp CLI, VS Code\n- **Official themes**: `references\u002Fofficial-themes.md` - default, gaia, uncover themes documentation\n\n### Quality & Selection Guides\n- **Theme selection**: `references\u002Ftheme-selection.md` - How to choose the right theme for content\n- **Best practices**: `references\u002Fbest-practices.md` - Quality guidelines for \"cool\" slides\n\n### Templates & Assets\n- **Templates**: `assets\u002Ftemplate-*.md` - Starting points with embedded CSS for each theme (7 themes)\n- **Standalone CSS**: `assets\u002Ftheme-*.css` - CSS files for reference (already embedded in templates)\n\n### Official External Links\n- **Marp Official Site**: https:\u002F\u002Fmarp.app\u002F\n- **Marpit Directives**: https:\u002F\u002Fmarpit.marp.app\u002Fdirectives\n- **Marpit Image Syntax**: https:\u002F\u002Fmarpit.marp.app\u002Fimage-syntax\n- **Marpit Theme CSS**: https:\u002F\u002Fmarpit.marp.app\u002Ftheme-css\n- **Marp Core GitHub**: https:\u002F\u002Fgithub.com\u002Fmarp-team\u002Fmarp-core\n- **Marp CLI GitHub**: https:\u002F\u002Fgithub.com\u002Fmarp-team\u002Fmarp-cli\n","# Marp Slide Creator\n\nCreate professional, visually appealing Marp presentation slides with 7 pre-designed themes and built-in best practices.\n\n## When to Use This Skill\n\nUse this skill when the user:\n- Requests to create presentation slides or Marp documents\n- Asks to \"make slides look good\" or \"improve slide design\"\n- Provides vague instructions like \"良い感じにして\" (make it nice) or \"かっこよく\" (make it cool)\n- Wants to create lecture or seminar materials\n- Needs bullet-point focused slides with occasional images\n\n## Quick Start\n\n### Step 1: Select Theme\n\nFirst, determine the appropriate theme based on the user's request and content.\n\n**Quick theme selection:**\n- **Technical\u002FDeveloper content** → tech theme\n- **Business\u002FCorporate** → business theme\n- **Creative\u002FEvent** → colorful or gradient theme\n- **Academic\u002FSimple** → minimal theme\n- **General\u002FUnsure** → default theme\n- **Dark background preferred** → dark or tech theme\n\nFor detailed theme selection guidance, read `references\u002Ftheme-selection.md`.\n\n### Step 2: Create Slides\n\n1. **Read relevant references first**:\n   - Always start by reading `references\u002Fmarp-syntax.md` for basic syntax\n   - For images: `references\u002Fimage-patterns.md` (official Marpit image syntax)\n   - For advanced features (math, emoji): `references\u002Fadvanced-features.md`\n   - For custom themes: `references\u002Ftheme-css-guide.md`\n\n2. Copy content from the appropriate template file:\n   - `assets\u002Ftemplate-basic.md` - Default theme (most common)\n   - `assets\u002Ftemplate-minimal.md` - Minimal theme\n   - `assets\u002Ftemplate-colorful.md` - Colorful theme\n   - `assets\u002Ftemplate-dark.md` - Dark mode theme\n   - `assets\u002Ftemplate-gradient.md` - Gradient theme\n   - `assets\u002Ftemplate-tech.md` - Tech\u002Fcode theme\n   - `assets\u002Ftemplate-business.md` - Business theme\n\n3. Read `references\u002Fbest-practices.md` for quality guidelines\n\n4. Structure content following best practices:\n   - Title slide with `\u003C!-- _class: lead -->`\n   - Concise h2 titles (5-7 characters in Japanese)\n   - 3-5 bullet points per slide\n   - Adequate whitespace\n\n5. Add images if needed using patterns from `references\u002Fimage-patterns.md`\n\n6. Save to `\u002Fmnt\u002Fuser-data\u002Foutputs\u002F` with `.md` extension\n\n## Available Themes\n\n### 1. Default Theme\n**Colors**: Beige background, navy text, blue headings\n**Style**: Clean, sophisticated with decorative lines\n**Use for**: General seminars, lectures, presentations\n**Template**: `template-basic.md`\n\n### 2. Minimal Theme\n**Colors**: White background, gray text, black headings\n**Style**: Minimal decoration, wide margins, light fonts\n**Use for**: Content-focused presentations, academic talks\n**Template**: `template-minimal.md`\n\n### 3. Colorful & Pop Theme\n**Colors**: Pink gradient background, multi-color accents\n**Style**: Vibrant gradients, bold fonts, rainbow accents\n**Use for**: Youth-oriented events, creative projects\n**Template**: `template-colorful.md`\n\n### 4. Dark Mode Theme\n**Colors**: Black background, cyan\u002Fpurple accents\n**Style**: Dark theme with glow effects, eye-friendly\n**Use for**: Tech presentations, evening talks, modern look\n**Template**: `template-dark.md`\n\n### 5. Gradient Background Theme\n**Colors**: Purple\u002Fpink\u002Fblue\u002Fgreen gradients (varies per slide)\n**Style**: Different gradient per slide, white text, shadows\n**Use for**: Visual-focused, creative presentations\n**Template**: `template-gradient.md`\n\n### 6. Tech\u002FCode Theme\n**Colors**: GitHub-style dark background, blue\u002Fgreen accents\n**Style**: Code fonts, Markdown-style headers with # symbols\n**Use for**: Programming tutorials, tech meetups, developer content\n**Template**: `template-tech.md`\n\n### 7. Business Theme\n**Colors**: White background, navy headings, blue accents\n**Style**: Corporate presentation style, top border, table support\n**Use for**: Business presentations, proposals, reports\n**Template**: `template-business.md`\n\n## Creating Slides Process\n\n### Basic Workflow\n\n1. **Understand requirements**\n   - Identify content: title, topics, key points\n   - Determine target audience\n   - Assess formality level\n\n2. **Select theme**\n   - Use quick selection rules above\n   - If uncertain, consult `references\u002Ftheme-selection.md`\n   - Default to default theme if still unsure\n\n3. **Apply template**\n   - Load appropriate template from `assets\u002F`\n   - CSS is already embedded - no external files needed\n   - Maintain template structure\n\n4. **Structure content**\n   - Title slide: `\u003C!-- _class: lead -->` + h1\n   - Content slides: h2 title + bullet points\n   - Keep titles to 5-7 characters (Japanese)\n   - Use 3-5 bullet points per slide\n\n5. **Refine quality**\n   - Read `references\u002Fbest-practices.md`\n   - Ensure adequate whitespace\n   - Maintain consistency\n   - Keep text concise (15-25 chars per line)\n\n6. **Add images**\n   - If needed, consult `references\u002Fimage-patterns.md`\n   - Common: `![bg right:40%](image.png)` for side images\n   - Use proper Marp image syntax\n\n7. **Output file**\n   - Save to `\u002Fmnt\u002Fuser-data\u002Foutputs\u002F`\n   - Use descriptive filename like `presentation.md`\n\n## Handling \"Make It Look Good\" Requests\n\nWhen users give vague instructions like \"良い感じにして\", \"かっこよく\", or \"make it cool\":\n\n1. **Infer theme from content**:\n   - Business content → business theme\n   - Technical content → tech or dark theme\n   - Creative content → gradient or colorful theme\n   - General → default theme\n\n2. **Apply best practices automatically**:\n   - Shorten titles to 5-7 characters\n   - Limit bullet points to 3-5 items\n   - Add adequate whitespace\n   - Use consistent structure\n\n3. **Enhance visual hierarchy**:\n   - Use h3 for sub-sections when appropriate\n   - Break up dense text into multiple slides\n   - Ensure logical flow (intro → body → conclusion)\n\n4. **Maintain professional tone**:\n   - Match formality to content\n   - Use parallel structure in lists\n   - Keep technical terms consistent\n\n## Image Integration\n\nFor slides with images, consult `references\u002Fimage-patterns.md` for detailed syntax.\n\nCommon patterns:\n- **Side image**: `![bg right:40%](image.png)` - Image on right, text on left\n- **Centered**: `![w:600px](image.png)` - Centered with specific width\n- **Full background**: `![bg](image.png)` - Full-screen background\n- **Multiple images**: Multiple `![bg]` declarations\n\nExample lecture pattern:\n```markdown\n\n## Slide Title\n\n![bg right:40%](diagram.png)\n\n- Explanation point 1\n- Explanation point 2\n- Explanation point 3\n```\n\n## File Output\n\nAlways save the final Marp file to `\u002Fmnt\u002Fuser-data\u002Foutputs\u002F` with `.md` extension:\n- `presentation.md`\n- `seminar-slides.md`\n- `lecture-materials.md`\n\n## Quality Checklist\n\nBefore delivering slides, verify:\n- [ ] Theme selected appropriately for content\n- [ ] CSS theme is embedded in the file\n- [ ] Title slide uses `\u003C!-- _class: lead -->`\n- [ ] All h2 titles are concise (5-7 chars)\n- [ ] Bullet points are 3-5 items per slide\n- [ ] Images use proper Marp syntax\n- [ ] File saved to outputs directory\n- [ ] Content follows best practices\n\n## References\n\n### Core Documentation\n- **Marp syntax**: `references\u002Fmarp-syntax.md` - Basic Marp\u002FMarpit syntax (directives, frontmatter, pagination, etc.)\n- **Image patterns**: `references\u002Fimage-patterns.md` - Official image syntax (bg, filters, split backgrounds)\n- **Theme CSS guide**: `references\u002Ftheme-css-guide.md` - How to create custom themes based on Marpit specification\n- **Advanced features**: `references\u002Fadvanced-features.md` - Math, emoji, fragmented lists, Marp CLI, VS Code\n- **Official themes**: `references\u002Fofficial-themes.md` - default, gaia, uncover themes documentation\n\n### Quality & Selection Guides\n- **Theme selection**: `references\u002Ftheme-selection.md` - How to choose the right theme for content\n- **Best practices**: `references\u002Fbest-practices.md` - Quality guidelines for \"cool\" slides\n\n### Templates & Assets\n- **Templates**: `assets\u002Ftemplate-*.md` - Starting points with embedded CSS for each theme (7 themes)\n- **Standalone CSS**: `assets\u002Ftheme-*.css` - CSS files for reference (already embedded in templates)\n\n### Official External Links\n- **Marp Official Site**: https:\u002F\u002Fmarp.app\u002F\n- **Marpit Directives**: https:\u002F\u002Fmarpit.marp.app\u002Fdirectives\n- **Marpit Image Syntax**: https:\u002F\u002Fmarpit.marp.app\u002Fimage-syntax\n- **Marpit Theme CSS**: https:\u002F\u002Fmarpit.marp.app\u002Ftheme-css\n- **Marp Core GitHub**: https:\u002F\u002Fgithub.com\u002Fmarp-team\u002Fmarp-core\n- **Marp CLI GitHub**: https:\u002F\u002Fgithub.com\u002Fmarp-team\u002Fmarp-cli\n",{"name":5,"description":7},"main","d8518247cb8ab8b2dac57a6be33543ffd23b97c5","build-pptx\u002Fsoftaworks\u002Fmarp-slide",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 marp-slide",{"tool":65,"command":66},"bunx","bunx skills add mattonweb\u002Fai-assistant-foundry --skill marp-slide",{"tool":68,"command":69},"pnpm","pnpm dlx skills add mattonweb\u002Fai-assistant-foundry --skill marp-slide","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmattonweb\u002Fai-assistant-foundry\u002Fblob\u002Fmain\u002Fbuild-pptx\u002Fsoftaworks\u002Fmarp-slide\u002FSKILL.md",true,[73,79,83,87,91,95,99,103,109,113,117,121,125,129,133],{"path":74,"resourceType":75,"resourceTypeDesc":76,"sizeBytes":77,"sourceHtmlUrl":78},"assets\u002Ftemplate-basic.md","ASSET","资产文件",2127,"https:\u002F\u002Fgithub.com\u002Fmattonweb\u002Fai-assistant-foundry\u002Fblob\u002Fmain\u002Fbuild-pptx\u002Fsoftaworks\u002Fmarp-slide\u002Fassets\u002Ftemplate-basic.md",{"path":80,"resourceType":75,"resourceTypeDesc":76,"sizeBytes":81,"sourceHtmlUrl":82},"assets\u002Ftemplate-business.md",2855,"https:\u002F\u002Fgithub.com\u002Fmattonweb\u002Fai-assistant-foundry\u002Fblob\u002Fmain\u002Fbuild-pptx\u002Fsoftaworks\u002Fmarp-slide\u002Fassets\u002Ftemplate-business.md",{"path":84,"resourceType":75,"resourceTypeDesc":76,"sizeBytes":85,"sourceHtmlUrl":86},"assets\u002Ftemplate-colorful.md",2810,"https:\u002F\u002Fgithub.com\u002Fmattonweb\u002Fai-assistant-foundry\u002Fblob\u002Fmain\u002Fbuild-pptx\u002Fsoftaworks\u002Fmarp-slide\u002Fassets\u002Ftemplate-colorful.md",{"path":88,"resourceType":75,"resourceTypeDesc":76,"sizeBytes":89,"sourceHtmlUrl":90},"assets\u002Ftemplate-dark.md",2400,"https:\u002F\u002Fgithub.com\u002Fmattonweb\u002Fai-assistant-foundry\u002Fblob\u002Fmain\u002Fbuild-pptx\u002Fsoftaworks\u002Fmarp-slide\u002Fassets\u002Ftemplate-dark.md",{"path":92,"resourceType":75,"resourceTypeDesc":76,"sizeBytes":93,"sourceHtmlUrl":94},"assets\u002Ftemplate-gradient.md",2766,"https:\u002F\u002Fgithub.com\u002Fmattonweb\u002Fai-assistant-foundry\u002Fblob\u002Fmain\u002Fbuild-pptx\u002Fsoftaworks\u002Fmarp-slide\u002Fassets\u002Ftemplate-gradient.md",{"path":96,"resourceType":75,"resourceTypeDesc":76,"sizeBytes":97,"sourceHtmlUrl":98},"assets\u002Ftemplate-minimal.md",1895,"https:\u002F\u002Fgithub.com\u002Fmattonweb\u002Fai-assistant-foundry\u002Fblob\u002Fmain\u002Fbuild-pptx\u002Fsoftaworks\u002Fmarp-slide\u002Fassets\u002Ftemplate-minimal.md",{"path":100,"resourceType":75,"resourceTypeDesc":76,"sizeBytes":101,"sourceHtmlUrl":102},"assets\u002Ftemplate-tech.md",2869,"https:\u002F\u002Fgithub.com\u002Fmattonweb\u002Fai-assistant-foundry\u002Fblob\u002Fmain\u002Fbuild-pptx\u002Fsoftaworks\u002Fmarp-slide\u002Fassets\u002Ftemplate-tech.md",{"path":104,"resourceType":105,"resourceTypeDesc":106,"sizeBytes":107,"sourceHtmlUrl":108},"README.md","REFERENCE","参考文档",7664,"https:\u002F\u002Fgithub.com\u002Fmattonweb\u002Fai-assistant-foundry\u002Fblob\u002Fmain\u002Fbuild-pptx\u002Fsoftaworks\u002Fmarp-slide\u002FREADME.md",{"path":110,"resourceType":105,"resourceTypeDesc":106,"sizeBytes":111,"sourceHtmlUrl":112},"references\u002Fadvanced-features.md",6779,"https:\u002F\u002Fgithub.com\u002Fmattonweb\u002Fai-assistant-foundry\u002Fblob\u002Fmain\u002Fbuild-pptx\u002Fsoftaworks\u002Fmarp-slide\u002Freferences\u002Fadvanced-features.md",{"path":114,"resourceType":105,"resourceTypeDesc":106,"sizeBytes":115,"sourceHtmlUrl":116},"references\u002Fbest-practices.md",3426,"https:\u002F\u002Fgithub.com\u002Fmattonweb\u002Fai-assistant-foundry\u002Fblob\u002Fmain\u002Fbuild-pptx\u002Fsoftaworks\u002Fmarp-slide\u002Freferences\u002Fbest-practices.md",{"path":118,"resourceType":105,"resourceTypeDesc":106,"sizeBytes":119,"sourceHtmlUrl":120},"references\u002Fimage-patterns.md",4913,"https:\u002F\u002Fgithub.com\u002Fmattonweb\u002Fai-assistant-foundry\u002Fblob\u002Fmain\u002Fbuild-pptx\u002Fsoftaworks\u002Fmarp-slide\u002Freferences\u002Fimage-patterns.md",{"path":122,"resourceType":105,"resourceTypeDesc":106,"sizeBytes":123,"sourceHtmlUrl":124},"references\u002Fmarp-syntax.md",3630,"https:\u002F\u002Fgithub.com\u002Fmattonweb\u002Fai-assistant-foundry\u002Fblob\u002Fmain\u002Fbuild-pptx\u002Fsoftaworks\u002Fmarp-slide\u002Freferences\u002Fmarp-syntax.md",{"path":126,"resourceType":105,"resourceTypeDesc":106,"sizeBytes":127,"sourceHtmlUrl":128},"references\u002Fofficial-themes.md",5590,"https:\u002F\u002Fgithub.com\u002Fmattonweb\u002Fai-assistant-foundry\u002Fblob\u002Fmain\u002Fbuild-pptx\u002Fsoftaworks\u002Fmarp-slide\u002Freferences\u002Fofficial-themes.md",{"path":130,"resourceType":105,"resourceTypeDesc":106,"sizeBytes":131,"sourceHtmlUrl":132},"references\u002Ftheme-css-guide.md",5464,"https:\u002F\u002Fgithub.com\u002Fmattonweb\u002Fai-assistant-foundry\u002Fblob\u002Fmain\u002Fbuild-pptx\u002Fsoftaworks\u002Fmarp-slide\u002Freferences\u002Ftheme-css-guide.md",{"path":134,"resourceType":105,"resourceTypeDesc":106,"sizeBytes":135,"sourceHtmlUrl":136},"references\u002Ftheme-selection.md",4001,"https:\u002F\u002Fgithub.com\u002Fmattonweb\u002Fai-assistant-foundry\u002Fblob\u002Fmain\u002Fbuild-pptx\u002Fsoftaworks\u002Fmarp-slide\u002Freferences\u002Ftheme-selection.md",[138,172,186,206,227,252],{"skillNo":139,"name":140,"nameZh":6,"description":141,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":142,"categories":143,"keywords":152,"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",[144,147],{"categoryNo":145,"categoryName":146,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":148,"categoryName":149,"taxonomyType":150,"taxonomyTypeDesc":151},"01JBSEEDCAT000000000000036","内容创作者","PROFESSION","适用职业",[153,154,155,156,157,158,159,160,37,161,162,163,164,165,166,167,168,169,170,171],"writing clearly and concisely","writing","concisely","text","for","more","timeless","error","prose","reports","use","read","Rules","commit messages","messages","error messages","ui","documentation","commit",{"skillNo":173,"name":174,"nameZh":6,"description":175,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":176,"categories":177,"keywords":178,"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",[],[179,180,154,181,182,163,183,184,185],"crafting effective readmes","README","templates","type","project","guidance","files",{"skillNo":187,"name":188,"nameZh":6,"description":189,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":190,"categories":191,"keywords":195,"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",[192],{"categoryNo":193,"categoryName":194,"taxonomyType":150,"taxonomyTypeDesc":151},"01JBSEEDCAT000000000000038","人力资源",[196,197,198,199,200,201,202,203,204,205,170],"wiki","architect","wiki architect","unknown","you","documentation architect","guides","structured","community","onboarding",{"skillNo":207,"name":208,"nameZh":6,"description":209,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":210,"categories":211,"keywords":212,"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",[],[180,213,214,215,200,216,217,183,218,219,52,220,221,222,223,224,170,225,226],"project documentation","tree","kind","expert","github","wish","writer","goal","write","technical writer","technical","https","write a readme","safe",{"skillNo":228,"name":229,"nameZh":6,"description":230,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":231,"categories":232,"keywords":233,"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",[],[234,235,163,236,237,238,239,240,241,44,242,243,244,245,246,247,248,249,250,251],"ubiquitous language","language","extract","user","glossary","model","terms","ddd","build","true","canonical","style","define","harden","domain model","domain","terminology","conversation",{"skillNo":253,"name":254,"nameZh":6,"description":255,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":256,"categories":257,"keywords":260,"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",[258,259],{"categoryNo":145,"categoryName":146,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":148,"categoryName":149,"taxonomyType":150,"taxonomyTypeDesc":151},[261,262,245,223,154,263,37,264,265,266,267,268,269,270,271,167,46,272,171,273],"writing style","technical writing style","technical writing","papers","types","runbooks","software development","incident","Poetry","decision","api","architecture","review"]