[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6P8JC7KD9E5D99RZJFYYZ5R":3,"skill-same:01M6P8JC7KD9E5D99RZJFYYZ5R":62},{"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":28,"publishedAt":35,"linkOnly":36,"markdownContent":37,"markdownBody":38,"frontMatter":39,"refName":40,"commitSha":41,"skillDirectory":42,"forksCount":43,"repositoryHtmlUrl":44,"repositoryHomepageUrl":45,"ownerHtmlUrl":46,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":47,"install":48,"resources":61},"01M6P8JC7KD9E5D99RZJFYYZ5R","chatto-api-rules",null,"Design rules concerning Chatto's ConnectRPC API, both resources and realtime","chattocorp\u002Fchatto","chattocorp","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F261891647?v=4","01M6P8ECJF78VVQ1TJBW2JAWQ8","ChattoCorp GmbH","01M6P8ECPWHQVQBB8XNCRR70B9",2972,"AGPL-3.0","https:\u002F\u002Fgithub.com\u002Fchattocorp\u002Fchatto\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fchatto-api-rules\u002FSKILL.md",[18,23],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000010","后端与接口","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[29,30,31,32,33,34],"api","Rules","chatto api rules","design","realtime","resources","2026-11-10 10:12:30",false,"---\nname: \"chatto-api-rules\"\ndescription: \"Design rules concerning Chatto's ConnectRPC API, both resources and realtime\"\n---\n\n### ConnectRPC Resource API\n\n- Define one canonical public protobuf for each resource. Reuse that protobuf\n  across list, get, batch, and mutation-response surfaces when the\n  authorization and lifecycle semantics are the same.\n- Keep services complete for their resource and scope. Add bounded batch reads\n  when events or related resources commonly expose IDs that clients must\n  hydrate.\n- Keep commands, explicit reads, pagination, history, and read-your-writes\n  responses in ConnectRPC. Realtime delivery does not replace these APIs.\n- Resource `Update*` RPCs must use `google.protobuf.FieldMask update_mask`.\n  Unselected fields stay unchanged; selected fields can be set or cleared,\n  subject to validation. Apply masks before validation. Omitted masks infer\n  populated fields; explicit empty masks are invalid. Clients should send\n  explicit paths. Commands use specific verbs such as `Set`, `Change`, or\n  `Refresh`.\n\n### Realtime API\n\n- Cover the complete useful product event surface for integrations, bots, and\n  clients. Do not limit the public event catalogue to events used by the\n  bundled frontend.\n- Use `chatto.core.evt.v1.Event` for durable EVT facts and\n  `chatto.core.pubsub.v1.PubSubEvent` for transient NATS Core signals. Use the\n  dedicated `chatto.realtime.v1.RealtimeEvent` union and domain payload catalog\n  for public delivery. Keep a semantic one-to-one relationship for selected\n  public events without importing core payload types into the public schema.\n  Client-facing `PubSubEvent` variants should reference public payload types\n  directly. Keep the restricted private union as the allow-list for cursorless\n  delivery.\n- Keep transport concerns in `chatto.realtime.v1` wrappers. Handshakes,\n  subscriptions, catch-up, cursors, heartbeats, errors, and close\n  guidance are not domain events.\n- Create a fresh authorized `RealtimeEvent` for each public delivery. The\n  public payload schema must omit internal variants and storage-only fields.\n  Never send stored bytes or mutate a stored event during mapping.\n- Keep current resources in ConnectRPC. Let a resource client bind reads to an\n  opaque realtime start cursor, then close the interval with event catch-up.\n  Do not attach resource sidecars to normal event frames.\n- Keep public cursors opaque, confidential, integrity-protected, and bound to\n  their viewer and scope. Do not expose NATS or JetStream coordinates.\n- Keep wire volume bounded. Resume must have sequence, event-count, time, and\n  concurrency limits. Large and lazy collections stay in paginated ConnectRPC\n  APIs.\n- Use consistent product terminology and names. Public comments must not\n  depend on backend terms such as projections, NATS, or JetStream.\n- Use a new behavioral protocol version when a change requires all clients to\n  change their behavior. Do not use a capability matrix to restate required\n  frame semantics.\n- When an `Event` or `PubSubEvent` variant must reach clients, update the\n  dedicated payload, public union member, authorization and mapper coverage,\n  consuming reducers, generated clients, architecture inventory, public\n  documentation, and compatibility notes in the same change. Keep public names\n  and compact union numbers independent from the internal event source. Use\n  independent public payload field numbers and explicit typed mapping for EVT.\n  Reference the public payload directly from client-facing pubsub variants and\n  deep-copy it at the delivery boundary.\n- Keep protobuf comments, public API overviews, tutorials, compatibility\n  guidance, and release notes current.\n","### ConnectRPC Resource API\n\n- Define one canonical public protobuf for each resource. Reuse that protobuf\n  across list, get, batch, and mutation-response surfaces when the\n  authorization and lifecycle semantics are the same.\n- Keep services complete for their resource and scope. Add bounded batch reads\n  when events or related resources commonly expose IDs that clients must\n  hydrate.\n- Keep commands, explicit reads, pagination, history, and read-your-writes\n  responses in ConnectRPC. Realtime delivery does not replace these APIs.\n- Resource `Update*` RPCs must use `google.protobuf.FieldMask update_mask`.\n  Unselected fields stay unchanged; selected fields can be set or cleared,\n  subject to validation. Apply masks before validation. Omitted masks infer\n  populated fields; explicit empty masks are invalid. Clients should send\n  explicit paths. Commands use specific verbs such as `Set`, `Change`, or\n  `Refresh`.\n\n### Realtime API\n\n- Cover the complete useful product event surface for integrations, bots, and\n  clients. Do not limit the public event catalogue to events used by the\n  bundled frontend.\n- Use `chatto.core.evt.v1.Event` for durable EVT facts and\n  `chatto.core.pubsub.v1.PubSubEvent` for transient NATS Core signals. Use the\n  dedicated `chatto.realtime.v1.RealtimeEvent` union and domain payload catalog\n  for public delivery. Keep a semantic one-to-one relationship for selected\n  public events without importing core payload types into the public schema.\n  Client-facing `PubSubEvent` variants should reference public payload types\n  directly. Keep the restricted private union as the allow-list for cursorless\n  delivery.\n- Keep transport concerns in `chatto.realtime.v1` wrappers. Handshakes,\n  subscriptions, catch-up, cursors, heartbeats, errors, and close\n  guidance are not domain events.\n- Create a fresh authorized `RealtimeEvent` for each public delivery. The\n  public payload schema must omit internal variants and storage-only fields.\n  Never send stored bytes or mutate a stored event during mapping.\n- Keep current resources in ConnectRPC. Let a resource client bind reads to an\n  opaque realtime start cursor, then close the interval with event catch-up.\n  Do not attach resource sidecars to normal event frames.\n- Keep public cursors opaque, confidential, integrity-protected, and bound to\n  their viewer and scope. Do not expose NATS or JetStream coordinates.\n- Keep wire volume bounded. Resume must have sequence, event-count, time, and\n  concurrency limits. Large and lazy collections stay in paginated ConnectRPC\n  APIs.\n- Use consistent product terminology and names. Public comments must not\n  depend on backend terms such as projections, NATS, or JetStream.\n- Use a new behavioral protocol version when a change requires all clients to\n  change their behavior. Do not use a capability matrix to restate required\n  frame semantics.\n- When an `Event` or `PubSubEvent` variant must reach clients, update the\n  dedicated payload, public union member, authorization and mapper coverage,\n  consuming reducers, generated clients, architecture inventory, public\n  documentation, and compatibility notes in the same change. Keep public names\n  and compact union numbers independent from the internal event source. Use\n  independent public payload field numbers and explicit typed mapping for EVT.\n  Reference the public payload directly from client-facing pubsub variants and\n  deep-copy it at the delivery boundary.\n- Keep protobuf comments, public API overviews, tutorials, compatibility\n  guidance, and release notes current.\n",{"name":5,"description":7},"main","d3d21f4a4fb6c1315aa62df97a6cb6617680af95",".agents\u002Fskills\u002Fchatto-api-rules",152,"https:\u002F\u002Fgithub.com\u002Fchattocorp\u002Fchatto","https:\u002F\u002Fchatto.run","https:\u002F\u002Fgithub.com\u002Fchattocorp","2026-11-15 04:17:01",{"source":8,"skillName":5,"commands":49,"prompt":59,"zipAvailable":60},[50,53,56],{"tool":51,"command":52},"npx","npx skills add chattocorp\u002Fchatto --skill chatto-api-rules",{"tool":54,"command":55},"bunx","bunx skills add chattocorp\u002Fchatto --skill chatto-api-rules",{"tool":57,"command":58},"pnpm","pnpm dlx skills add chattocorp\u002Fchatto --skill chatto-api-rules","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fchattocorp\u002Fchatto\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fchatto-api-rules\u002FSKILL.md",true,[],[63,71,79,97,116,132],{"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":70},"01M78PF8DVTF8P9QFT6G0SW80Z","chatto-release-checklist","Check Chatto release readiness, including release metadata, upgrade guidance, and docs website consistency. Use when preparing or reviewing a Chatto release or release PR.","https:\u002F\u002Fgithub.com\u002Fchattocorp\u002Fchatto\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fchatto-release-checklist\u002FSKILL.md",[],[],"2026-11-15 14:19:17",{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"publishedAt":78},"01M747DN6Q5J07Z2N6P1JEVASV","github","Work with GitHub issues, pull requests, and repository information for Chatto. Use for issue searches, bug reports, feature requests, issue updates, and GitHub access checks.","https:\u002F\u002Fgithub.com\u002Fchattocorp\u002Fchatto\u002Fblob\u002Fmain\u002Fexamples\u002Fbotto\u002F.agents\u002Fskills\u002Fgithub\u002FSKILL.md",[],[],"2026-11-11 15:11:14",{"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":91,"publishedAt":35},"01M6P8S7F1NYMKD9PW2RGZ0B2P","writing-tests","Instructions and hints for writing tests.","https:\u002F\u002Fgithub.com\u002Fchattocorp\u002Fchatto\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fwriting-tests\u002FSKILL.md",[85,88],{"categoryNo":86,"categoryName":87,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":89,"categoryName":90,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000036","内容创作者",[92,93,94,95,96],"writing tests","writing","tests","for","instructions",{"skillNo":98,"name":99,"nameZh":6,"description":100,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":101,"categories":102,"keywords":106,"publishedAt":35},"01M6P8S131Q068WC04FS0YW3RR","update-project-dependencies","Update Chatto Go and frontend dependencies within their compatible version ranges, then run tests.","https:\u002F\u002Fgithub.com\u002Fchattocorp\u002Fchatto\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fupdate-project-dependencies\u002FSKILL.md",[103],{"categoryNo":104,"categoryName":105,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000009","前端开发",[107,108,109,110,111,112,113,94,114,115],"update project dependencies","update","dependencies","project","run tests","run","frontend","go","version",{"skillNo":117,"name":118,"nameZh":6,"description":119,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":120,"categories":121,"keywords":122,"publishedAt":35},"01M6P8RERB7E3KYD4PW98D94SR","svelte-docs","Look up official Svelte, SvelteKit, and Svelte CLI documentation.","https:\u002F\u002Fgithub.com\u002Fchattocorp\u002Fchatto\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fsvelte-docs\u002FSKILL.md",[],[123,124,125,126,127,128,129,130,131],"docs","svelte docs","svelte","look","up","sveltekit","cli","official","documentation",{"skillNo":133,"name":134,"nameZh":6,"description":135,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":136,"categories":137,"keywords":138,"publishedAt":35},"01M6P8RA0PS8DFAR8GXMB1CBFN","svelte-core-bestpractices","Guidance on writing fast, robust, modern Svelte code. Load this skill whenever in a Svelte project and asked to write\u002Fedit or analyze a Svelte component or module. Covers reactivity, event handling, styling, integration with libraries and more.","https:\u002F\u002Fgithub.com\u002Fchattocorp\u002Fchatto\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fsvelte-core-bestpractices\u002FSKILL.md",[],[139,125,140,141,142,143,93,110,144,145,146,147,148,149,150,151,152,153,154,155],"core","svelte core bestpractices","libraries","analyze","code","styling","component","write","edit","fast","guidance","integration","with","load","module","more","event"]