[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7BKVQQDPV76YN5AVTA977Y9":3,"skill-same:01M7BKVQQDPV76YN5AVTA977Y9":87},{"skillNo":4,"name":5,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":23,"commitSha":24,"skillDirectory":25,"forksCount":26,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":29,"ownerDescription":6,"updatedAt":30,"install":31,"resources":44},"01M7BKVQQDPV76YN5AVTA977Y9","local-development",null,"devarispbrown\u002Fdevex-skills","devarispbrown","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F769307?v=4","01M7BKQ227RE7WBV6G929609KC","DeVaris Brown","01M7BKQ23B73Z8CVNF4R1K072W",1,"MIT","https:\u002F\u002Fgithub.com\u002Fdevarispbrown\u002Fdevex-skills\u002Fblob\u002Fmain\u002Fskills\u002Flocal-development\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: local-development\ndescription: Make a fresh repository clone productive in 10 minutes or less: runtime and toolchain setup, dependencies, backing services, environment variables, fixtures, containers, and hot reload. Use to design or repair make dev, devcontainer, and docker compose workflows and replace tribal knowledge with reproducible setup. For designing onboarding journeys use developer-onboarding; to measure an existing setup's timing use developer-experience-auditor.\nlicense: MIT\ncompatibility: Claude Code and Agent Skills-compatible coding agents; best with repository access and build tooling.\nmetadata:\n  version: \"2.9.4\"\n---\n\n# Local Development Setup and Repair\n\n## Mission\n\nA fresh clone reaching a productive state is boring infrastructure. Make it boring: committed automation, one canonical dev command, zero tribal knowledge.\n\n**Reproducibility over tribal knowledge.** Every setup step that lives only in one developer's memory, shell history, or machine is a defect. The standard is a clean checkout that reaches the productive state using only committed instructions and automation, and a setup that fails that standard is a `NON_REPRODUCIBLE_BUILD` gate failure.\n\n**Fix the automation, do not document around it.** When setup is hard to reproduce, repair the automation instead of writing longer READMEs. Documentation records committed automation; it never substitutes for it.\n\nThis skill designs and repairs `make dev`, `devcontainer`, and `docker compose` workflows and the environment configuration, backing services, fixtures, and hot reload they rely on.\n\nRead `references\u002Fclone-to-productive.md` before measuring or designing the gate procedure.\n\n## Hard gate: productive state on a clean clone\n\nA clean clone must reach the productive state — tests run and the dev loop is exercised — within `LOCAL_DEV_MAX_MIN` using only committed instructions and automation.\n\nRead `references\u002Fstandards.md` for the canonical thresholds, severity vocabulary, and release gates.\n\nThe gate has three parts:\n\n- **Bands.** Interpret elapsed time against the canonical bands defined for `LOCAL_DEV_MAX_MIN` in `references\u002Fstandards.md`: far under the limit is exceptional, comfortably under is strong, under the limit passes, at or over the limit is P1 FAIL.\n- **Gate constant.** A clean checkout that cannot reach the productive state within `LOCAL_DEV_MAX_MIN` using only committed instructions and automation triggers `NON_REPRODUCIBLE_BUILD` (P1). A high-quality README cannot override this gate.\n- **Evidence.** Label every measurement **Observed**, **CI-observed**, or **Estimated**. An estimate can never prove a PASS; a metric without an evidence label is UNVERIFIED.\n\nDo not move setup steps into \"prerequisites\" to game the timer. Do not claim the gate passes without executing it.\n\n## Local-dev workflow\n\n### 1. Inventory the setup\n\nRun `scripts\u002Fcheck_local_dev.py` from the repository root and inspect what it reports:\n\n- dev commands and scripts in `Makefile`, `package.json`, and other task runners\n- devcontainer, docker compose, and `.env.example` files\n- lockfiles and toolchain pins\n- README\u002Fcontributing setup instructions and CI setup steps\n\n**Find the gaps between what the inventory shows and what a fresh clone actually needs.** Interview the setup owner only to confirm behavior, never to extract steps that should already be committed. Do not accept \"everyone knows\" or \"just run it like I do\" as a specification.\n\n### 2. Choose the dev target\n\n**Pick exactly one primary dev target** — `make dev`, a devcontainer, or `docker compose up` — and make it the canonical path. Parallel dev paths are allowed when they serve genuinely different environments, but the chosen one must be the documented default.\n\nRead `references\u002Fdev-targets.md` when choosing, repairing, or comparing dev targets.\n\nDecide and record:\n\n- who runs it, and from where\n- what it starts, and in what order\n- what counts as \"up\" (healthcheck green, port responding, expected log line)\n- what the fallback is when a piece fails\n\n### 3. Eliminate manual steps\n\n**Automate every step a human currently performs by hand**: version selection, install, migration, seed, credential fetch, service start, port forwarding. Manual steps are the source of tribal knowledge.\n\nVerify:\n\n- toolchain install and version pinning are committed\n- the number of commands from clone to first successful run stays within `LOCAL_DEV_MAX_COMMANDS`\n- no step requires a step owner's memory, a personal shell alias, or a machine-specific path\n\nRead `references\u002Fdependencies-toolchain.md` when pinning versions or structuring workspaces.\n\nDo not document a manual step as \"expected\" when it can be automated.\n\n### 4. Wire services, fixtures, and credentials\n\n**Make backing services, seed data, and test credentials one command away.** Prefer emulators and committed fixtures over shared environments for the default dev loop.\n\nRead `references\u002Fservices-and-infra.md` when wiring databases, caches, queues, emulators, or fixtures.\n\nVerify:\n\n- services start with the dev target, or with one documented command\n- the database arrives with a schema and seeded data\n- credentials are generated locally, never shared or committed\n- no developer needs access to a shared staging or production environment to run the app\n\n### 5. Configure hot reload\n\n**Make the dev loop restart-free where the stack supports it**: file watchers, auto-reload, live-reload, or container volume mounts. The dev loop is one of the two stop conditions of the hard gate; if editing a file does not show up in the running app within a reasonable cycle, the loop is not exercised.\n\nRead `references\u002Fdev-targets.md` for hot-reload wiring per target.\n\nVerify: change a file, observe the reload, confirm the change is live. If hot reload is not possible, document the exact restart cycle and count it in the timer.\n\n### 6. Automate and document setup\n\n**Commit the automation, then document what remains.** Setup instructions in the README must match committed automation exactly; every command must be copy-pasteable and every requirement stated up front.\n\nRead `references\u002Fenvironment-config.md` when designing `.env.example` and environment handling.\nRead `references\u002Freproducibility.md` when designing clean-machine validation.\n\nVerify:\n\n- a fresh clone plus the documented commands reproduces the environment\n- `.env.example` is the contract and matches what the code reads\n- docs cover the three most likely failures and their recovery\n\nUse the `developer-docs` skill if available when authoring setup documentation.\n\n### 7. Validate from a clean machine\n\n**Execute the gate procedure end to end on a clean checkout**, record the elapsed time, label the evidence, interpret the band, and return the verdict.\n\nRead `references\u002Fclone-to-productive.md` before measuring.\n\nNever convert UNVERIFIED to PASS based on assumptions. Never report a band you did not measure.\n\nHand off to the `developer-experience-auditor` skill if available for an independent audit, and to `developer-onboarding` if available when the goal is the full onboarding journey rather than the dev environment.\n\n## Dev-target contract\n\nThe primary dev target must expose a predictable contract.\n\n- **`make dev`**: a `Makefile` with standard phony targets — `install`, `services`, `migrate`, `seed`, `dev`, `test`, `lint`, `clean` — where `dev` is a dependency chain that ends with a running, health-checked dev process and a documented stop target.\n- **devcontainer**: a `devcontainer.json` with a pinned image, declared features, a `postCreateCommand` that completes the setup, and forwarded ports matching the app's default ports. It must work from the default config with no manual edits. See `assets\u002Fdevcontainer.example.json` for the shape.\n- **`docker compose up`**: a compose file whose services declare healthchecks, whose app service mounts source for hot reload, and whose \"up\" result is verifiable (port responds, healthcheck green).\n\n**Graceful degradation**: when a required piece is unavailable (port taken, image missing, feature unsupported), fail with a clear message naming the cause and the recovery — never a silent partial start.\n\n## Environment configuration contract\n\n**`.env.example` is the contract.** It lists every variable the code reads, with safe development defaults and a comment for each non-obvious value.\n\n- Discover variables from code, CI, and config files — never from memory.\n- Keep secrets out of the repo: real values live in gitignored local files or a local secret store; dev defaults must be safe to commit.\n- Use the framework's canonical precedence order and document it. Do not invent a load order that contradicts the framework.\n- On a missing or invalid variable, fail with the variable name and its role, or use an explicitly safe default — never a silent wrong value.\n\nRead `references\u002Fenvironment-config.md` for the full procedure.\n\n## Required output\n\nProduce a **local-dev assessment** containing:\n\n1. **Verdict**: PASS \u002F PASS WITH DEBT \u002F FAIL \u002F UNVERIFIED, using the vocabulary in `references\u002Fstandards.md`.\n2. **Evidence label** for every measurement: Observed, CI-observed, or Estimated.\n3. **Gate result**: elapsed time against `LOCAL_DEV_MAX_MIN`, the band, and — when it fails — the `NON_REPRODUCIBLE_BUILD` trigger.\n4. **Dev-target contract status**: which contract elements hold and which are missing.\n5. **Environment contract status**: `.env.example` completeness and precedence behavior.\n6. **Findings** with severity (P0–P4) and the specific repair for each.\n\n## Definition of done\n\nThe work is done when:\n\n- a clean clone reaches the productive state within `LOCAL_DEV_MAX_MIN` using only committed instructions and automation, verified from a clean checkout\n- one canonical dev target is documented and works\n- every manual setup step found during inventory is automated or explicitly justified\n- services, fixtures, and credentials come up with the dev target or one documented command\n- hot reload works, or the restart cycle is documented and counted in the timer\n- `.env.example` matches the code and holds no real secrets\n- the local-dev assessment reports a verdict, an evidence label, and severities\n- tribal-knowledge steps that could not be automated are listed explicitly as debt, never silently\n","# Local Development Setup and Repair\n\n## Mission\n\nA fresh clone reaching a productive state is boring infrastructure. Make it boring: committed automation, one canonical dev command, zero tribal knowledge.\n\n**Reproducibility over tribal knowledge.** Every setup step that lives only in one developer's memory, shell history, or machine is a defect. The standard is a clean checkout that reaches the productive state using only committed instructions and automation, and a setup that fails that standard is a `NON_REPRODUCIBLE_BUILD` gate failure.\n\n**Fix the automation, do not document around it.** When setup is hard to reproduce, repair the automation instead of writing longer READMEs. Documentation records committed automation; it never substitutes for it.\n\nThis skill designs and repairs `make dev`, `devcontainer`, and `docker compose` workflows and the environment configuration, backing services, fixtures, and hot reload they rely on.\n\nRead `references\u002Fclone-to-productive.md` before measuring or designing the gate procedure.\n\n## Hard gate: productive state on a clean clone\n\nA clean clone must reach the productive state — tests run and the dev loop is exercised — within `LOCAL_DEV_MAX_MIN` using only committed instructions and automation.\n\nRead `references\u002Fstandards.md` for the canonical thresholds, severity vocabulary, and release gates.\n\nThe gate has three parts:\n\n- **Bands.** Interpret elapsed time against the canonical bands defined for `LOCAL_DEV_MAX_MIN` in `references\u002Fstandards.md`: far under the limit is exceptional, comfortably under is strong, under the limit passes, at or over the limit is P1 FAIL.\n- **Gate constant.** A clean checkout that cannot reach the productive state within `LOCAL_DEV_MAX_MIN` using only committed instructions and automation triggers `NON_REPRODUCIBLE_BUILD` (P1). A high-quality README cannot override this gate.\n- **Evidence.** Label every measurement **Observed**, **CI-observed**, or **Estimated**. An estimate can never prove a PASS; a metric without an evidence label is UNVERIFIED.\n\nDo not move setup steps into \"prerequisites\" to game the timer. Do not claim the gate passes without executing it.\n\n## Local-dev workflow\n\n### 1. Inventory the setup\n\nRun `scripts\u002Fcheck_local_dev.py` from the repository root and inspect what it reports:\n\n- dev commands and scripts in `Makefile`, `package.json`, and other task runners\n- devcontainer, docker compose, and `.env.example` files\n- lockfiles and toolchain pins\n- README\u002Fcontributing setup instructions and CI setup steps\n\n**Find the gaps between what the inventory shows and what a fresh clone actually needs.** Interview the setup owner only to confirm behavior, never to extract steps that should already be committed. Do not accept \"everyone knows\" or \"just run it like I do\" as a specification.\n\n### 2. Choose the dev target\n\n**Pick exactly one primary dev target** — `make dev`, a devcontainer, or `docker compose up` — and make it the canonical path. Parallel dev paths are allowed when they serve genuinely different environments, but the chosen one must be the documented default.\n\nRead `references\u002Fdev-targets.md` when choosing, repairing, or comparing dev targets.\n\nDecide and record:\n\n- who runs it, and from where\n- what it starts, and in what order\n- what counts as \"up\" (healthcheck green, port responding, expected log line)\n- what the fallback is when a piece fails\n\n### 3. Eliminate manual steps\n\n**Automate every step a human currently performs by hand**: version selection, install, migration, seed, credential fetch, service start, port forwarding. Manual steps are the source of tribal knowledge.\n\nVerify:\n\n- toolchain install and version pinning are committed\n- the number of commands from clone to first successful run stays within `LOCAL_DEV_MAX_COMMANDS`\n- no step requires a step owner's memory, a personal shell alias, or a machine-specific path\n\nRead `references\u002Fdependencies-toolchain.md` when pinning versions or structuring workspaces.\n\nDo not document a manual step as \"expected\" when it can be automated.\n\n### 4. Wire services, fixtures, and credentials\n\n**Make backing services, seed data, and test credentials one command away.** Prefer emulators and committed fixtures over shared environments for the default dev loop.\n\nRead `references\u002Fservices-and-infra.md` when wiring databases, caches, queues, emulators, or fixtures.\n\nVerify:\n\n- services start with the dev target, or with one documented command\n- the database arrives with a schema and seeded data\n- credentials are generated locally, never shared or committed\n- no developer needs access to a shared staging or production environment to run the app\n\n### 5. Configure hot reload\n\n**Make the dev loop restart-free where the stack supports it**: file watchers, auto-reload, live-reload, or container volume mounts. The dev loop is one of the two stop conditions of the hard gate; if editing a file does not show up in the running app within a reasonable cycle, the loop is not exercised.\n\nRead `references\u002Fdev-targets.md` for hot-reload wiring per target.\n\nVerify: change a file, observe the reload, confirm the change is live. If hot reload is not possible, document the exact restart cycle and count it in the timer.\n\n### 6. Automate and document setup\n\n**Commit the automation, then document what remains.** Setup instructions in the README must match committed automation exactly; every command must be copy-pasteable and every requirement stated up front.\n\nRead `references\u002Fenvironment-config.md` when designing `.env.example` and environment handling.\nRead `references\u002Freproducibility.md` when designing clean-machine validation.\n\nVerify:\n\n- a fresh clone plus the documented commands reproduces the environment\n- `.env.example` is the contract and matches what the code reads\n- docs cover the three most likely failures and their recovery\n\nUse the `developer-docs` skill if available when authoring setup documentation.\n\n### 7. Validate from a clean machine\n\n**Execute the gate procedure end to end on a clean checkout**, record the elapsed time, label the evidence, interpret the band, and return the verdict.\n\nRead `references\u002Fclone-to-productive.md` before measuring.\n\nNever convert UNVERIFIED to PASS based on assumptions. Never report a band you did not measure.\n\nHand off to the `developer-experience-auditor` skill if available for an independent audit, and to `developer-onboarding` if available when the goal is the full onboarding journey rather than the dev environment.\n\n## Dev-target contract\n\nThe primary dev target must expose a predictable contract.\n\n- **`make dev`**: a `Makefile` with standard phony targets — `install`, `services`, `migrate`, `seed`, `dev`, `test`, `lint`, `clean` — where `dev` is a dependency chain that ends with a running, health-checked dev process and a documented stop target.\n- **devcontainer**: a `devcontainer.json` with a pinned image, declared features, a `postCreateCommand` that completes the setup, and forwarded ports matching the app's default ports. It must work from the default config with no manual edits. See `assets\u002Fdevcontainer.example.json` for the shape.\n- **`docker compose up`**: a compose file whose services declare healthchecks, whose app service mounts source for hot reload, and whose \"up\" result is verifiable (port responds, healthcheck green).\n\n**Graceful degradation**: when a required piece is unavailable (port taken, image missing, feature unsupported), fail with a clear message naming the cause and the recovery — never a silent partial start.\n\n## Environment configuration contract\n\n**`.env.example` is the contract.** It lists every variable the code reads, with safe development defaults and a comment for each non-obvious value.\n\n- Discover variables from code, CI, and config files — never from memory.\n- Keep secrets out of the repo: real values live in gitignored local files or a local secret store; dev defaults must be safe to commit.\n- Use the framework's canonical precedence order and document it. Do not invent a load order that contradicts the framework.\n- On a missing or invalid variable, fail with the variable name and its role, or use an explicitly safe default — never a silent wrong value.\n\nRead `references\u002Fenvironment-config.md` for the full procedure.\n\n## Required output\n\nProduce a **local-dev assessment** containing:\n\n1. **Verdict**: PASS \u002F PASS WITH DEBT \u002F FAIL \u002F UNVERIFIED, using the vocabulary in `references\u002Fstandards.md`.\n2. **Evidence label** for every measurement: Observed, CI-observed, or Estimated.\n3. **Gate result**: elapsed time against `LOCAL_DEV_MAX_MIN`, the band, and — when it fails — the `NON_REPRODUCIBLE_BUILD` trigger.\n4. **Dev-target contract status**: which contract elements hold and which are missing.\n5. **Environment contract status**: `.env.example` completeness and precedence behavior.\n6. **Findings** with severity (P0–P4) and the specific repair for each.\n\n## Definition of done\n\nThe work is done when:\n\n- a clean clone reaches the productive state within `LOCAL_DEV_MAX_MIN` using only committed instructions and automation, verified from a clean checkout\n- one canonical dev target is documented and works\n- every manual setup step found during inventory is automated or explicitly justified\n- services, fixtures, and credentials come up with the dev target or one documented command\n- hot reload works, or the restart cycle is documented and counted in the timer\n- `.env.example` matches the code and holds no real secrets\n- the local-dev assessment reports a verdict, an evidence label, and severities\n- tribal-knowledge steps that could not be automated are listed explicitly as debt, never silently\n",{},"main","8ecb082bfab6f317fa3cada530206ffa7c2917bb","skills\u002Flocal-development",0,"https:\u002F\u002Fgithub.com\u002Fdevarispbrown\u002Fdevex-skills","https:\u002F\u002Fgithub.com\u002Fdevarispbrown","floodgateacademy.com","2026-09-09 03:10:32",{"source":7,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add devarispbrown\u002Fdevex-skills --skill local-development",{"tool":37,"command":38},"bunx","bunx skills add devarispbrown\u002Fdevex-skills --skill local-development",{"tool":40,"command":41},"pnpm","pnpm dlx skills add devarispbrown\u002Fdevex-skills --skill local-development","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fdevarispbrown\u002Fdevex-skills\u002Fblob\u002Fmain\u002Fskills\u002Flocal-development\u002FSKILL.md",true,[45,51,57,61,65,69,73,77,81],{"path":46,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":49,"sourceHtmlUrl":50},"assets\u002Fdevcontainer.example.json","ASSET","资产文件",1325,"https:\u002F\u002Fgithub.com\u002Fdevarispbrown\u002Fdevex-skills\u002Fblob\u002Fmain\u002Fskills\u002Flocal-development\u002Fassets\u002Fdevcontainer.example.json",{"path":52,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":55,"sourceHtmlUrl":56},"references\u002Fclone-to-productive.md","REFERENCE","参考文档",2980,"https:\u002F\u002Fgithub.com\u002Fdevarispbrown\u002Fdevex-skills\u002Fblob\u002Fmain\u002Fskills\u002Flocal-development\u002Freferences\u002Fclone-to-productive.md",{"path":58,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":59,"sourceHtmlUrl":60},"references\u002Fdependencies-toolchain.md",2608,"https:\u002F\u002Fgithub.com\u002Fdevarispbrown\u002Fdevex-skills\u002Fblob\u002Fmain\u002Fskills\u002Flocal-development\u002Freferences\u002Fdependencies-toolchain.md",{"path":62,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":63,"sourceHtmlUrl":64},"references\u002Fdev-targets.md",3436,"https:\u002F\u002Fgithub.com\u002Fdevarispbrown\u002Fdevex-skills\u002Fblob\u002Fmain\u002Fskills\u002Flocal-development\u002Freferences\u002Fdev-targets.md",{"path":66,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":67,"sourceHtmlUrl":68},"references\u002Fenvironment-config.md",2403,"https:\u002F\u002Fgithub.com\u002Fdevarispbrown\u002Fdevex-skills\u002Fblob\u002Fmain\u002Fskills\u002Flocal-development\u002Freferences\u002Fenvironment-config.md",{"path":70,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":71,"sourceHtmlUrl":72},"references\u002Freproducibility.md",2235,"https:\u002F\u002Fgithub.com\u002Fdevarispbrown\u002Fdevex-skills\u002Fblob\u002Fmain\u002Fskills\u002Flocal-development\u002Freferences\u002Freproducibility.md",{"path":74,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":75,"sourceHtmlUrl":76},"references\u002Fservices-and-infra.md",2629,"https:\u002F\u002Fgithub.com\u002Fdevarispbrown\u002Fdevex-skills\u002Fblob\u002Fmain\u002Fskills\u002Flocal-development\u002Freferences\u002Fservices-and-infra.md",{"path":78,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":79,"sourceHtmlUrl":80},"references\u002Fstandards.md",4421,"https:\u002F\u002Fgithub.com\u002Fdevarispbrown\u002Fdevex-skills\u002Fblob\u002Fmain\u002Fskills\u002Flocal-development\u002Freferences\u002Fstandards.md",{"path":82,"resourceType":83,"resourceTypeDesc":84,"sizeBytes":85,"sourceHtmlUrl":86},"scripts\u002Fcheck_local_dev.py","SCRIPT","脚本",3932,"https:\u002F\u002Fgithub.com\u002Fdevarispbrown\u002Fdevex-skills\u002Fblob\u002Fmain\u002Fskills\u002Flocal-development\u002Fscripts\u002Fcheck_local_dev.py",[88,94,101,107,113,119],{"skillNo":89,"name":90,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":91,"categories":92,"keywords":93,"publishedAt":18},"01M7BKX6J9JRE4333WETDZ02YA","web-console-dx","https:\u002F\u002Fgithub.com\u002Fdevarispbrown\u002Fdevex-skills\u002Fblob\u002Fmain\u002Fskills\u002Fweb-console-dx\u002FSKILL.md",[],[],{"skillNo":95,"name":96,"nameZh":6,"description":97,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":98,"categories":99,"keywords":100,"publishedAt":18},"01M7BKX16CMSFAF11E19Y3838A","test-data-and-fixtures","Author fixtures, seed data, factories, fake services, mock servers, record-replay cassettes, golden files, synthetic datasets, and sanitization, with a project test-data create pattern. For sandbox route design use sandbox-experience; for per-system-type test strategy use quality-engineer.","https:\u002F\u002Fgithub.com\u002Fdevarispbrown\u002Fdevex-skills\u002Fblob\u002Fmain\u002Fskills\u002Ftest-data-and-fixtures\u002FSKILL.md",[],[],{"skillNo":102,"name":103,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":104,"categories":105,"keywords":106,"publishedAt":18},"01M7BKWX1EA5BTM9CF8Y4K7PBJ","security-supply-chain","https:\u002F\u002Fgithub.com\u002Fdevarispbrown\u002Fdevex-skills\u002Fblob\u002Fmain\u002Fskills\u002Fsecurity-supply-chain\u002FSKILL.md",[],[],{"skillNo":108,"name":109,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":110,"categories":111,"keywords":112,"publishedAt":18},"01M7BKWS9R0SAZ1WK3JV0EFD9E","sdk-engineer","https:\u002F\u002Fgithub.com\u002Fdevarispbrown\u002Fdevex-skills\u002Fblob\u002Fmain\u002Fskills\u002Fsdk-engineer\u002FSKILL.md",[],[],{"skillNo":114,"name":115,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":116,"categories":117,"keywords":118,"publishedAt":18},"01M7BKWN2MAK1WN87H7VZD3KP6","sandbox-experience","https:\u002F\u002Fgithub.com\u002Fdevarispbrown\u002Fdevex-skills\u002Fblob\u002Fmain\u002Fskills\u002Fsandbox-experience\u002FSKILL.md",[],[],{"skillNo":120,"name":121,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":122,"categories":123,"keywords":124,"publishedAt":18},"01M7BKWH9WMK5M9H41802TGNJC","release-guardian","https:\u002F\u002Fgithub.com\u002Fdevarispbrown\u002Fdevex-skills\u002Fblob\u002Fmain\u002Fskills\u002Frelease-guardian\u002FSKILL.md",[],[]]