[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7ANVMGH896FYRVFCG4RXPRC":3,"skill-same:01M7ANVMGH896FYRVFCG4RXPRC":48},{"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":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":29,"ownerHtmlUrl":30,"ownerBlogUrl":31,"ownerDescription":32,"updatedAt":33,"install":34,"resources":47},"01M7ANVMGH896FYRVFCG4RXPRC","gis-indexing-databases-tiling-and-rendering",null,"Use when storing, querying, or drawing spatial data at scale: spatial indexing with R-trees, quadtrees and geohashes and their query characteristics, spatial databases including PostGIS and the operations worth knowing, tiling schemes and vector versus raster tiles, and rendering including styling, generalization and label placement.","the-vibey-project\u002Fvibey","the-vibey-project","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F329298758?v=4","01M7AJHGZ9722CTJ4JNQZVRH0Q","the vibey project","01M7AJHGZVMG2K7TGXQ6XFHVG3",5,"MIT","https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey\u002Fblob\u002Fdevelop\u002Fsrc\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fgeospatial-software\u002Fskills\u002Fgis-indexing-databases-tiling-and-rendering\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: gis-indexing-databases-tiling-and-rendering\ndescription: \"Use when storing, querying, or drawing spatial data at scale: spatial indexing with R-trees, quadtrees and geohashes and their query characteristics, spatial databases including PostGIS and the operations worth knowing, tiling schemes and vector versus raster tiles, and rendering including styling, generalization and label placement.\"\n---\n\n# Geospatial Software: Spatial Indexing, Spatial Databases, Tiling, and Rendering\n\n> **Part 2 of 5** of the *Geospatial Software* reference (plugin `geospatial-software`), covering §4–§7. Sibling skills: `gis-coordinate-systems-data-models-and-formats` (§0–§3), `gis-routing-geocoding-and-positioning` (§8–§10), `gis-spatial-analysis-remote-sensing-and-privacy` (§11–§14), `gis-reference` (§15–§20). Section numbers are shared across the set; a reference written as §N → `skill` points into that sibling skill.\n>\n> **Currency:** Geodesy and projection mathematics are settled. Two areas moved. See §16 → `gis-reference` for the open basemap landscape and the cloud-native format stack.\n\n> **Scope.** ⚠️ **§1 → `gis-coordinate-systems-data-models-and-formats` is the most important section and the one most often skipped.**\n> Almost every serious geospatial bug is a coordinate reference system problem wearing a\n> different hat.\n>\n> **⚠️ GOTCHA** boxes mark the errors that silently produce wrong answers — and this\n> domain specializes in bugs that look plausible.\n>\n> **The three ideas that prevent most disasters:**\n> 1. **⚠️ A coordinate is meaningless without its CRS.** \"40.7128, −74.0060\" is not a\n>    location until you say which datum and which axis order. **Data with an unknown CRS\n>    is not data** (§1 → `gis-coordinate-systems-data-models-and-formats`).\n> 2. **⚠️ Every flat map lies.** Projection to a plane necessarily distorts area, angle,\n>    distance, or shape — you choose which. **Web Mercator, the default of the entire web,\n>    is unsuitable for area calculation and most analysis** (§1.3 → `gis-coordinate-systems-data-models-and-formats`).\n> 3. **⚠️ The Earth is not a sphere, and for many purposes not even an ellipsoid.**\n>    Haversine on a sphere is off by up to ~0.5%; the geoid differs from the ellipsoid by\n>    ±100 m vertically. **Whether that matters is a requirements question you must\n>    actually ask** (§1.1 → `gis-coordinate-systems-data-models-and-formats`, §10.3 → `gis-routing-geocoding-and-positioning`).\n\n---\n\n## §4. Spatial Indexing\n\n**⚠️ Spatial queries without an index are table scans, and the whole field exists to avoid\nthat.**\n```\nR-tree            ⚠️ hierarchical bounding boxes; THE standard for vector data\n                  (PostGIS GiST, SQLite, GeoPackage)\nQuadtree          recursive quadrant subdivision; rasters, tiles\nk-d tree          point data, nearest-neighbour\nGrid \u002F geohash    ⚠️ base32 string; PREFIX = containment, which makes it work in\n                  any plain key-value store\nS2 (Google)       ⚠️ sphere → cube → Hilbert curve. No projection distortion; excellent\n                  for global spherical work\nH3 (Uber)         ⚠️ HEXAGONAL global grid. Uniform neighbour distance — better for\n                  flow, aggregation and movement analysis\n```\n> **⚠️ GOTCHA — geohash has an edge problem people trip over.** ⚠️ **Two points a metre\n> apart can have completely different prefixes if they straddle a cell boundary.**\n> **Proximity search must check neighbouring cells, not just the shared prefix.** **S2 and\n> H3 handle adjacency explicitly and are better for anything doing neighbourhood\n> queries.**\n>\n> ⚠️ **And hexagons aren't a gimmick**: **a hexagon's six neighbours are all equidistant\n> from its centre; a square's eight are not.** **That matters for anything modelling\n> spread, flow or movement.** **The trade is that hexagons don't subdivide perfectly, so\n> H3's hierarchy is approximate.**\n\n**⚠️ The two-phase query pattern** underlies essentially all spatial querying: **filter by\nbounding box using the index (cheap), then refine with exact geometry (expensive).**\n**Getting this wrong — doing exact tests first — is a common performance bug.**\n\n---\n\n## §5. Spatial Databases\n\n**PostGIS** is the reference implementation and the default choice.\n```sql\n-- ⚠️ Always index, always use && or ST_DWithin to hit it\nCREATE INDEX idx ON t USING GIST (geom);\n\nST_Intersects, ST_Contains, ST_Within, ST_DWithin   -- ⚠️ these use the index\nST_Distance, ST_Area, ST_Length, ST_Buffer\nST_Transform(geom, 3857)     -- ⚠️ reproject\nST_MakeValid(geom)           -- §2\n```\n> **⚠️ GOTCHA — `geometry` vs `geography` is the type decision that matters.**\n> ⚠️ **`geometry` is planar and fast; distances and areas are in the CRS's units, so\n> using it with EPSG:4326 gives you answers in DEGREES, which are meaningless as\n> distance.** **`geography` computes on the spheroid and returns metres, correctly, and is\n> slower with fewer functions.**\n> **⚠️ The pragmatic pattern: store `geometry` in a suitable projected CRS, or use\n> `geography` for global data where correctness beats speed, and cast where needed.**\n> **`ST_Distance` on 4326 geometry returning \"0.0043\" is the classic symptom.**\n\n**⚠️ `ST_DWithin` beats `ST_Distance(...) \u003C x`** — the former uses the index, the latter\ncomputes distance for every row first.\n**Others**: **SpatiaLite**, **DuckDB spatial** (⚠️ **increasingly the analytics choice, and\nit reads GeoParquet directly**), **BigQuery GIS**, **Snowflake**, **Elasticsearch geo**,\n**MongoDB 2dsphere**, **Apache Sedona** for distributed work.\n\n---\n\n## §6. Tiling\n\n**⚠️ Serve maps as small pre-cut squares, not one giant image.**\n**Slippy map scheme**: `z\u002Fx\u002Fy`, ⚠️ **doubling resolution per zoom level, in Web Mercator\n(§1.3 → `gis-coordinate-systems-data-models-and-formats`).** **Zoom 0 is one 256×256 tile of the world; zoom `z` has `4^z` tiles.**\n**⚠️ TMS flips the Y axis relative to XYZ\u002FGoogle convention — a small, recurring source of\nupside-down maps.**\n\n**Raster vs vector tiles:**\n- **Raster** — pre-rendered images. ⚠️ **Simple; styling is baked in, so restyling means\n  re-rendering everything.**\n- **Vector (MVT)** — ⚠️ **geometry plus attributes, styled on the client.** **Restyle\n  instantly, rotate and tilt, high-DPI for free, smaller.** **The default for new work.**\n\n**⚠️ Generation**: **tippecanoe** (⚠️ **the standard tool; it adaptively simplifies and\ndrops features per zoom to keep tiles small — that behaviour is a feature and it will\nsurprise you if you don't expect dropped features at low zoom**), **planetiler** for\nplanet-scale, **Martin** and **tegola** for dynamic serving from PostGIS.\n**⚠️ Overzooming** lets you serve zoom 14 tiles up to zoom 20 by scaling client-side —\n**which is why most vector basemaps stop generating at 14.**\n\n---\n\n## §7. Rendering\n\n| Library | ⚠️ Character |\n|---|---|\n| **MapLibre GL JS** | ⚠️ **The open fork of Mapbox GL JS. WebGL vector rendering; the default for new open work** |\n| **Leaflet** | ⚠️ **Simple, tiny, huge plugin ecosystem. Raster-first** |\n| **OpenLayers** | ⚠️ **Most feature-complete; handles projections properly — the pick when CRS matters** |\n| **deck.gl** | ⚠️ **Large-scale data visualization; GPU layers** |\n| **Cesium** | 3D globe, terrain, time |\n| **Mapbox GL JS** | Proprietary since v2 |\n| **QGIS** | ⚠️ **Desktop GIS; free, excellent, and the tool for actually looking at your data** |\n\n**⚠️ Style specification** (MapLibre\u002FMapbox style JSON) — declarative layers, sources,\npaint and layout properties, **data-driven styling and expressions.** ⚠️ **This is the\npiece that makes vector tiles worth it: the same tiles support unlimited cartography.**\n\n**⚠️ Performance**: **simplify by zoom, cluster points, use the GPU rather than DOM,\navoid re-creating sources, and watch that \"just add a GeoJSON layer\" with 100k features\nwill destroy your frame rate.** **Put it in a tile pipeline instead.**\n","# Geospatial Software: Spatial Indexing, Spatial Databases, Tiling, and Rendering\n\n> **Part 2 of 5** of the *Geospatial Software* reference (plugin `geospatial-software`), covering §4–§7. Sibling skills: `gis-coordinate-systems-data-models-and-formats` (§0–§3), `gis-routing-geocoding-and-positioning` (§8–§10), `gis-spatial-analysis-remote-sensing-and-privacy` (§11–§14), `gis-reference` (§15–§20). Section numbers are shared across the set; a reference written as §N → `skill` points into that sibling skill.\n>\n> **Currency:** Geodesy and projection mathematics are settled. Two areas moved. See §16 → `gis-reference` for the open basemap landscape and the cloud-native format stack.\n\n> **Scope.** ⚠️ **§1 → `gis-coordinate-systems-data-models-and-formats` is the most important section and the one most often skipped.**\n> Almost every serious geospatial bug is a coordinate reference system problem wearing a\n> different hat.\n>\n> **⚠️ GOTCHA** boxes mark the errors that silently produce wrong answers — and this\n> domain specializes in bugs that look plausible.\n>\n> **The three ideas that prevent most disasters:**\n> 1. **⚠️ A coordinate is meaningless without its CRS.** \"40.7128, −74.0060\" is not a\n>    location until you say which datum and which axis order. **Data with an unknown CRS\n>    is not data** (§1 → `gis-coordinate-systems-data-models-and-formats`).\n> 2. **⚠️ Every flat map lies.** Projection to a plane necessarily distorts area, angle,\n>    distance, or shape — you choose which. **Web Mercator, the default of the entire web,\n>    is unsuitable for area calculation and most analysis** (§1.3 → `gis-coordinate-systems-data-models-and-formats`).\n> 3. **⚠️ The Earth is not a sphere, and for many purposes not even an ellipsoid.**\n>    Haversine on a sphere is off by up to ~0.5%; the geoid differs from the ellipsoid by\n>    ±100 m vertically. **Whether that matters is a requirements question you must\n>    actually ask** (§1.1 → `gis-coordinate-systems-data-models-and-formats`, §10.3 → `gis-routing-geocoding-and-positioning`).\n\n---\n\n## §4. Spatial Indexing\n\n**⚠️ Spatial queries without an index are table scans, and the whole field exists to avoid\nthat.**\n```\nR-tree            ⚠️ hierarchical bounding boxes; THE standard for vector data\n                  (PostGIS GiST, SQLite, GeoPackage)\nQuadtree          recursive quadrant subdivision; rasters, tiles\nk-d tree          point data, nearest-neighbour\nGrid \u002F geohash    ⚠️ base32 string; PREFIX = containment, which makes it work in\n                  any plain key-value store\nS2 (Google)       ⚠️ sphere → cube → Hilbert curve. No projection distortion; excellent\n                  for global spherical work\nH3 (Uber)         ⚠️ HEXAGONAL global grid. Uniform neighbour distance — better for\n                  flow, aggregation and movement analysis\n```\n> **⚠️ GOTCHA — geohash has an edge problem people trip over.** ⚠️ **Two points a metre\n> apart can have completely different prefixes if they straddle a cell boundary.**\n> **Proximity search must check neighbouring cells, not just the shared prefix.** **S2 and\n> H3 handle adjacency explicitly and are better for anything doing neighbourhood\n> queries.**\n>\n> ⚠️ **And hexagons aren't a gimmick**: **a hexagon's six neighbours are all equidistant\n> from its centre; a square's eight are not.** **That matters for anything modelling\n> spread, flow or movement.** **The trade is that hexagons don't subdivide perfectly, so\n> H3's hierarchy is approximate.**\n\n**⚠️ The two-phase query pattern** underlies essentially all spatial querying: **filter by\nbounding box using the index (cheap), then refine with exact geometry (expensive).**\n**Getting this wrong — doing exact tests first — is a common performance bug.**\n\n---\n\n## §5. Spatial Databases\n\n**PostGIS** is the reference implementation and the default choice.\n```sql\n-- ⚠️ Always index, always use && or ST_DWithin to hit it\nCREATE INDEX idx ON t USING GIST (geom);\n\nST_Intersects, ST_Contains, ST_Within, ST_DWithin   -- ⚠️ these use the index\nST_Distance, ST_Area, ST_Length, ST_Buffer\nST_Transform(geom, 3857)     -- ⚠️ reproject\nST_MakeValid(geom)           -- §2\n```\n> **⚠️ GOTCHA — `geometry` vs `geography` is the type decision that matters.**\n> ⚠️ **`geometry` is planar and fast; distances and areas are in the CRS's units, so\n> using it with EPSG:4326 gives you answers in DEGREES, which are meaningless as\n> distance.** **`geography` computes on the spheroid and returns metres, correctly, and is\n> slower with fewer functions.**\n> **⚠️ The pragmatic pattern: store `geometry` in a suitable projected CRS, or use\n> `geography` for global data where correctness beats speed, and cast where needed.**\n> **`ST_Distance` on 4326 geometry returning \"0.0043\" is the classic symptom.**\n\n**⚠️ `ST_DWithin` beats `ST_Distance(...) \u003C x`** — the former uses the index, the latter\ncomputes distance for every row first.\n**Others**: **SpatiaLite**, **DuckDB spatial** (⚠️ **increasingly the analytics choice, and\nit reads GeoParquet directly**), **BigQuery GIS**, **Snowflake**, **Elasticsearch geo**,\n**MongoDB 2dsphere**, **Apache Sedona** for distributed work.\n\n---\n\n## §6. Tiling\n\n**⚠️ Serve maps as small pre-cut squares, not one giant image.**\n**Slippy map scheme**: `z\u002Fx\u002Fy`, ⚠️ **doubling resolution per zoom level, in Web Mercator\n(§1.3 → `gis-coordinate-systems-data-models-and-formats`).** **Zoom 0 is one 256×256 tile of the world; zoom `z` has `4^z` tiles.**\n**⚠️ TMS flips the Y axis relative to XYZ\u002FGoogle convention — a small, recurring source of\nupside-down maps.**\n\n**Raster vs vector tiles:**\n- **Raster** — pre-rendered images. ⚠️ **Simple; styling is baked in, so restyling means\n  re-rendering everything.**\n- **Vector (MVT)** — ⚠️ **geometry plus attributes, styled on the client.** **Restyle\n  instantly, rotate and tilt, high-DPI for free, smaller.** **The default for new work.**\n\n**⚠️ Generation**: **tippecanoe** (⚠️ **the standard tool; it adaptively simplifies and\ndrops features per zoom to keep tiles small — that behaviour is a feature and it will\nsurprise you if you don't expect dropped features at low zoom**), **planetiler** for\nplanet-scale, **Martin** and **tegola** for dynamic serving from PostGIS.\n**⚠️ Overzooming** lets you serve zoom 14 tiles up to zoom 20 by scaling client-side —\n**which is why most vector basemaps stop generating at 14.**\n\n---\n\n## §7. Rendering\n\n| Library | ⚠️ Character |\n|---|---|\n| **MapLibre GL JS** | ⚠️ **The open fork of Mapbox GL JS. WebGL vector rendering; the default for new open work** |\n| **Leaflet** | ⚠️ **Simple, tiny, huge plugin ecosystem. Raster-first** |\n| **OpenLayers** | ⚠️ **Most feature-complete; handles projections properly — the pick when CRS matters** |\n| **deck.gl** | ⚠️ **Large-scale data visualization; GPU layers** |\n| **Cesium** | 3D globe, terrain, time |\n| **Mapbox GL JS** | Proprietary since v2 |\n| **QGIS** | ⚠️ **Desktop GIS; free, excellent, and the tool for actually looking at your data** |\n\n**⚠️ Style specification** (MapLibre\u002FMapbox style JSON) — declarative layers, sources,\npaint and layout properties, **data-driven styling and expressions.** ⚠️ **This is the\npiece that makes vector tiles worth it: the same tiles support unlimited cartography.**\n\n**⚠️ Performance**: **simplify by zoom, cluster points, use the GPU rather than DOM,\navoid re-creating sources, and watch that \"just add a GeoJSON layer\" with 100k features\nwill destroy your frame rate.** **Put it in a tile pipeline instead.**\n",{"name":5,"description":7},"develop","ae32736a1aabddabca5d2c96d665aa0ebc7d8700","src\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fgeospatial-software\u002Fskills\u002Fgis-indexing-databases-tiling-and-rendering",3,"https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey","https:\u002F\u002Fthe-vibey-project.github.io\u002Fvibey\u002F","https:\u002F\u002Fgithub.com\u002Fthe-vibey-project","https:\u002F\u002Fvibewithadam.matthewsteinberger.com","freedom for software engineers","2026-11-15 05:47:42",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add the-vibey-project\u002Fvibey --skill gis-indexing-databases-tiling-and-rendering",{"tool":40,"command":41},"bunx","bunx skills add the-vibey-project\u002Fvibey --skill gis-indexing-databases-tiling-and-rendering",{"tool":43,"command":44},"pnpm","pnpm dlx skills add the-vibey-project\u002Fvibey --skill gis-indexing-databases-tiling-and-rendering","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey\u002Fblob\u002Fdevelop\u002Fsrc\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fgeospatial-software\u002Fskills\u002Fgis-indexing-databases-tiling-and-rendering\u002FSKILL.md",true,[],[49,56,63,70,77,84],{"skillNo":50,"name":51,"nameZh":6,"description":52,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":53,"categories":54,"keywords":55,"publishedAt":19},"01M7AT1FQJAE1FQYAMDTF490Y4","white-paper-writing","Use when writing white papers, technical reports, policy documents, thought leadership pieces, or any long-form authoritative document. Triggers on requests to write, structure, outline, or review white papers, technical reports, position papers, policy briefs, or evidence-driven arguments. Also use for B2B content marketing strategy, technical documentation requiring authority, academic-style reports, or any document that must educate while persuading. Use when someone asks \"how should I structure this\" for a long-form document.","https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey\u002Fblob\u002Fdevelop\u002Fsrc\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fwriting-craft\u002Fskills\u002Fwhite-paper-writing\u002FSKILL.md",[],[],{"skillNo":57,"name":58,"nameZh":6,"description":59,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":60,"categories":61,"keywords":62,"publishedAt":19},"01M7AT16BJRJJKK2MASXRZS76G","prose-technical-mechanics","Use when editing or writing prose at a technical\u002Fmechanical level: choosing between Anglo-Saxon and Latinate diction, placing information in topic vs stress positions, writing periodic vs cumulative sentences, handling sentence rhythm, punctuation as logic, transitions, paragraph structure, or phonesthetics. Use when someone wants to understand WHY prose works or doesn't, not just surface-level style advice. Triggers on word choice, sentence structure, emphasis, rhythm, diction, or any deep writing mechanics question.","https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey\u002Fblob\u002Fdevelop\u002Fsrc\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fwriting-craft\u002Fskills\u002Fprose-technical-mechanics\u002FSKILL.md",[],[],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":19},"01M7AT0W9HT0ZZ9Y287NW99MR3","prose-mechanics","Use when writing, editing, or analyzing prose style; when trying to avoid generic AI-sounding writing; when applying specific prose styles such as journalistic, academic, narrative, KJV biblical, Hemingway plain, Latinate\u002FJamesian, Orwellian, Augustan, Victorian, Early Modern (Bacon, Browne, Milton), or free indirect discourse; or when coaching someone on writing voice and mechanics. Triggers on any request to improve, analyze, or write in a specific prose style, to fix \"AI-sounding\" writing, to make prose more vivid or concrete, to vary sentence rhythm, or to understand how a particular writer achieves their effects.","https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey\u002Fblob\u002Fdevelop\u002Fsrc\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fwriting-craft\u002Fskills\u002Fprose-mechanics\u002FSKILL.md",[],[],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":19},"01M7AT0KR635JX66X2X6F3E2CP","narrative-structure","Use when structuring stories, pitches, presentations, white papers, or any persuasive narrative; analyzing the hero's journey in fiction or non-fiction; applying StoryBrand for business communication; designing narrative arcs for thought leadership; or understanding Vogler, Snyder, Propp, or Campbell frameworks. Triggers on any narrative structure, storytelling, pitch structure, StoryBrand, hero's journey, three-act structure, Freytag, Save the Cat, narrative arc, or \"how should I structure this story\u002Fpitch\u002Fpresentation\" request.","https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey\u002Fblob\u002Fdevelop\u002Fsrc\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fwriting-craft\u002Fskills\u002Fnarrative-structure\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":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":19},"01M7AT0AKGW09NKKZDYBT8VRDE","legal-brief-writing","Use when writing legal briefs, motions, or any court filing; when analyzing judicial cognition and persuasion; when applying elite brief-writing techniques from Roberts, Clement, Kagan, Garner; or when structuring legal arguments for maximum persuasion. Also use for autistic\u002Fneurodivergent advocates who need to understand how their natural communication style maps to elite legal advocacy. Triggers on any legal writing, brief drafting, motion preparation, or legal argument structuring request.","https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey\u002Fblob\u002Fdevelop\u002Fsrc\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fwriting-craft\u002Fskills\u002Flegal-brief-writing\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":19},"01M7AT00VWPS4Q8B5VEMXX9NQT","journal-publishability-criteria","Use whenever a research paper, article or preprint is being written, revised, reviewed or published, and specifically before every publication of docs\u002Fpaper.md. Covers what legitimate journals actually gate on, in order of gating — the editor's desk screen (scope, novelty, package problems), what reviewers judge (methodological soundness, claims the evidence can carry, statistical and qualitative reporting), EQUATOR reporting guidelines, the ICMJE authorship criteria, COPE's view of text recycling, the near-universal generative-AI policy (no AI author, disclosure, author responsibility), TOP 2025 transparency standards, how to verify a journal is legitimate, submitting without an institution, and a pre-submission checklist. Triggers on requests to evaluate, review, prepare or submit a paper, to judge publishability, to write a declarations or data-availability section, to disclose AI use, or to check a journal.","https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey\u002Fblob\u002Fdevelop\u002Fsrc\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fwriting-craft\u002Fskills\u002Fjournal-publishability-criteria\u002FSKILL.md",[],[]]