[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6KW73BXENRAKGHC60V992RY":3,"skill-same:01M6KW73BXENRAKGHC60V992RY":64},{"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":43,"commitSha":44,"skillDirectory":45,"forksCount":14,"repositoryHtmlUrl":46,"repositoryHomepageUrl":6,"ownerHtmlUrl":47,"ownerBlogUrl":6,"ownerDescription":48,"updatedAt":49,"install":50,"resources":63},"01M6KW73BXENRAKGHC60V992RY","rules-management",null,"Create, modify, delete, and sync Claude rules files (.claude\u002Frules\u002F*.md) and GitHub Copilot instruction files (.github\u002Finstructions\u002F*.instructions.md) safely using a discovery-first, non-destructive workflow. Invoked by agent-manager whenever a rules or instructions file lifecycle operation is requested.","rafsanulhasan\u002FHypermediaEngine","rafsanulhasan","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F2341142?v=4","01M6KW2HWPTZWK051N7B0HTBVG","Rafsanul Hasan","01M6KW2J0N3613382MF5DRN79H",0,"GPL-3.0","https:\u002F\u002Fgithub.com\u002Frafsanulhasan\u002FHypermediaEngine\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Frules-management\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37],"rules management","management","Rules","lifecycle","manager","operation","agent-manager","files","instructions","discovery","github","first","file","delete","create","copilot","sync","github copilot","workflow","2026-11-10 10:12:30",false,"---\nname: rules-management\ndescription: Create, modify, delete, and sync Claude rules files (.claude\u002Frules\u002F*.md) and GitHub Copilot instruction files (.github\u002Finstructions\u002F*.instructions.md) safely using a discovery-first, non-destructive workflow. Invoked by agent-manager whenever a rules or instructions file lifecycle operation is requested.\n---\n\n# Rules and Instructions Management\n\nUse this skill when a user asks to create, update, or remove a repository rule or instruction file on either the Claude Code or GitHub Copilot platform in this repository.\n\nThis skill is platform-aware and actionable. It always discovers existing rule and instruction files first, then applies minimal, reversible changes. Both platforms are kept in sync unless a platform-specific scope is explicitly requested.\n\nThis skill is invoked by `agent-manager` for rules and instructions lifecycle operations.\n\n---\n\n## Inputs Expected\n\n- Operation: `create` | `modify` | `delete` | `sync`\n- Platform target: `claude` | `copilot` | `both` (default: `both`)\n- Rule\u002Finstruction name: kebab-case identifier\n- Description: what the rule or instruction enforces\n- Scope pattern: `globs` for Claude rules and `applyTo` for Copilot instructions\n- Body: the markdown guidance content to enforce\n\nIf any required input is missing, ask only the minimum clarifying questions needed to proceed.\n\n---\n\n## Phase 0 - Context Load (silent)\n\n1. Read `.claude\u002FCLAUDE.md` and `AGENTS.md`.\n2. Invoke `Skill(\"manage-memory\", args: \"agent-manager\")`.\n3. Read repository governance files relevant to rule and instruction ownership.\n4. Discover current rule and instruction surfaces before proposing edits.\n\n---\n\n## Phase 1 - Discovery And Classification\n\n1. Glob `.claude\u002Frules\u002F*.md` - list all existing Claude rules files.\n2. Glob `.github\u002Finstructions\u002F*.instructions.md` - list all existing Copilot instruction files.\n3. Build an inventory table:\n   | Name | Claude rule path | Copilot instruction path | Status |\n   |------|------------------|--------------------------|--------|\n4. Check for drift (rule exists on one platform but not the other).\n5. Classify request into one mutation strategy:\n   - `create` - neither platform file exists for the given name\n   - `modify` - one or both platform files exist and need updating\n   - `delete` - one or both platform files must be removed\n   - `sync` - files exist on both platforms but have drifted out of sync\n\nDecision rule:\n- If operation is `modify` or `delete` and the target file is not discoverable, pause and ask for disambiguation instead of guessing.\n\n---\n\n## Phase 2 - Plan The Change\n\n1. Identify exact file paths for all affected files.\n2. Determine minimum edit set:\n   - For `create`: new file(s) to write\n   - For `modify`: field(s) or section(s) to update\n   - For `delete`: file(s) to archive\u002Fremove\n   - For `sync`: diff both files and reconcile to the authoritative source\n3. Confirm scope with the caller if ambiguous (for example, only one platform was targeted).\n4. For `delete`, require explicit confirmation before any irreversible removal.\n\n---\n\n## Phase 3 - Execute\n\n### create\n\n**Claude rule** - write `.claude\u002Frules\u002F\u003Cname>.md`:\n\n```markdown\n---\ndescription: \u003Cone-line description>\nglobs: \"**\u002F*\"\nalwaysApply: false\n---\n\n# \u003CRule Title>\n\n\u003Crule body>\n```\n\n**Copilot instruction** - write `.github\u002Finstructions\u002F\u003Cname>.instructions.md`:\n\n```markdown\n---\napplyTo: \"**\u002F*\"\ndescription: \"\u003Cone-line description>\"\n---\n\n# \u003CInstruction Title>\n\n\u003Cinstruction body>\n```\n\n### modify\n\n1. Read both existing files.\n2. Apply requested changes to frontmatter fields (`description`, `globs`\u002F`applyTo`, `alwaysApply`) and body sections.\n3. Keep both files in sync unless a platform-specific change is explicitly requested.\n4. Preserve all unrelated content.\n\n### delete\n\n1. Default to **soft delete**: rename to `\u003Cname>.md.deprecated` (Claude) or `\u003Cname>.instructions.md.deprecated` (Copilot).\n2. Hard delete only with explicit `hard-delete` flag and user confirmation.\n3. Report what was removed or archived.\n\n### sync\n\n1. Diff the Claude rule and Copilot instruction for the same name.\n2. Identify which is authoritative (typically the one most recently updated, or the one intentionally specified by the user).\n3. Reconcile the non-authoritative file to match, preserving platform-specific frontmatter fields.\n\n---\n\n## Phase 4 - Validation\n\n1. Confirm all written files parse as valid Markdown with correct YAML frontmatter.\n2. Verify frontmatter contains at minimum a `description` field.\n3. Verify frontmatter contains scope fields (`globs` for Claude, `applyTo` for Copilot).\n4. Report any drift found (for example, rule exists but no matching instruction, or vice versa).\n\n---\n\n## Quality Gate\n\n- No rule or instruction is written without frontmatter and a `description` field.\n- Soft delete is always the default for `delete` operations.\n- Both platform files must be written or updated together unless scope is explicitly restricted.\n- Never read or modify `.env` or sensitive configuration files.\n","# Rules and Instructions Management\n\nUse this skill when a user asks to create, update, or remove a repository rule or instruction file on either the Claude Code or GitHub Copilot platform in this repository.\n\nThis skill is platform-aware and actionable. It always discovers existing rule and instruction files first, then applies minimal, reversible changes. Both platforms are kept in sync unless a platform-specific scope is explicitly requested.\n\nThis skill is invoked by `agent-manager` for rules and instructions lifecycle operations.\n\n---\n\n## Inputs Expected\n\n- Operation: `create` | `modify` | `delete` | `sync`\n- Platform target: `claude` | `copilot` | `both` (default: `both`)\n- Rule\u002Finstruction name: kebab-case identifier\n- Description: what the rule or instruction enforces\n- Scope pattern: `globs` for Claude rules and `applyTo` for Copilot instructions\n- Body: the markdown guidance content to enforce\n\nIf any required input is missing, ask only the minimum clarifying questions needed to proceed.\n\n---\n\n## Phase 0 - Context Load (silent)\n\n1. Read `.claude\u002FCLAUDE.md` and `AGENTS.md`.\n2. Invoke `Skill(\"manage-memory\", args: \"agent-manager\")`.\n3. Read repository governance files relevant to rule and instruction ownership.\n4. Discover current rule and instruction surfaces before proposing edits.\n\n---\n\n## Phase 1 - Discovery And Classification\n\n1. Glob `.claude\u002Frules\u002F*.md` - list all existing Claude rules files.\n2. Glob `.github\u002Finstructions\u002F*.instructions.md` - list all existing Copilot instruction files.\n3. Build an inventory table:\n   | Name | Claude rule path | Copilot instruction path | Status |\n   |------|------------------|--------------------------|--------|\n4. Check for drift (rule exists on one platform but not the other).\n5. Classify request into one mutation strategy:\n   - `create` - neither platform file exists for the given name\n   - `modify` - one or both platform files exist and need updating\n   - `delete` - one or both platform files must be removed\n   - `sync` - files exist on both platforms but have drifted out of sync\n\nDecision rule:\n- If operation is `modify` or `delete` and the target file is not discoverable, pause and ask for disambiguation instead of guessing.\n\n---\n\n## Phase 2 - Plan The Change\n\n1. Identify exact file paths for all affected files.\n2. Determine minimum edit set:\n   - For `create`: new file(s) to write\n   - For `modify`: field(s) or section(s) to update\n   - For `delete`: file(s) to archive\u002Fremove\n   - For `sync`: diff both files and reconcile to the authoritative source\n3. Confirm scope with the caller if ambiguous (for example, only one platform was targeted).\n4. For `delete`, require explicit confirmation before any irreversible removal.\n\n---\n\n## Phase 3 - Execute\n\n### create\n\n**Claude rule** - write `.claude\u002Frules\u002F\u003Cname>.md`:\n\n```markdown\n---\ndescription: \u003Cone-line description>\nglobs: \"**\u002F*\"\nalwaysApply: false\n---\n\n# \u003CRule Title>\n\n\u003Crule body>\n```\n\n**Copilot instruction** - write `.github\u002Finstructions\u002F\u003Cname>.instructions.md`:\n\n```markdown\n---\napplyTo: \"**\u002F*\"\ndescription: \"\u003Cone-line description>\"\n---\n\n# \u003CInstruction Title>\n\n\u003Cinstruction body>\n```\n\n### modify\n\n1. Read both existing files.\n2. Apply requested changes to frontmatter fields (`description`, `globs`\u002F`applyTo`, `alwaysApply`) and body sections.\n3. Keep both files in sync unless a platform-specific change is explicitly requested.\n4. Preserve all unrelated content.\n\n### delete\n\n1. Default to **soft delete**: rename to `\u003Cname>.md.deprecated` (Claude) or `\u003Cname>.instructions.md.deprecated` (Copilot).\n2. Hard delete only with explicit `hard-delete` flag and user confirmation.\n3. Report what was removed or archived.\n\n### sync\n\n1. Diff the Claude rule and Copilot instruction for the same name.\n2. Identify which is authoritative (typically the one most recently updated, or the one intentionally specified by the user).\n3. Reconcile the non-authoritative file to match, preserving platform-specific frontmatter fields.\n\n---\n\n## Phase 4 - Validation\n\n1. Confirm all written files parse as valid Markdown with correct YAML frontmatter.\n2. Verify frontmatter contains at minimum a `description` field.\n3. Verify frontmatter contains scope fields (`globs` for Claude, `applyTo` for Copilot).\n4. Report any drift found (for example, rule exists but no matching instruction, or vice versa).\n\n---\n\n## Quality Gate\n\n- No rule or instruction is written without frontmatter and a `description` field.\n- Soft delete is always the default for `delete` operations.\n- Both platform files must be written or updated together unless scope is explicitly restricted.\n- Never read or modify `.env` or sensitive configuration files.\n",{"name":5,"description":7},"main","00b2c68281930728ee390bb16cec32b88d2caac7",".claude\u002Fskills\u002Frules-management","https:\u002F\u002Fgithub.com\u002Frafsanulhasan\u002FHypermediaEngine","https:\u002F\u002Fgithub.com\u002Frafsanulhasan","\r\n    MCSD || A-CSD || Software Architect\r\n\r\n","2026-06-06 07:47:06",{"source":8,"skillName":5,"commands":51,"prompt":61,"zipAvailable":62},[52,55,58],{"tool":53,"command":54},"npx","npx skills add rafsanulhasan\u002FHypermediaEngine --skill rules-management",{"tool":56,"command":57},"bunx","bunx skills add rafsanulhasan\u002FHypermediaEngine --skill rules-management",{"tool":59,"command":60},"pnpm","pnpm dlx skills add rafsanulhasan\u002FHypermediaEngine --skill rules-management","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Frafsanulhasan\u002FHypermediaEngine\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Frules-management\u002FSKILL.md",true,[],[65,97,115,134,162,185],{"skillNo":66,"name":67,"nameZh":6,"description":68,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":69,"categories":70,"keywords":76,"publishedAt":38},"01M6KWEJD606FG3DBBRM0W4DKW","write-tests","Test implementation skill for HypermediaEngine. Takes a confirmed test plan from design-test-cases and produces compilable, runnable xUnit tests following project conventions. Validates coverage quality through mutation testing. Invoked by the sqa-engineer agent after the test plan is approved.","https:\u002F\u002Fgithub.com\u002Frafsanulhasan\u002FHypermediaEngine\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fwrite-tests\u002FSKILL.md",[71],{"categoryNo":72,"categoryName":73,"taxonomyType":74,"taxonomyTypeDesc":75},"01JBSEEDCAT000000000000008","测试与质量","SCENARIO","使用场景",[77,78,79,80,81,82,83,84,85,86,87,88,89,90,91,92,93,94,95,96],"write tests","write","tests","testing","design","test","project conventions","test plan","Bash","plan","quality","xunit","read","edit","coverage","engineer","mutation testing","project","mutation","for",{"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":103,"publishedAt":38},"01M6KWEF2XQ00C1Y6QCK7YHZ1H","write-documentation","Structured documentation writing workflow for HypermediaEngine. Writes or updates README.md files at the repo root and in each project directory (src\u002F, tests\u002F, samples\u002F, etc.) based on current implementation, ADRs, and architecture decisions.","https:\u002F\u002Fgithub.com\u002Frafsanulhasan\u002FHypermediaEngine\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fwrite-documentation\u002FSKILL.md",[],[104,78,105,106,107,37,108,85,109,110,111,112,89,90,26,94,79,113,114,96],"documentation","write documentation","writing","directory","architecture","src","repo","decisions","README","updates","at",{"skillNo":116,"name":117,"nameZh":6,"description":118,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":119,"categories":120,"keywords":121,"publishedAt":38},"01M6KWEBDXTXAVPQ3BHS3YYYNT","write-adr","Writes a numbered Architecture Decision Record (ADR) for a significant architectural choice in the HypermediaEngine project. Invoked by the software-architect agent whenever a consequential design decision is made or ratified. Saves the ADR to docs\u002Farchitecture\u002Fdecisions\u002F.","https:\u002F\u002Fgithub.com\u002Frafsanulhasan\u002FHypermediaEngine\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fwrite-adr\u002FSKILL.md",[],[122,78,123,81,124,108,125,126,127,128,111,89,129,130,94,131,132,96,133],"adr","write adr","docs","architect","decision","choice","grep","architecture decision record","record","software","opus","architecture decision",{"skillNo":135,"name":136,"nameZh":6,"description":137,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":138,"categories":139,"keywords":146,"publishedAt":38},"01M6KWE76TM3QHGQ08PEB3KY6D","tunit-playwright-ui-testing","Comprehensive guidance for writing coded end-to-end UI tests in C# using TUnit.Playwright. Tests inherit from PageTest — the base class manages all browser lifecycle. Covers NuGet setup, PageTest inheritance, Page Object Model, browser configuration, parallelism limiting, and CI integration. Based on the official TUnit docs at https:\u002F\u002Ftunit.dev\u002Fdocs\u002Fexamples\u002Fplaywright.","https:\u002F\u002Fgithub.com\u002Frafsanulhasan\u002FHypermediaEngine\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Ftunit-playwright-ui-testing\u002FSKILL.md",[140,141],{"categoryNo":72,"categoryName":73,"taxonomyType":74,"taxonomyTypeDesc":75},{"categoryNo":142,"categoryName":143,"taxonomyType":144,"taxonomyTypeDesc":145},"01JBSEEDCAT000000000000032","设计师","PROFESSION","适用职业",[80,147,148,149,150,151,152,106,153,154,155,156,22,157,158,159,79,160,161,96],"playwright","ui","playwright ui testing","ui testing","tunit","tunit playwright ui testing","official","dev","examples","ci","model","page","inheritance","end","object",{"skillNo":163,"name":164,"nameZh":6,"description":165,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":166,"categories":167,"keywords":171,"publishedAt":38},"01M6KWE44A738GDK65QS02XJBG","triage","Task classification, decomposition, dependency mapping, and routing skill. Invoked by the triage-agent to break any user request into discrete, independently-routable work items with assigned priorities and agent chains.","https:\u002F\u002Fgithub.com\u002Frafsanulhasan\u002FHypermediaEngine\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Ftriage\u002FSKILL.md",[168],{"categoryNo":169,"categoryName":170,"taxonomyType":74,"taxonomyTypeDesc":75},"01JBSEEDCAT000000000000023","Skill与智能体开发",[164,172,173,174,175,176,177,178,179,180,181,182,183,184],"routing","classification","work","user","dependency","task","priorities","decomposition","user request","mapping","with","break","request",{"skillNo":186,"name":187,"nameZh":6,"description":188,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":189,"categories":190,"keywords":195,"publishedAt":38},"01M6KWDZ3W9ZKPR7FTTTSX8H2K","system-design","Expert system design skill. Use PROACTIVELY to design systems, review architectures, and assist software engineers in learning design principles and implementing them in the code with design patterns.","https:\u002F\u002Fgithub.com\u002Frafsanulhasan\u002FHypermediaEngine\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fsystem-design\u002FSKILL.md",[191,194],{"categoryNo":192,"categoryName":193,"taxonomyType":74,"taxonomyTypeDesc":75},"01JBSEEDCAT000000000000015","视觉设计",{"categoryNo":142,"categoryName":143,"taxonomyType":144,"taxonomyTypeDesc":145},[81,196,197,198,199,200,201,128,89,202,203,204,205,206,207,131,208,209,182,210],"system","system design","web","design systems","learning","haiku","use","design patterns","design principles","expert","patterns","systems","architectures","principles","implementing"]