[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6X7HMRMEXB2QVTQ19CP85B7":3,"skill-same:01M6X7HMRMEXB2QVTQ19CP85B7":73},{"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":23,"publishedAt":40,"linkOnly":41,"markdownContent":42,"markdownBody":43,"frontMatter":44,"refName":50,"commitSha":51,"skillDirectory":52,"forksCount":53,"repositoryHtmlUrl":54,"repositoryHomepageUrl":55,"ownerHtmlUrl":56,"ownerBlogUrl":55,"ownerDescription":57,"updatedAt":58,"install":59,"resources":72},"01M6X7HMRMEXB2QVTQ19CP85B7","project-docs",null,"Use when looking for project-specific documentation. Knows which docs exist in agents\u002Freference\u002Fdocs\u002F and agents\u002Fsettings\u002Fcontexts\u002F and maps work areas to relevant docs.","event4u-app\u002Fagent-config","event4u-app","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F199339632?v=4","01M6X5TWBNCQCE1VDKT4E9KF7N","event4u.app","01M6X5TWF4HRM266RG2Q5VVH1X",19,"MIT","https:\u002F\u002Fgithub.com\u002Fevent4u-app\u002Fagent-config\u002Fblob\u002Fmain\u002Fsrc\u002Fskills\u002Fproject-docs\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39],"docs","project","project docs","config","documentation","Meta","work","settings","process","use","reference","maps","relevant","which","for","when","2026-11-10 10:12:30",false,"---\nmodel_tier: medium\nname: project-docs\ndescription: \"Use when looking for project-specific documentation. Knows which docs exist in agents\u002Freference\u002Fdocs\u002F and agents\u002Fsettings\u002Fcontexts\u002F and maps work areas to relevant docs.\"\ndomain: process\nworkspaces:\n  - agent-config-maintainer\npacks:\n  - meta\n---\n\n# project-docs\n\n## When to use\n\nUse this skill when:\n- Starting work on an unfamiliar area of the codebase\n- Need to find relevant documentation for a specific module or feature\n- Want to understand project-specific patterns before making changes\n\nDo NOT use when:\n- Looking for coding guidelines (use `guidelines` skill)\n- Looking for infrastructure docs (use `aws-infrastructure` or `docker` skill)\n\n## Description\n\nThis skill maps work areas to their relevant project documentation. It ensures agents\nconsult the right docs before making changes — preventing mistakes that come from not\nunderstanding project-specific patterns, legacy conventions, or architectural decisions.\n\n## When to Activate\n\n- Before working on **any** area that has project-specific documentation\n- When an agent is unsure about project conventions for a specific domain\n- When creating or modifying code in areas covered by these docs\n\n## Procedure: Find project documentation\n\n1. Identify the work area from the user's request.\n2. Look up the relevant docs in the mapping table below.\n3. Read the **context** first (quick orientation), then the **detail docs** if needed.\n4. Follow the conventions described in the docs.\n\n## Documentation Structure\n\n```\nagents\u002F\n├── contexts\u002F          → Quick orientation (read first)\n│   ├── *.md           → Technical contexts (multi-tenancy, API versioning, etc.)\n│   └── domain\u002F        → Domain\u002Findustry knowledge (business logic, terminology)\n│       └── job-*.md   → Domain context files (e.g., job-time-tracking.md)\n├── docs\u002F              → Deep dives (read when working on the area)\n│   └── *.md           → Detailed conventions per topic\n├── features\u002F          → Feature plans\n├── roadmaps\u002F          → Step-by-step work plans\n├── sessions\u002F          → Session tracking\n└── overrides\u002F         → Project-specific overrides of .augment\u002F resources\n```\n\n## Domain Contexts\n\nIf `agents\u002Fsettings\u002Fcontexts\u002Fdomain\u002F` exists, it contains **business domain knowledge** — industry terms,\nregulations, workflows, and edge cases that the agent needs to understand the problem space.\n\n**When to read domain contexts:**\n- Before working on any feature that touches business logic\n- When you encounter domain-specific terms you don't fully understand\n- When writing validations, business rules, or data models for a specific domain\n\n**How to find the right file:**\n- List `agents\u002Fsettings\u002Fcontexts\u002Fdomain\u002F` and read files whose name matches the work area\n- Files prefixed with `job-` describe industry\u002Fprofession knowledge\n- When in doubt, read all domain context files — they are short orientation docs\n\n## How to Find Relevant Docs\n\n1. **List `agents\u002Fsettings\u002Fcontexts\u002F`** — read any context file whose name matches the work area.\n2. **List `agents\u002Fsettings\u002Fcontexts\u002Fdomain\u002F`** — read domain knowledge files relevant to the business logic.\n3. **List `agents\u002Freference\u002Fdocs\u002F`** — read detail docs for the specific topic you're working on.\n4. **Check module docs** — if working in a module, resolve `{module_root}` from\n   `modules.root_paths` and `{agent_folder}` from `modules.agent_folder` (see\n   `scripts\u002F_lib\u002Fagent_settings.ts::enumerate_modules()`), then check:\n   - `{module_root}\u002F{Module}\u002F{agent_folder}\u002F` — module-specific docs\n   - `{module_root}\u002F{Module}\u002F{agent_folder}\u002Fsettings\u002Fcontexts\u002F` — module-specific contexts (if exists)\n   - `{module_root}\u002F{Module}\u002F{agent_folder}\u002Fsettings\u002Fcontexts\u002Fdomain\u002F` — module-specific domain knowledge (if exists)\n\n### Reading order\n\n| Step | What | Why |\n|---|---|---|\n| 1 | `agents\u002Fsettings\u002Fcontexts\u002F*.md` | Quick orientation — big picture in ~100 lines |\n| 2 | `agents\u002Fsettings\u002Fcontexts\u002Fdomain\u002Fjob-*.md` | Domain knowledge — business terms, rules, edge cases |\n| 3 | Module `agents\u002Fsettings\u002Fcontexts\u002F` | Module-specific contexts (if working in a module) |\n| 4 | `agents\u002Freference\u002Fdocs\u002F*.md` | Deep dive — code examples, conventions, patterns |\n\n### Matching work areas to docs\n\nMatch by **filename** — doc filenames describe their topic. Examples:\n- Working on API endpoints → look for `controller`, `api-*`, `middleware`, `authentication` docs\n- Working on database → look for `database-*`, `multi-tenancy`, `customer-*` docs\n- Working on time tracking → look for `job-time-tracking` in domain contexts\n- Working on tests → look for `testing`, `seeders` docs\n\nDo NOT hardcode a mapping — always **list the directory** and pick by relevance.\n\n## Rules\n\n- **Always read the context first** — it gives you the big picture in ~100 lines.\n- **Read detail docs when you need to write code** — they have code examples and conventions.\n- **Don't skip docs because you \"know\" the pattern** — project-specific conventions often differ\n  from standard framework patterns.\n- **Update docs when you change conventions** — if your change introduces a new pattern or\n  deprecates an old one, update the relevant doc in `agents\u002Freference\u002Fdocs\u002F`.\n\n## Cross-References\n\n| Skill | Relationship |\n|---|---|\n| `agent-docs-writing` | When to read\u002Fcreate\u002Fupdate agent docs in general |\n| `context-create` | How to create new context documents |\n| `module-management` | Module-specific docs in module `agents\u002F` directories |\n\n\n## Output format\n\n1. Relevant doc paths and their key content summarized\n2. Recommendation for which docs to read for the current task\n\n## Gotcha\n\n- Project docs are NOT the same as agent docs — project docs describe the codebase, agent docs describe agent behavior.\n- Don't assume a doc exists because the area is important — always check the filesystem first.\n- Stale docs are worse than missing docs — always verify doc content against actual code.\n\n## Do NOT\n\n- Do NOT create documentation that duplicates existing docs.\n- Do NOT write docs for trivial or self-explanatory code.\n\n## Auto-trigger keywords\n\n- project documentation\n- doc mapping\n- work area docs\n","# project-docs\n\n## When to use\n\nUse this skill when:\n- Starting work on an unfamiliar area of the codebase\n- Need to find relevant documentation for a specific module or feature\n- Want to understand project-specific patterns before making changes\n\nDo NOT use when:\n- Looking for coding guidelines (use `guidelines` skill)\n- Looking for infrastructure docs (use `aws-infrastructure` or `docker` skill)\n\n## Description\n\nThis skill maps work areas to their relevant project documentation. It ensures agents\nconsult the right docs before making changes — preventing mistakes that come from not\nunderstanding project-specific patterns, legacy conventions, or architectural decisions.\n\n## When to Activate\n\n- Before working on **any** area that has project-specific documentation\n- When an agent is unsure about project conventions for a specific domain\n- When creating or modifying code in areas covered by these docs\n\n## Procedure: Find project documentation\n\n1. Identify the work area from the user's request.\n2. Look up the relevant docs in the mapping table below.\n3. Read the **context** first (quick orientation), then the **detail docs** if needed.\n4. Follow the conventions described in the docs.\n\n## Documentation Structure\n\n```\nagents\u002F\n├── contexts\u002F          → Quick orientation (read first)\n│   ├── *.md           → Technical contexts (multi-tenancy, API versioning, etc.)\n│   └── domain\u002F        → Domain\u002Findustry knowledge (business logic, terminology)\n│       └── job-*.md   → Domain context files (e.g., job-time-tracking.md)\n├── docs\u002F              → Deep dives (read when working on the area)\n│   └── *.md           → Detailed conventions per topic\n├── features\u002F          → Feature plans\n├── roadmaps\u002F          → Step-by-step work plans\n├── sessions\u002F          → Session tracking\n└── overrides\u002F         → Project-specific overrides of .augment\u002F resources\n```\n\n## Domain Contexts\n\nIf `agents\u002Fsettings\u002Fcontexts\u002Fdomain\u002F` exists, it contains **business domain knowledge** — industry terms,\nregulations, workflows, and edge cases that the agent needs to understand the problem space.\n\n**When to read domain contexts:**\n- Before working on any feature that touches business logic\n- When you encounter domain-specific terms you don't fully understand\n- When writing validations, business rules, or data models for a specific domain\n\n**How to find the right file:**\n- List `agents\u002Fsettings\u002Fcontexts\u002Fdomain\u002F` and read files whose name matches the work area\n- Files prefixed with `job-` describe industry\u002Fprofession knowledge\n- When in doubt, read all domain context files — they are short orientation docs\n\n## How to Find Relevant Docs\n\n1. **List `agents\u002Fsettings\u002Fcontexts\u002F`** — read any context file whose name matches the work area.\n2. **List `agents\u002Fsettings\u002Fcontexts\u002Fdomain\u002F`** — read domain knowledge files relevant to the business logic.\n3. **List `agents\u002Freference\u002Fdocs\u002F`** — read detail docs for the specific topic you're working on.\n4. **Check module docs** — if working in a module, resolve `{module_root}` from\n   `modules.root_paths` and `{agent_folder}` from `modules.agent_folder` (see\n   `scripts\u002F_lib\u002Fagent_settings.ts::enumerate_modules()`), then check:\n   - `{module_root}\u002F{Module}\u002F{agent_folder}\u002F` — module-specific docs\n   - `{module_root}\u002F{Module}\u002F{agent_folder}\u002Fsettings\u002Fcontexts\u002F` — module-specific contexts (if exists)\n   - `{module_root}\u002F{Module}\u002F{agent_folder}\u002Fsettings\u002Fcontexts\u002Fdomain\u002F` — module-specific domain knowledge (if exists)\n\n### Reading order\n\n| Step | What | Why |\n|---|---|---|\n| 1 | `agents\u002Fsettings\u002Fcontexts\u002F*.md` | Quick orientation — big picture in ~100 lines |\n| 2 | `agents\u002Fsettings\u002Fcontexts\u002Fdomain\u002Fjob-*.md` | Domain knowledge — business terms, rules, edge cases |\n| 3 | Module `agents\u002Fsettings\u002Fcontexts\u002F` | Module-specific contexts (if working in a module) |\n| 4 | `agents\u002Freference\u002Fdocs\u002F*.md` | Deep dive — code examples, conventions, patterns |\n\n### Matching work areas to docs\n\nMatch by **filename** — doc filenames describe their topic. Examples:\n- Working on API endpoints → look for `controller`, `api-*`, `middleware`, `authentication` docs\n- Working on database → look for `database-*`, `multi-tenancy`, `customer-*` docs\n- Working on time tracking → look for `job-time-tracking` in domain contexts\n- Working on tests → look for `testing`, `seeders` docs\n\nDo NOT hardcode a mapping — always **list the directory** and pick by relevance.\n\n## Rules\n\n- **Always read the context first** — it gives you the big picture in ~100 lines.\n- **Read detail docs when you need to write code** — they have code examples and conventions.\n- **Don't skip docs because you \"know\" the pattern** — project-specific conventions often differ\n  from standard framework patterns.\n- **Update docs when you change conventions** — if your change introduces a new pattern or\n  deprecates an old one, update the relevant doc in `agents\u002Freference\u002Fdocs\u002F`.\n\n## Cross-References\n\n| Skill | Relationship |\n|---|---|\n| `agent-docs-writing` | When to read\u002Fcreate\u002Fupdate agent docs in general |\n| `context-create` | How to create new context documents |\n| `module-management` | Module-specific docs in module `agents\u002F` directories |\n\n\n## Output format\n\n1. Relevant doc paths and their key content summarized\n2. Recommendation for which docs to read for the current task\n\n## Gotcha\n\n- Project docs are NOT the same as agent docs — project docs describe the codebase, agent docs describe agent behavior.\n- Don't assume a doc exists because the area is important — always check the filesystem first.\n- Stale docs are worse than missing docs — always verify doc content against actual code.\n\n## Do NOT\n\n- Do NOT create documentation that duplicates existing docs.\n- Do NOT write docs for trivial or self-explanatory code.\n\n## Auto-trigger keywords\n\n- project documentation\n- doc mapping\n- work area docs\n",{"name":5,"packs":45,"domain":32,"model_tier":47,"workspaces":48,"description":7},[46],"meta","medium",[49],"agent-config-maintainer","main","12bd765ce1d800501d45dfb8232102793af01290","src\u002Fskills\u002Fproject-docs",1,"https:\u002F\u002Fgithub.com\u002Fevent4u-app\u002Fagent-config","https:\u002F\u002Fevent4u.app","https:\u002F\u002Fgithub.com\u002Fevent4u-app","Your events in your hand","2026-11-14 02:29:41",{"source":8,"skillName":5,"commands":60,"prompt":70,"zipAvailable":71},[61,64,67],{"tool":62,"command":63},"npx","npx skills add event4u-app\u002Fagent-config --skill project-docs",{"tool":65,"command":66},"bunx","bunx skills add event4u-app\u002Fagent-config --skill project-docs",{"tool":68,"command":69},"pnpm","pnpm dlx skills add event4u-app\u002Fagent-config --skill project-docs","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fevent4u-app\u002Fagent-config\u002Fblob\u002Fmain\u002Fsrc\u002Fskills\u002Fproject-docs\u002FSKILL.md",true,[],[74,88,101,113,125,135],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":81,"publishedAt":40},"01M6X84PK96XBPENXH66JCTSD1","unknown-key-fixture","Declares a key the schema does not know.","https:\u002F\u002Fgithub.com\u002Fevent4u-app\u002Fagent-config\u002Fblob\u002Fmain\u002Ftests\u002Fscripts\u002Ffixtures\u002Fbody-portable\u002Funknown-key\u002FSKILL.md",[80],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[82,83,84,85,86,87],"unknown key fixture","Unknown key","fixture","unknown","schema","package",{"skillNo":89,"name":90,"nameZh":6,"description":91,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":92,"categories":93,"keywords":95,"publishedAt":40},"01M6X84HW7NAHZ7GZMQ9RXK1XJ","portable-fixture","Declares only semantics the MCP-lite carrier transports whole.","https:\u002F\u002Fgithub.com\u002Fevent4u-app\u002Fagent-config\u002Fblob\u002Fmain\u002Ftests\u002Fscripts\u002Ffixtures\u002Fbody-portable\u002Fportable\u002FSKILL.md",[94],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[84,96,97,98,99,87,100],"portable","portable fixture","engineer","only","MCP",{"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":108,"publishedAt":40},"01M6X84F29FE0RGGZ1ZTFGZTX2","non-portable-fixture","Declares a runtime semantic the carrier drops.","https:\u002F\u002Fgithub.com\u002Fevent4u-app\u002Fagent-config\u002Fblob\u002Fmain\u002Ftests\u002Fscripts\u002Ffixtures\u002Fbody-portable\u002Fnon-portable\u002FSKILL.md",[107],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[97,109,96,84,110,111,112,87],"non portable fixture","semantic","high","runtime",{"skillNo":114,"name":115,"nameZh":6,"description":116,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":117,"categories":118,"keywords":120,"publishedAt":40},"01M6X848F706PT9MDCX75JKJ6B","candidate-zero-width","A candidate whose prose carries an invisible joiner.","https:\u002F\u002Fgithub.com\u002Fevent4u-app\u002Fagent-config\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fskill-scout-candidates\u002Fzero-width-injection\u002FSKILL.md",[119],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[121,122,123,124],"candidate zero width","candidate","ZeRO","prose",{"skillNo":126,"name":127,"nameZh":6,"description":128,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":129,"categories":130,"keywords":132,"publishedAt":40},"01M6X841SSC2T31VDF41SA6DG1","candidate-disclosure-suppression","A candidate whose prose tells the agent to withhold from the user.","https:\u002F\u002Fgithub.com\u002Fevent4u-app\u002Fagent-config\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fskill-scout-candidates\u002Fdisclosure-suppression\u002FSKILL.md",[131],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[133,122,124,134],"candidate disclosure suppression","user",{"skillNo":136,"name":137,"nameZh":6,"description":138,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":139,"categories":140,"keywords":142,"publishedAt":40},"01M6X83TFS5AGPBPVTQNWP0BB3","candidate-dangerous-frontmatter","A candidate claiming an unscoped tool grant and a permission bypass.","https:\u002F\u002Fgithub.com\u002Fevent4u-app\u002Fagent-config\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fskill-scout-candidates\u002Fdangerous-frontmatter\u002FSKILL.md",[141],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[143,122,144,145,146,147],"candidate dangerous frontmatter","frontmatter","shell","permission","tool"]