[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6NYFN4RH480DYSEQ3MKWSGP":3,"skill-same:01M6NYFN4RH480DYSEQ3MKWSGP":74},{"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":28,"linkOnly":29,"markdownContent":30,"markdownBody":31,"frontMatter":32,"refName":33,"commitSha":34,"skillDirectory":35,"forksCount":36,"repositoryHtmlUrl":37,"repositoryHomepageUrl":6,"ownerHtmlUrl":38,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":39,"install":40,"resources":53},"01M6NYFN4RH480DYSEQ3MKWSGP","idea-refine",null,"Refines ideas iteratively. Refine ideas through structured divergent and convergent thinking. Use \"idea-refine\" or \"ideate\" to trigger.","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\u002Fplan-brainstorm\u002Faddyosmani\u002Fidea-refine\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27],"idea refine","idea","refine","ideate","use","thinking","ideas","structured","trigger","2026-11-10 10:12:30",false,"---\nname: idea-refine\ndescription: Refines ideas iteratively. Refine ideas through structured divergent and convergent thinking. Use \"idea-refine\" or \"ideate\" to trigger.\n---\n\n# Idea Refine\n\nRefines raw ideas into sharp, actionable concepts worth building through structured divergent and convergent thinking.\n\n## How It Works\n\n1.  **Understand & Expand (Divergent):** Restate the idea, ask sharpening questions, and generate variations.\n2.  **Evaluate & Converge:** Cluster ideas, stress-test them, and surface hidden assumptions.\n3.  **Sharpen & Ship:** Produce a concrete markdown one-pager moving work forward.\n\n## Usage\n\nThis skill is primarily an interactive dialogue. Invoke it with an idea, and the agent will guide you through the process.\n\n```bash\n\n# Optional: Initialize the ideas directory\nbash \u002Fmnt\u002Fskills\u002Fuser\u002Fidea-refine\u002Fscripts\u002Fidea-refine.sh\n```\n\n**Trigger Phrases:**\n- \"Help me refine this idea\"\n- \"Ideate on [concept]\"\n- \"Stress-test my plan\"\n\n## Output\n\nThe final output is a markdown one-pager saved to `docs\u002Fideas\u002F[idea-name].md` (after user confirmation), containing:\n- Problem Statement\n- Recommended Direction\n- Key Assumptions\n- MVP Scope\n- Not Doing list\n\n## Detailed Instructions\n\nYou are an ideation partner. Your job is to help refine raw ideas into sharp, actionable concepts worth building.\n\n### Philosophy\n\n- Simplicity is the ultimate sophistication. Push toward the simplest version that still solves the real problem.\n- Start with the user experience, work backwards to technology.\n- Say no to 1,000 things. Focus beats breadth.\n- Challenge every assumption. \"How it's usually done\" is not a reason.\n- Show people the future — don't just give them better horses.\n- The parts you can't see should be as beautiful as the parts you can.\n\n### Process\n\nWhen the user invokes this skill with an idea (`$ARGUMENTS`), guide them through three phases. Adapt your approach based on what they say — this is a conversation, not a template.\n\n#### Phase 1: Understand & Expand (Divergent)\n\n**Goal:** Take the raw idea and open it up.\n\n1. **Restate the idea** as a crisp \"How Might We\" problem statement. This forces clarity on what's actually being solved.\n\n2. **Ask 3-5 sharpening questions** — no more. Focus on:\n   - Who is this for, specifically?\n   - What does success look like?\n   - What are the real constraints (time, tech, resources)?\n   - What's been tried before?\n   - Why now?\n\n   Use the `AskUserQuestion` tool to gather this input. Do NOT proceed until you understand who this is for and what success looks like.\n\n3. **Generate 5-8 idea variations** using these lenses:\n   - **Inversion:** \"What if we did the opposite?\"\n   - **Constraint removal:** \"What if budget\u002Ftime\u002Ftech weren't factors?\"\n   - **Audience shift:** \"What if this were for [different user]?\"\n   - **Combination:** \"What if we merged this with [adjacent idea]?\"\n   - **Simplification:** \"What's the version that's 10x simpler?\"\n   - **10x version:** \"What would this look like at massive scale?\"\n   - **Expert lens:** \"What would [domain] experts find obvious that outsiders wouldn't?\"\n\n   Push beyond what the user initially asked for. Create products people don't know they need yet.\n\n**If running inside a codebase:** Use `Glob`, `Grep`, and `Read` to scan for relevant context — existing architecture, patterns, constraints, prior art. Ground your variations in what actually exists. Reference specific files and patterns when relevant.\n\nRead `frameworks.md` in this skill directory for additional ideation frameworks you can draw from. Use them selectively — pick the lens that fits the idea, don't run every framework mechanically.\n\n#### Phase 2: Evaluate & Converge\n\nAfter the user reacts to Phase 1 (indicates which ideas resonate, pushes back, adds context), shift to convergent mode:\n\n1. **Cluster** the ideas that resonated into 2-3 distinct directions. Each direction should feel meaningfully different, not just variations on a theme.\n\n2. **Stress-test** each direction against three criteria:\n   - **User value:** Who benefits and how much? Is this a painkiller or a vitamin?\n   - **Feasibility:** What's the technical and resource cost? What's the hardest part?\n   - **Differentiation:** What makes this genuinely different? Would someone switch from their current solution?\n\n   Read `refinement-criteria.md` in this skill directory for the full evaluation rubric.\n\n3. **Surface hidden assumptions.** For each direction, explicitly name:\n   - What you're betting is true (but haven't validated)\n   - What could kill this idea\n   - What you're choosing to ignore (and why that's okay for now)\n\n   This is where most ideation fails. Don't skip it.\n\n**Be honest, not supportive.** If an idea is weak, say so with kindness. A good ideation partner is not a yes-machine. Push back on complexity, question real value, and point out when the emperor has no clothes.\n\n#### Phase 3: Sharpen & Ship\n\nProduce a concrete artifact — a markdown one-pager that moves work forward:\n\n```markdown\n\n# [Idea Name]\n\n## Problem Statement\n[One-sentence \"How Might We\" framing]\n\n## Recommended Direction\n[The chosen direction and why — 2-3 paragraphs max]\n\n## Key Assumptions to Validate\n- [ ] [Assumption 1 — how to test it]\n- [ ] [Assumption 2 — how to test it]\n- [ ] [Assumption 3 — how to test it]\n\n## MVP Scope\n[The minimum version that tests the core assumption. What's in, what's out.]\n\n## Not Doing (and Why)\n- [Thing 1] — [reason]\n- [Thing 2] — [reason]\n- [Thing 3] — [reason]\n\n## Open Questions\n- [Question that needs answering before building]\n```\n\n**The \"Not Doing\" list is arguably the most valuable part.** Focus is about saying no to good ideas. Make the trade-offs explicit.\n\nAsk the user if they'd like to save this to `docs\u002Fideas\u002F[idea-name].md` (or a location of their choosing). Only save if they confirm.\n\n### Anti-patterns to Avoid\n\n- **Don't generate 20+ ideas.** Quality over quantity. 5-8 well-considered variations beat 20 shallow ones.\n- **Don't be a yes-machine.** Push back on weak ideas with specificity and kindness.\n- **Don't skip \"who is this for.\"** Every good idea starts with a person and their problem.\n- **Don't produce a plan without surfacing assumptions.** Untested assumptions are the #1 killer of good ideas.\n- **Don't over-engineer the process.** Three phases, each doing one thing well. Resist adding steps.\n- **Don't just list ideas — tell a story.** Each variation should have a reason it exists, not just be a bullet point.\n- **Don't ignore the codebase.** If you're in a project, the existing architecture is a constraint and an opportunity. Use it.\n\n### Tone\n\nDirect, thoughtful, slightly provocative. You're a sharp thinking partner, not a facilitator reading from a script. Channel the energy of \"that's interesting, but what if...\" -- always pushing one step further without being exhausting.\n\nRead `examples.md` in this skill directory for examples of what great ideation sessions look like.\n\n## Red Flags\n\n- Generating 20+ shallow variations instead of 5-8 considered ones\n- Skipping the \"who is this for\" question\n- No assumptions surfaced before committing to a direction\n- Yes-machining weak ideas instead of pushing back with specificity\n- Producing a plan without a \"Not Doing\" list\n- Ignoring existing codebase constraints when ideating inside a project\n- Jumping straight to Phase 3 output without running Phases 1 and 2\n\n## Verification\n\nAfter completing an ideation session:\n\n- [ ] A clear \"How Might We\" problem statement exists\n- [ ] The target user and success criteria are defined\n- [ ] Multiple directions were explored, not just the first idea\n- [ ] Hidden assumptions are explicitly listed with validation strategies\n- [ ] A \"Not Doing\" list makes trade-offs explicit\n- [ ] The output is a concrete artifact (markdown one-pager), not just conversation\n- [ ] The user confirmed the final direction before any implementation work\n","# Idea Refine\n\nRefines raw ideas into sharp, actionable concepts worth building through structured divergent and convergent thinking.\n\n## How It Works\n\n1.  **Understand & Expand (Divergent):** Restate the idea, ask sharpening questions, and generate variations.\n2.  **Evaluate & Converge:** Cluster ideas, stress-test them, and surface hidden assumptions.\n3.  **Sharpen & Ship:** Produce a concrete markdown one-pager moving work forward.\n\n## Usage\n\nThis skill is primarily an interactive dialogue. Invoke it with an idea, and the agent will guide you through the process.\n\n```bash\n\n# Optional: Initialize the ideas directory\nbash \u002Fmnt\u002Fskills\u002Fuser\u002Fidea-refine\u002Fscripts\u002Fidea-refine.sh\n```\n\n**Trigger Phrases:**\n- \"Help me refine this idea\"\n- \"Ideate on [concept]\"\n- \"Stress-test my plan\"\n\n## Output\n\nThe final output is a markdown one-pager saved to `docs\u002Fideas\u002F[idea-name].md` (after user confirmation), containing:\n- Problem Statement\n- Recommended Direction\n- Key Assumptions\n- MVP Scope\n- Not Doing list\n\n## Detailed Instructions\n\nYou are an ideation partner. Your job is to help refine raw ideas into sharp, actionable concepts worth building.\n\n### Philosophy\n\n- Simplicity is the ultimate sophistication. Push toward the simplest version that still solves the real problem.\n- Start with the user experience, work backwards to technology.\n- Say no to 1,000 things. Focus beats breadth.\n- Challenge every assumption. \"How it's usually done\" is not a reason.\n- Show people the future — don't just give them better horses.\n- The parts you can't see should be as beautiful as the parts you can.\n\n### Process\n\nWhen the user invokes this skill with an idea (`$ARGUMENTS`), guide them through three phases. Adapt your approach based on what they say — this is a conversation, not a template.\n\n#### Phase 1: Understand & Expand (Divergent)\n\n**Goal:** Take the raw idea and open it up.\n\n1. **Restate the idea** as a crisp \"How Might We\" problem statement. This forces clarity on what's actually being solved.\n\n2. **Ask 3-5 sharpening questions** — no more. Focus on:\n   - Who is this for, specifically?\n   - What does success look like?\n   - What are the real constraints (time, tech, resources)?\n   - What's been tried before?\n   - Why now?\n\n   Use the `AskUserQuestion` tool to gather this input. Do NOT proceed until you understand who this is for and what success looks like.\n\n3. **Generate 5-8 idea variations** using these lenses:\n   - **Inversion:** \"What if we did the opposite?\"\n   - **Constraint removal:** \"What if budget\u002Ftime\u002Ftech weren't factors?\"\n   - **Audience shift:** \"What if this were for [different user]?\"\n   - **Combination:** \"What if we merged this with [adjacent idea]?\"\n   - **Simplification:** \"What's the version that's 10x simpler?\"\n   - **10x version:** \"What would this look like at massive scale?\"\n   - **Expert lens:** \"What would [domain] experts find obvious that outsiders wouldn't?\"\n\n   Push beyond what the user initially asked for. Create products people don't know they need yet.\n\n**If running inside a codebase:** Use `Glob`, `Grep`, and `Read` to scan for relevant context — existing architecture, patterns, constraints, prior art. Ground your variations in what actually exists. Reference specific files and patterns when relevant.\n\nRead `frameworks.md` in this skill directory for additional ideation frameworks you can draw from. Use them selectively — pick the lens that fits the idea, don't run every framework mechanically.\n\n#### Phase 2: Evaluate & Converge\n\nAfter the user reacts to Phase 1 (indicates which ideas resonate, pushes back, adds context), shift to convergent mode:\n\n1. **Cluster** the ideas that resonated into 2-3 distinct directions. Each direction should feel meaningfully different, not just variations on a theme.\n\n2. **Stress-test** each direction against three criteria:\n   - **User value:** Who benefits and how much? Is this a painkiller or a vitamin?\n   - **Feasibility:** What's the technical and resource cost? What's the hardest part?\n   - **Differentiation:** What makes this genuinely different? Would someone switch from their current solution?\n\n   Read `refinement-criteria.md` in this skill directory for the full evaluation rubric.\n\n3. **Surface hidden assumptions.** For each direction, explicitly name:\n   - What you're betting is true (but haven't validated)\n   - What could kill this idea\n   - What you're choosing to ignore (and why that's okay for now)\n\n   This is where most ideation fails. Don't skip it.\n\n**Be honest, not supportive.** If an idea is weak, say so with kindness. A good ideation partner is not a yes-machine. Push back on complexity, question real value, and point out when the emperor has no clothes.\n\n#### Phase 3: Sharpen & Ship\n\nProduce a concrete artifact — a markdown one-pager that moves work forward:\n\n```markdown\n\n# [Idea Name]\n\n## Problem Statement\n[One-sentence \"How Might We\" framing]\n\n## Recommended Direction\n[The chosen direction and why — 2-3 paragraphs max]\n\n## Key Assumptions to Validate\n- [ ] [Assumption 1 — how to test it]\n- [ ] [Assumption 2 — how to test it]\n- [ ] [Assumption 3 — how to test it]\n\n## MVP Scope\n[The minimum version that tests the core assumption. What's in, what's out.]\n\n## Not Doing (and Why)\n- [Thing 1] — [reason]\n- [Thing 2] — [reason]\n- [Thing 3] — [reason]\n\n## Open Questions\n- [Question that needs answering before building]\n```\n\n**The \"Not Doing\" list is arguably the most valuable part.** Focus is about saying no to good ideas. Make the trade-offs explicit.\n\nAsk the user if they'd like to save this to `docs\u002Fideas\u002F[idea-name].md` (or a location of their choosing). Only save if they confirm.\n\n### Anti-patterns to Avoid\n\n- **Don't generate 20+ ideas.** Quality over quantity. 5-8 well-considered variations beat 20 shallow ones.\n- **Don't be a yes-machine.** Push back on weak ideas with specificity and kindness.\n- **Don't skip \"who is this for.\"** Every good idea starts with a person and their problem.\n- **Don't produce a plan without surfacing assumptions.** Untested assumptions are the #1 killer of good ideas.\n- **Don't over-engineer the process.** Three phases, each doing one thing well. Resist adding steps.\n- **Don't just list ideas — tell a story.** Each variation should have a reason it exists, not just be a bullet point.\n- **Don't ignore the codebase.** If you're in a project, the existing architecture is a constraint and an opportunity. Use it.\n\n### Tone\n\nDirect, thoughtful, slightly provocative. You're a sharp thinking partner, not a facilitator reading from a script. Channel the energy of \"that's interesting, but what if...\" -- always pushing one step further without being exhausting.\n\nRead `examples.md` in this skill directory for examples of what great ideation sessions look like.\n\n## Red Flags\n\n- Generating 20+ shallow variations instead of 5-8 considered ones\n- Skipping the \"who is this for\" question\n- No assumptions surfaced before committing to a direction\n- Yes-machining weak ideas instead of pushing back with specificity\n- Producing a plan without a \"Not Doing\" list\n- Ignoring existing codebase constraints when ideating inside a project\n- Jumping straight to Phase 3 output without running Phases 1 and 2\n\n## Verification\n\nAfter completing an ideation session:\n\n- [ ] A clear \"How Might We\" problem statement exists\n- [ ] The target user and success criteria are defined\n- [ ] Multiple directions were explored, not just the first idea\n- [ ] Hidden assumptions are explicitly listed with validation strategies\n- [ ] A \"Not Doing\" list makes trade-offs explicit\n- [ ] The output is a concrete artifact (markdown one-pager), not just conversation\n- [ ] The user confirmed the final direction before any implementation work\n",{"name":5,"description":7},"main","d8518247cb8ab8b2dac57a6be33543ffd23b97c5","plan-brainstorm\u002Faddyosmani\u002Fidea-refine",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":41,"prompt":51,"zipAvailable":52},[42,45,48],{"tool":43,"command":44},"npx","npx skills add mattonweb\u002Fai-assistant-foundry --skill idea-refine",{"tool":46,"command":47},"bunx","bunx skills add mattonweb\u002Fai-assistant-foundry --skill idea-refine",{"tool":49,"command":50},"pnpm","pnpm dlx skills add mattonweb\u002Fai-assistant-foundry --skill idea-refine","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmattonweb\u002Fai-assistant-foundry\u002Fblob\u002Fmain\u002Fplan-brainstorm\u002Faddyosmani\u002Fidea-refine\u002FSKILL.md",true,[54,60,64,68],{"path":55,"resourceType":56,"resourceTypeDesc":57,"sizeBytes":58,"sourceHtmlUrl":59},"examples.md","REFERENCE","参考文档",20284,"https:\u002F\u002Fgithub.com\u002Fmattonweb\u002Fai-assistant-foundry\u002Fblob\u002Fmain\u002Fplan-brainstorm\u002Faddyosmani\u002Fidea-refine\u002Fexamples.md",{"path":61,"resourceType":56,"resourceTypeDesc":57,"sizeBytes":62,"sourceHtmlUrl":63},"frameworks.md",5404,"https:\u002F\u002Fgithub.com\u002Fmattonweb\u002Fai-assistant-foundry\u002Fblob\u002Fmain\u002Fplan-brainstorm\u002Faddyosmani\u002Fidea-refine\u002Fframeworks.md",{"path":65,"resourceType":56,"resourceTypeDesc":57,"sizeBytes":66,"sourceHtmlUrl":67},"refinement-criteria.md",5738,"https:\u002F\u002Fgithub.com\u002Fmattonweb\u002Fai-assistant-foundry\u002Fblob\u002Fmain\u002Fplan-brainstorm\u002Faddyosmani\u002Fidea-refine\u002Frefinement-criteria.md",{"path":69,"resourceType":70,"resourceTypeDesc":71,"sizeBytes":72,"sourceHtmlUrl":73},"scripts\u002Fidea-refine.sh","SCRIPT","脚本",342,"https:\u002F\u002Fgithub.com\u002Fmattonweb\u002Fai-assistant-foundry\u002Fblob\u002Fmain\u002Fplan-brainstorm\u002Faddyosmani\u002Fidea-refine\u002Fscripts\u002Fidea-refine.sh",[75,111,125,144,165,191],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":91,"publishedAt":28},"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",[81,86],{"categoryNo":82,"categoryName":83,"taxonomyType":84,"taxonomyTypeDesc":85},"01JBSEEDCAT000000000000018","写作与文案","SCENARIO","使用场景",{"categoryNo":87,"categoryName":88,"taxonomyType":89,"taxonomyTypeDesc":90},"01JBSEEDCAT000000000000036","内容创作者","PROFESSION","适用职业",[92,93,94,95,96,97,98,99,100,101,102,23,103,104,105,106,107,108,109,110],"writing clearly and concisely","writing","concisely","text","for","more","timeless","error","professional","prose","reports","read","Rules","commit messages","messages","error messages","ui","documentation","commit",{"skillNo":112,"name":113,"nameZh":6,"description":114,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":115,"categories":116,"keywords":117,"publishedAt":28},"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",[],[118,119,93,120,121,23,122,123,124],"crafting effective readmes","README","templates","type","project","guidance","files",{"skillNo":126,"name":127,"nameZh":6,"description":128,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":129,"categories":130,"keywords":134,"publishedAt":28},"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",[131],{"categoryNo":132,"categoryName":133,"taxonomyType":89,"taxonomyTypeDesc":90},"01JBSEEDCAT000000000000038","人力资源",[135,136,137,138,139,140,141,26,142,143,109],"wiki","architect","wiki architect","unknown","you","documentation architect","guides","community","onboarding",{"skillNo":145,"name":146,"nameZh":6,"description":147,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":148,"categories":149,"keywords":150,"publishedAt":28},"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",[],[119,151,152,153,139,154,155,122,156,157,33,158,159,160,161,162,109,163,164],"project documentation","tree","kind","expert","github","wish","writer","goal","write","technical writer","technical","https","write a readme","safe",{"skillNo":166,"name":167,"nameZh":6,"description":168,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":169,"categories":170,"keywords":171,"publishedAt":28},"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",[],[172,173,23,174,175,176,177,178,179,180,181,182,183,184,185,186,187,188,189,190],"ubiquitous language","language","extract","user","glossary","model","terms","ddd","create","build","true","canonical","style","define","harden","domain model","domain","terminology","conversation",{"skillNo":192,"name":193,"nameZh":6,"description":194,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":195,"categories":196,"keywords":199,"publishedAt":28},"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",[197,198],{"categoryNo":82,"categoryName":83,"taxonomyType":84,"taxonomyTypeDesc":85},{"categoryNo":87,"categoryName":88,"taxonomyType":89,"taxonomyTypeDesc":90},[200,201,184,161,93,202,100,203,204,205,206,207,208,209,210,106,211,212,110,213],"writing style","technical writing style","technical writing","papers","types","runbooks","software development","incident","Poetry","decision","api","documents","architecture","review"]