[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6BYBJ668G2TN91YZ5Q8CK7W":3,"skill-same:01M6BYBJ668G2TN91YZ5Q8CK7W":113},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":15,"sourceHtmlUrl":16,"categories":17,"keywords":34,"publishedAt":53,"linkOnly":54,"markdownContent":55,"markdownBody":56,"frontMatter":57,"refName":58,"commitSha":59,"skillDirectory":60,"forksCount":13,"repositoryHtmlUrl":61,"repositoryHomepageUrl":62,"ownerHtmlUrl":63,"ownerBlogUrl":64,"ownerDescription":65,"updatedAt":66,"install":67,"resources":80},"01M6BYBJ668G2TN91YZ5Q8CK7W","cratis-discoverability",null,"Check Cratis content before publishing for search and AI answers without sacrificing readability. Use when reviewing discoverability, SEO, AEO or GEO; writing fact blocks or download claims; editing package\u002Frepo metadata; checking docs titles, descriptions or LLM export budgets; or reviewing founder\u002Fcompany JSON-LD and member profile indexing. Not for page voice and structure (cratis-documentation-writing), llms.txt design (cratis-llm-friendly-documentation), distribution plans (cratis-developer-marketing) or length decisions (cratis-content-length).","Cratis\u002FDockerfiles","Cratis","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F16456213?v=4","01M6BXRH290K4C8RS4PTKK3HXQ","01M6BYBCFVMKSVX02FYW65R34V",0,"MIT","https:\u002F\u002Fgithub.com\u002FCratis\u002FDockerfiles\u002Fblob\u002Fmain\u002F.cratis\u002Fai\u002Fskills\u002Fcratis-discoverability\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FCratis\u002FDockerfiles\u002Fblob\u002Fmain\u002F.cratis\u002Fai\u002Fskills\u002Fcratis-discoverability\u002FSKILL.md",[18,23,28,31],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000019","营销推广","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",{"categoryNo":29,"categoryName":30,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000035","市场营销",{"categoryNo":32,"categoryName":33,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000036","内容创作者",[35,36,37,38,39,40,41,42,43,44,45,46,47,48,49,50,51,52],"cratis discoverability","cratis","developer","page","download","json","voice","marketing","seo","design","metadata","content","search","package","documentation","llms","docs","writing","2026-11-10 10:12:30",false,"---\nname: cratis-discoverability\ndescription: Check Cratis content before publishing for search and AI answers without sacrificing readability. Use when reviewing discoverability, SEO, AEO or GEO; writing fact blocks or download claims; editing package\u002Frepo metadata; checking docs titles, descriptions or LLM export budgets; or reviewing founder\u002Fcompany JSON-LD and member profile indexing. Not for page voice and structure (cratis-documentation-writing), llms.txt design (cratis-llm-friendly-documentation), distribution plans (cratis-developer-marketing) or length decisions (cratis-content-length).\nlicense: MIT\n---\n\u003C!-- cratis-ai-managed: skills\u002Fcratis-discoverability\u002FSKILL.md -->\n\n# Discoverability before you publish\n\nDiscoverability is a property of good content: a clear definition, an honest title, one name per\nthing and working links. The always-on rule is [discoverability.md](..\u002F..\u002Frules\u002Fdiscoverability.md);\nthis skill is the procedure to run on the finished draft. If a fix makes the page worse to read,\ndrop the fix and say so.\n\n## Procedure\n\n1. Name the content type: docs page, blog post, landing page, README, package\u002Frepo metadata or member profile.\n2. Name the reader's one job and, for docs, the page type (tutorial, how-to, reference, explanation).\n3. Apply the checks for that type below, including facts, adoption claims and privacy without waiting for a separate request. Fix the draft; do not annotate it.\n4. For a built site, run the checker and fix errors; warnings are judgment calls to report.\n5. Report what was changed, what was left alone and why.\n\nRead `references\u002Fpage-checklist.md` when checking a page, including docs lint baselines and LLM export budgets.\n\n## Checks by content type\n\n- **Docs page.** The `description` is written by hand as one self-contained\n  definition or outcome sentence. Tutorials, getting-started pages and explanations follow\n  `writing-cratis-docs` (scenario first); the definition lives in the `description`, and one\n  definition sentence may follow the opening scenario where it reads naturally. `writing-cratis-docs`\n  wins on voice and structure. Product index pages open with the definition sentence.\n  Reference pages stay terse: title is the exact name plus its product, no question headings, no\n  intro. Titles are unique across the site and name the product (\"Chronicle projections\"). Keep\n  description and duplicate-title lint baselines at 0; never raise a baseline to pass. Check\n  rendered titles and measure `llms.txt` \u002F `llms-small.txt` bytes against the site budgets.\n- **Blog post.** The title states the topic in the words a reader would search. The intro gives the\n  conclusion in two sentences. Show the named author and date, add `lastUpdated` only for real\n  changes, link the owning docs pages with `https:\u002F\u002Fwww.cratis.io\u002F...`, keep `description` apart\n  from the card `excerpt`.\n- **Landing page.** One primary term in the title, the `\u003Ch1>` or the first paragraph, and a\n  one-sentence definition above the fold. Brand lines stay; pair them with a category term in the\n  title and description. Respect the claim gate in `BRAND.md`, `MESSAGING.md` and `SITE.md`.\n- **README.** The H1 may be the product name (\"Cratis \u003CProduct>\"). The first sentence defines the product in 15-35 plain\n  nouns, with no logo-only or metaphor opener. Links are absolute; link the docs page.\n- **Package metadata.** One sentence naming what the package is and which Cratis product it belongs\n  to, identical to the README opener. `PackageProjectUrl` and `homepage` point at the docs page, not\n  only at GitHub. Read `references\u002Fpackage-metadata.md` when editing package fields, GitHub About,\n  Docker Hub descriptions, analyzer help links, template messages or README footers. Check these\n  surfaces together; Authors and Company are `Cratis`.\n\n## Fact blocks and adoption claims\n\nFor each entity page, assemble one sourced \"at a glance\" block from verifiable facts, with dates\nfor counts. Read `references\u002Ffacts-and-adoption.md` when selecting facts or calculating downloads:\nidentify entry packages and continuation predecessors, exclude sub-packages and overlapping\nshared dependencies, round down to a stated threshold, and publish the month and registries.\nDownloads are never users or customers. Omit unsupported claims instead of inventing customers,\nuser counts, benchmarks, certifications, prices or competitor comparisons. Keep shared guidance\ngeneric; do not copy private integration names, legal entity details or factual counts into it.\n\n## Names\n\nUse the canonical names, one per concept, and the first-mention rule. Read\n`references\u002Fentities.md` when naming a product, writing a definition sentence or filling `sameAs`.\nDo not invent a name, URL, maturity word or claim that the references do not state.\n\n## Structured data\n\nDescribe only what is visible on the page, one `@graph` per page, stable `@id`s. Add no `HowTo` and\nno new `FAQPage`. Read `references\u002Fstructured-data.md` for the patterns and what each page type\ngets. Use only public, owner-approved founder\u002Fcompany facts. Do not name other people in\nstructured data; never add personal data or `Person` entities for community members. Member\nprofiles are `noindex`; check profile and CV routes, rendered robots directives and JSON-LD.\nWithout approved public founder facts, reference the organization by `@id` instead.\n\n## Checking a built site\n\nFor a built static site (Astro `dist\u002F` or a plain-HTML repository root), run with Node.js:\n`node \u003Cskill-directory>\u002Fscripts\u002Fverify-discoverability.mjs --root \u003Cdir> --site \u003Chttps:\u002F\u002Fhost>`.\nIt reports `\u003Chtml lang>`, title, description, canonical host, `\u003Ch1>` count, JSON-LD parse errors,\n`robots.txt`, the sitemap and `llms.txt` structure. Errors exit 1; warnings do not. Pass\n`--warn-only` to downgrade errors and `--require-llms` where the site ships `llms.txt`.\nRead `scripts\u002Fverify-discoverability.mjs` only when changing the checker.\n\n## Pitfalls\n\n- Question headings everywhere: use them only where they read naturally (concept pages, FAQs,\n  comparisons, blog), never on reference pages or tutorial steps.\n- Padding to a word count: there is no minimum length; a complete page is done.\n- Apex `https:\u002F\u002Fcratis.io\u002F` links: the docs host is `https:\u002F\u002Fwww.cratis.io`.\n- A description that repeats the title or a sibling page's description.\n","\u003C!-- cratis-ai-managed: skills\u002Fcratis-discoverability\u002FSKILL.md -->\n\n# Discoverability before you publish\n\nDiscoverability is a property of good content: a clear definition, an honest title, one name per\nthing and working links. The always-on rule is [discoverability.md](..\u002F..\u002Frules\u002Fdiscoverability.md);\nthis skill is the procedure to run on the finished draft. If a fix makes the page worse to read,\ndrop the fix and say so.\n\n## Procedure\n\n1. Name the content type: docs page, blog post, landing page, README, package\u002Frepo metadata or member profile.\n2. Name the reader's one job and, for docs, the page type (tutorial, how-to, reference, explanation).\n3. Apply the checks for that type below, including facts, adoption claims and privacy without waiting for a separate request. Fix the draft; do not annotate it.\n4. For a built site, run the checker and fix errors; warnings are judgment calls to report.\n5. Report what was changed, what was left alone and why.\n\nRead `references\u002Fpage-checklist.md` when checking a page, including docs lint baselines and LLM export budgets.\n\n## Checks by content type\n\n- **Docs page.** The `description` is written by hand as one self-contained\n  definition or outcome sentence. Tutorials, getting-started pages and explanations follow\n  `writing-cratis-docs` (scenario first); the definition lives in the `description`, and one\n  definition sentence may follow the opening scenario where it reads naturally. `writing-cratis-docs`\n  wins on voice and structure. Product index pages open with the definition sentence.\n  Reference pages stay terse: title is the exact name plus its product, no question headings, no\n  intro. Titles are unique across the site and name the product (\"Chronicle projections\"). Keep\n  description and duplicate-title lint baselines at 0; never raise a baseline to pass. Check\n  rendered titles and measure `llms.txt` \u002F `llms-small.txt` bytes against the site budgets.\n- **Blog post.** The title states the topic in the words a reader would search. The intro gives the\n  conclusion in two sentences. Show the named author and date, add `lastUpdated` only for real\n  changes, link the owning docs pages with `https:\u002F\u002Fwww.cratis.io\u002F...`, keep `description` apart\n  from the card `excerpt`.\n- **Landing page.** One primary term in the title, the `\u003Ch1>` or the first paragraph, and a\n  one-sentence definition above the fold. Brand lines stay; pair them with a category term in the\n  title and description. Respect the claim gate in `BRAND.md`, `MESSAGING.md` and `SITE.md`.\n- **README.** The H1 may be the product name (\"Cratis \u003CProduct>\"). The first sentence defines the product in 15-35 plain\n  nouns, with no logo-only or metaphor opener. Links are absolute; link the docs page.\n- **Package metadata.** One sentence naming what the package is and which Cratis product it belongs\n  to, identical to the README opener. `PackageProjectUrl` and `homepage` point at the docs page, not\n  only at GitHub. Read `references\u002Fpackage-metadata.md` when editing package fields, GitHub About,\n  Docker Hub descriptions, analyzer help links, template messages or README footers. Check these\n  surfaces together; Authors and Company are `Cratis`.\n\n## Fact blocks and adoption claims\n\nFor each entity page, assemble one sourced \"at a glance\" block from verifiable facts, with dates\nfor counts. Read `references\u002Ffacts-and-adoption.md` when selecting facts or calculating downloads:\nidentify entry packages and continuation predecessors, exclude sub-packages and overlapping\nshared dependencies, round down to a stated threshold, and publish the month and registries.\nDownloads are never users or customers. Omit unsupported claims instead of inventing customers,\nuser counts, benchmarks, certifications, prices or competitor comparisons. Keep shared guidance\ngeneric; do not copy private integration names, legal entity details or factual counts into it.\n\n## Names\n\nUse the canonical names, one per concept, and the first-mention rule. Read\n`references\u002Fentities.md` when naming a product, writing a definition sentence or filling `sameAs`.\nDo not invent a name, URL, maturity word or claim that the references do not state.\n\n## Structured data\n\nDescribe only what is visible on the page, one `@graph` per page, stable `@id`s. Add no `HowTo` and\nno new `FAQPage`. Read `references\u002Fstructured-data.md` for the patterns and what each page type\ngets. Use only public, owner-approved founder\u002Fcompany facts. Do not name other people in\nstructured data; never add personal data or `Person` entities for community members. Member\nprofiles are `noindex`; check profile and CV routes, rendered robots directives and JSON-LD.\nWithout approved public founder facts, reference the organization by `@id` instead.\n\n## Checking a built site\n\nFor a built static site (Astro `dist\u002F` or a plain-HTML repository root), run with Node.js:\n`node \u003Cskill-directory>\u002Fscripts\u002Fverify-discoverability.mjs --root \u003Cdir> --site \u003Chttps:\u002F\u002Fhost>`.\nIt reports `\u003Chtml lang>`, title, description, canonical host, `\u003Ch1>` count, JSON-LD parse errors,\n`robots.txt`, the sitemap and `llms.txt` structure. Errors exit 1; warnings do not. Pass\n`--warn-only` to downgrade errors and `--require-llms` where the site ships `llms.txt`.\nRead `scripts\u002Fverify-discoverability.mjs` only when changing the checker.\n\n## Pitfalls\n\n- Question headings everywhere: use them only where they read naturally (concept pages, FAQs,\n  comparisons, blog), never on reference pages or tutorial steps.\n- Padding to a word count: there is no minimum length; a complete page is done.\n- Apex `https:\u002F\u002Fcratis.io\u002F` links: the docs host is `https:\u002F\u002Fwww.cratis.io`.\n- A description that repeats the title or a sibling page's description.\n",{"name":5,"license":14,"description":7},"main","adc3520af8e347e0f66cef6775d9eb85e409a1fc",".cratis\u002Fai\u002Fskills\u002Fcratis-discoverability","https:\u002F\u002Fgithub.com\u002FCratis\u002FDockerfiles","https:\u002F\u002Fwww.cratis.io\u002F","https:\u002F\u002Fgithub.com\u002FCratis","https:\u002F\u002Fwww.cratis.io","Open-source (MIT) event sourcing and CQRS for .NET and beyond: Chronicle, Arc, Components and Screenplay.","2026-11-14 06:36:08",{"source":8,"skillName":5,"commands":68,"prompt":78,"zipAvailable":79},[69,72,75],{"tool":70,"command":71},"npx","npx skills add Cratis\u002FDockerfiles --skill cratis-discoverability",{"tool":73,"command":74},"bunx","bunx skills add Cratis\u002FDockerfiles --skill cratis-discoverability",{"tool":76,"command":77},"pnpm","pnpm dlx skills add Cratis\u002FDockerfiles --skill cratis-discoverability","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FCratis\u002FDockerfiles\u002Fblob\u002Fmain\u002F.cratis\u002Fai\u002Fskills\u002Fcratis-discoverability\u002FSKILL.md",true,[81,85,91,95,99,103,107],{"path":82,"resourceType":82,"resourceTypeDesc":83,"sizeBytes":84,"sourceHtmlUrl":15},"LICENSE","许可证",201,{"path":86,"resourceType":87,"resourceTypeDesc":88,"sizeBytes":89,"sourceHtmlUrl":90},"references\u002Fentities.md","REFERENCE","参考文档",4434,"https:\u002F\u002Fgithub.com\u002FCratis\u002FDockerfiles\u002Fblob\u002Fmain\u002F.cratis\u002Fai\u002Fskills\u002Fcratis-discoverability\u002Freferences\u002Fentities.md",{"path":92,"resourceType":87,"resourceTypeDesc":88,"sizeBytes":93,"sourceHtmlUrl":94},"references\u002Ffacts-and-adoption.md",3577,"https:\u002F\u002Fgithub.com\u002FCratis\u002FDockerfiles\u002Fblob\u002Fmain\u002F.cratis\u002Fai\u002Fskills\u002Fcratis-discoverability\u002Freferences\u002Ffacts-and-adoption.md",{"path":96,"resourceType":87,"resourceTypeDesc":88,"sizeBytes":97,"sourceHtmlUrl":98},"references\u002Fpackage-metadata.md",3742,"https:\u002F\u002Fgithub.com\u002FCratis\u002FDockerfiles\u002Fblob\u002Fmain\u002F.cratis\u002Fai\u002Fskills\u002Fcratis-discoverability\u002Freferences\u002Fpackage-metadata.md",{"path":100,"resourceType":87,"resourceTypeDesc":88,"sizeBytes":101,"sourceHtmlUrl":102},"references\u002Fpage-checklist.md",5857,"https:\u002F\u002Fgithub.com\u002FCratis\u002FDockerfiles\u002Fblob\u002Fmain\u002F.cratis\u002Fai\u002Fskills\u002Fcratis-discoverability\u002Freferences\u002Fpage-checklist.md",{"path":104,"resourceType":87,"resourceTypeDesc":88,"sizeBytes":105,"sourceHtmlUrl":106},"references\u002Fstructured-data.md",3385,"https:\u002F\u002Fgithub.com\u002FCratis\u002FDockerfiles\u002Fblob\u002Fmain\u002F.cratis\u002Fai\u002Fskills\u002Fcratis-discoverability\u002Freferences\u002Fstructured-data.md",{"path":108,"resourceType":109,"resourceTypeDesc":110,"sizeBytes":111,"sourceHtmlUrl":112},"scripts\u002Fverify-discoverability.mjs","SCRIPT","脚本",6129,"https:\u002F\u002Fgithub.com\u002FCratis\u002FDockerfiles\u002Fblob\u002Fmain\u002F.cratis\u002Fai\u002Fskills\u002Fcratis-discoverability\u002Fscripts\u002Fverify-discoverability.mjs",[114,136,151,163,179],{"skillNo":115,"name":116,"nameZh":6,"description":117,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":118,"sourceHtmlUrl":119,"categories":120,"keywords":125,"publishedAt":53},"01M6BYCFTY1KMFAH80NSX999AM","cratis-writing-voice-and-cadence","Review and revise existing prose so it reads as written by a person, by finding overused constructions and stock phrasing in one piece and structural sameness across a batch, then fixing both with specifics instead of injected variety, without changing any technical claim. Flags are editing prompts and never a verdict on who wrote something. Use when reviewing or rewriting documentation, release notes, pull request descriptions, posts or reviews for voice. Do not use for technical accuracy review, original drafting, authorship detection, or as a reason to touch approved copy without authorization.","https:\u002F\u002Fgithub.com\u002FCratis\u002FDockerfiles\u002Fblob\u002Fmain\u002F.cratis\u002Fai\u002Fskills\u002Fcratis-writing-voice-and-cadence\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FCratis\u002FDockerfiles\u002Fblob\u002Fmain\u002F.cratis\u002Fai\u002Fskills\u002Fcratis-writing-voice-and-cadence\u002FSKILL.md",[121,124],{"categoryNo":122,"categoryName":123,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":32,"categoryName":33,"taxonomyType":26,"taxonomyTypeDesc":27},[126,36,41,52,127,128,49,129,130,131,132,133,134,135],"cratis writing voice and cadence","notes","review","pull request","release notes","release","pull","batch","authorization","detection",{"skillNo":137,"name":138,"nameZh":6,"description":139,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":140,"sourceHtmlUrl":141,"categories":142,"keywords":144,"publishedAt":53},"01M6BYCD1JW206XHGATQH6AW2Y","cratis-technical-examples","Design and verify developer-facing code samples, tutorial projects, and documentation snippets against real Cratis APIs. Use when adding or reviewing a runnable example, multi-client snippet, sample app, command\u002Foutput pair, or migration before\u002Fafter code. Do not invent API shapes or treat rendering as a compilation check.","https:\u002F\u002Fgithub.com\u002FCratis\u002FDockerfiles\u002Fblob\u002Fmain\u002F.cratis\u002Fai\u002Fskills\u002Fcratis-technical-examples\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FCratis\u002FDockerfiles\u002Fblob\u002Fmain\u002F.cratis\u002Fai\u002Fskills\u002Fcratis-technical-examples\u002FSKILL.md",[143],{"categoryNo":24,"categoryName":25,"taxonomyType":26,"taxonomyTypeDesc":27},[145,36,146,37,147,148,149,49,150,44],"cratis technical examples","examples","api","verify","projects","code",{"skillNo":152,"name":153,"nameZh":6,"description":154,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":155,"sourceHtmlUrl":156,"categories":157,"keywords":159,"publishedAt":53},"01M6BYCAQ4X8JY1YS6YM87G0HG","cratis-release-notes","Draft or review developer-facing release notes and migration guidance from verified changes for a specific Cratis product version. Use for GitHub releases, upgrade guides, and release announcements; not for deciding release authority, publishing, or selecting a version label.","https:\u002F\u002Fgithub.com\u002FCratis\u002FDockerfiles\u002Fblob\u002Fmain\u002F.cratis\u002Fai\u002Fskills\u002Fcratis-release-notes\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FCratis\u002FDockerfiles\u002Fblob\u002Fmain\u002F.cratis\u002Fai\u002Fskills\u002Fcratis-release-notes\u002FSKILL.md",[158],{"categoryNo":24,"categoryName":25,"taxonomyType":26,"taxonomyTypeDesc":27},[127,160,36,131,130,128,161,162,37],"cratis release notes","github","product",{"skillNo":164,"name":165,"nameZh":6,"description":166,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":167,"sourceHtmlUrl":168,"categories":169,"keywords":173,"publishedAt":53},"01M6BYC813BG62GF2MYCP61M0E","cratis-llm-friendly-documentation","Design or review machine-readable documentation indexes, Markdown mirrors and bounded product\u002Ftopic exports for AI assistants. Use for llms.txt, llms-full.txt, per-product context sets, and documentation retrieval quality. Do not treat public exports as system instructions or promise crawler adoption.","https:\u002F\u002Fgithub.com\u002FCratis\u002FDockerfiles\u002Fblob\u002Fmain\u002F.cratis\u002Fai\u002Fskills\u002Fcratis-llm-friendly-documentation\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FCratis\u002FDockerfiles\u002Fblob\u002Fmain\u002F.cratis\u002Fai\u002Fskills\u002Fcratis-llm-friendly-documentation\u002FSKILL.md",[170],{"categoryNo":171,"categoryName":172,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000015","视觉设计",[174,36,49,44,128,50,162,175,176,177,178],"cratis llm friendly documentation","adoption","markdown","system","quality",{"skillNo":180,"name":181,"nameZh":6,"description":182,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":183,"sourceHtmlUrl":184,"categories":185,"keywords":188,"publishedAt":53},"01M6BYBNC7CJ3HZT58VEFCWF9E","cratis-documentation-writing","Plan, write, and improve user-centered Cratis documentation with a clear reader journey and one primary Diátaxis purpose per page. Use for product docs, tutorials, how-to guides, reference, explanations, and documentation reviews. For executable examples use cratis-technical-examples; for release notes use cratis-release-notes. Do not invent APIs or publish content.","https:\u002F\u002Fgithub.com\u002FCratis\u002FDockerfiles\u002Fblob\u002Fmain\u002F.cratis\u002Fai\u002Fskills\u002Fcratis-documentation-writing\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FCratis\u002FDockerfiles\u002Fblob\u002Fmain\u002F.cratis\u002Fai\u002Fskills\u002Fcratis-documentation-writing\u002FSKILL.md",[186,187],{"categoryNo":122,"categoryName":123,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":32,"categoryName":33,"taxonomyType":26,"taxonomyTypeDesc":27},[52,49,189,36,162,190,131,130,127,51,38,191,192,193,194,146,46],"cratis documentation writing","release-notes","plan","improve","how","publish"]