[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7C3YYNYYYCMMJ5PPR32DBFY":3,"skill-same:01M7C3YYNYYYCMMJ5PPR32DBFY":75},{"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":16,"sourceHtmlUrl":17,"categories":18,"keywords":19,"publishedAt":20,"linkOnly":21,"markdownContent":22,"markdownBody":23,"frontMatter":24,"refName":26,"commitSha":27,"skillDirectory":28,"forksCount":29,"repositoryHtmlUrl":30,"repositoryHomepageUrl":6,"ownerHtmlUrl":31,"ownerBlogUrl":6,"ownerDescription":32,"updatedAt":33,"install":34,"resources":46},"01M7C3YYNYYYCMMJ5PPR32DBFY","lay-out",null,"Show a topic with the smallest useful view; avoid unneeded artifacts.","IamGroooooot\u002Fthink-with","IamGroooooot","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F38830620?v=4","01M7C3WS2BYY3Z7TRJ9M0E6AA1","Juhyeong Ko","01M7C3WS2ZYAT203A2N0Q6TRR4",1,"MIT","https:\u002F\u002Fgithub.com\u002FIamGroooooot\u002Fthink-with\u002Fblob\u002Fmain\u002Fplugins\u002Fclaude\u002Fthink-with\u002Fskills\u002Flay-out\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FIamGroooooot\u002Fthink-with\u002Fblob\u002Fmain\u002Fplugins\u002Fclaude\u002Fthink-with\u002Fskills\u002Flay-out\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: lay-out\ndescription: Show a topic with the smallest useful view; avoid unneeded artifacts.\ndisable-model-invocation: true\n---\n\nShow the current topic so the reader gets the key relationship from the diagrams alone. Prose adds at most a one-line takeaway and caveats that change a decision.\n\nBefore drawing, choose:\n- the one relationship the user must see (a change, comparison, decision, dependency, or flow) and its most consequential fact, which the view shows first and sets apart instead of burying it among routine details\n- the level that shows it: components, layers, states, or steps; drop to a code line only when that line alone carries the behavior\n- the form that fits the relationship\n- only supported edges; label relevant inference or dispute, and mark an unknown only where it changes the answer\n\nChoose forms first; read only their selected links:\n- condition or algorithm → pseudocode\n- one ordered path, or how a failure unfolds → trace or timeline\n- messages or handoffs between participants over time → horizontal [sequence](references\u002Fsequence.md)\n- data movement and storage → horizontal [data flow](references\u002Fdfd.md)\n- dependencies between modules or packages → [layered dependencies](references\u002Fdependencies.md)\n- call reachability → call tree\n- hierarchy or UI → shallow tree\n- state transition → state diagram that shows terminal states; a state table when exact guards matter\n- the same properties compared across parallel items, such as options or each route's guard before and after → aligned table, one row per item; when the answer is a path or what depends on what, draw it instead\n- spatial layout → wireframe\n- exact implementation → focused code\n\nUse one main view. Add a second only for a different relationship the question needs. When the user names several concerns, give each its own view; in a whole-system view, collapse parts off the relevant path into one box and mark the change in place.\n\nPrefer text fences and fit the terminal; if width is unknown, target 60 columns. Never wrap a connector. In a diff fence, reserve column 1 for +, -, or space and align unchanged context. Use Mermaid only if text loses a required relationship. Create HTML only if explicitly requested or necessary interaction cannot be provided inline.\n\nFor a diff or PR, start with the changed files as a short tree, one line each, so the reader knows where the change lives before how it behaves, and say whether it is proposed or applied. Then show the behavior change in the form the change takes. When the same property changes across parallel items, such as each route's auth or each client's timeout, use a before\u002Fafter table with one row per item so each pair reads across one row. When wiring or order changes, mark + for added and - for removed on one shared structure. Either way, lead with the change that alters behavior most, such as newly exposed or newly protected data, and group the routine deltas. For any other question, go straight to the view.\n\nRead [structural-diff](references\u002Fstructural-diff.md) only when changed diagram branches or connectors need realignment, not for ordinary file summaries or code patches.\n\nTreat diffs as evidence claims: separate file edits from behavior changes, mark only supported deltas, and leave preserved steps unmarked. Preserve guards and qualifiers. If the user asks what changed but gives no comparison data, say so in one line instead of inventing a comparison. Do not turn unprovided facts into settled claims. For a change, end with at most three short lines on what else it could break.\n","Show the current topic so the reader gets the key relationship from the diagrams alone. Prose adds at most a one-line takeaway and caveats that change a decision.\n\nBefore drawing, choose:\n- the one relationship the user must see (a change, comparison, decision, dependency, or flow) and its most consequential fact, which the view shows first and sets apart instead of burying it among routine details\n- the level that shows it: components, layers, states, or steps; drop to a code line only when that line alone carries the behavior\n- the form that fits the relationship\n- only supported edges; label relevant inference or dispute, and mark an unknown only where it changes the answer\n\nChoose forms first; read only their selected links:\n- condition or algorithm → pseudocode\n- one ordered path, or how a failure unfolds → trace or timeline\n- messages or handoffs between participants over time → horizontal [sequence](references\u002Fsequence.md)\n- data movement and storage → horizontal [data flow](references\u002Fdfd.md)\n- dependencies between modules or packages → [layered dependencies](references\u002Fdependencies.md)\n- call reachability → call tree\n- hierarchy or UI → shallow tree\n- state transition → state diagram that shows terminal states; a state table when exact guards matter\n- the same properties compared across parallel items, such as options or each route's guard before and after → aligned table, one row per item; when the answer is a path or what depends on what, draw it instead\n- spatial layout → wireframe\n- exact implementation → focused code\n\nUse one main view. Add a second only for a different relationship the question needs. When the user names several concerns, give each its own view; in a whole-system view, collapse parts off the relevant path into one box and mark the change in place.\n\nPrefer text fences and fit the terminal; if width is unknown, target 60 columns. Never wrap a connector. In a diff fence, reserve column 1 for +, -, or space and align unchanged context. Use Mermaid only if text loses a required relationship. Create HTML only if explicitly requested or necessary interaction cannot be provided inline.\n\nFor a diff or PR, start with the changed files as a short tree, one line each, so the reader knows where the change lives before how it behaves, and say whether it is proposed or applied. Then show the behavior change in the form the change takes. When the same property changes across parallel items, such as each route's auth or each client's timeout, use a before\u002Fafter table with one row per item so each pair reads across one row. When wiring or order changes, mark + for added and - for removed on one shared structure. Either way, lead with the change that alters behavior most, such as newly exposed or newly protected data, and group the routine deltas. For any other question, go straight to the view.\n\nRead [structural-diff](references\u002Fstructural-diff.md) only when changed diagram branches or connectors need realignment, not for ordinary file summaries or code patches.\n\nTreat diffs as evidence claims: separate file edits from behavior changes, mark only supported deltas, and leave preserved steps unmarked. Preserve guards and qualifiers. If the user asks what changed but gives no comparison data, say so in one line instead of inventing a comparison. Do not turn unprovided facts into settled claims. For a change, end with at most three short lines on what else it could break.\n",{"name":5,"description":7,"disable-model-invocation":25},true,"main","442b06fa7fd97decb5d1ad405ae32a3d564e6e90","plugins\u002Fclaude\u002Fthink-with\u002Fskills\u002Flay-out",0,"https:\u002F\u002Fgithub.com\u002FIamGroooooot\u002Fthink-with","https:\u002F\u002Fgithub.com\u002FIamGroooooot","☕️","2026-10-08 10:34:28",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":25},[36,39,42],{"tool":37,"command":38},"npx","npx skills add IamGroooooot\u002Fthink-with --skill lay-out",{"tool":40,"command":41},"bunx","bunx skills add IamGroooooot\u002Fthink-with --skill lay-out",{"tool":43,"command":44},"pnpm","pnpm dlx skills add IamGroooooot\u002Fthink-with --skill lay-out","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FIamGroooooot\u002Fthink-with\u002Fblob\u002Fmain\u002Fplugins\u002Fclaude\u002Fthink-with\u002Fskills\u002Flay-out\u002FSKILL.md",[47,51,57,63,67,71],{"path":48,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":50,"sourceHtmlUrl":16},"LICENSE","许可证",1067,{"path":52,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":55,"sourceHtmlUrl":56},"NOTICE","OTHER","其他",459,"https:\u002F\u002Fgithub.com\u002FIamGroooooot\u002Fthink-with\u002Fblob\u002Fmain\u002Fplugins\u002Fclaude\u002Fthink-with\u002Fskills\u002Flay-out\u002FNOTICE",{"path":58,"resourceType":59,"resourceTypeDesc":60,"sizeBytes":61,"sourceHtmlUrl":62},"references\u002Fdependencies.md","REFERENCE","参考文档",1379,"https:\u002F\u002Fgithub.com\u002FIamGroooooot\u002Fthink-with\u002Fblob\u002Fmain\u002Fplugins\u002Fclaude\u002Fthink-with\u002Fskills\u002Flay-out\u002Freferences\u002Fdependencies.md",{"path":64,"resourceType":59,"resourceTypeDesc":60,"sizeBytes":65,"sourceHtmlUrl":66},"references\u002Fdfd.md",440,"https:\u002F\u002Fgithub.com\u002FIamGroooooot\u002Fthink-with\u002Fblob\u002Fmain\u002Fplugins\u002Fclaude\u002Fthink-with\u002Fskills\u002Flay-out\u002Freferences\u002Fdfd.md",{"path":68,"resourceType":59,"resourceTypeDesc":60,"sizeBytes":69,"sourceHtmlUrl":70},"references\u002Fsequence.md",635,"https:\u002F\u002Fgithub.com\u002FIamGroooooot\u002Fthink-with\u002Fblob\u002Fmain\u002Fplugins\u002Fclaude\u002Fthink-with\u002Fskills\u002Flay-out\u002Freferences\u002Fsequence.md",{"path":72,"resourceType":59,"resourceTypeDesc":60,"sizeBytes":73,"sourceHtmlUrl":74},"references\u002Fstructural-diff.md",573,"https:\u002F\u002Fgithub.com\u002FIamGroooooot\u002Fthink-with\u002Fblob\u002Fmain\u002Fplugins\u002Fclaude\u002Fthink-with\u002Fskills\u002Flay-out\u002Freferences\u002Fstructural-diff.md",[76,82],{"skillNo":77,"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":78,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":20},"01M7C3ZNQ6K8GP1BZVAX28KXPW","https:\u002F\u002Fgithub.com\u002FIamGroooooot\u002Fthink-with\u002Fblob\u002Fmain\u002Fsrc\u002Fskills\u002Flay-out\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FIamGroooooot\u002Fthink-with\u002Fblob\u002Fmain\u002Fsrc\u002Fskills\u002Flay-out\u002FSKILL.md",[],[],{"skillNo":83,"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":84,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":20},"01M7C3Z6H5EEEFT6KS976F055W","https:\u002F\u002Fgithub.com\u002FIamGroooooot\u002Fthink-with\u002Fblob\u002Fmain\u002Fplugins\u002Fcodex\u002Fthink-with\u002Fskills\u002Flay-out\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FIamGroooooot\u002Fthink-with\u002Fblob\u002Fmain\u002Fplugins\u002Fcodex\u002Fthink-with\u002Fskills\u002Flay-out\u002FSKILL.md",[],[]]