[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7F27Q214435H67M8296E2B2":3,"skill-same:01M7F27Q214435H67M8296E2B2":71},{"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":26,"commitSha":27,"skillDirectory":28,"forksCount":14,"repositoryHtmlUrl":29,"repositoryHomepageUrl":30,"ownerHtmlUrl":31,"ownerBlogUrl":32,"ownerDescription":33,"updatedAt":34,"install":35,"resources":48},"01M7F27Q214435H67M8296E2B2","slipway-content",null,"Write or edit a page on a Slipway site, or translate one into another language, using the engine's front matter keys and directives, then check it with slipway check.","arminazimi\u002Fslipway","arminazimi","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F33401832?v=4","01M7F1ZTKSXGKQGEXS7MJAEB2N","Armin Azimi","01M7F26NCHMY6W6ZZT1YDRNGSV",2,"MIT","https:\u002F\u002Fgithub.com\u002Farminazimi\u002Fslipway\u002Fblob\u002Fmain\u002Fskills\u002Fslipway-content\u002FSKILL.md",[],[],"2026-11-16 10:05:34",false,"---\nname: slipway-content\ndescription: Write or edit a page on a Slipway site, or translate one into another language, using the engine's front matter keys and directives, then check it with slipway check.\nmetadata:\n  version: \"0.3.0\"\n---\n\n# Write pages on a Slipway site\n\nA Slipway site is a folder of Markdown files, each with an optional block of front matter. The engine builds every `.md` and `.html` file under the site's `source` folder into a page; the theme renders the title, the navigation, the table of contents, and the language switcher. You write the front matter and the words. If the site has an `AGENTS.md`, read it first; it wins where it differs from this Skill.\n\n## 1. Take a baseline\n\nRun the check once, before you change anything, and keep its output:\n\n```sh\nslipway check .\n```\n\nRun it from the site folder. Your edit is done when it adds no finding that names your file.\n\n`slipway` is the engine's command line. It is released with the engine (`engine.cli`). Until it is installed, no check can run: say so in your report and do not invent a result.\n\n## 2. Pick the file and its URL\n\n| You are writing | File | URL |\n| --- | --- | --- |\n| A page | any `.md` file under the source folder, such as `guide\u002Finstall.md` | the path: `\u002Fguide\u002Finstall\u002F` |\n| A folder's index | `index.md`, or `README.md` when the folder has no `index.md` | the folder: `\u002Fguide\u002F` |\n| A page in another language | a file under that language's prefix folder, such as `fa\u002Finstall.md` | the prefix and the path: `\u002Ffa\u002Finstall\u002F` |\n| A page that moves or has a custom address | any file, with `permalink` | the `permalink` value |\n\nFolders whose names start with `.` or `_` are skipped, unless `slipway.yml` lists them under `include`. Files in `node_modules`, the output folder, and `slipway.yml` are never pages.\n\nDo not rename or move a published page to change its title. Set `title`. A page's address is its path or its `permalink`, and links to it would break if you change it. To change an address on purpose, set `permalink` and add a `redirect_from` entry for the old one.\n\nSet `published: false` to keep a draft out of the build. Do not create `_posts\u002F` folders: posts are not part of the engine.\n\n## 3. Fill the front matter\n\nEvery key the engine reads, its type, and its allowed values are in [reference\u002Ffront-matter.md](reference\u002Ffront-matter.md). Use only keys it lists.\n\n- `title` is the page heading. Without it, the first `h1` is used.\n- `description`: one sentence for the meta description, `llms.txt`, and search.\n- `order`: a number that sorts the page among its siblings in navigation built from folders.\n- `layout` is usually left out. The folder's `defaults` in `slipway.yml` or the theme's default layout applies. Set it only when the theme documents the layout name.\n- `permalink` starts with `\u002F`. Leave it out unless the address must differ from the path.\n- `redirect_from` lists old addresses (a string or a list) that now redirect to this page.\n- `status` is one of `experimental`, `beta`, `deprecated`, `proposed`, `accepted`, `rejected`, or `superseded`.\n- `agent` tells agents how to edit the page: `edit: false` for a generated page, `source` for the file to edit instead, and `notes` for one short instruction.\n- Quote a value that contains `: ` or starts with a character YAML treats specially (`[`, `{`, `*`, `&`, `!`, `#`, `|`, `>`, `@`, or a backtick).\n\nTwo keys are deprecated aliases: `nav_order` is `order`, and `direction` is `dir`. Do not write them in new content; the engine warns about them.\n\n## 4. Write the body\n\n- Plain Markdown. The title is the page heading, so start sections at `##` and never add a second `#` heading.\n- Keep heading levels in order (`##`, then `###`), so the table of contents finds every section.\n- Link to a page by its URL path, such as `[Install](\u002Fdocs\u002Finstall\u002F)`. Check the link with `slipway check`.\n- Give each image alt text: `![A chart of build times](\u002Fassets\u002Fbuild-times.png)`.\n- Give every code block a language (` ```yaml `), so it highlights and reads left to right on a right-to-left page.\n\n### Directives\n\nThe engine turns these into theme components. A name the theme does not ship renders as an unknown-component warning, so use only the names below.\n\n| Write | Component | Options |\n| --- | --- | --- |\n| `:::callout{type=tip}` … `:::` | `callout` | `type`: `note` (default), `tip`, `important`, `warning`, `caution`. `title=\"…\"` replaces the default heading. |\n| `> [!WARNING]` followed by a quote | `callout` | GitHub alert: `NOTE`, `TIP`, `IMPORTANT`, `WARNING`, `CAUTION`. |\n| `:::details{summary=\"…\"}` … `:::` | `details` | `summary` is the visible label. Add `open` to start expanded. |\n| `:::steps` … `:::` | `steps` | The body is one ordered list. |\n| `:::file-tree{label=\"…\"}` … `:::` | `file-tree` | The body is a nested list. A name ending in `\u002F` is a folder; text after ` # ` is a note on that row; `**name**` highlights it. |\n| `:badge[New]{variant=tip}` | `badge` | Inline. `variant`: `note` (default), `tip`, `important`, `warning`, `caution`. |\n| `::badge{label=new}` | `badge` | Block form, with `label` as the text. |\n\nExample, from [examples\u002Fdoc-page.md](examples\u002Fdoc-page.md):\n\n```markdown\n:::callout{type=tip}\nThe binary has no dependencies. Copying it to another machine is enough.\n:::\n```\n\nUse a callout for a note the reader must not miss, not for decoration.\n\n[examples\u002Fdoc-page.md](examples\u002Fdoc-page.md) is a template for a doc page: its first comment says where the file goes.\n\n## 5. Add a translation\n\n1. The language must be in `languages` in `slipway.yml`, with a `code`, a `name`, and a `prefix` such as `\u002Ffa`. If it is missing, ask the owner before you add it: it changes every page's language switcher.\n2. Give the original page a `translation_key` (such as `install`) if it has none, and a `lang` if it does not inherit one from its folder. The switcher links a page and its translations by `translation_key`.\n3. Give the translation the same `translation_key`, and `lang` set to its language code. Its URL comes from its path under the prefix folder: `fa\u002Finstall.md` becomes `\u002Ffa\u002Finstall\u002F`.\n4. Translate `title`, `description`, and the body. Keep the `translation_key`, the code, the commands, the file names, and the URLs as they are.\n5. Do not set `dir` on a translation. The direction comes from `lang`: `fa`, `ar`, `he`, and `ur` are right to left.\n6. In Persian text, use Persian `ی` and `ک` (not the Arabic `ي` and `ك`), a zero-width non-joiner in words such as `می‌شود`, and Persian punctuation (`،` and `؟`). Put commands, file names, and code in backticks: they stay left to right inside the sentence.\n\nChange `translation_key` on every page that shares it, or on none. Changing it on one translation only breaks the link.\n\n## 6. Check the edit\n\nFrom the site folder:\n\n```sh\nslipway check .\n```\n\nEach finding is printed with its file and line. Fix it at that line and run the check again. To get a machine-readable report, add `--format json` or `--format sarif`.\n\nBuild the site before you finish a change to navigation, languages, or directives:\n\n```sh\nslipway build . --out dist\n```\n\nRead every error and warning and fix it at the file it names. Then compare the result with your baseline: a finding that names your file is yours to fix.\n\n## Never\n\n- Never invent a front matter key that [reference\u002Ffront-matter.md](reference\u002Ffront-matter.md) does not list.\n- Never write a second `#` heading in the body.\n- Never edit the output folder (`dist\u002F` or the folder you passed to `--out`); the build replaces it.\n- Never create `_posts\u002F` pages. Posts are not part of the engine.\n- Never rename or move a published page to change its title; set `title`.\n- Never change `translation_key` on one translation only.\n- Never change theme layouts or components to change how one page looks.\n","# Write pages on a Slipway site\n\nA Slipway site is a folder of Markdown files, each with an optional block of front matter. The engine builds every `.md` and `.html` file under the site's `source` folder into a page; the theme renders the title, the navigation, the table of contents, and the language switcher. You write the front matter and the words. If the site has an `AGENTS.md`, read it first; it wins where it differs from this Skill.\n\n## 1. Take a baseline\n\nRun the check once, before you change anything, and keep its output:\n\n```sh\nslipway check .\n```\n\nRun it from the site folder. Your edit is done when it adds no finding that names your file.\n\n`slipway` is the engine's command line. It is released with the engine (`engine.cli`). Until it is installed, no check can run: say so in your report and do not invent a result.\n\n## 2. Pick the file and its URL\n\n| You are writing | File | URL |\n| --- | --- | --- |\n| A page | any `.md` file under the source folder, such as `guide\u002Finstall.md` | the path: `\u002Fguide\u002Finstall\u002F` |\n| A folder's index | `index.md`, or `README.md` when the folder has no `index.md` | the folder: `\u002Fguide\u002F` |\n| A page in another language | a file under that language's prefix folder, such as `fa\u002Finstall.md` | the prefix and the path: `\u002Ffa\u002Finstall\u002F` |\n| A page that moves or has a custom address | any file, with `permalink` | the `permalink` value |\n\nFolders whose names start with `.` or `_` are skipped, unless `slipway.yml` lists them under `include`. Files in `node_modules`, the output folder, and `slipway.yml` are never pages.\n\nDo not rename or move a published page to change its title. Set `title`. A page's address is its path or its `permalink`, and links to it would break if you change it. To change an address on purpose, set `permalink` and add a `redirect_from` entry for the old one.\n\nSet `published: false` to keep a draft out of the build. Do not create `_posts\u002F` folders: posts are not part of the engine.\n\n## 3. Fill the front matter\n\nEvery key the engine reads, its type, and its allowed values are in [reference\u002Ffront-matter.md](reference\u002Ffront-matter.md). Use only keys it lists.\n\n- `title` is the page heading. Without it, the first `h1` is used.\n- `description`: one sentence for the meta description, `llms.txt`, and search.\n- `order`: a number that sorts the page among its siblings in navigation built from folders.\n- `layout` is usually left out. The folder's `defaults` in `slipway.yml` or the theme's default layout applies. Set it only when the theme documents the layout name.\n- `permalink` starts with `\u002F`. Leave it out unless the address must differ from the path.\n- `redirect_from` lists old addresses (a string or a list) that now redirect to this page.\n- `status` is one of `experimental`, `beta`, `deprecated`, `proposed`, `accepted`, `rejected`, or `superseded`.\n- `agent` tells agents how to edit the page: `edit: false` for a generated page, `source` for the file to edit instead, and `notes` for one short instruction.\n- Quote a value that contains `: ` or starts with a character YAML treats specially (`[`, `{`, `*`, `&`, `!`, `#`, `|`, `>`, `@`, or a backtick).\n\nTwo keys are deprecated aliases: `nav_order` is `order`, and `direction` is `dir`. Do not write them in new content; the engine warns about them.\n\n## 4. Write the body\n\n- Plain Markdown. The title is the page heading, so start sections at `##` and never add a second `#` heading.\n- Keep heading levels in order (`##`, then `###`), so the table of contents finds every section.\n- Link to a page by its URL path, such as `[Install](\u002Fdocs\u002Finstall\u002F)`. Check the link with `slipway check`.\n- Give each image alt text: `![A chart of build times](\u002Fassets\u002Fbuild-times.png)`.\n- Give every code block a language (` ```yaml `), so it highlights and reads left to right on a right-to-left page.\n\n### Directives\n\nThe engine turns these into theme components. A name the theme does not ship renders as an unknown-component warning, so use only the names below.\n\n| Write | Component | Options |\n| --- | --- | --- |\n| `:::callout{type=tip}` … `:::` | `callout` | `type`: `note` (default), `tip`, `important`, `warning`, `caution`. `title=\"…\"` replaces the default heading. |\n| `> [!WARNING]` followed by a quote | `callout` | GitHub alert: `NOTE`, `TIP`, `IMPORTANT`, `WARNING`, `CAUTION`. |\n| `:::details{summary=\"…\"}` … `:::` | `details` | `summary` is the visible label. Add `open` to start expanded. |\n| `:::steps` … `:::` | `steps` | The body is one ordered list. |\n| `:::file-tree{label=\"…\"}` … `:::` | `file-tree` | The body is a nested list. A name ending in `\u002F` is a folder; text after ` # ` is a note on that row; `**name**` highlights it. |\n| `:badge[New]{variant=tip}` | `badge` | Inline. `variant`: `note` (default), `tip`, `important`, `warning`, `caution`. |\n| `::badge{label=new}` | `badge` | Block form, with `label` as the text. |\n\nExample, from [examples\u002Fdoc-page.md](examples\u002Fdoc-page.md):\n\n```markdown\n:::callout{type=tip}\nThe binary has no dependencies. Copying it to another machine is enough.\n:::\n```\n\nUse a callout for a note the reader must not miss, not for decoration.\n\n[examples\u002Fdoc-page.md](examples\u002Fdoc-page.md) is a template for a doc page: its first comment says where the file goes.\n\n## 5. Add a translation\n\n1. The language must be in `languages` in `slipway.yml`, with a `code`, a `name`, and a `prefix` such as `\u002Ffa`. If it is missing, ask the owner before you add it: it changes every page's language switcher.\n2. Give the original page a `translation_key` (such as `install`) if it has none, and a `lang` if it does not inherit one from its folder. The switcher links a page and its translations by `translation_key`.\n3. Give the translation the same `translation_key`, and `lang` set to its language code. Its URL comes from its path under the prefix folder: `fa\u002Finstall.md` becomes `\u002Ffa\u002Finstall\u002F`.\n4. Translate `title`, `description`, and the body. Keep the `translation_key`, the code, the commands, the file names, and the URLs as they are.\n5. Do not set `dir` on a translation. The direction comes from `lang`: `fa`, `ar`, `he`, and `ur` are right to left.\n6. In Persian text, use Persian `ی` and `ک` (not the Arabic `ي` and `ك`), a zero-width non-joiner in words such as `می‌شود`, and Persian punctuation (`،` and `؟`). Put commands, file names, and code in backticks: they stay left to right inside the sentence.\n\nChange `translation_key` on every page that shares it, or on none. Changing it on one translation only breaks the link.\n\n## 6. Check the edit\n\nFrom the site folder:\n\n```sh\nslipway check .\n```\n\nEach finding is printed with its file and line. Fix it at that line and run the check again. To get a machine-readable report, add `--format json` or `--format sarif`.\n\nBuild the site before you finish a change to navigation, languages, or directives:\n\n```sh\nslipway build . --out dist\n```\n\nRead every error and warning and fix it at the file it names. Then compare the result with your baseline: a finding that names your file is yours to fix.\n\n## Never\n\n- Never invent a front matter key that [reference\u002Ffront-matter.md](reference\u002Ffront-matter.md) does not list.\n- Never write a second `#` heading in the body.\n- Never edit the output folder (`dist\u002F` or the folder you passed to `--out`); the build replaces it.\n- Never create `_posts\u002F` pages. Posts are not part of the engine.\n- Never rename or move a published page to change its title; set `title`.\n- Never change `translation_key` on one translation only.\n- Never change theme layouts or components to change how one page looks.\n",{"name":5,"metadata":24,"description":7},{"version":25},"0.3.0","main","4ace9213edc3d1c6f4c08a1bc4f2f3aebcd70401","skills\u002Fslipway-content","https:\u002F\u002Fgithub.com\u002Farminazimi\u002Fslipway","https:\u002F\u002Farminazimi.github.io\u002Fslipway\u002F","https:\u002F\u002Fgithub.com\u002Farminazimi","https:\u002F\u002Fvelella.sh","I make codebases confess what they’ve been hiding.","2026-11-11 00:40:10",{"source":8,"skillName":5,"commands":36,"prompt":46,"zipAvailable":47},[37,40,43],{"tool":38,"command":39},"npx","npx skills add arminazimi\u002Fslipway --skill slipway-content",{"tool":41,"command":42},"bunx","bunx skills add arminazimi\u002Fslipway --skill slipway-content",{"tool":44,"command":45},"pnpm","pnpm dlx skills add arminazimi\u002Fslipway --skill slipway-content","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Farminazimi\u002Fslipway\u002Fblob\u002Fmain\u002Fskills\u002Fslipway-content\u002FSKILL.md",true,[49,55,59,63,67],{"path":50,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":53,"sourceHtmlUrl":54},"examples\u002Fdoc-page.md","REFERENCE","参考文档",575,"https:\u002F\u002Fgithub.com\u002Farminazimi\u002Fslipway\u002Fblob\u002Fmain\u002Fskills\u002Fslipway-content\u002Fexamples\u002Fdoc-page.md",{"path":56,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":57,"sourceHtmlUrl":58},"examples\u002Fpost-fa.md",902,"https:\u002F\u002Fgithub.com\u002Farminazimi\u002Fslipway\u002Fblob\u002Fmain\u002Fskills\u002Fslipway-content\u002Fexamples\u002Fpost-fa.md",{"path":60,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":61,"sourceHtmlUrl":62},"examples\u002Fpost.md",580,"https:\u002F\u002Fgithub.com\u002Farminazimi\u002Fslipway\u002Fblob\u002Fmain\u002Fskills\u002Fslipway-content\u002Fexamples\u002Fpost.md",{"path":64,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":65,"sourceHtmlUrl":66},"reference\u002Ffront-matter.md",3207,"https:\u002F\u002Fgithub.com\u002Farminazimi\u002Fslipway\u002Fblob\u002Fmain\u002Fskills\u002Fslipway-content\u002Freference\u002Ffront-matter.md",{"path":68,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":69,"sourceHtmlUrl":70},"reference\u002Ftranslate-page.md",2130,"https:\u002F\u002Fgithub.com\u002Farminazimi\u002Fslipway\u002Fblob\u002Fmain\u002Fskills\u002Fslipway-content\u002Freference\u002Ftranslate-page.md",[72,79,86,93,100,107],{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":19},"01M7F28EHG0XQBYM34ECQ1YAWP","slipway-translate","Add a language to a Slipway site, translate pages, and keep every translation linked through lang and translation_key, then check it with slipway check.","https:\u002F\u002Fgithub.com\u002Farminazimi\u002Fslipway\u002Fblob\u002Fmain\u002Fskills\u002Fslipway-translate\u002FSKILL.md",[],[],{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":19},"01M7F28A1J1XNA5Z5P333SM3MT","slipway-site","Create a Slipway docs site, or customize an existing one through slipway.yml, navigation, languages, redirects, and theme options, then check it with slipway check.","https:\u002F\u002Fgithub.com\u002Farminazimi\u002Fslipway\u002Fblob\u002Fmain\u002Fskills\u002Fslipway-site\u002FSKILL.md",[],[],{"skillNo":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":19},"01M7F286GG3M7GQ2Q4D7V0J065","slipway-release-notes","Write a changelog entry and a release page from merged pull requests, for a site built with Slipway or for Slipway itself.","https:\u002F\u002Fgithub.com\u002Farminazimi\u002Fslipway\u002Fblob\u002Fmain\u002Fskills\u002Fslipway-release-notes\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":6,"sourceHtmlUrl":97,"categories":98,"keywords":99,"publishedAt":19},"01M7F2820BADMX1S5SQA09TCC2","slipway-doctor","Check a static site with slipway doctor after you edit it, read the findings, and fix them until the site reaches its conformance level. Use for any Slipway site or any site that follows the agent-editable site spec.","https:\u002F\u002Fgithub.com\u002Farminazimi\u002Fslipway\u002Fblob\u002Fmain\u002Fskills\u002Fslipway-doctor\u002FSKILL.md",[],[],{"skillNo":101,"name":102,"nameZh":6,"description":103,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":104,"categories":105,"keywords":106,"publishedAt":19},"01M7F27YCP18CYDNKSZHZFPMHJ","slipway-design","Restyle a Slipway site with design tokens and a preset, add CSS through the override slots, and keep light and dark contrast passing.","https:\u002F\u002Fgithub.com\u002Farminazimi\u002Fslipway\u002Fblob\u002Fmain\u002Fskills\u002Fslipway-design\u002FSKILL.md",[],[],{"skillNo":108,"name":109,"nameZh":6,"description":110,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":111,"categories":112,"keywords":113,"publishedAt":19},"01M7F27TZM9YAAV5NZPAFBK233","slipway-deploy","Publish a Slipway site to GitHub Pages with the deploy Action, set a custom domain, and fix the common build, base path, theme, and permission failures.","https:\u002F\u002Fgithub.com\u002Farminazimi\u002Fslipway\u002Fblob\u002Fmain\u002Fskills\u002Fslipway-deploy\u002FSKILL.md",[],[]]