[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7DEX2FQR89DB4B44P5XJ4S0":3,"skill-same:01M7DEX2FQR89DB4B44P5XJ4S0":55},{"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":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":30,"install":31,"resources":44},"01M7DEX2FQR89DB4B44P5XJ4S0","context-discovery",null,"Use when a user asks for repository orientation or onboarding: map an unfamiliar codebase's structure, entry points, key modules, tests or verification flow, even when no change is requested. Also use when starting discovery for a change or locating what an existing task may affect.","andersonmrodrigues\u002Fpaved","andersonmrodrigues","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F13907380?v=4","01M7DEV3FP2VMQZ3FP2FP1TK1C","Anderson Rodrigues","01M7DEV3GC2QAQBW4FMNT98H48",1,"MIT","https:\u002F\u002Fgithub.com\u002Fandersonmrodrigues\u002Fpaved\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Fdiscovery\u002Fcontext-discovery\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: context-discovery\ndescription: >-\n  Use when a user asks for repository orientation or onboarding: map an unfamiliar codebase's structure, entry points, key modules, tests or verification flow, even when no change is requested. Also use when starting discovery for a change or locating what an existing task may affect.\n---\n\n# Context discovery\n\n## When to use\n\nAt the start of every workflow (`context` and `discovery` phases), during onboarding, and\nagain whenever the task turns out to touch something you have not read. Discovery\nchanges nothing; it produces understanding and a list of unknowns.\n\n## Required context\n\nNone is required. Use what exists: `manifest` first, then `feature-map`, and the\n`architecture`, `technology`, `rules` and `verification` areas only as the task needs\nthem. In a repository without Paved, the repository itself is the only source.\n\n## Preconditions\n\nThe task, or the purpose of the investigation, can be stated in a sentence. If not, ask\nbefore exploring.\n\n## Procedure\n\n1. **Restate the goal** in one or two sentences, including what is out of scope.\n2. **Use Project Context first when it exists.** Look the feature up in the feature map\n   by name, path or entrypoint and read only the documents its entry links to.\n3. **Survey the repository** when there is no context, or the context does not cover the\n   code: walk the signals in\n   [references\u002Frepository-signals.md](references\u002Frepository-signals.md) in order, and\n   stop as soon as you can answer the goal.\n4. **Follow the code path** from an entry point to the code the task affects. Prefer\n   reading code over reading summaries of code.\n5. **Find a sibling** that already solves a similar problem (same layer, same kind of\n   change). That is the pattern to follow.\n6. **List rules in scope**: project and Core rules whose `applies_to` matches the files\n   you expect to change.\n7. **Check freshness.** When a context document's recorded sources changed since it was\n   generated, confirm its claims in the code before relying on them.\n8. **Write the unknowns down.** Ask about the ones that change the plan; record the rest.\n\n## Tools\n\n`core.repository.status` shows local changes that may affect the task. `core.repository.history` shows\nwhere recent work happened and who changed the area. `core.repository.diff` shows what those\nchanges did.\n\n## Rules\n\n`core.architecture.follow-existing-patterns` is why step 5 exists.\n`core.quality.unknowns-stay-unknown` is why step 8 exists.\n\n## Verification\n\nDiscovery produces no code and has no checks. Its output is judged by the steps that use\nit: did the plan name the affected files, the pattern followed and the unknowns?\n\n## Evidence\n\nNone of its own. The summary (files read, pattern chosen, rules in scope, unknowns) goes\ninto the plan that the next phase works from.\n\n## Completion criteria\n\n- The affected files and the pattern to follow are named.\n- Applicable rules are listed.\n- Unknowns that affect the plan are resolved or explicitly accepted.\n\n## Failure modes\n\n| Failure | Signal | Response |\n|---|---|---|\n| Context overload | Reading documents unrelated to the goal | Return to the feature map; follow links only |\n| Survey without end | Every signal is being read regardless of the goal | Stop at the first signal that answers it |\n| Stale context | Context disagrees with code | Trust the code; report the discrepancy |\n| No feature entry | Feature map has nothing relevant | Search code by names in the task; suggest an entry |\n\n## References\n\n- [references\u002Frepository-signals.md](references\u002Frepository-signals.md): where to look,\n  and what each signal tells you.\n","# Context discovery\n\n## When to use\n\nAt the start of every workflow (`context` and `discovery` phases), during onboarding, and\nagain whenever the task turns out to touch something you have not read. Discovery\nchanges nothing; it produces understanding and a list of unknowns.\n\n## Required context\n\nNone is required. Use what exists: `manifest` first, then `feature-map`, and the\n`architecture`, `technology`, `rules` and `verification` areas only as the task needs\nthem. In a repository without Paved, the repository itself is the only source.\n\n## Preconditions\n\nThe task, or the purpose of the investigation, can be stated in a sentence. If not, ask\nbefore exploring.\n\n## Procedure\n\n1. **Restate the goal** in one or two sentences, including what is out of scope.\n2. **Use Project Context first when it exists.** Look the feature up in the feature map\n   by name, path or entrypoint and read only the documents its entry links to.\n3. **Survey the repository** when there is no context, or the context does not cover the\n   code: walk the signals in\n   [references\u002Frepository-signals.md](references\u002Frepository-signals.md) in order, and\n   stop as soon as you can answer the goal.\n4. **Follow the code path** from an entry point to the code the task affects. Prefer\n   reading code over reading summaries of code.\n5. **Find a sibling** that already solves a similar problem (same layer, same kind of\n   change). That is the pattern to follow.\n6. **List rules in scope**: project and Core rules whose `applies_to` matches the files\n   you expect to change.\n7. **Check freshness.** When a context document's recorded sources changed since it was\n   generated, confirm its claims in the code before relying on them.\n8. **Write the unknowns down.** Ask about the ones that change the plan; record the rest.\n\n## Tools\n\n`core.repository.status` shows local changes that may affect the task. `core.repository.history` shows\nwhere recent work happened and who changed the area. `core.repository.diff` shows what those\nchanges did.\n\n## Rules\n\n`core.architecture.follow-existing-patterns` is why step 5 exists.\n`core.quality.unknowns-stay-unknown` is why step 8 exists.\n\n## Verification\n\nDiscovery produces no code and has no checks. Its output is judged by the steps that use\nit: did the plan name the affected files, the pattern followed and the unknowns?\n\n## Evidence\n\nNone of its own. The summary (files read, pattern chosen, rules in scope, unknowns) goes\ninto the plan that the next phase works from.\n\n## Completion criteria\n\n- The affected files and the pattern to follow are named.\n- Applicable rules are listed.\n- Unknowns that affect the plan are resolved or explicitly accepted.\n\n## Failure modes\n\n| Failure | Signal | Response |\n|---|---|---|\n| Context overload | Reading documents unrelated to the goal | Return to the feature map; follow links only |\n| Survey without end | Every signal is being read regardless of the goal | Stop at the first signal that answers it |\n| Stale context | Context disagrees with code | Trust the code; report the discrepancy |\n| No feature entry | Feature map has nothing relevant | Search code by names in the task; suggest an entry |\n\n## References\n\n- [references\u002Frepository-signals.md](references\u002Frepository-signals.md): where to look,\n  and what each signal tells you.\n",{"name":5,"description":7},"main","1cd80f05aff924ea609012e864fa5c22c16c7d2d","core\u002Fskills\u002Fdiscovery\u002Fcontext-discovery",0,"https:\u002F\u002Fgithub.com\u002Fandersonmrodrigues\u002Fpaved","https:\u002F\u002Fgithub.com\u002Fandersonmrodrigues","2026-11-14 20:09:28",{"source":8,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add andersonmrodrigues\u002Fpaved --skill context-discovery",{"tool":37,"command":38},"bunx","bunx skills add andersonmrodrigues\u002Fpaved --skill context-discovery",{"tool":40,"command":41},"pnpm","pnpm dlx skills add andersonmrodrigues\u002Fpaved --skill context-discovery","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fandersonmrodrigues\u002Fpaved\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Fdiscovery\u002Fcontext-discovery\u002FSKILL.md",true,[45,51],{"path":46,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":49,"sourceHtmlUrl":50},"references\u002Frepository-signals.md","REFERENCE","参考文档",3011,"https:\u002F\u002Fgithub.com\u002Fandersonmrodrigues\u002Fpaved\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Fdiscovery\u002Fcontext-discovery\u002Freferences\u002Frepository-signals.md",{"path":52,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":53,"sourceHtmlUrl":54},"skill.yaml",531,"https:\u002F\u002Fgithub.com\u002Fandersonmrodrigues\u002Fpaved\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Fdiscovery\u002Fcontext-discovery\u002Fskill.yaml",[56,63,69,75,81,87],{"skillNo":57,"name":58,"nameZh":6,"description":59,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":60,"categories":61,"keywords":62,"publishedAt":19},"01M7DFBWJT4T1MPBHTWT19PBEK","sample-skill","Does a sample task. Use when a sample is needed.","https:\u002F\u002Fgithub.com\u002Fandersonmrodrigues\u002Fpaved\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fskills\u002Fvalid\u002Fsample-skill\u002FSKILL.md",[],[],{"skillNo":64,"name":65,"nameZh":6,"description":59,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":66,"categories":67,"keywords":68,"publishedAt":19},"01M7DFBS6WTK30PBSW4ZS0NPWT","unexplained-contract","https:\u002F\u002Fgithub.com\u002Fandersonmrodrigues\u002Fpaved\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fskills\u002Finvalid\u002Funexplained-contract\u002FSKILL.md",[],[],{"skillNo":70,"name":71,"nameZh":6,"description":59,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":19},"01M7DFBPJGG170V9WTMFWY73R4","shell-block","https:\u002F\u002Fgithub.com\u002Fandersonmrodrigues\u002Fpaved\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fskills\u002Finvalid\u002Fshell-block\u002FSKILL.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":59,"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":80,"publishedAt":19},"01M7DFBMZYR20JPTXNE5A8EFG6","project-identifier","https:\u002F\u002Fgithub.com\u002Fandersonmrodrigues\u002Fpaved\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fskills\u002Finvalid\u002Fproject-identifier\u002FSKILL.md",[],[],{"skillNo":82,"name":83,"nameZh":6,"description":59,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":19},"01M7DFBJ8J533DAKA3FTF54SX3","oversized","https:\u002F\u002Fgithub.com\u002Fandersonmrodrigues\u002Fpaved\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fskills\u002Finvalid\u002Foversized\u002FSKILL.md",[],[],{"skillNo":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":91,"categories":92,"keywords":93,"publishedAt":19},"01M7DFBFAD0RYCRHTZ2JW4RX7E","no-activation","Does a sample task.","https:\u002F\u002Fgithub.com\u002Fandersonmrodrigues\u002Fpaved\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fskills\u002Finvalid\u002Fno-activation\u002FSKILL.md",[],[]]