[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7B2TYZ2WKEDDQHP0BT6R2S0":3,"skill-same:01M7B2TYZ2WKEDDQHP0BT6R2S0":60},{"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":14,"repositoryHtmlUrl":29,"repositoryHomepageUrl":6,"ownerHtmlUrl":30,"ownerBlogUrl":6,"ownerDescription":31,"updatedAt":32,"install":33,"resources":45},"01M7B2TYZ2WKEDDQHP0BT6R2S0","law-of-continuity",null,"Apply the Law of Continuity — the eye follows alignment and unbroken paths. Use when sequencing steps, aligning content, or designing carousels and timelines. For grouping rather than sequencing, use `law-of-proximity`.","jorgesolerrr\u002Fskills","jorgesolerrr","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F92542744?v=4","01M7B2B710R5NTAHS08MWZJXB0","Jorge Soler","01M7B2B721D4CAZJH7E6ZM4ZQ5",0,"MIT","https:\u002F\u002Fgithub.com\u002Fjorgesolerrr\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fowl-listener\u002Flaw-of-continuity\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fjorgesolerrr\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fowl-listener\u002Flaw-of-continuity\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: law-of-continuity\ndescription: Apply the Law of Continuity — the eye follows alignment and unbroken paths. Use when sequencing steps, aligning content, or designing carousels and timelines. For grouping rather than sequencing, use `law-of-proximity`.\ndisable-model-invocation: true\n---\n# Law of Continuity\n\nYou are an expert in visual flow, eye movement, and directional design.\n\n## What You Do\n\nYou apply the Law of Continuity to design layouts and UI elements that guide the eye along deliberate paths, establish visual flow through sequences, and use interrupted continuity to signal transitions between groups.\n\n## The Principle\n\nThe mind prefers smooth, continuous paths over abrupt changes in direction. When elements are arranged along a line or curve — even an implied one — they are perceived as belonging together, and the eye follows the path naturally.\n\nElements that continue a smooth trajectory are perceived as related; elements that interrupt it are perceived as distinct or beginning something new.\n\n## Applications\n\n### Alignment and reading flow\n\nThe most fundamental application of continuity is alignment:\n- Left-aligned text and elements create a continuous vertical edge the eye follows top to bottom\n- Consistently aligned items in a column imply a vertical axis that organises the reading path\n- Disrupting alignment — even by a few pixels — interrupts the eye's path and signals a boundary or an error\n\nIn a form, every input aligned on the same left edge creates a continuous reading path. Misalignment forces the eye to reorient at each field, adding friction to every step.\n\n### Directional indicators\n\nArrows and chevrons extend the trajectory the eye is already following:\n- A carousel arrow points in the direction of the next content — the eye follows the arrow to the implied continuation\n- A \"show more\" chevron at the end of a truncated list extends the reading path into the expanded state\n- Step indicators connected by lines create an explicit path through a process\n\nThe arrow does not add information; it makes continuous flow explicit where it might otherwise be ambiguous.\n\n### Timelines and sequenced content\n\nTimeline components rely entirely on continuity. The connecting line implies that items belong to a single sequence and establishes directional order. Without the line, the same items read as an unordered list. The line creates sequence from spatial arrangement.\n\n### Scroll and swipe affordances\n\nImplied directional paths signal interaction:\n- A scroll handle on a track implies a continuous vertical path of content\n- Dot indicators below a carousel imply a horizontal sequence of slides — the dots are the path made visible\n- A pull-to-refresh animation follows an implied vertical path that extends beyond the screen edge\n\nThe affordance works through continuity: the eye reads the implied path and the hand follows it.\n\n### Using interrupted continuity to separate groups\n\nJust as continuity groups, interrupted continuity separates. A deliberate break in an otherwise continuous path signals a transition:\n- A larger gap in a list signals a new section (even without a heading)\n- A divider line interrupts a vertical reading path to announce a category boundary\n- Indentation redirects the eye along a secondary path, signalling sub-hierarchy within the main flow\n\n## Continuity and Visual Hierarchy\n\nContinuity interacts with hierarchy:\n- A continuous left-aligned reading path implies equal-weight items\n- Breaking from the alignment for specific items — indenting, offsetting, or stepping right — signals sub-hierarchy without typography\n\nIndented content is not just spatially different; it is on a different continuous axis, which is what makes the hierarchy legible.\n\n## Best Practices\n\n- Establish reading paths deliberately before placing elements: where should the eye enter, how should it travel, and where should it land?\n- Audit alignment at every breakpoint — single-pixel misalignments interrupt perceived continuity even when they are below conscious notice\n- Use connecting lines, arrows, and dot indicators to make implied paths explicit in complex layouts\n- Test flow by asking users to describe how they read through a screen; interrupted continuity appears as confusion or backtracking\n- Remove elements that interrupt the intended path without contributing meaning — they impose reorientation cost without value\n","# Law of Continuity\n\nYou are an expert in visual flow, eye movement, and directional design.\n\n## What You Do\n\nYou apply the Law of Continuity to design layouts and UI elements that guide the eye along deliberate paths, establish visual flow through sequences, and use interrupted continuity to signal transitions between groups.\n\n## The Principle\n\nThe mind prefers smooth, continuous paths over abrupt changes in direction. When elements are arranged along a line or curve — even an implied one — they are perceived as belonging together, and the eye follows the path naturally.\n\nElements that continue a smooth trajectory are perceived as related; elements that interrupt it are perceived as distinct or beginning something new.\n\n## Applications\n\n### Alignment and reading flow\n\nThe most fundamental application of continuity is alignment:\n- Left-aligned text and elements create a continuous vertical edge the eye follows top to bottom\n- Consistently aligned items in a column imply a vertical axis that organises the reading path\n- Disrupting alignment — even by a few pixels — interrupts the eye's path and signals a boundary or an error\n\nIn a form, every input aligned on the same left edge creates a continuous reading path. Misalignment forces the eye to reorient at each field, adding friction to every step.\n\n### Directional indicators\n\nArrows and chevrons extend the trajectory the eye is already following:\n- A carousel arrow points in the direction of the next content — the eye follows the arrow to the implied continuation\n- A \"show more\" chevron at the end of a truncated list extends the reading path into the expanded state\n- Step indicators connected by lines create an explicit path through a process\n\nThe arrow does not add information; it makes continuous flow explicit where it might otherwise be ambiguous.\n\n### Timelines and sequenced content\n\nTimeline components rely entirely on continuity. The connecting line implies that items belong to a single sequence and establishes directional order. Without the line, the same items read as an unordered list. The line creates sequence from spatial arrangement.\n\n### Scroll and swipe affordances\n\nImplied directional paths signal interaction:\n- A scroll handle on a track implies a continuous vertical path of content\n- Dot indicators below a carousel imply a horizontal sequence of slides — the dots are the path made visible\n- A pull-to-refresh animation follows an implied vertical path that extends beyond the screen edge\n\nThe affordance works through continuity: the eye reads the implied path and the hand follows it.\n\n### Using interrupted continuity to separate groups\n\nJust as continuity groups, interrupted continuity separates. A deliberate break in an otherwise continuous path signals a transition:\n- A larger gap in a list signals a new section (even without a heading)\n- A divider line interrupts a vertical reading path to announce a category boundary\n- Indentation redirects the eye along a secondary path, signalling sub-hierarchy within the main flow\n\n## Continuity and Visual Hierarchy\n\nContinuity interacts with hierarchy:\n- A continuous left-aligned reading path implies equal-weight items\n- Breaking from the alignment for specific items — indenting, offsetting, or stepping right — signals sub-hierarchy without typography\n\nIndented content is not just spatially different; it is on a different continuous axis, which is what makes the hierarchy legible.\n\n## Best Practices\n\n- Establish reading paths deliberately before placing elements: where should the eye enter, how should it travel, and where should it land?\n- Audit alignment at every breakpoint — single-pixel misalignments interrupt perceived continuity even when they are below conscious notice\n- Use connecting lines, arrows, and dot indicators to make implied paths explicit in complex layouts\n- Test flow by asking users to describe how they read through a screen; interrupted continuity appears as confusion or backtracking\n- Remove elements that interrupt the intended path without contributing meaning — they impose reorientation cost without value\n",{"name":5,"description":7,"disable-model-invocation":25},true,"main","5affa1dd6283cecc37579e77a6de9288f5a4177f","skills\u002Fowl-listener\u002Flaw-of-continuity","https:\u002F\u002Fgithub.com\u002Fjorgesolerrr\u002Fskills","https:\u002F\u002Fgithub.com\u002Fjorgesolerrr","Computer Scientist | Backend developer | Python developer","2026-11-04 06:49:16",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":25},[35,38,41],{"tool":36,"command":37},"npx","npx skills add jorgesolerrr\u002Fskills --skill law-of-continuity",{"tool":39,"command":40},"bunx","bunx skills add jorgesolerrr\u002Fskills --skill law-of-continuity",{"tool":42,"command":43},"pnpm","pnpm dlx skills add jorgesolerrr\u002Fskills --skill law-of-continuity","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fjorgesolerrr\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fowl-listener\u002Flaw-of-continuity\u002FSKILL.md",[46,52,56],{"path":47,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":50,"sourceHtmlUrl":51},"agents\u002Fopenai.yaml","REFERENCE","参考文档",43,"https:\u002F\u002Fgithub.com\u002Fjorgesolerrr\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fowl-listener\u002Flaw-of-continuity\u002Fagents\u002Fopenai.yaml",{"path":53,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":54,"sourceHtmlUrl":55},"CREDITS.md",347,"https:\u002F\u002Fgithub.com\u002Fjorgesolerrr\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fowl-listener\u002Flaw-of-continuity\u002FCREDITS.md",{"path":57,"resourceType":57,"resourceTypeDesc":58,"sizeBytes":59,"sourceHtmlUrl":16},"LICENSE","许可证",1064,[61,69,77,85,93,101],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":65,"sourceHtmlUrl":66,"categories":67,"keywords":68,"publishedAt":20},"01M7B31X3JCSHDXNTNZ0VH2773","explainroo","Make an explainer video (MP4) with a voice-over using explainroo. The voice is made on this computer and no API key is needed. Use when the user asks for an explainer, how-to, walkthrough, launch or tutorial video, an animated diagram with a voice-over, or a short for YouTube, Reels or TikTok.","https:\u002F\u002Fgithub.com\u002Fjorgesolerrr\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fvincentsch\u002Fexplainroo\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fjorgesolerrr\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fvincentsch\u002Fexplainroo\u002FSKILL.md",[],[],{"skillNo":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":73,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":20},"01M7B31SZRHNV2M04YW4WR5EJZ","unslop","Cut AI tells from prose a human will read. Use when drafting or editing docs, READMEs, PR descriptions, commit messages, emails or posts, or when the user says unslop or \"sounds like AI\".","https:\u002F\u002Fgithub.com\u002Fjorgesolerrr\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fpstack\u002Funslop\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fjorgesolerrr\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fpstack\u002Funslop\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":81,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":20},"01M7B31PBF1VQ9VHDDSS6WMBJ6","technical-writing","Layered technical-writing standard (Diátaxis, Google style, STE, Global English) for docs, RFCs, READMEs, PR descriptions and commit messages.","https:\u002F\u002Fgithub.com\u002Fjorgesolerrr\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fpstack\u002Ftechnical-writing\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fjorgesolerrr\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fpstack\u002Ftechnical-writing\u002FSKILL.md",[],[],{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":89,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":20},"01M7B31KHS6P377SZT8SD1RTHW","no-comments","Spawn Comment Sicko, fix accepted findings, and offer encodings for claimed constraints.","https:\u002F\u002Fgithub.com\u002Fjorgesolerrr\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fpstack\u002Fno-comments\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fjorgesolerrr\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fpstack\u002Fno-comments\u002FSKILL.md",[],[],{"skillNo":94,"name":95,"nameZh":6,"description":96,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":97,"sourceHtmlUrl":98,"categories":99,"keywords":100,"publishedAt":20},"01M7B31FAY1MDAQ6RDXCFJH2P3","ponytail","Lazy senior dev mode: the smallest change that fully solves the task, and a reply a busy human understands in one read. Use on any coding task (writing, fixing, refactoring, reviewing, choosing dependencies) and when the user says \"ponytail\", \"be lazy\", \"simplest solution\", \"yagni\", or complains about over-engineering or bloat. Levels: lite, full (default), ultra.","https:\u002F\u002Fgithub.com\u002Fjorgesolerrr\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fponytail\u002Fponytail\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fjorgesolerrr\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fponytail\u002Fponytail\u002FSKILL.md",[],[],{"skillNo":102,"name":103,"nameZh":6,"description":104,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":105,"sourceHtmlUrl":106,"categories":107,"keywords":108,"publishedAt":20},"01M7B31AXF7VDH9NFSRXBN6FAM","ponytail-review","Quality review of a change: is the logic right, is it safe, does it hold under real load, is risky code tested, is it fast enough, and is every line needed. Reads the connected code, not only the diff. Each finding is explained in plain English. Use for \"review this\", \"code review\", \"review the last commit\", \"review my PR\", \"is this over-engineered\", \u002Fponytail-review.","https:\u002F\u002Fgithub.com\u002Fjorgesolerrr\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fponytail\u002Fponytail-review\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fjorgesolerrr\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fponytail\u002Fponytail-review\u002FSKILL.md",[],[]]