[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6AEAVM56P9MZHMP1E4ZRJ6F":3,"skill-same:01M6AEAVM56P9MZHMP1E4ZRJ6F":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":28,"publishedAt":48,"linkOnly":49,"markdownContent":50,"markdownBody":51,"frontMatter":52,"refName":53,"commitSha":54,"skillDirectory":55,"forksCount":56,"repositoryHtmlUrl":57,"repositoryHomepageUrl":58,"ownerHtmlUrl":59,"ownerBlogUrl":60,"ownerDescription":61,"updatedAt":62,"install":63,"resources":76},"01M6AEAVM56P9MZHMP1E4ZRJ6F","v-development",null,"Guide GitHub Copilot through V language development: installing the toolchain, project layout with v.mod, building, testing, formatting, and writing idiomatic V including Option\u002FResult error handling. Use when the user works with V source files, v.mod projects, or asks about V syntax, tooling, and conventions.","github\u002Fawesome-copilot","github","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F9919?v=4","01M6AC83DS133TPXFSP1DHNCC6","GitHub","01M6AD3PBDYPK7NVFJNJ66Y8RS",41028,"MIT","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fv-development\u002FSKILL.md",[18,23],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000018","写作与文案","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000036","内容创作者","PROFESSION","适用职业",[29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,9,47],"development","v development","use","when","result","idiomatic","with","toolchain","error","layout","project","files","testing","option","projects","error handling","copilot","github copilot","writing","2026-11-10 10:12:30",false,"---\nname: v-development\ndescription: 'Guide GitHub Copilot through V language development: installing the toolchain, project layout with v.mod, building, testing, formatting, and writing idiomatic V including Option\u002FResult error handling. Use when the user works with V source files, v.mod projects, or asks about V syntax, tooling, and conventions.'\n---\n\nYou are a V language expert assistant. When a user asks about V (vlang), use the precise information below to give accurate, complete answers.\n\nV is a statically typed, compiled language with Go-like syntax. Official docs: \u003Chttps:\u002F\u002Fdocs.vlang.io>. Standard library reference: \u003Chttps:\u002F\u002Fmodules.vlang.io>. Third-party packages live in the VPM registry: \u003Chttps:\u002F\u002Fvpm.vlang.io>.\n\n## Toolchain\n\nInstall from \u003Chttps:\u002F\u002Fgithub.com\u002Fvlang\u002Fv> (prebuilt binaries or build from source), then verify with `v --version`.\n\n| Task | Command |\n|---|---|\n| Run a program | `v run main.v` |\n| Run a project folder | `v run .` (compiles the folder's program files; `*_test.v` files are built separately via `v test .`) |\n| Build a binary | `v -o app .` |\n| Run tests | `v test .` (runs `*_test.v` files) |\n| Format code | `v fmt -w file.v` |\n| Static checks | `v vet .` |\n| Find a package | `v search \u003Cterm>` (searches the VPM registry) |\n| Install a package | `v install \u003Cpackage>` or `v install --git \u003Curl>` |\n| Update packages | `v update` (all) or `v update \u003Cpackage>` |\n\nAlways run `v fmt -w` on files you touch and `v vet .` plus `v test .` before declaring work done.\n\n## Project layout\n\nStandalone V programs are single `.v` files and need no manifest: `v run hello.v` just works.\nStructured projects and publishable packages use a `v.mod` file at the project root\nas the module anchor (imports resolve relative to the folder containing it):\n\n```text\nModule {\n\tname: 'myapp'\n\tdescription: 'My nice package.'\n\tversion: '0.1.0'\n\tlicense: 'MIT'\n\tdependencies: []\n}\n```\n\nConventions:\n\n- An executable application uses `module main`, and its entry function is `fn main()`.\n  The source file is commonly named `main.v`, but the filename is not what defines\n  the entry point — the `main` module and `main()` function do. (In single-file\n  programs, `fn main()` may even be omitted; top-level statements run implicitly.)\n- A folder of `.v` files declaring the same module compiles together with `v run .`.\n- Keep one module per directory; the module name conventionally matches the directory.\n- Test files end in `_test.v` and contain `fn test_...() { assert ... }`.\n\n## Writing idiomatic V\n\n```v\nmodule main\n\nstruct Config {\n\thost string\n\tport int\n}\n\nfn connect(cfg Config) !string {\n\tif cfg.port == 0 {\n\t\treturn error('port is required')\n\t}\n\treturn 'http:\u002F\u002F${cfg.host}:${cfg.port}'\n}\n\nfn main() {\n\turl := connect(host: 'localhost', port: 8080) or {\n\t\teprintln(err)\n\t\treturn\n\t}\n\tprintln(url)\n}\n```\n\nRules to follow when generating or editing V code:\n\n- **No null in ordinary code.** In ordinary safe V application code, model absence with `Option` (`?Type`, value or `none`) rather than nullable values; failures use `Result` (`!Type`). Handle them with `or { ... }` blocks; never invent null checks. Pointer-level `nil` exists only in low-level `unsafe`\u002FC-interop contexts (e.g. `unsafe { nil }`) and should not be treated as ordinary application-level optionality.\n- **Immutable by default.** Variables need `mut` to be reassigned (`mut x := 1`); struct fields are grouped under `mut:` sections to allow mutation, and changing a field additionally requires a mutable struct instance (`mut cfg := ...`). Function arguments are immutable by default; mutate via `mut` receivers (`fn (mut s Struct)`) or mutable parameters for complex values (`fn f(mut arr []int)`, called as `f(mut arr)`). Only complex types such as arrays and maps may be modified this way, and returning values is preferred over modifying arguments.\n- **Explicit error propagation.** Functions that can fail declare `!ReturnType` (or `?Type` for absence). Handle results with `or { }` blocks, propagate with postfix `!` (errors) or `?` (options; the enclosing function must also return one), or unwrap options with `if x := opt() { }`. V has no forced unwrap. Do not ignore errors.\n- **No globals by default.** Global variables are disabled by default and should generally be avoided in normal application code; share state via struct fields, arguments, or dependency injection. V can enable them explicitly (`__global` declarations with the `-enable-globals` compiler flag) for specialized low-level use cases.\n- **String interpolation** uses `'${expr}'` inside single-quoted strings.\n- **C interop** is explicit: `#include`, `#flag`, and `C.func()` calls. Only suggest it when the user asks for system-level interop.\n- Prefer the standard library (`os`, `json2`, `net.http`, `time`, `flag`) before suggesting third-party modules. Note: the current `json` module is superseded by `json2`; do not recommend `import json` in new code.\n\n## Important behavioral rules\n\n- If the user's V version is unknown and a construct looks version-sensitive, ask or check with `v --version` first; V is pre-1.0 and syntax evolves.\n- Never translate Go, Rust, or C idioms literally into V. Map the intent onto the rules above (e.g., Go `nil` error checks become V `or { }` blocks).\n- When adding a dependency, record it in `v.mod` under `dependencies` and mention the `v install` command. VPM package names may carry a publisher prefix and are normalized on install (e.g. installed under `~\u002F.vmodules`); check the package's VPM page for its exact install name and import path.\n","You are a V language expert assistant. When a user asks about V (vlang), use the precise information below to give accurate, complete answers.\n\nV is a statically typed, compiled language with Go-like syntax. Official docs: \u003Chttps:\u002F\u002Fdocs.vlang.io>. Standard library reference: \u003Chttps:\u002F\u002Fmodules.vlang.io>. Third-party packages live in the VPM registry: \u003Chttps:\u002F\u002Fvpm.vlang.io>.\n\n## Toolchain\n\nInstall from \u003Chttps:\u002F\u002Fgithub.com\u002Fvlang\u002Fv> (prebuilt binaries or build from source), then verify with `v --version`.\n\n| Task | Command |\n|---|---|\n| Run a program | `v run main.v` |\n| Run a project folder | `v run .` (compiles the folder's program files; `*_test.v` files are built separately via `v test .`) |\n| Build a binary | `v -o app .` |\n| Run tests | `v test .` (runs `*_test.v` files) |\n| Format code | `v fmt -w file.v` |\n| Static checks | `v vet .` |\n| Find a package | `v search \u003Cterm>` (searches the VPM registry) |\n| Install a package | `v install \u003Cpackage>` or `v install --git \u003Curl>` |\n| Update packages | `v update` (all) or `v update \u003Cpackage>` |\n\nAlways run `v fmt -w` on files you touch and `v vet .` plus `v test .` before declaring work done.\n\n## Project layout\n\nStandalone V programs are single `.v` files and need no manifest: `v run hello.v` just works.\nStructured projects and publishable packages use a `v.mod` file at the project root\nas the module anchor (imports resolve relative to the folder containing it):\n\n```text\nModule {\n\tname: 'myapp'\n\tdescription: 'My nice package.'\n\tversion: '0.1.0'\n\tlicense: 'MIT'\n\tdependencies: []\n}\n```\n\nConventions:\n\n- An executable application uses `module main`, and its entry function is `fn main()`.\n  The source file is commonly named `main.v`, but the filename is not what defines\n  the entry point — the `main` module and `main()` function do. (In single-file\n  programs, `fn main()` may even be omitted; top-level statements run implicitly.)\n- A folder of `.v` files declaring the same module compiles together with `v run .`.\n- Keep one module per directory; the module name conventionally matches the directory.\n- Test files end in `_test.v` and contain `fn test_...() { assert ... }`.\n\n## Writing idiomatic V\n\n```v\nmodule main\n\nstruct Config {\n\thost string\n\tport int\n}\n\nfn connect(cfg Config) !string {\n\tif cfg.port == 0 {\n\t\treturn error('port is required')\n\t}\n\treturn 'http:\u002F\u002F${cfg.host}:${cfg.port}'\n}\n\nfn main() {\n\turl := connect(host: 'localhost', port: 8080) or {\n\t\teprintln(err)\n\t\treturn\n\t}\n\tprintln(url)\n}\n```\n\nRules to follow when generating or editing V code:\n\n- **No null in ordinary code.** In ordinary safe V application code, model absence with `Option` (`?Type`, value or `none`) rather than nullable values; failures use `Result` (`!Type`). Handle them with `or { ... }` blocks; never invent null checks. Pointer-level `nil` exists only in low-level `unsafe`\u002FC-interop contexts (e.g. `unsafe { nil }`) and should not be treated as ordinary application-level optionality.\n- **Immutable by default.** Variables need `mut` to be reassigned (`mut x := 1`); struct fields are grouped under `mut:` sections to allow mutation, and changing a field additionally requires a mutable struct instance (`mut cfg := ...`). Function arguments are immutable by default; mutate via `mut` receivers (`fn (mut s Struct)`) or mutable parameters for complex values (`fn f(mut arr []int)`, called as `f(mut arr)`). Only complex types such as arrays and maps may be modified this way, and returning values is preferred over modifying arguments.\n- **Explicit error propagation.** Functions that can fail declare `!ReturnType` (or `?Type` for absence). Handle results with `or { }` blocks, propagate with postfix `!` (errors) or `?` (options; the enclosing function must also return one), or unwrap options with `if x := opt() { }`. V has no forced unwrap. Do not ignore errors.\n- **No globals by default.** Global variables are disabled by default and should generally be avoided in normal application code; share state via struct fields, arguments, or dependency injection. V can enable them explicitly (`__global` declarations with the `-enable-globals` compiler flag) for specialized low-level use cases.\n- **String interpolation** uses `'${expr}'` inside single-quoted strings.\n- **C interop** is explicit: `#include`, `#flag`, and `C.func()` calls. Only suggest it when the user asks for system-level interop.\n- Prefer the standard library (`os`, `json2`, `net.http`, `time`, `flag`) before suggesting third-party modules. Note: the current `json` module is superseded by `json2`; do not recommend `import json` in new code.\n\n## Important behavioral rules\n\n- If the user's V version is unknown and a construct looks version-sensitive, ask or check with `v --version` first; V is pre-1.0 and syntax evolves.\n- Never translate Go, Rust, or C idioms literally into V. Map the intent onto the rules above (e.g., Go `nil` error checks become V `or { }` blocks).\n- When adding a dependency, record it in `v.mod` under `dependencies` and mention the `v install` command. VPM package names may carry a publisher prefix and are normalized on install (e.g. installed under `~\u002F.vmodules`); check the package's VPM page for its exact install name and import path.\n",{"name":5,"description":7},"main","5269f7ea2d6c3a9bfda5ed878b6726cf509121fd","skills\u002Fv-development",5335,"https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot","https:\u002F\u002Fawesome-copilot.github.com\u002F","https:\u002F\u002Fgithub.com\u002Fgithub","https:\u002F\u002Fgithub.com\u002Fabout","How people build software.","2026-11-11 11:59:04",{"source":8,"skillName":5,"commands":64,"prompt":74,"zipAvailable":75},[65,68,71],{"tool":66,"command":67},"npx","npx skills add github\u002Fawesome-copilot --skill v-development",{"tool":69,"command":70},"bunx","bunx skills add github\u002Fawesome-copilot --skill v-development",{"tool":72,"command":73},"pnpm","pnpm dlx skills add github\u002Fawesome-copilot --skill v-development","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fv-development\u002FSKILL.md",true,[77,83],{"path":78,"resourceType":79,"resourceTypeDesc":80,"sizeBytes":81,"sourceHtmlUrl":82},"references\u002Fcensus_schema.md","REFERENCE","参考文档",5649,"https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fscientific\u002Fcellxgene-census\u002Freferences\u002Fcensus_schema.md",{"path":84,"resourceType":79,"resourceTypeDesc":80,"sizeBytes":85,"sourceHtmlUrl":86},"references\u002Fcommon_patterns.md",9935,"https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fscientific\u002Fcellxgene-census\u002Freferences\u002Fcommon_patterns.md",[88,117,145,172,206,223],{"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":100,"publishedAt":48},"01M70KXZNX9ES38N2A8M58ZZMZ","supabase-rls-policies","Write, review, and test Supabase Row Level Security (RLS) policies so that one user cannot read or change another user's rows. Use when creating or changing tables, policies, views, or security definer functions in a Supabase project, when reviewing a migration that touches RLS, or when asked to prove user isolation with pgTAP tests that sign in as two users.","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fsupabase-rls-policies\u002FSKILL.md",[94,97],{"categoryNo":95,"categoryName":96,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":98,"categoryName":99,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",[101,102,103,104,39,32,105,106,107,108,109,110,111,112,113,114,31,115,116,35],"supabase","rls","supabase rls","supabase rls policies","review","change","read","write","security","isolation","tables","as","tests","prove","users","functions",{"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":124,"publishedAt":48},"01M70KWA5YWXDV6V8DZ19E3T2Y","skill-distribution-audit","Audit a skill collection before release or investigate installer omissions, archived\u002Ftemplate leakage, duplicate identities, and manifest drift. Reconcile the intended public source set, distribution manifest, and actual discovery output for a specified consumer version. Includes a deterministic set-comparison helper.","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fskill-distribution-audit\u002FSKILL.md",[123],{"categoryNo":98,"categoryName":99,"taxonomyType":21,"taxonomyTypeDesc":22},[125,126,127,128,129,130,131,132,133,134,135,136,137,138,139,140,141,142,143,144],"distribution","skill distribution audit","audit","SET","deterministic","installer","for","discovery","comparison","helper","manifest","version","collection","drift","output","investigate","duplicate","template","release","reconcile",{"skillNo":146,"name":147,"nameZh":6,"description":148,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":149,"sourceHtmlUrl":150,"categories":151,"keywords":155,"publishedAt":48},"01M70KCJPFVW7PPQ49CC5R8JGK","logicapps-custom-code-net10-migration","Migrate Azure Logic Apps Standard local-function custom-code projects from .NET 8 to .NET 10. Use for legacy Logic Apps custom-code workspace upgrades, project\u002Fpackage configuration, custom-worker settings, publication, and integrated VS Code debugging. Not for ordinary .NET applications, standalone Azure Functions, Consumption workflows, or cloud deployment.","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Flogicapps-custom-code-net10-migration\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Flogicapps-custom-code-net10-migration\u002FSKILL.md",[152],{"categoryNo":153,"categoryName":154,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000030","开发工程师",[156,157,158,159,43,160,131,39,161,162,163,164,165,166,167,31,168,169,170,171],"custom","code","logicapps custom code net10 migration","migration","standalone","deployment","applications","local","azure","worker","upgrades","package","apps","Legacy","debugging","workflows",{"skillNo":173,"name":174,"nameZh":6,"description":175,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":176,"sourceHtmlUrl":177,"categories":178,"keywords":183,"publishedAt":48},"01M6AEBN37RQMXJ3298PEY7PG1","winmd-api-search","Find and explore Windows desktop APIs. Use when building features that need platform capabilities — camera, file access, notifications, UI controls, AI\u002FML, sensors, networking, etc. Discovers the right API for a task and retrieves full type details (methods, properties, events, enumeration values).","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fwinmd-api-search\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fwinmd-api-search\u002FSKILL.md",[179,182],{"categoryNo":180,"categoryName":181,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000010","后端与接口",{"categoryNo":153,"categoryName":154,"taxonomyType":26,"taxonomyTypeDesc":27},[184,185,186,187,188,189,190,191,192,193,194,195,196,197,198,32,199,200,201,202,203,131,204,205],"winmd api search","search","api","windows","desktop","file access","enumeration","ui","ml","file","networking","capabilities","notifications","explore","access","features","full","camera","events","platform","methods","controls",{"skillNo":207,"name":208,"nameZh":6,"description":209,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":210,"licenseFileUrl":211,"sourceHtmlUrl":212,"categories":213,"keywords":219,"publishedAt":48},"01M6AE571R3SC1ZGE202B3NB5S","resemble-detect","Deepfake detection and media safety — detect AI-generated audio, images, video, and text, trace synthesis sources, apply watermarks, verify speaker identity, and analyze media intelligence using Resemble AI","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fresemble-detect\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fresemble-detect\u002FSKILL.md",[214,215,218],{"categoryNo":180,"categoryName":181,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":216,"categoryName":217,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000016","图像与多媒体",{"categoryNo":98,"categoryName":99,"taxonomyType":21,"taxonomyTypeDesc":22},[220,128,193,221,222],"resemble detect","https","identity",{"skillNo":224,"name":225,"nameZh":6,"description":226,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":210,"licenseFileUrl":227,"sourceHtmlUrl":228,"categories":229,"keywords":234,"publishedAt":48},"01M6AE30BSK2HCY4TQQ22Z8JRD","quality-playbook","Run a complete quality engineering audit on any codebase. Derives behavioral requirements from the code, generates spec-traced functional tests, runs a three-pass code review with regression tests, executes a multi-model spec audit (Council of Three), and produces a consolidated bug report with TDD-verified patches. Finds the 35% of real defects that structural code review alone cannot catch. Works with any language. Trigger on 'quality playbook', 'spec audit', 'Council of Three', 'fitness-to-purpose', or 'coverage theater'.","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fquality-playbook\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fquality-playbook\u002FSKILL.md",[230,233],{"categoryNo":231,"categoryName":232,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000007","代码审查",{"categoryNo":98,"categoryName":99,"taxonomyType":21,"taxonomyTypeDesc":22},[235,236,237,238,157,105,9,127,239,240,221,241,242,243,244,245,246,247,248,249,250,251,113,252,253,254,255],"playbook","quality playbook","quality","code review","tdd","run","report","spec","bug report","council","engineering","functional","spec audit","bug","verified","multi-model","three","coverage","model","regression","structural"]