[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6NQ9YPWWFBNMRAT43091GFP":3,"skill-same:01M6NQ9YPWWFBNMRAT43091GFP":93},{"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":38,"linkOnly":39,"markdownContent":40,"markdownBody":41,"frontMatter":42,"refName":61,"commitSha":62,"skillDirectory":63,"forksCount":14,"repositoryHtmlUrl":64,"repositoryHomepageUrl":65,"ownerHtmlUrl":66,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":67,"install":68,"resources":81},"01M6NQ9YPWWFBNMRAT43091GFP","category-management",null,"Manage Category entities — taxonomies and classification schemes that group other entities by type, area, tier, etc. Use when defining a new classification axis (priority levels, bug severity, feature tier, product area) that other entities will be tagged with.","projectious-work\u002Fprocesskit","projectious-work","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F263889726?v=4","01M6N97TJJ118WQ35CHRV8RD0E","projectious.work","01M6N97TPWJPF0BMKYQ4PBY5W8",0,"MIT","https:\u002F\u002Fgithub.com\u002Fprojectious-work\u002Fprocesskit\u002Fblob\u002Fmain\u002Fsrc\u002Fcontext\u002Fskills\u002Fprocesskit\u002Fcategory-management\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37],"category management","management","bug","trail","with","event","keep","events","type","feature","manage","product","log","use","write","work","classification","severity","audit","2026-11-10 10:12:30",false,"---\nname: category-management\ndescription: |\n  Manage Category entities — taxonomies and classification schemes that group other entities by type, area, tier, etc. Use when defining a new classification axis (priority levels, bug severity, feature tier, product area) that other entities will be tagged with.\nmetadata:\n  processkit:\n    apiVersion: processkit.projectious.work\u002Fv2\n    id: SKILL-category-management\n    version: \"1.0.0\"\n    created: 2026-04-06T00:00:00Z\n    category: processkit\n    layer: 2\n    uses:\n      - skill: event-log\n        purpose: Log events to keep the audit trail accurate after every write.\n    provides:\n      primitives: [Category]\n      templates: [category]\n---\n\n# Category Management\n\n## Intro\n\nA Category is a named classification — a list of possible values for a\nlabeling axis. Examples: priority (critical\u002Fhigh\u002Fmedium\u002Flow), bug severity\n(sev1\u002Fsev2\u002Fsev3), feature tier (core\u002Fenhancement\u002Fexperiment), product area\n(frontend\u002Fbackend\u002Finfra).\n\n## Overview\n\n### When to create a Category\n\nCreate a Category when:\n- A labeling axis is used across many entities\n- The values are constrained to a specific set\n- The set is worth documenting (meanings, SLAs per value)\n\nDon't create a Category for one-off tags or freeform labels.\n\n### Shape\n\n```yaml\n---\napiVersion: processkit.projectious.work\u002Fv2\nkind: Category\nmetadata:\n  id: CAT-priority\n  created: 2026-04-06T00:00:00Z\nspec:\n  name: priority\n  description: \"Business priority for work items.\"\n  axis: priority\n  values:\n    - name: critical\n      description: \"Drop everything. Affects production or blocks a release.\"\n    - name: high\n      description: \"Top of the queue. Assigned this sprint.\"\n    - name: medium\n      description: \"Important but schedulable.\"\n    - name: low\n      description: \"Nice to have. Pick up when capacity allows.\"\n  applies_to: [WorkItem]\n---\n```\n\n### Using a category\n\nEntities tag themselves via `metadata.labels.\u003Caxis>: \u003Cvalue>` or\n`spec.\u003Caxis>: \u003Cvalue>`. The index MCP server validates that the value is\none of the category's defined values.\n\n### Workflow\n\n1. Pick `CAT-\u003Caxis>` where axis is the labeling dimension.\n2. List `values` with clear, non-overlapping definitions.\n3. Declare which primitive `kinds` this category `applies_to`.\n4. Save to `context\u002Fcategories\u002F`.\n5. When you add a new value, write a `category.value_added` LogEntry so\n   the change is traceable.\n\n## Gotchas\n\nAgent-specific failure modes — provider-neutral pause-and-self-check items:\n\n- **Creating a Category when an enum field would suffice.** If the\n  values are fixed and known at design time (e.g., `priority:\n  low|medium|high|critical`), put them in the entity's schema\n  enum, not in a Category entity. Categories are for taxonomies\n  the project actively curates.\n- **Inventing a new Category when an existing one fits.** Always\n  list existing categories first via `list_categories`. Two\n  Categories with overlapping meaning (\"severity\" and \"priority\"\n  both used for bugs) is a maintenance trap.\n- **Categories with overlapping meaning.** If two Categories cover\n  the same axis from different angles, merge them or pick one as\n  canonical. Overlap silently splits the same data into different\n  buckets and breaks reports.\n- **Forgetting to mark a Category as deprecated when superseded.**\n  Don't just stop using a Category and leave it in the catalog —\n  set its state to deprecated so future queries don't surface it\n  as a current option.\n- **Adding categories without examples.** A Category like \"Tier 1\"\n  with no description of what qualifies is an empty bucket. Each\n  Category value should ship with at least one example so future\n  agents apply it consistently.\n- **Treating Category as a tag.** Categories are structured\n  taxonomies the project curates. Free-form tags belong in\n  `metadata.tags` on the consuming entity, not in a Category\n  entity.\n- **Creating a Category for one-off use.** If the Category will be\n  applied to a single entity and never reused, it's not a\n  Category — it's just metadata on that entity.\n\n## Full reference\n\n### Fields\n\n| Field         | Type           | Notes                                                  |\n|---------------|----------------|--------------------------------------------------------|\n| `name`        | string         | Category name                                          |\n| `description` | string         | What this axis categorizes                             |\n| `axis`        | string         | The label key used on entities (e.g. `priority`)       |\n| `values`      | list[object]   | `{name, description, optional metadata}`               |\n| `applies_to`  | list[string]   | Primitive kinds this category applies to               |\n| `default`     | string         | Optional. Default value if unspecified.                |\n| `multi`       | bool           | Can an entity have multiple values? Default false.     |\n\n### Hierarchical categories\n\nA category value may have its own `children` for nested taxonomies:\n\n```yaml\nvalues:\n  - name: backend\n    children:\n      - name: backend-api\n      - name: backend-db\n      - name: backend-queue\n  - name: frontend\n    children:\n      - name: frontend-web\n      - name: frontend-mobile\n```\n\nThe validator accepts any leaf or any intermediate name.\n\n### Retiring a value\n\nSet `deprecated: true` on a value rather than removing it — existing entities\nstill reference it, and removing it would invalidate them.\n\n### Categories vs Labels vs Roles\n\n- **Category**: defined set of values for a classification axis.\n- **Labels**: freeform key\u002Fvalue tags. No schema.\n- **Roles**: named sets of responsibilities actors fill.\n\nCategories are for closed sets. If the set is open and changes often, use\nlabels. If it's about who does things, it's a role.\n","# Category Management\n\n## Intro\n\nA Category is a named classification — a list of possible values for a\nlabeling axis. Examples: priority (critical\u002Fhigh\u002Fmedium\u002Flow), bug severity\n(sev1\u002Fsev2\u002Fsev3), feature tier (core\u002Fenhancement\u002Fexperiment), product area\n(frontend\u002Fbackend\u002Finfra).\n\n## Overview\n\n### When to create a Category\n\nCreate a Category when:\n- A labeling axis is used across many entities\n- The values are constrained to a specific set\n- The set is worth documenting (meanings, SLAs per value)\n\nDon't create a Category for one-off tags or freeform labels.\n\n### Shape\n\n```yaml\n---\napiVersion: processkit.projectious.work\u002Fv2\nkind: Category\nmetadata:\n  id: CAT-priority\n  created: 2026-04-06T00:00:00Z\nspec:\n  name: priority\n  description: \"Business priority for work items.\"\n  axis: priority\n  values:\n    - name: critical\n      description: \"Drop everything. Affects production or blocks a release.\"\n    - name: high\n      description: \"Top of the queue. Assigned this sprint.\"\n    - name: medium\n      description: \"Important but schedulable.\"\n    - name: low\n      description: \"Nice to have. Pick up when capacity allows.\"\n  applies_to: [WorkItem]\n---\n```\n\n### Using a category\n\nEntities tag themselves via `metadata.labels.\u003Caxis>: \u003Cvalue>` or\n`spec.\u003Caxis>: \u003Cvalue>`. The index MCP server validates that the value is\none of the category's defined values.\n\n### Workflow\n\n1. Pick `CAT-\u003Caxis>` where axis is the labeling dimension.\n2. List `values` with clear, non-overlapping definitions.\n3. Declare which primitive `kinds` this category `applies_to`.\n4. Save to `context\u002Fcategories\u002F`.\n5. When you add a new value, write a `category.value_added` LogEntry so\n   the change is traceable.\n\n## Gotchas\n\nAgent-specific failure modes — provider-neutral pause-and-self-check items:\n\n- **Creating a Category when an enum field would suffice.** If the\n  values are fixed and known at design time (e.g., `priority:\n  low|medium|high|critical`), put them in the entity's schema\n  enum, not in a Category entity. Categories are for taxonomies\n  the project actively curates.\n- **Inventing a new Category when an existing one fits.** Always\n  list existing categories first via `list_categories`. Two\n  Categories with overlapping meaning (\"severity\" and \"priority\"\n  both used for bugs) is a maintenance trap.\n- **Categories with overlapping meaning.** If two Categories cover\n  the same axis from different angles, merge them or pick one as\n  canonical. Overlap silently splits the same data into different\n  buckets and breaks reports.\n- **Forgetting to mark a Category as deprecated when superseded.**\n  Don't just stop using a Category and leave it in the catalog —\n  set its state to deprecated so future queries don't surface it\n  as a current option.\n- **Adding categories without examples.** A Category like \"Tier 1\"\n  with no description of what qualifies is an empty bucket. Each\n  Category value should ship with at least one example so future\n  agents apply it consistently.\n- **Treating Category as a tag.** Categories are structured\n  taxonomies the project curates. Free-form tags belong in\n  `metadata.tags` on the consuming entity, not in a Category\n  entity.\n- **Creating a Category for one-off use.** If the Category will be\n  applied to a single entity and never reused, it's not a\n  Category — it's just metadata on that entity.\n\n## Full reference\n\n### Fields\n\n| Field         | Type           | Notes                                                  |\n|---------------|----------------|--------------------------------------------------------|\n| `name`        | string         | Category name                                          |\n| `description` | string         | What this axis categorizes                             |\n| `axis`        | string         | The label key used on entities (e.g. `priority`)       |\n| `values`      | list[object]   | `{name, description, optional metadata}`               |\n| `applies_to`  | list[string]   | Primitive kinds this category applies to               |\n| `default`     | string         | Optional. Default value if unspecified.                |\n| `multi`       | bool           | Can an entity have multiple values? Default false.     |\n\n### Hierarchical categories\n\nA category value may have its own `children` for nested taxonomies:\n\n```yaml\nvalues:\n  - name: backend\n    children:\n      - name: backend-api\n      - name: backend-db\n      - name: backend-queue\n  - name: frontend\n    children:\n      - name: frontend-web\n      - name: frontend-mobile\n```\n\nThe validator accepts any leaf or any intermediate name.\n\n### Retiring a value\n\nSet `deprecated: true` on a value rather than removing it — existing entities\nstill reference it, and removing it would invalidate them.\n\n### Categories vs Labels vs Roles\n\n- **Category**: defined set of values for a classification axis.\n- **Labels**: freeform key\u002Fvalue tags. No schema.\n- **Roles**: named sets of responsibilities actors fill.\n\nCategories are for closed sets. If the set is open and changes often, use\nlabels. If it's about who does things, it's a role.\n",{"name":5,"metadata":43,"description":60},{"processkit":44},{"id":45,"uses":46,"layer":50,"created":51,"version":52,"category":53,"provides":54,"apiVersion":59},"SKILL-category-management",[47],{"skill":48,"purpose":49},"event-log","Log events to keep the audit trail accurate after every write.",2,1775433600000,"1.0.0","processkit",{"templates":55,"primitives":57},[56],"category",[58],"Category","processkit.projectious.work\u002Fv2","Manage Category entities — taxonomies and classification schemes that group other entities by type, area, tier, etc. Use when defining a new classification axis (priority levels, bug severity, feature tier, product area) that other entities will be tagged with.\n","main","7231f100e266e30d2c1699ecde5c00602471dc3c","src\u002Fcontext\u002Fskills\u002Fprocesskit\u002Fcategory-management","https:\u002F\u002Fgithub.com\u002Fprojectious-work\u002Fprocesskit","https:\u002F\u002Fprojectious-work.github.io\u002Fprocesskit\u002F","https:\u002F\u002Fgithub.com\u002Fprojectious-work","2026-11-11 23:24:18",{"source":8,"skillName":5,"commands":69,"prompt":79,"zipAvailable":80},[70,73,76],{"tool":71,"command":72},"npx","npx skills add projectious-work\u002Fprocesskit --skill category-management",{"tool":74,"command":75},"bunx","bunx skills add projectious-work\u002Fprocesskit --skill category-management",{"tool":77,"command":78},"pnpm","pnpm dlx skills add projectious-work\u002Fprocesskit --skill category-management","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fprojectious-work\u002Fprocesskit\u002Fblob\u002Fmain\u002Fsrc\u002Fcontext\u002Fskills\u002Fprocesskit\u002Fcategory-management\u002FSKILL.md",true,[82,88],{"path":83,"resourceType":84,"resourceTypeDesc":85,"sizeBytes":86,"sourceHtmlUrl":87},"assets\u002Fcategory.yaml","ASSET","资产文件",254,"https:\u002F\u002Fgithub.com\u002Fprojectious-work\u002Fprocesskit\u002Fblob\u002Fmain\u002Fsrc\u002Fcontext\u002Fskills\u002Fprocesskit\u002Fcategory-management\u002Fassets\u002Fcategory.yaml",{"path":89,"resourceType":90,"resourceTypeDesc":91,"sizeBytes":14,"sourceHtmlUrl":92},"scripts\u002F.gitkeep","SCRIPT","脚本","https:\u002F\u002Fgithub.com\u002Fprojectious-work\u002Fprocesskit\u002Fblob\u002Fmain\u002Fsrc\u002Fcontext\u002Fskills\u002Fprocesskit\u002Fcategory-management\u002Fscripts\u002F.gitkeep",[94,101,108,114,139,159],{"skillNo":95,"name":96,"nameZh":6,"description":6,"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":100},"01M7665G2ED3624R3X93304265","standard-ui-design","https:\u002F\u002Fgithub.com\u002Fprojectious-work\u002Fprocesskit\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fstandard-ui-design\u002FSKILL.md",[],[],"2026-11-12 13:55:43",{"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":6,"sourceHtmlUrl":105,"categories":106,"keywords":107,"publishedAt":100},"01M76651QTC6W0HJ4AFW2MMR3V","standard-agent-use","Company standard for working with AI agents. Use when deciding what to delegate to agents, capturing open work, keeping agent memory or knowledge notes, improving an agent workflow, or introducing agent work in a team or for a client.","https:\u002F\u002Fgithub.com\u002Fprojectious-work\u002Fprocesskit\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fstandard-agent-use\u002FSKILL.md",[],[],{"skillNo":109,"name":110,"nameZh":6,"description":6,"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":100},"01M76650NN4T8P241021NBR64S","standard-agent-building","https:\u002F\u002Fgithub.com\u002Fprojectious-work\u002Fprocesskit\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fstandard-agent-building\u002FSKILL.md",[],[],{"skillNo":115,"name":116,"nameZh":6,"description":117,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":118,"categories":119,"keywords":125,"publishedAt":38},"01M6X5MTC89B4ZGXW3JVSQCPF8","skill-management","Manage Skill package manifests as v1 ontology entities.","https:\u002F\u002Fgithub.com\u002Fprojectious-work\u002Fprocesskit\u002Fblob\u002Fmain\u002Fsrc\u002Fcontext\u002Fskills\u002Fprocesskit\u002Fskill-management\u002FSKILL.md",[120],{"categoryNo":121,"categoryName":122,"taxonomyType":123,"taxonomyTypeDesc":124},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[20,126,127,128,129,130,34,131,132,29,133,134,116,135,136,137,138],"skill management","ontology","v1","create","as","transition","get","update","alpha","list","package","skill package","manifests",{"skillNo":140,"name":141,"nameZh":6,"description":142,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":143,"categories":144,"keywords":146,"publishedAt":38},"01M6X5MCV74NHW5MEDNHZRF2C8","schema-management","Manage generated processkit schema contracts through deterministic MCP rebuild and inspection workflows.","https:\u002F\u002Fgithub.com\u002Fprojectious-work\u002Fprocesskit\u002Fblob\u002Fmain\u002Fsrc\u002Fcontext\u002Fskills\u002Fprocesskit\u002Fschema-management\u002FSKILL.md",[145],{"categoryNo":121,"categoryName":122,"taxonomyType":123,"taxonomyTypeDesc":124},[147,148,20,149,150,151,152,153,154,155,156,157,34,132,29,134,158],"schema","schema management","contract","rebuild","contracts","workflows","wed","generated","MCP","validation","deterministic","mode",{"skillNo":160,"name":161,"nameZh":6,"description":162,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":163,"categories":164,"keywords":165,"publishedAt":38},"01M6X5M5G6YJ96AMZGSCZJ1D13","proposition-management","Record claims, risks, beliefs, world facts, WSJF estimates, and assumptions through the Proposition interface.","https:\u002F\u002Fgithub.com\u002Fprojectious-work\u002Fprocesskit\u002Fblob\u002Fmain\u002Fsrc\u002Fcontext\u002Fskills\u002Fprocesskit\u002Fproposition-management\u002FSKILL.md",[],[166,20,167,168,129,169,170,171,34,132,172,24,133,173,134,174,175,176,177,31],"proposition management","proposition","interface","claims","record","world","creation","WSJF","index","updates","query","facts"]