[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M79XWFVHEJYGHK4G540JPCSC":3,"skill-same:01M79XWFVHEJYGHK4G540JPCSC":48},{"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":26,"commitSha":27,"skillDirectory":28,"forksCount":29,"repositoryHtmlUrl":30,"repositoryHomepageUrl":6,"ownerHtmlUrl":31,"ownerBlogUrl":6,"ownerDescription":32,"updatedAt":33,"install":34,"resources":47},"01M79XWFVHEJYGHK4G540JPCSC","programming-typescript",null,"Guides the procedure for writing or changing TypeScript: loading the TypeScript standard first, driving each increment test-first, finding which rule a decision falls under, and confirming the gates before handing off.","wahidyankf\u002Fbeaver-nest","wahidyankf","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F10843406?v=4","01M79XPZPDMM2D076E49HRJT8A","Wahidyan Kresna Fridayoka","01M79XPZQGDA87TNY0HYDREYDP",2,"MIT","https:\u002F\u002Fgithub.com\u002Fwahidyankf\u002Fbeaver-nest\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fprogramming-typescript\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: programming-typescript\ndescription: >-\n  Guides the procedure for writing or changing TypeScript: loading the TypeScript standard first, driving each increment\n  test-first, finding which rule a decision falls under, and confirming the gates before handing off.\nwhen_to_use: >-\n  Use when writing, changing, or reviewing TypeScript code, before the first edit, alongside the language-agnostic\n  application skill.\ncompatibility: Requires a TypeScript project with type check, lint, format, and unit test targets.\n---\n\n# Programming TypeScript\n\n[TypeScript Standards](..\u002F..\u002F..\u002Frepo-governance\u002Fdevelopment\u002Fquality\u002Fstacks\u002Ftypescript-standards.md) owns every\nTypeScript rule, strict typing included. This skill restates none of them. It carries the procedure for applying that\nstandard, and the judgement of noticing which rule a decision falls under.\n[developing-applications](..\u002Fdeveloping-applications\u002FSKILL.md) covers the language-agnostic judgement, and\n[Red, Green, Refactor](..\u002F..\u002F..\u002Frepo-governance\u002Fworkflows\u002Fquality\u002Fred-green-refactor.md) owns the test-first cycle.\n\n## Before the First Edit\n\n1. **Read the standard.** Read TypeScript Standards in full, plus\n   React Standards or\n   Next.js Standards when the code uses them.\n2. **Compare the project's configuration with it.** A relaxed compiler option or a lint rule switched off is a finding\n   to raise, not a baseline to copy into new code.\n3. **Read the tests that cover the code** before interpreting or changing it.\n4. **List the increments,** each one observable behaviour, simplest first, including every expected failure path.\n\n## Drive Each Increment Test-First\n\nRun each increment through Red, Green, Refactor at the narrowest target that can prove it, usually a unit test with its\noperating-system-facing dependencies injected. Run the type check as part of each green, not only at the end: a type\nerror discovered after several cycles tends to force a redesign of work already written.\n\nWhen the compiler rejects a change, fix the code. The standard lists what never silences a type error, and reaching for\none of those means the design, not the checker, needs attention.\n\n## Notice Which Rule Applies\n\nThese moments recur. Each points at the part of the standard that decides it:\n\n| While writing, you meet                                               | Apply, in TypeScript Standards |\n| --------------------------------------------------------------------- | ------------------------------ |\n| data arriving from a request, file, storage, or the environment       | Typing Rules, on validation    |\n| a value whose shape is not known yet                                  | Typing Rules, on `any`         |\n| two flags or optional fields that must never be set together          | Typing Rules, on unions        |\n| two identifiers or quantities of the same primitive that must not mix | Typing Rules, on branded types |\n| a call that can fail during normal operation                          | Expected Failures Are Returned |\n| a promise started without being awaited or returned                   | Expected Failures Are Returned |\n| a business decision taking shape inside an effectful function         | Typing Rules, on code shape    |\n\nTo decide between a returned failure and an exception, ask whether a caller in normal operation would need to handle it.\nIf it would, the failure is expected, and it gets its own test.\n\n## Before Handing Off\n\n- The type check, lint, and format gates pass, and then the fast gate from\n  [Quality Gates](..\u002F..\u002F..\u002Frepo-governance\u002Fdevelopment\u002Fquality-gates.md).\n- Every increment carries its red, green, and refactor records.\n- The diff has been read once against the Typing Rules section, looking for what no linter sees, such as a failure\n  thrown where callers should expect it.\n- No compiler option, lint rule, or coverage exclusion was relaxed to let the change pass.\n","# Programming TypeScript\n\n[TypeScript Standards](..\u002F..\u002F..\u002Frepo-governance\u002Fdevelopment\u002Fquality\u002Fstacks\u002Ftypescript-standards.md) owns every\nTypeScript rule, strict typing included. This skill restates none of them. It carries the procedure for applying that\nstandard, and the judgement of noticing which rule a decision falls under.\n[developing-applications](..\u002Fdeveloping-applications\u002FSKILL.md) covers the language-agnostic judgement, and\n[Red, Green, Refactor](..\u002F..\u002F..\u002Frepo-governance\u002Fworkflows\u002Fquality\u002Fred-green-refactor.md) owns the test-first cycle.\n\n## Before the First Edit\n\n1. **Read the standard.** Read TypeScript Standards in full, plus\n   React Standards or\n   Next.js Standards when the code uses them.\n2. **Compare the project's configuration with it.** A relaxed compiler option or a lint rule switched off is a finding\n   to raise, not a baseline to copy into new code.\n3. **Read the tests that cover the code** before interpreting or changing it.\n4. **List the increments,** each one observable behaviour, simplest first, including every expected failure path.\n\n## Drive Each Increment Test-First\n\nRun each increment through Red, Green, Refactor at the narrowest target that can prove it, usually a unit test with its\noperating-system-facing dependencies injected. Run the type check as part of each green, not only at the end: a type\nerror discovered after several cycles tends to force a redesign of work already written.\n\nWhen the compiler rejects a change, fix the code. The standard lists what never silences a type error, and reaching for\none of those means the design, not the checker, needs attention.\n\n## Notice Which Rule Applies\n\nThese moments recur. Each points at the part of the standard that decides it:\n\n| While writing, you meet                                               | Apply, in TypeScript Standards |\n| --------------------------------------------------------------------- | ------------------------------ |\n| data arriving from a request, file, storage, or the environment       | Typing Rules, on validation    |\n| a value whose shape is not known yet                                  | Typing Rules, on `any`         |\n| two flags or optional fields that must never be set together          | Typing Rules, on unions        |\n| two identifiers or quantities of the same primitive that must not mix | Typing Rules, on branded types |\n| a call that can fail during normal operation                          | Expected Failures Are Returned |\n| a promise started without being awaited or returned                   | Expected Failures Are Returned |\n| a business decision taking shape inside an effectful function         | Typing Rules, on code shape    |\n\nTo decide between a returned failure and an exception, ask whether a caller in normal operation would need to handle it.\nIf it would, the failure is expected, and it gets its own test.\n\n## Before Handing Off\n\n- The type check, lint, and format gates pass, and then the fast gate from\n  [Quality Gates](..\u002F..\u002F..\u002Frepo-governance\u002Fdevelopment\u002Fquality-gates.md).\n- Every increment carries its red, green, and refactor records.\n- The diff has been read once against the Typing Rules section, looking for what no linter sees, such as a failure\n  thrown where callers should expect it.\n- No compiler option, lint rule, or coverage exclusion was relaxed to let the change pass.\n",{"name":5,"description":7,"when_to_use":24,"compatibility":25},"Use when writing, changing, or reviewing TypeScript code, before the first edit, alongside the language-agnostic application skill.","Requires a TypeScript project with type check, lint, format, and unit test targets.","main","e6a21f0c020e81a73b28f6923bd898af898f17e4",".agents\u002Fskills\u002Fprogramming-typescript",0,"https:\u002F\u002Fgithub.com\u002Fwahidyankf\u002Fbeaver-nest","https:\u002F\u002Fgithub.com\u002Fwahidyankf","Software Engineer","2026-11-15 04:32:43",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add wahidyankf\u002Fbeaver-nest --skill programming-typescript",{"tool":40,"command":41},"bunx","bunx skills add wahidyankf\u002Fbeaver-nest --skill programming-typescript",{"tool":43,"command":44},"pnpm","pnpm dlx skills add wahidyankf\u002Fbeaver-nest --skill programming-typescript","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fwahidyankf\u002Fbeaver-nest\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fprogramming-typescript\u002FSKILL.md",true,[],[49,56,63,70,75,82],{"skillNo":50,"name":51,"nameZh":6,"description":52,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":53,"categories":54,"keywords":55,"publishedAt":19},"01M79Y04GAQQJXY8N9BD749WDJ","writing-browser-e2e-tests","Guides writing browser end-to-end tests that find elements as users do, wait on what the action produced, keep page knowledge in page objects, organize one feature per file, and run scenario-backed suites from generated specs.","https:\u002F\u002Fgithub.com\u002Fwahidyankf\u002Fbeaver-nest\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fwriting-browser-e2e-tests\u002FSKILL.md",[],[],{"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},"01M79Y0001QFQM6ZZQMG91MMN6","usability-heuristic-evaluation","Guides judging a running interface as a first-time user would, without its specifications: citing a named principle for every finding, walking each task step, reading labels and addresses for scent, and rating severity.","https:\u002F\u002Fgithub.com\u002Fwahidyankf\u002Fbeaver-nest\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fusability-heuristic-evaluation\u002FSKILL.md",[],[],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":19},"01M79XZX1AF54RXJRYZZ5KRA3Z","tooling-nx","Guides Nx workspace work under the Nx standard: selecting projects by the graph, adding a target only where a capability exists, tracing a stale cached pass to its missing input, and answering a module-boundary finding.","https:\u002F\u002Fgithub.com\u002Fwahidyankf\u002Fbeaver-nest\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Ftooling-nx\u002FSKILL.md",[],[],{"skillNo":71,"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":72,"categories":73,"keywords":74,"publishedAt":19},"01M79XZT0D49C6D7DHBE0960H6","https:\u002F\u002Fgithub.com\u002Fwahidyankf\u002Fbeaver-nest\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fprogramming-typescript\u002FSKILL.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":19},"01M79XZPYGRRJ4CK2EGA3P5RYP","programming-shell","Guides shell work under the shell standards: checking the declared dialect first, deciding whether logic belongs in shell at all, tracing where exit-on-error does not reach, and testing the script as its callers run it.","https:\u002F\u002Fgithub.com\u002Fwahidyankf\u002Fbeaver-nest\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fprogramming-shell\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":19},"01M79XZKN2R9RR0MX66DEM5W2Z","programming-javascript","Guides JavaScript work under the JavaScript standard: confirming the file is type-checked, typing through JSDoc, validating input the checker cannot see, and noticing floating promises and swallowed errors before handing off.","https:\u002F\u002Fgithub.com\u002Fwahidyankf\u002Fbeaver-nest\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fprogramming-javascript\u002FSKILL.md",[],[]]