[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6RB3T7YJ6C1BH289ZP9NH06":3,"skill-same:01M6RB3T7YJ6C1BH289ZP9NH06":77},{"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":34,"linkOnly":35,"markdownContent":36,"markdownBody":37,"frontMatter":38,"refName":39,"commitSha":40,"skillDirectory":41,"forksCount":42,"repositoryHtmlUrl":43,"repositoryHomepageUrl":6,"ownerHtmlUrl":44,"ownerBlogUrl":45,"ownerDescription":46,"updatedAt":47,"install":48,"resources":61},"01M6RB3T7YJ6C1BH289ZP9NH06","architect",null,"Sketch types, signatures, and module structure before code, then stay in the loop while implementation fills in. Use for \u002Farchitect, 'architect this', 'design this', or non-trivial work where jumping to code would lock in the wrong shape.","Nairon-AI\u002Fagentic-starter-pack","Nairon-AI","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F260662138?v=4","01M6R8PZ1Y8CSQGFN61VACZGTH","Nairon AI","01M6R8PZ6184VR3BA88YZFBC3N",4,"MIT","https:\u002F\u002Fgithub.com\u002FNairon-AI\u002Fagentic-starter-pack\u002Fblob\u002Fmain\u002Fplanning\u002Farchitect\u002FSKILL.md",[],[5,19,20,21,22,23,24,25,26,27,28,29,30,31,32,33],"design","code","loop","work","use","sketch","shape","implementation","signatures","structure","module","types","lock","for","Wrong","2026-11-10 10:12:30",false,"---\nname: architect\ndescription: \"Sketch types, signatures, and module structure before code, then stay in the loop while implementation fills in. Use for \u002Farchitect, 'architect this', 'design this', or non-trivial work where jumping to code would lock in the wrong shape.\"\n---\n\n# Architect\n\nDesign before implementing. Sketch types, function signatures, class shapes, and module boundaries with `not implemented` bodies and pseudocode. Synthesize across multiple model perspectives, then fill in code against the chosen sketch. If implementation proves the sketch wrong, throw it out and redesign.\n\n## Start\n\nUse the environment's plan or task tracker with one entry per phase before starting. Autonomous mode without checkpoints needs visible phase position.\n\n1. Ground\n2. Sketch\n3. Agree\n4. Implement\n5. Scrap\n\n## Phase A: Ground the problem\n\nBuild a real mental model of every system the new code touches. Run the **how** skill over the relevant subsystems. Critique mode if existing structure is the constraint or the design must push back on it.\n\nNaming a file isn't grounding. Produce the traced model `how` prescribes. If the design redefines ownership or layering, also run the **why** skill on the existing shape so the rationale becomes a constraint, not a guess.\n\nSkip Phase A only when the work is genuinely greenfield with no surrounding system to integrate.\n\n## Phase B: Sketch\n\nRun the **arena** skill with the design-sketch task and the Phase A grounding artifacts. Pass `references\u002Frunner-prompt.md` as each runner's prompt. Each candidate produces a design package shaped per `references\u002Frationale-template.md`: the caller's usage written first, then the type sketch, function signatures, module map, and prose rationale derived from it.\n\nUse the available subagent pool. Prefer different model families when the host supports model selection; otherwise give each runner a distinct design constraint.\n\nThis makes `brain\u002Fprinciples\u002Fexhaust-the-design-space.md` concrete: whole-shape alternatives, not point fixes inside one shape.\n\nArena returns one synthesized design package. The synthesis decision populates the rationale's \"Synthesis decision\" section.\n\n## Phase C: Agree (opt-in)\n\nDefault: proceed directly to implementation with the synthesized design. No human checkpoint.\n\nOpt in to a checkpoint when the invoker explicitly asks: \"\u002Farchitect with checkpoint,\" \"stop and show me before implementing,\" or similar. Then surface the synthesized design and pause for sign-off.\n\nThe synthesis can ship as its own commit either way. Follow the scaffold-first guidance in `brain\u002Fprinciples\u002Ffoundational-thinking.md`; subsequent commits fill bodies against a stable contract. Planned, scoped breakage during fill-in is acceptable under `brain\u002Fprinciples\u002Foutcome-oriented-execution.md`. For adversarial pressure before implementation, run `interrogate` on the synthesized sketch.\n\nIf the human pushes back on the shape (in a checkpoint or after the fact), treat that as Phase A evidence. Re-ground and re-run Phase B before writing more code.\n\n## Phase D: Implement against the sketch\n\nReplace `not implemented` bodies with code, pseudocode with logic. The synthesized sketch is the contract.\n\nDeviations from the sketch are signal worth surfacing, not friction to absorb silently. If a function needs a parameter the sketch didn't anticipate, ask whether the sketch was wrong, the requirement was missed, or the implementation is overreaching. Surface it; don't bolt it on.\n\n## Phase E: Scrap when the architecture is wrong\n\nIf implementation keeps producing friction the sketch cannot absorb, throw the sketch out. Follow `brain\u002Fprinciples\u002Fredesign-from-first-principles.md` and `brain\u002Fprinciples\u002Ffix-root-causes.md`; do not bolt fixes onto a wrong design.\n\nThe signal is a *pattern*, not single instances. Tells:\n\n- The same shape of workaround appearing repeatedly across unrelated code.\n- Multiple unrelated edge cases that all need special-case branches.\n- Types that need escape hatches (`any`, casts, optional fields always set in practice) to compile.\n- The \"we need a lock\" reflex when the sketch said the state wasn't shared.\n- Callers having to know the abstraction's internal rules to use it.\n- Two or more independent Phase D deviations of the same shape across the implementation. Surfacing deviations is Phase D's job; a repeated pattern of them is Phase E's trigger.\n\nUse judgment. A few edge cases don't condemn an architecture. Some problems are legitimately complex; complexity in the data is not complexity in the design. The rewrite signal is repeated friction of the same shape, not single hard cases.\n\nWhen you scrap:\n\n1. Re-run the **how** skill over what's been built. The implementation lessons enter the new design as inputs, not vibes.\n2. Redesign as if the new constraints had been day-one assumptions, per redesign-from-first-principles.\n3. Follow `brain\u002Fprinciples\u002Fsubtract-before-you-add.md`. The new sketch should be smaller than the old one before it grows.\n4. Return to Phase B and re-run arena.\n\n## Outputs\n\nThe caller's usage is written first and the type sketch derived from it. One file with new types and signatures for small changes; module map plus type definitions for larger work. The rationale ships alongside, shaped per `references\u002Frationale-template.md`, including the usage sketch and the synthesis decision.\n","# Architect\n\nDesign before implementing. Sketch types, function signatures, class shapes, and module boundaries with `not implemented` bodies and pseudocode. Synthesize across multiple model perspectives, then fill in code against the chosen sketch. If implementation proves the sketch wrong, throw it out and redesign.\n\n## Start\n\nUse the environment's plan or task tracker with one entry per phase before starting. Autonomous mode without checkpoints needs visible phase position.\n\n1. Ground\n2. Sketch\n3. Agree\n4. Implement\n5. Scrap\n\n## Phase A: Ground the problem\n\nBuild a real mental model of every system the new code touches. Run the **how** skill over the relevant subsystems. Critique mode if existing structure is the constraint or the design must push back on it.\n\nNaming a file isn't grounding. Produce the traced model `how` prescribes. If the design redefines ownership or layering, also run the **why** skill on the existing shape so the rationale becomes a constraint, not a guess.\n\nSkip Phase A only when the work is genuinely greenfield with no surrounding system to integrate.\n\n## Phase B: Sketch\n\nRun the **arena** skill with the design-sketch task and the Phase A grounding artifacts. Pass `references\u002Frunner-prompt.md` as each runner's prompt. Each candidate produces a design package shaped per `references\u002Frationale-template.md`: the caller's usage written first, then the type sketch, function signatures, module map, and prose rationale derived from it.\n\nUse the available subagent pool. Prefer different model families when the host supports model selection; otherwise give each runner a distinct design constraint.\n\nThis makes `brain\u002Fprinciples\u002Fexhaust-the-design-space.md` concrete: whole-shape alternatives, not point fixes inside one shape.\n\nArena returns one synthesized design package. The synthesis decision populates the rationale's \"Synthesis decision\" section.\n\n## Phase C: Agree (opt-in)\n\nDefault: proceed directly to implementation with the synthesized design. No human checkpoint.\n\nOpt in to a checkpoint when the invoker explicitly asks: \"\u002Farchitect with checkpoint,\" \"stop and show me before implementing,\" or similar. Then surface the synthesized design and pause for sign-off.\n\nThe synthesis can ship as its own commit either way. Follow the scaffold-first guidance in `brain\u002Fprinciples\u002Ffoundational-thinking.md`; subsequent commits fill bodies against a stable contract. Planned, scoped breakage during fill-in is acceptable under `brain\u002Fprinciples\u002Foutcome-oriented-execution.md`. For adversarial pressure before implementation, run `interrogate` on the synthesized sketch.\n\nIf the human pushes back on the shape (in a checkpoint or after the fact), treat that as Phase A evidence. Re-ground and re-run Phase B before writing more code.\n\n## Phase D: Implement against the sketch\n\nReplace `not implemented` bodies with code, pseudocode with logic. The synthesized sketch is the contract.\n\nDeviations from the sketch are signal worth surfacing, not friction to absorb silently. If a function needs a parameter the sketch didn't anticipate, ask whether the sketch was wrong, the requirement was missed, or the implementation is overreaching. Surface it; don't bolt it on.\n\n## Phase E: Scrap when the architecture is wrong\n\nIf implementation keeps producing friction the sketch cannot absorb, throw the sketch out. Follow `brain\u002Fprinciples\u002Fredesign-from-first-principles.md` and `brain\u002Fprinciples\u002Ffix-root-causes.md`; do not bolt fixes onto a wrong design.\n\nThe signal is a *pattern*, not single instances. Tells:\n\n- The same shape of workaround appearing repeatedly across unrelated code.\n- Multiple unrelated edge cases that all need special-case branches.\n- Types that need escape hatches (`any`, casts, optional fields always set in practice) to compile.\n- The \"we need a lock\" reflex when the sketch said the state wasn't shared.\n- Callers having to know the abstraction's internal rules to use it.\n- Two or more independent Phase D deviations of the same shape across the implementation. Surfacing deviations is Phase D's job; a repeated pattern of them is Phase E's trigger.\n\nUse judgment. A few edge cases don't condemn an architecture. Some problems are legitimately complex; complexity in the data is not complexity in the design. The rewrite signal is repeated friction of the same shape, not single hard cases.\n\nWhen you scrap:\n\n1. Re-run the **how** skill over what's been built. The implementation lessons enter the new design as inputs, not vibes.\n2. Redesign as if the new constraints had been day-one assumptions, per redesign-from-first-principles.\n3. Follow `brain\u002Fprinciples\u002Fsubtract-before-you-add.md`. The new sketch should be smaller than the old one before it grows.\n4. Return to Phase B and re-run arena.\n\n## Outputs\n\nThe caller's usage is written first and the type sketch derived from it. One file with new types and signatures for small changes; module map plus type definitions for larger work. The rationale ships alongside, shaped per `references\u002Frationale-template.md`, including the usage sketch and the synthesis decision.\n",{"name":5,"description":7},"main","c9d0c408715983e993b2f9ebffdbfa7f10153bcb","planning\u002Farchitect",0,"https:\u002F\u002Fgithub.com\u002FNairon-AI\u002Fagentic-starter-pack","https:\u002F\u002Fgithub.com\u002FNairon-AI","https:\u002F\u002Fwww.naironai.com\u002F","Building the future of Work","2026-09-20 17:40:05",{"source":8,"skillName":5,"commands":49,"prompt":59,"zipAvailable":60},[50,53,56],{"tool":51,"command":52},"npx","npx skills add Nairon-AI\u002Fagentic-starter-pack --skill architect",{"tool":54,"command":55},"bunx","bunx skills add Nairon-AI\u002Fagentic-starter-pack --skill architect",{"tool":57,"command":58},"pnpm","pnpm dlx skills add Nairon-AI\u002Fagentic-starter-pack --skill architect","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FNairon-AI\u002Fagentic-starter-pack\u002Fblob\u002Fmain\u002Fplanning\u002Farchitect\u002FSKILL.md",true,[62,67,73],{"path":63,"resourceType":63,"resourceTypeDesc":64,"sizeBytes":65,"sourceHtmlUrl":66},"LICENSE","许可证",1067,"https:\u002F\u002Fgithub.com\u002FNairon-AI\u002Fagentic-starter-pack\u002Fblob\u002Fmain\u002Fplanning\u002Farchitect\u002FLICENSE",{"path":68,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":71,"sourceHtmlUrl":72},"references\u002Frationale-template.md","REFERENCE","参考文档",2737,"https:\u002F\u002Fgithub.com\u002FNairon-AI\u002Fagentic-starter-pack\u002Fblob\u002Fmain\u002Fplanning\u002Farchitect\u002Freferences\u002Frationale-template.md",{"path":74,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":75,"sourceHtmlUrl":76},"references\u002Frunner-prompt.md",2716,"https:\u002F\u002Fgithub.com\u002FNairon-AI\u002Fagentic-starter-pack\u002Fblob\u002Fmain\u002Fplanning\u002Farchitect\u002Freferences\u002Frunner-prompt.md",[78,113,133,154,174,195],{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":94,"publishedAt":34},"01M6RBCG630Y8X99XWR9Q4GYNY","writing-shape","Take a markdown file of raw material and shape it into an article through a conversational session — drafting candidate openings, growing the piece paragraph by paragraph, arguing about format (lists, tables, callouts, quotes) at each step. Use when the user has a pile of notes, fragments, or a rough draft and wants help turning it into something publishable.","https:\u002F\u002Fgithub.com\u002FNairon-AI\u002Fagentic-starter-pack\u002Fblob\u002Fmain\u002Fwriting\u002Fwriting-shape\u002FSKILL.md",[84,89],{"categoryNo":85,"categoryName":86,"taxonomyType":87,"taxonomyTypeDesc":88},"01JBSEEDCAT000000000000018","写作与文案","SCENARIO","使用场景",{"categoryNo":90,"categoryName":91,"taxonomyType":92,"taxonomyTypeDesc":93},"01JBSEEDCAT000000000000036","内容创作者","PROFESSION","适用职业",[95,96,25,97,98,99,100,101,102,23,103,104,105,106,107,108,109,110,111,112],"writing","writing shape","notes","help","file","markdown","format","session","take","draft","article","material","it","about","quotes","at","candidate","when",{"skillNo":114,"name":115,"nameZh":6,"description":116,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":117,"categories":118,"keywords":121,"publishedAt":34},"01M6RBCCCB1KMF01P5SYGFWBSW","writing-fragments","Grilling session that mines the user for fragments — heterogeneous nuggets of writing (claims, vignettes, sharp sentences, half-thoughts) — and appends them to a single document as raw material for a future article. Use when the user wants to develop ideas before imposing structure, or mentions \"fragments\", \"ideate\", or \"raw material\" for writing.","https:\u002F\u002Fgithub.com\u002FNairon-AI\u002Fagentic-starter-pack\u002Fblob\u002Fmain\u002Fwriting\u002Fwriting-fragments\u002FSKILL.md",[119,120],{"categoryNo":85,"categoryName":86,"taxonomyType":87,"taxonomyTypeDesc":88},{"categoryNo":90,"categoryName":91,"taxonomyType":92,"taxonomyTypeDesc":93},[95,122,123,124,125,126,102,23,127,28,128,105,129,106,130,131,32,132,112],"writing fragments","grilling","ideate","develop","user","document","ideas","as","sharp","claims","single",{"skillNo":134,"name":135,"nameZh":6,"description":136,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":137,"categories":138,"keywords":141,"publishedAt":34},"01M6RBC8V7NHHKMTAZB4BPXVYQ","writing-beats","Shape an article as a journey of beats, choose-your-own-adventure style. The user picks a starting beat from the raw material, you write only that beat, then offer options for where to pivot next, beat by beat, until the article reaches a natural end. Use when the user has raw material and wants to assemble it as a narrative rather than an argument.","https:\u002F\u002Fgithub.com\u002FNairon-AI\u002Fagentic-starter-pack\u002Fblob\u002Fmain\u002Fwriting\u002Fwriting-beats\u002FSKILL.md",[139,140],{"categoryNo":85,"categoryName":86,"taxonomyType":87,"taxonomyTypeDesc":88},{"categoryNo":90,"categoryName":91,"taxonomyType":92,"taxonomyTypeDesc":93},[95,142,143,144,23,145,146,25,147,148,149,105,150,129,151,106,152,153,32,112],"writing beats","choose","write","assemble","only","journey","next","options","end","style","narrative","argument",{"skillNo":155,"name":156,"nameZh":6,"description":157,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":158,"categories":159,"keywords":162,"publishedAt":34},"01M6RBC58SG5Y5SC4ZV4ZNEFHC","stop-slop","Remove AI writing patterns from prose. Use when drafting, editing, or reviewing text to eliminate predictable AI tells.","https:\u002F\u002Fgithub.com\u002FNairon-AI\u002Fagentic-starter-pack\u002Fblob\u002Fmain\u002Fwriting\u002Fstop-slop\u002FSKILL.md",[160,161],{"categoryNo":85,"categoryName":86,"taxonomyType":87,"taxonomyTypeDesc":88},{"categoryNo":90,"categoryName":91,"taxonomyType":92,"taxonomyTypeDesc":93},[163,164,165,95,166,167,168,169,170,23,171,172,173,32,112],"stop","stop slop","slop","content","https","text","editing","remove","prose","patterns","drafts",{"skillNo":175,"name":176,"nameZh":6,"description":177,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":178,"categories":179,"keywords":182,"publishedAt":34},"01M6RBBJTTCJ7KZCP16G9JDFZH","humanizer","Remove signs of AI-generated writing from text. Use when editing or reviewing\ntext to make it sound more natural and human-written. Based on Wikipedia's\ncomprehensive \"Signs of AI writing\" guide. Detects and fixes patterns including:\ninflated symbolism, promotional language, superficial -ing analyses, vague\nattributions, em dash overuse, rule of three, AI vocabulary words, passive\nvoice, negative parallelisms, and filler phrases.","https:\u002F\u002Fgithub.com\u002FNairon-AI\u002Fagentic-starter-pack\u002Fblob\u002Fmain\u002Fwriting\u002Fhumanizer\u002FSKILL.md",[180,181],{"categoryNo":85,"categoryName":86,"taxonomyType":87,"taxonomyTypeDesc":88},{"categoryNo":90,"categoryName":91,"taxonomyType":92,"taxonomyTypeDesc":93},[176,95,20,183,168,184,144,185,186,170,187,188,172,189,190,191,192,193,194,112],"em dash","read","edit","generated","guide","opencode","three","human","make","wikipedia","vague","dash",{"skillNo":196,"name":197,"nameZh":6,"description":198,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":199,"categories":200,"keywords":201,"publishedAt":34},"01M6RBBEQKJ5HRH8AV9J85QB1T","feedback","Prepare, deliver, and debrief timely interpersonal feedback using a question-first coaching flow, observable behavior, owned experience, and concrete impact. Use when drafting feedback, coaching managers, rehearsing a feedback conversation, praising specific behavior, or reviewing whether feedback landed.","https:\u002F\u002Fgithub.com\u002FNairon-AI\u002Fagentic-starter-pack\u002Fblob\u002Fmain\u002Fwriting\u002Ffeedback\u002FSKILL.md",[],[197,202,203,204,205,206,23,207,208,209,210,211,112,212],"prepare","flow","first","question","behavior","conversation","coaching","debrief","impact","managers","deliver"]