[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6BX4SD76X75HF96WRXZ395T":3,"skill-same:01M6BX4SD76X75HF96WRXZ395T":87},{"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":44,"linkOnly":45,"markdownContent":46,"markdownBody":47,"frontMatter":48,"refName":51,"commitSha":52,"skillDirectory":53,"forksCount":14,"repositoryHtmlUrl":54,"repositoryHomepageUrl":6,"ownerHtmlUrl":55,"ownerBlogUrl":56,"ownerDescription":57,"updatedAt":58,"install":59,"resources":72},"01M6BX4SD76X75HF96WRXZ395T","code-style",null,"Review, write, and edit non-trivial code using the project's conventions and these code style rules. Read the applicable language reference. For read-only reviews, report findings without edits; run change-verification checks after editing.","yrahul3910\u002Fdotfiles","yrahul3910","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F8930954?v=4","01M6BX4Q28SQREB3XFY3BAQ6YC","Rahul Yedida","01M6BX4Q737JXBCN69KPPT5TG9",0,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fyrahul3910\u002Fdotfiles\u002Fblob\u002Fmaster\u002F.agents\u002Fskills\u002Fcode-style\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43],"code style","code","style","write","for","reviews","read-only","project","conventions","reference","only","edit","review","read","editing","Rules","verification","report","run","change","2026-11-10 10:12:30",false,"---\nname: add-seed-data\ndescription: \"Creates or updates believable deterministic raw fixture scenarios without breaking an existing prototype. Use when asked to add or change fixtures, seed data, sample data, scenarios, or cross-record relationships. Not for UI redesign, live-data infrastructure, or unrelated commands.\"\n---\n\n# Add seed data\n\n## Resolve the target\n\nResolve an explicit target first: a fixture, scenario, page or surface.\nOtherwise use the known current target and consumer-declared entry points.\nAsk only when the target or requested scenario is consequential and unknown.\nPreserve the original request and answers. Do not infer a route, duplicate a\nprototype or scaffold a missing surface. Report an absent target before edits.\n\nBefore implementation, read the required\n[context contract](.\u002Freferences\u002Fcontext.md) and its shared resolution owner.\nMissing required context or installed companions stops affected work with\nexact paths. Do not automatically run setup, install skills or activate context.\n\n## Update the smallest scenario\n\n1. Read the target's canonical fixtures, raw types if present, existing\n   data-to-view assembly and directly affected consumers\u002Ftests. Use the\n   consumer-declared locations and formats, not an assumed directory or JSON.\n2. Identify the smallest believable scenario from product context and the\n   request, including needed records, identities and relationships. Reuse\n   canonical fixtures before adding records. Preserve unaffected data and\n   existing scenario intent, including intentional empty or failure cases.\n3. Edit authored raw inputs only. Keep stable IDs, unique keys, consistent\n   cross-record references and deterministic values, order and timestamps\n   where relevant. Avoid runtime randomness, current-time drift and environment\n   dependence. Do not overwrite private data or copy secrets\u002Fprivate payloads\n   into fixtures. Use synthetic data or data explicitly authorized for this\n   purpose by the user or a public source, not merely accessible data.\n4. Keep derived counts, picker options, formatted values, grouping, filtering,\n   sorting and pagination output in the existing assembly layer. Do not write\n   assembled view models back to fixtures or invent missing domain collections\n   in components or loaders. Fixed UI text and enums may stay inline.\n5. Update raw types and assembly only when required by the requested shape,\n   not as a general refactor. A plain HTML\u002FJS consumer can use its existing\n   simple data-to-view function. No framework, schema system or generator is\n   required. Keep valid empty collections distinct from invalid relationships.\n   Expose actual invalid inputs through existing error behavior and focused\n   checks, never repair them with fabricated records or silent success.\n6. Remain static\u002Foffline compatible. Do not add APIs, capture scripts, network\n   access, credentials or a live-mode migration. For an already dual-source\n   consumer, preserve its single source-independent assembly, source reporting\n   and explicit fallback contracts. Do not turn failures into fake live success\n   or import another platform's runtime or URL protocol.\n7. Change the UI only if the requested shape actually requires it. Before\n   those edits, read the existing\n   [prototype authoring guidance](..\u002Fcreate-prototype\u002Freferences\u002Fauthoring.md)\n   and its required context. Follow applicable UI guidance for the scoped\n   change, not a redesign. Data-only changes skip this read and UI workflows.\n\n## Verify and report\n\nRun the narrow consumer-owned checks for raw format\u002Ftype validity, uniqueness,\nreferential integrity, derived behavior and the requested scenarios. Add focused\ntests through existing tooling when needed. Include relevant empty,\nsingle\u002Fmultiple and boundary records when applicable, not a mandatory matrix.\nCheck that unaffected canonical records and meaningful failure cases survive.\n\nIf rendered output changes, use the consumer-authorized preview behavior and\nrespect its visual approval\u002Fvalidation order. Do not assume a browser is\navailable. Static checks do not prove rendered correctness. Report unavailable\nchecks and unverified behavior explicitly rather than calling them passed.\n\nFollow consumer validation\u002Flifecycle and commit policy. Do not commit unless\nauthorized, publish automatically or treat fixture work as context activation.\nReturn the target, context document paths, scoped changes, checks actually run and results,\nplus remaining limits. No automatic independent review or infrastructure work.\n","# Add seed data\n\n## Resolve the target\n\nResolve an explicit target first: a fixture, scenario, page or surface.\nOtherwise use the known current target and consumer-declared entry points.\nAsk only when the target or requested scenario is consequential and unknown.\nPreserve the original request and answers. Do not infer a route, duplicate a\nprototype or scaffold a missing surface. Report an absent target before edits.\n\nBefore implementation, read the required\n[context contract](.\u002Freferences\u002Fcontext.md) and its shared resolution owner.\nMissing required context or installed companions stops affected work with\nexact paths. Do not automatically run setup, install skills or activate context.\n\n## Update the smallest scenario\n\n1. Read the target's canonical fixtures, raw types if present, existing\n   data-to-view assembly and directly affected consumers\u002Ftests. Use the\n   consumer-declared locations and formats, not an assumed directory or JSON.\n2. Identify the smallest believable scenario from product context and the\n   request, including needed records, identities and relationships. Reuse\n   canonical fixtures before adding records. Preserve unaffected data and\n   existing scenario intent, including intentional empty or failure cases.\n3. Edit authored raw inputs only. Keep stable IDs, unique keys, consistent\n   cross-record references and deterministic values, order and timestamps\n   where relevant. Avoid runtime randomness, current-time drift and environment\n   dependence. Do not overwrite private data or copy secrets\u002Fprivate payloads\n   into fixtures. Use synthetic data or data explicitly authorized for this\n   purpose by the user or a public source, not merely accessible data.\n4. Keep derived counts, picker options, formatted values, grouping, filtering,\n   sorting and pagination output in the existing assembly layer. Do not write\n   assembled view models back to fixtures or invent missing domain collections\n   in components or loaders. Fixed UI text and enums may stay inline.\n5. Update raw types and assembly only when required by the requested shape,\n   not as a general refactor. A plain HTML\u002FJS consumer can use its existing\n   simple data-to-view function. No framework, schema system or generator is\n   required. Keep valid empty collections distinct from invalid relationships.\n   Expose actual invalid inputs through existing error behavior and focused\n   checks, never repair them with fabricated records or silent success.\n6. Remain static\u002Foffline compatible. Do not add APIs, capture scripts, network\n   access, credentials or a live-mode migration. For an already dual-source\n   consumer, preserve its single source-independent assembly, source reporting\n   and explicit fallback contracts. Do not turn failures into fake live success\n   or import another platform's runtime or URL protocol.\n7. Change the UI only if the requested shape actually requires it. Before\n   those edits, read the existing\n   [prototype authoring guidance](..\u002Fcreate-prototype\u002Freferences\u002Fauthoring.md)\n   and its required context. Follow applicable UI guidance for the scoped\n   change, not a redesign. Data-only changes skip this read and UI workflows.\n\n## Verify and report\n\nRun the narrow consumer-owned checks for raw format\u002Ftype validity, uniqueness,\nreferential integrity, derived behavior and the requested scenarios. Add focused\ntests through existing tooling when needed. Include relevant empty,\nsingle\u002Fmultiple and boundary records when applicable, not a mandatory matrix.\nCheck that unaffected canonical records and meaningful failure cases survive.\n\nIf rendered output changes, use the consumer-authorized preview behavior and\nrespect its visual approval\u002Fvalidation order. Do not assume a browser is\navailable. Static checks do not prove rendered correctness. Report unavailable\nchecks and unverified behavior explicitly rather than calling them passed.\n\nFollow consumer validation\u002Flifecycle and commit policy. Do not commit unless\nauthorized, publish automatically or treat fixture work as context activation.\nReturn the target, context document paths, scoped changes, checks actually run and results,\nplus remaining limits. No automatic independent review or infrastructure work.\n",{"name":49,"description":50},"add-seed-data","Creates or updates believable deterministic raw fixture scenarios without breaking an existing prototype. Use when asked to add or change fixtures, seed data, sample data, scenarios, or cross-record relationships. Not for UI redesign, live-data infrastructure, or unrelated commands.","main","0e8bdbd952ce0d93c8976876fa59e9f119614ae8",".agents\u002Fskills\u002Fcode-style","https:\u002F\u002Fgithub.com\u002Fyrahul3910\u002Fdotfiles","https:\u002F\u002Fgithub.com\u002Fyrahul3910","https:\u002F\u002Fryedida.me","CS PhD @ NC State; Sr. Data Scientist @ LexisNexis","2026-11-13 01:37:12",{"source":8,"skillName":49,"commands":60,"prompt":70,"zipAvailable":71},[61,64,67],{"tool":62,"command":63},"npx","npx skills add yrahul3910\u002Fdotfiles --skill add-seed-data",{"tool":65,"command":66},"bunx","bunx skills add yrahul3910\u002Fdotfiles --skill add-seed-data",{"tool":68,"command":69},"pnpm","pnpm dlx skills add yrahul3910\u002Fdotfiles --skill add-seed-data","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fyrahul3910\u002Fdotfiles\u002Fblob\u002Fmaster\u002F.agents\u002Fskills\u002Fcode-style\u002FSKILL.md",true,[73,79,83],{"path":74,"resourceType":75,"resourceTypeDesc":76,"sizeBytes":77,"sourceHtmlUrl":78},"references\u002Fcontext.md","REFERENCE","参考文档",2060,"https:\u002F\u002Fgithub.com\u002Fgithub\u002Freplica\u002Fblob\u002Fmain\u002Fstarters\u002Fshared\u002F.agents\u002Fskills\u002Fadd-seed-data\u002Freferences\u002Fcontext.md",{"path":80,"resourceType":75,"resourceTypeDesc":76,"sizeBytes":81,"sourceHtmlUrl":82},"references\u002Fpython.md",1049,"https:\u002F\u002Fgithub.com\u002Fyrahul3910\u002Fdotfiles\u002Fblob\u002Fmaster\u002F.agents\u002Fskills\u002Fcode-style\u002Freferences\u002Fpython.md",{"path":84,"resourceType":75,"resourceTypeDesc":76,"sizeBytes":85,"sourceHtmlUrl":86},"references\u002Ftypescript.md",1619,"https:\u002F\u002Fgithub.com\u002Fyrahul3910\u002Fdotfiles\u002Fblob\u002Fmaster\u002F.agents\u002Fskills\u002Fcode-style\u002Freferences\u002Ftypescript.md",[88,117,148,179,199,228],{"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":94,"publishedAt":44},"01M6BX5T7VBBNA50W28PGXFVBK","pr-babysit","Watch a GitHub pull request through CI and bot reviews (Copilot, Codex, Claude, Greptile), fix feedback locally as it arrives, and push only once everything has settled. Use when asked to babysit, shepherd, or watch a PR until it is green and reviewed. Not for a one-off look at PR comments or CI status.","https:\u002F\u002Fgithub.com\u002Fyrahul3910\u002Fdotfiles\u002Fblob\u002Fmaster\u002F.pi\u002Fagent\u002Fskills\u002Fpr-babysit\u002FSKILL.md",[],[95,96,97,98,99,100,101,102,103,104,105,106,107,108,109,110,111,34,112,113,114,115,29,28,116],"pr","pr babysit","babysit","bot","github","codex","status","copilot","pull request","pull","push","ci","pr comments","feedback","ci status","fix","use","green","shepherd","as","comments","when",{"skillNo":118,"name":119,"nameZh":6,"description":120,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":121,"categories":122,"keywords":123,"publishedAt":44},"01M6BX5PZTGZCZMWB46DEZY1RB","okf","Read, create, and update Open Knowledge Format (OKF) knowledge bundles — wikis of markdown concept files with YAML frontmatter, per Google's OKF v0.1 spec. Use when browsing or consuming an OKF bundle, when asked to create a knowledge wiki for a codebase or data system, or when editing a directory of .md files that carry `type:` frontmatter alongside index.md\u002Flog.md files. Covers the frontmatter schema, bundle-root-relative linking, index.md maintenance, and log.md changelog conventions.","https:\u002F\u002Fgithub.com\u002Fyrahul3910\u002Fdotfiles\u002Fblob\u002Fmaster\u002F.pi\u002Fagent\u002Fskills\u002Fokf\u002FSKILL.md",[],[119,124,125,126,127,128,129,130,131,132,133,134,135,136,137,138,38,111,139,140,141,142,143,144,145,146,28,147,116],"directory","google","spec","create","update","changelog","index","yaml","data","open","markdown","wiki","knowledge","system","format","schema","maintenance","log","files","type","wikis","with","concept","browsing",{"skillNo":149,"name":150,"nameZh":6,"description":151,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":152,"categories":153,"keywords":162,"publishedAt":44},"01M6BX5MWN3YRXQ447DBGGTHM5","design-doc","Write an explicit design document, RFC, or consequential architecture proposal with adversarial review. Use for decisions with material ownership, compatibility, migration, or operational consequences. Do not activate for ordinary comparisons, syntax questions, or small implementation choices.","https:\u002F\u002Fgithub.com\u002Fyrahul3910\u002Fdotfiles\u002Fblob\u002Fmaster\u002F.pi\u002Fagent\u002Fskills\u002Fdesign-doc\u002FSKILL.md",[154,159],{"categoryNo":155,"categoryName":156,"taxonomyType":157,"taxonomyTypeDesc":158},"01JBSEEDCAT000000000000015","视觉设计","SCENARIO","使用场景",{"categoryNo":160,"categoryName":161,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000032","设计师",[163,164,165,36,166,167,168,169,170,27,111,171,172,173,174,175,176,145,177,28,178],"design","doc","design doc","architecture","adversarial review","RFC","syntax","decisions","migration","document","activate","do","material","proposal","questions","adversarial",{"skillNo":180,"name":181,"nameZh":6,"description":182,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":183,"categories":184,"keywords":185,"publishedAt":44},"01M6BX5K2H9A93MD355DKQ21MV","background-terminals","Run and manage long-lived shell commands in background terminals. Use for dev servers, watchers, streaming builds, and other commands that should keep running while the agent continues working.","https:\u002F\u002Fgithub.com\u002Fyrahul3910\u002Fdotfiles\u002Fblob\u002Fmaster\u002F.pi\u002Fagent\u002Fskills\u002Fbackground-terminals\u002FSKILL.md",[],[186,187,42,188,189,190,111,191,192,193,194,195,196,28,197,198],"background terminals","background","dev","streaming","shell","manage","commands","watchers","long","keep","dev servers","servers","running",{"skillNo":200,"name":201,"nameZh":6,"description":202,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":203,"categories":204,"keywords":214,"publishedAt":44},"01M6BX5H39CTKJKDXRA35MNGRW","writing-for-agents","Write or revise skills, AGENTS.md, CLAUDE.md, prompts, and other instructions consumed by coding agents. Use when agent behavior, skill routing, instruction structure, or prompt maintenance is part of the task.","https:\u002F\u002Fgithub.com\u002Fyrahul3910\u002Fdotfiles\u002Fblob\u002Fmaster\u002F.agents\u002Fskills\u002Fwriting-for-agents\u002FSKILL.md",[205,208,211],{"categoryNo":206,"categoryName":207,"taxonomyType":157,"taxonomyTypeDesc":158},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":209,"categoryName":210,"taxonomyType":157,"taxonomyTypeDesc":158},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":212,"categoryName":213,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000036","内容创作者",[215,216,28,217,218,219,220,27,221,222,111,223,140,224,225,226,227,116],"writing","writing for agents","coding agents","routing","coding","prompt","instructions","behavior","prompts","task","structure","revise","skill routing",{"skillNo":229,"name":230,"nameZh":6,"description":231,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":232,"categories":233,"keywords":234,"publishedAt":44},"01M6BX5FE0MPK7EXN5ZT590428","wait-what","Stop. That last message did not land: re-pitch it.","https:\u002F\u002Fgithub.com\u002Fyrahul3910\u002Fdotfiles\u002Fblob\u002Fmaster\u002F.agents\u002Fskills\u002Fwait-what\u002FSKILL.md",[],[235,236,237,238,239,240,241,242,243,244],"wait what","wait","land","stop","message","pitch","it","re","last","true"]