[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7F2Q3WDF8HFDZZQTQPV5MBM":3,"skill-same:01M7F2Q3WDF8HFDZZQTQPV5MBM":180},{"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":29,"ownerHtmlUrl":30,"ownerBlogUrl":31,"ownerDescription":32,"updatedAt":33,"install":34,"resources":47},"01M7F2Q3WDF8HFDZZQTQPV5MBM","spec-traceability",null,"Keeps spec IDs traced in tests, code, commits and reports; flags dangling or untraced IDs. Use when a task cites a spec ID (REQ-4, SCR-2), asks what is required or in scope, or hits a spec gap. Not for screens (screen-contracts).","zakariaf\u002FReactNative-Skills","zakariaf","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F2259803?v=4","01M7DEF0YMPS6Y6RQ4WGA0JH9R","Zakaria Fatahi","01M7F1VKYEK96M7SYJE1EPGD0A",13,"MIT","https:\u002F\u002Fgithub.com\u002Fzakariaf\u002FReactNative-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fspec-traceability\u002FSKILL.md",[],[],"2026-11-16 10:05:34",false,"---\nname: spec-traceability\ndescription: Keeps spec IDs traced in tests, code, commits and reports; flags dangling or untraced IDs. Use when a task cites a spec ID (REQ-4, SCR-2), asks what is required or in scope, or hits a spec gap. Not for screens (screen-contracts).\n---\n\n# Spec traceability\n\nThe app's spec says what to build, and every piece of work can prove which part of it it serves: each\nrequirement, screen, decision and non-negotiable has a stable ID in a markdown spec folder; the first\nfailing test, the code comment, the end-to-end flow, the commit body and the report quote that ID;\nand two scripts print any entry verbatim and prove that every citation in the repo and its history\nresolves. Works the same for iOS and Android; an app without a spec gets a clean NOT APPLICABLE.\n\n## Rules that must hold\n\n1. **The spec decides what; its non-negotiables never bend.** If a task, a design, a library or another\n   requirement would break a non-negotiable (`NN-` entries), stop and ask before writing code. Why: a\n   silently traded rule passes every test of the new work and is caught by nobody.\n2. **Quote the spec, never paraphrase it from memory.** Print the entry with\n   `spec-lookup.mjs \u003Cid>` and put the ID and the rule in the first failing test's title or the comment\n   above it, and in the commit body. Why: a misremembered number (4 seconds instead of 5, 4 free lists\n   instead of 3) is the bug no test catches, because the test asserts the same wrong number.\n3. **Cite IDs exactly as the spec defines them, and name screens by title and ID together:**\n   \"Task list (SCR-1)\". The prefixes come from the app's `contracts\u002Fspec.json` (default `NN-`, `SCR-`,\n   `REQ-`, `DEC-`, `OOS-`). Why: a cited ID that does not exist, or a name paired with the wrong ID,\n   sends the reader to the wrong requirement (`dangling-id`, `unknown-spec-section`,\n   `screen-name-mismatch`).\n4. **When the spec is silent, ambiguous or contradicts itself about anything a user would see, stop\n   and ask:** quote the lines, give two or three options with a recommended default, and keep working\n   on everything else. Never invent product behaviour; never ask what the spec already answers. Why:\n   an agent's guess ships as a product decision nobody made.\n5. **Use the documented default of an open decision and say so in the report;** ask only when the\n   default stops working. Every open decision carries `Default:`, a settled one `Decided:`, and a\n   settled decision is never asked again. Why: an open decision without a default blocks work, and a\n   re-asked one wastes the reviewer's time (`entry-field-missing`).\n6. **Build nothing the spec puts out of scope, and treat its numbers as limits, not targets.** A test\n   or flow that cites an `OOS-` entry or a dropped requirement fails. Why: agents over-deliver, and\n   every extra is code to test, translate, declare to the stores and maintain\n   (`out-of-scope-traced`).\n7. **IDs are stable forever.** A new entry takes the next free number; an entry is never renamed,\n   renumbered or reused, and a dropped one stays with `Status: dropped`. Why: old commits, tests and\n   reports cite it (`duplicate-spec-id`, `malformed-heading`, `invalid-field`).\n8. **A built requirement is traced by a test or flow.** Mark a requirement or screen `Status: built`\n   in the commit that adds its green test citing it, and a built screen's `Route:` names a file that\n   exists. Why: \"built\" with no test is a claim, not evidence (`untraced-requirement`,\n   `route-missing`).\n9. **Traced IDs fit the commit and test reference patterns.** The commit-msg hook\n   (`contracts\u002Fcommits.json` `requirementRef`, else `scripts\u002Fgit\u002Frequirement-ref.json`) and\n   tdd-workflow's `requirementIdPattern` must accept every traced ID. Why: an ID the hook rejects\n   makes the commit that cites it impossible (`ref-pattern-mismatch`).\n10. **Platform differences are written down, never assumed.** When iOS and Android behave differently\n    (a permission prompt, back navigation, a widget), the entry says so with `Platforms:` or splits\n    into one child per platform, each traced by its own test or flow; a spec that describes one\n    platform only is silent about the other (rule 4). Why: the platform nobody specified ships\n    whatever the library does by default.\n11. **Behaviour several features need is built once, in the shared layer,** and cited where that\n    shared piece is tested, never copied inside one feature. Why: copies drift, and the spec describes\n    the behaviour once for the same reason.\n\n## Workflow\n\n1. **Find out whether the app keeps a spec:** `node ${CLAUDE_SKILL_DIR}\u002Fscripts\u002Fspec-lookup.mjs . --list`.\n   `NOT APPLICABLE: the app keeps no requirement spec` means requirements come from the issue or the\n   acceptance criteria: quote them with their key (`TASKS-12`, `#41`) and skip to step 6. Start a spec\n   (step 9) only when the developer wants one.\n2. **Print the entries the task serves:** `node ${CLAUDE_SKILL_DIR}\u002Fscripts\u002Fspec-lookup.mjs . REQ-4 SCR-2`\n   (`--list --kind screen` lists one kind, `--brief` prints headings only, `--from \u003Cfile>` reads IDs\n   from a file). An entry marked dropped or out-of-scope prints a NOTE: do not build it.\n3. **Read the non-negotiables the task touches** (`--list --kind non-negotiable`): any network, data,\n   layout, text, accessibility or permission work touches at least one. Plan so none bends (rule 1);\n   [references\u002Fquestions-and-decisions.md](references\u002Fquestions-and-decisions.md) lists the typical\n   collisions.\n4. **Check decisions and scope:** `--list --kind decision` and `--kind out-of-scope`. Use each open\n   decision's default and note it for the report; build nothing out of scope.\n5. **If the spec is silent, ambiguous or contradicts itself** on anything a user would see, or covers\n   one platform only, write the requirement question (quoted lines, options, default) as\n   [references\u002Fquestions-and-decisions.md](references\u002Fquestions-and-decisions.md) describes, send it\n   in git-commits-and-reporting's request format, and keep working on the rest.\n6. **Write the IDs into the work,** as [examples\u002Fspec-citations.md](examples\u002Fspec-citations.md) shows:\n   the first failing test's title or comment quotes the rule (`it('moves the task to Done (REQ-2)')`),\n   a constant that holds a decision's default cites it, flows name screens as \"Task list (SCR-1)\", the\n   commit body names the IDs, the report names screens by title and ID.\n7. **Update the spec in the same commit:** set `Status: in-progress` when a slice starts and\n   `Status: built` when its citing test is green. When a changed requirement changes a test\n   expectation, that commit updates the entry, says why in its body and carries\n   `Spec-Change: \u003CID> \u003Cwhat changed>` (git-commits-and-reporting owns the format); a spec edit with no\n   test change carries no trailer.\n8. **Run the check** from the repo root: `node ${CLAUDE_SKILL_DIR}\u002Fscripts\u002Fcheck-spec-refs.mjs .`, and\n   for the session's commits `node ${CLAUDE_SKILL_DIR}\u002Fscripts\u002Fcheck-spec-refs.mjs . --range \u003Cbase>..HEAD`\n   (`--trace` adds the requirement-to-test matrix for the report). Fix every `FAIL` line and rerun\n   until it prints `RESULT: PASS`.\n9. **Starting a spec** (once per app): copy [templates\u002Fdocs\u002Fspec\u002F](templates\u002Fdocs\u002Fspec\u002F) to\n   `docs\u002Fspec\u002F` and [templates\u002Fcontracts\u002Fspec.json](templates\u002Fcontracts\u002Fspec.json) with its schema to\n   `contracts\u002F`, replace the Tasks examples with the app's own entries (all `planned`), and keep the\n   default prefixes unless the app already has IDs. [references\u002Fspec-format.md](references\u002Fspec-format.md)\n   has the heading grammar, the fields, every contract key and what counts as a citation. If the\n   commit contract sets its own `requirementRef` pattern, make it accept the spec's IDs (rule 9).\n   When the app had no `docs\u002F` before, the root tooling treats it as pre-existing: in the same commit\n   add `docs\u002F` to `.prettierignore` and `'docs\u002F**'` to `PRE_EXISTING` in `eslint.config.mjs` (with a\n   `Gate-Change:` trailer), or declare `\"docs\"` in `rn-skills.config.json` `\"layoutEntries\"` when the\n   team wants Prettier to format the spec.\n\n## Definition of done\n\n- [ ] The entries the work serves were printed with `spec-lookup.mjs` and are quoted in the first\n      failing test (title or comment) and in the commit body.\n- [ ] No non-negotiable was traded away; any collision was raised before building.\n- [ ] Every open decision the work relied on is named in the report with the default used, and every\n      spec gap was asked about with quoted lines and a default.\n- [ ] Nothing out of scope was built; numbers from the spec were used as limits.\n- [ ] Entries finished by this work are `Status: built`, each cited by a test or flow; behaviour that\n      differs by platform is specified and traced per platform.\n- [ ] The check prints no SKIP line; an app with no spec prints\n      `NOT APPLICABLE: the app keeps no requirement spec (...)`, which passes.\n- [ ] `node ${CLAUDE_SKILL_DIR}\u002Fscripts\u002Fcheck-spec-refs.mjs . --range \u003Cbase>..HEAD` prints `RESULT: PASS`\n      (before the session's first commit the range is empty: it prints one `NOTE --range ... holds no\n      commit yet` line and checks the files only)\n\n## Anti-patterns\n\n- **Citing from memory** (\"REQ-2 says Undo lasts 4 seconds\"). Print the entry: the time lives in\n  DEC-1, and its default is 5 seconds.\n- **Inventing an ID for a new idea** (`\u002F\u002F Leaderboard (SCR-16)`). A new screen is a product decision:\n  the entry is added to the spec with the reviewer's agreement first; until then the checker reports\n  `dangling-id`.\n- **Renumbering the spec to tidy it up.** Every old commit, test and report now points at the wrong\n  entry. Add, drop, never reuse.\n- **Marking an entry built because the code exists.** Built means a test or flow cites it and passes.\n- **Asking the reviewer how to build something.** Architecture and libraries are engineering\n  questions; the reviewer answers what the user gets.\n- **Asking about something the spec or a default already answers.** Read the entry first; ask only\n  about real gaps.\n- **\"Helpful\" extras** (a widget, a sign-in for later sync, sample data beyond the stated count).\n  Out of scope means not built.\n- **Writing the iOS behaviour into the spec and letting Android do whatever the library does.**\n  Split the entry per platform and trace each.\n- **Silencing a real citation with `spec-refs-ignore`.** The marker is for test data that names a\n  missing ID on purpose.\n- **Bare short codes as IDs** (`S7`, `D4`). They collide with crypto names, model numbers and data;\n  keep a prefix that ends in `-`.\n\n## Files in this skill\n\n| File | What it is | Read\u002Frun when |\n|---|---|---|\n| [references\u002Fspec-format.md](references\u002Fspec-format.md) | The spec folder, heading grammar, fields and statuses, every `contracts\u002Fspec.json` key, what counts as a citation, tracing, agreement with the commit and test patterns, every rule, adopting a spec, when multi-package | Workflow step 9, and whenever the checker reports something unexpected |\n| [references\u002Fquestions-and-decisions.md](references\u002Fquestions-and-decisions.md) | What the spec decides, non-negotiables and their collisions, when and how to ask, open decisions and defaults, out of scope and content caps, changing the spec, shared behaviour | Workflow steps 3 to 5 |\n| [examples\u002Fspec-citations.md](examples\u002Fspec-citations.md) | One requirement followed from `spec-lookup` through the test, a constant, a flow, the commit, the report and a question, with what the checker flags | Once, before the first slice in an app with a spec |\n| [templates\u002Fdocs\u002Fspec\u002FREADME.md](templates\u002Fdocs\u002Fspec\u002FREADME.md) | `docs\u002Fspec\u002FREADME.md`: how the spec folder is organized and changed | Workflow step 9 |\n| [templates\u002Fdocs\u002Fspec\u002Fnon-negotiables.md](templates\u002Fdocs\u002Fspec\u002Fnon-negotiables.md) | `docs\u002Fspec\u002Fnon-negotiables.md`: four Tasks-app non-negotiables, each with `Enforced by:` | Workflow step 9 |\n| [templates\u002Fdocs\u002Fspec\u002Fscreens.md](templates\u002Fdocs\u002Fspec\u002Fscreens.md) | `docs\u002Fspec\u002Fscreens.md`: three screens with actions, states and routes | Workflow step 9 |\n| [templates\u002Fdocs\u002Fspec\u002Frequirements.md](templates\u002Fdocs\u002Fspec\u002Frequirements.md) | `docs\u002Fspec\u002Frequirements.md`: Tasks requirements, including a per-platform child (iOS and Android notification permission) | Workflow step 9 |\n| [templates\u002Fdocs\u002Fspec\u002Fdecisions.md](templates\u002Fdocs\u002Fspec\u002Fdecisions.md) | `docs\u002Fspec\u002Fdecisions.md`: an open decision with options and default, and a settled one | Workflow step 9 |\n| [templates\u002Fdocs\u002Fspec\u002Fout-of-scope.md](templates\u002Fdocs\u002Fspec\u002Fout-of-scope.md) | `docs\u002Fspec\u002Fout-of-scope.md`: what this version does not build | Workflow step 9 |\n| [templates\u002Fcontracts\u002Fspec.json](templates\u002Fcontracts\u002Fspec.json) | `contracts\u002Fspec.json`: the ID scheme, filled with the defaults | Workflow step 9, or when the app uses other prefixes |\n| [templates\u002Fcontracts\u002Fspec.schema.json](templates\u002Fcontracts\u002Fspec.schema.json) | `contracts\u002Fspec.schema.json`: JSON Schema of the contract | With the contract |\n| `scripts\u002Fspec-lookup.mjs` | Prints spec entries verbatim (`REQ-4 SCR-2 spec 1.1`), `--list [--kind]`, `--brief`, `--from`; fails on unknown IDs with the nearest ones | Workflow steps 1 to 4, whenever a spec line is quoted |\n| `scripts\u002Fcheck-spec-refs.mjs` | Checks the spec (headings, unique IDs, fields, routes, defaults, reference patterns) and every citation in files and commits (dangling IDs, sections, name pairs, tracing, excluded work) | Workflow step 8 and the definition of done |\n| `scripts\u002Flib\u002Fspec-model.mjs` | Reads the contract and the spec entries (shared by both scripts) | When changing a script |\n| `scripts\u002Fselftest.mjs` | Proves both scripts pass the shipped templates and catch each planted bug | After changing a script or a template |\n| `scripts\u002Fcheck-lib.mjs` | Shared script helper, synced from the library (do not edit here) | Never by hand |\n| `assets\u002Frequirement-ref.json` | The default requirement-reference pattern of the commit rules, synced from git-commits-and-reporting's `scripts\u002Fgit\u002Frequirement-ref.json`; used when the app has no copy and no `requirementRef` | Never by hand (synced) |\n| `assets\u002Fshared.json` | Declares the shared files this skill copies in | When adding a shared file |\n| `tests\u002Fbases\u002Fapp\u002F` | A minimal Tasks app the fixtures add to the shipped templates | When changing the fixtures |\n| `tests\u002Ffixtures\u002F` | Overlay cases on the templates: good, pass, bad (one per rule) and error | When adding a rule to a script |\n\n## Related skills\n\n- `tdd-workflow` - turns a quoted entry into the first failing test; its history check reads the same IDs.\n- `git-commits-and-reporting` - commit bodies, `Spec-Change:` trailers, reports and the request format for questions.\n- `screen-contracts` - how each screen named in the spec is built (states, testIDs).\n- `design-visual-parity` - proves a built screen matches its approved design baseline; the spec says what it shows.\n- `navigation-and-routing` - the route files that screen entries name.\n- `e2e-maestro` - the flows that trace screens and requirements on both platforms.\n- `react-native-conventions-index` - which skill to load for a task.\n","# Spec traceability\n\nThe app's spec says what to build, and every piece of work can prove which part of it it serves: each\nrequirement, screen, decision and non-negotiable has a stable ID in a markdown spec folder; the first\nfailing test, the code comment, the end-to-end flow, the commit body and the report quote that ID;\nand two scripts print any entry verbatim and prove that every citation in the repo and its history\nresolves. Works the same for iOS and Android; an app without a spec gets a clean NOT APPLICABLE.\n\n## Rules that must hold\n\n1. **The spec decides what; its non-negotiables never bend.** If a task, a design, a library or another\n   requirement would break a non-negotiable (`NN-` entries), stop and ask before writing code. Why: a\n   silently traded rule passes every test of the new work and is caught by nobody.\n2. **Quote the spec, never paraphrase it from memory.** Print the entry with\n   `spec-lookup.mjs \u003Cid>` and put the ID and the rule in the first failing test's title or the comment\n   above it, and in the commit body. Why: a misremembered number (4 seconds instead of 5, 4 free lists\n   instead of 3) is the bug no test catches, because the test asserts the same wrong number.\n3. **Cite IDs exactly as the spec defines them, and name screens by title and ID together:**\n   \"Task list (SCR-1)\". The prefixes come from the app's `contracts\u002Fspec.json` (default `NN-`, `SCR-`,\n   `REQ-`, `DEC-`, `OOS-`). Why: a cited ID that does not exist, or a name paired with the wrong ID,\n   sends the reader to the wrong requirement (`dangling-id`, `unknown-spec-section`,\n   `screen-name-mismatch`).\n4. **When the spec is silent, ambiguous or contradicts itself about anything a user would see, stop\n   and ask:** quote the lines, give two or three options with a recommended default, and keep working\n   on everything else. Never invent product behaviour; never ask what the spec already answers. Why:\n   an agent's guess ships as a product decision nobody made.\n5. **Use the documented default of an open decision and say so in the report;** ask only when the\n   default stops working. Every open decision carries `Default:`, a settled one `Decided:`, and a\n   settled decision is never asked again. Why: an open decision without a default blocks work, and a\n   re-asked one wastes the reviewer's time (`entry-field-missing`).\n6. **Build nothing the spec puts out of scope, and treat its numbers as limits, not targets.** A test\n   or flow that cites an `OOS-` entry or a dropped requirement fails. Why: agents over-deliver, and\n   every extra is code to test, translate, declare to the stores and maintain\n   (`out-of-scope-traced`).\n7. **IDs are stable forever.** A new entry takes the next free number; an entry is never renamed,\n   renumbered or reused, and a dropped one stays with `Status: dropped`. Why: old commits, tests and\n   reports cite it (`duplicate-spec-id`, `malformed-heading`, `invalid-field`).\n8. **A built requirement is traced by a test or flow.** Mark a requirement or screen `Status: built`\n   in the commit that adds its green test citing it, and a built screen's `Route:` names a file that\n   exists. Why: \"built\" with no test is a claim, not evidence (`untraced-requirement`,\n   `route-missing`).\n9. **Traced IDs fit the commit and test reference patterns.** The commit-msg hook\n   (`contracts\u002Fcommits.json` `requirementRef`, else `scripts\u002Fgit\u002Frequirement-ref.json`) and\n   tdd-workflow's `requirementIdPattern` must accept every traced ID. Why: an ID the hook rejects\n   makes the commit that cites it impossible (`ref-pattern-mismatch`).\n10. **Platform differences are written down, never assumed.** When iOS and Android behave differently\n    (a permission prompt, back navigation, a widget), the entry says so with `Platforms:` or splits\n    into one child per platform, each traced by its own test or flow; a spec that describes one\n    platform only is silent about the other (rule 4). Why: the platform nobody specified ships\n    whatever the library does by default.\n11. **Behaviour several features need is built once, in the shared layer,** and cited where that\n    shared piece is tested, never copied inside one feature. Why: copies drift, and the spec describes\n    the behaviour once for the same reason.\n\n## Workflow\n\n1. **Find out whether the app keeps a spec:** `node ${CLAUDE_SKILL_DIR}\u002Fscripts\u002Fspec-lookup.mjs . --list`.\n   `NOT APPLICABLE: the app keeps no requirement spec` means requirements come from the issue or the\n   acceptance criteria: quote them with their key (`TASKS-12`, `#41`) and skip to step 6. Start a spec\n   (step 9) only when the developer wants one.\n2. **Print the entries the task serves:** `node ${CLAUDE_SKILL_DIR}\u002Fscripts\u002Fspec-lookup.mjs . REQ-4 SCR-2`\n   (`--list --kind screen` lists one kind, `--brief` prints headings only, `--from \u003Cfile>` reads IDs\n   from a file). An entry marked dropped or out-of-scope prints a NOTE: do not build it.\n3. **Read the non-negotiables the task touches** (`--list --kind non-negotiable`): any network, data,\n   layout, text, accessibility or permission work touches at least one. Plan so none bends (rule 1);\n   [references\u002Fquestions-and-decisions.md](references\u002Fquestions-and-decisions.md) lists the typical\n   collisions.\n4. **Check decisions and scope:** `--list --kind decision` and `--kind out-of-scope`. Use each open\n   decision's default and note it for the report; build nothing out of scope.\n5. **If the spec is silent, ambiguous or contradicts itself** on anything a user would see, or covers\n   one platform only, write the requirement question (quoted lines, options, default) as\n   [references\u002Fquestions-and-decisions.md](references\u002Fquestions-and-decisions.md) describes, send it\n   in git-commits-and-reporting's request format, and keep working on the rest.\n6. **Write the IDs into the work,** as [examples\u002Fspec-citations.md](examples\u002Fspec-citations.md) shows:\n   the first failing test's title or comment quotes the rule (`it('moves the task to Done (REQ-2)')`),\n   a constant that holds a decision's default cites it, flows name screens as \"Task list (SCR-1)\", the\n   commit body names the IDs, the report names screens by title and ID.\n7. **Update the spec in the same commit:** set `Status: in-progress` when a slice starts and\n   `Status: built` when its citing test is green. When a changed requirement changes a test\n   expectation, that commit updates the entry, says why in its body and carries\n   `Spec-Change: \u003CID> \u003Cwhat changed>` (git-commits-and-reporting owns the format); a spec edit with no\n   test change carries no trailer.\n8. **Run the check** from the repo root: `node ${CLAUDE_SKILL_DIR}\u002Fscripts\u002Fcheck-spec-refs.mjs .`, and\n   for the session's commits `node ${CLAUDE_SKILL_DIR}\u002Fscripts\u002Fcheck-spec-refs.mjs . --range \u003Cbase>..HEAD`\n   (`--trace` adds the requirement-to-test matrix for the report). Fix every `FAIL` line and rerun\n   until it prints `RESULT: PASS`.\n9. **Starting a spec** (once per app): copy [templates\u002Fdocs\u002Fspec\u002F](templates\u002Fdocs\u002Fspec\u002F) to\n   `docs\u002Fspec\u002F` and [templates\u002Fcontracts\u002Fspec.json](templates\u002Fcontracts\u002Fspec.json) with its schema to\n   `contracts\u002F`, replace the Tasks examples with the app's own entries (all `planned`), and keep the\n   default prefixes unless the app already has IDs. [references\u002Fspec-format.md](references\u002Fspec-format.md)\n   has the heading grammar, the fields, every contract key and what counts as a citation. If the\n   commit contract sets its own `requirementRef` pattern, make it accept the spec's IDs (rule 9).\n   When the app had no `docs\u002F` before, the root tooling treats it as pre-existing: in the same commit\n   add `docs\u002F` to `.prettierignore` and `'docs\u002F**'` to `PRE_EXISTING` in `eslint.config.mjs` (with a\n   `Gate-Change:` trailer), or declare `\"docs\"` in `rn-skills.config.json` `\"layoutEntries\"` when the\n   team wants Prettier to format the spec.\n\n## Definition of done\n\n- [ ] The entries the work serves were printed with `spec-lookup.mjs` and are quoted in the first\n      failing test (title or comment) and in the commit body.\n- [ ] No non-negotiable was traded away; any collision was raised before building.\n- [ ] Every open decision the work relied on is named in the report with the default used, and every\n      spec gap was asked about with quoted lines and a default.\n- [ ] Nothing out of scope was built; numbers from the spec were used as limits.\n- [ ] Entries finished by this work are `Status: built`, each cited by a test or flow; behaviour that\n      differs by platform is specified and traced per platform.\n- [ ] The check prints no SKIP line; an app with no spec prints\n      `NOT APPLICABLE: the app keeps no requirement spec (...)`, which passes.\n- [ ] `node ${CLAUDE_SKILL_DIR}\u002Fscripts\u002Fcheck-spec-refs.mjs . --range \u003Cbase>..HEAD` prints `RESULT: PASS`\n      (before the session's first commit the range is empty: it prints one `NOTE --range ... holds no\n      commit yet` line and checks the files only)\n\n## Anti-patterns\n\n- **Citing from memory** (\"REQ-2 says Undo lasts 4 seconds\"). Print the entry: the time lives in\n  DEC-1, and its default is 5 seconds.\n- **Inventing an ID for a new idea** (`\u002F\u002F Leaderboard (SCR-16)`). A new screen is a product decision:\n  the entry is added to the spec with the reviewer's agreement first; until then the checker reports\n  `dangling-id`.\n- **Renumbering the spec to tidy it up.** Every old commit, test and report now points at the wrong\n  entry. Add, drop, never reuse.\n- **Marking an entry built because the code exists.** Built means a test or flow cites it and passes.\n- **Asking the reviewer how to build something.** Architecture and libraries are engineering\n  questions; the reviewer answers what the user gets.\n- **Asking about something the spec or a default already answers.** Read the entry first; ask only\n  about real gaps.\n- **\"Helpful\" extras** (a widget, a sign-in for later sync, sample data beyond the stated count).\n  Out of scope means not built.\n- **Writing the iOS behaviour into the spec and letting Android do whatever the library does.**\n  Split the entry per platform and trace each.\n- **Silencing a real citation with `spec-refs-ignore`.** The marker is for test data that names a\n  missing ID on purpose.\n- **Bare short codes as IDs** (`S7`, `D4`). They collide with crypto names, model numbers and data;\n  keep a prefix that ends in `-`.\n\n## Files in this skill\n\n| File | What it is | Read\u002Frun when |\n|---|---|---|\n| [references\u002Fspec-format.md](references\u002Fspec-format.md) | The spec folder, heading grammar, fields and statuses, every `contracts\u002Fspec.json` key, what counts as a citation, tracing, agreement with the commit and test patterns, every rule, adopting a spec, when multi-package | Workflow step 9, and whenever the checker reports something unexpected |\n| [references\u002Fquestions-and-decisions.md](references\u002Fquestions-and-decisions.md) | What the spec decides, non-negotiables and their collisions, when and how to ask, open decisions and defaults, out of scope and content caps, changing the spec, shared behaviour | Workflow steps 3 to 5 |\n| [examples\u002Fspec-citations.md](examples\u002Fspec-citations.md) | One requirement followed from `spec-lookup` through the test, a constant, a flow, the commit, the report and a question, with what the checker flags | Once, before the first slice in an app with a spec |\n| [templates\u002Fdocs\u002Fspec\u002FREADME.md](templates\u002Fdocs\u002Fspec\u002FREADME.md) | `docs\u002Fspec\u002FREADME.md`: how the spec folder is organized and changed | Workflow step 9 |\n| [templates\u002Fdocs\u002Fspec\u002Fnon-negotiables.md](templates\u002Fdocs\u002Fspec\u002Fnon-negotiables.md) | `docs\u002Fspec\u002Fnon-negotiables.md`: four Tasks-app non-negotiables, each with `Enforced by:` | Workflow step 9 |\n| [templates\u002Fdocs\u002Fspec\u002Fscreens.md](templates\u002Fdocs\u002Fspec\u002Fscreens.md) | `docs\u002Fspec\u002Fscreens.md`: three screens with actions, states and routes | Workflow step 9 |\n| [templates\u002Fdocs\u002Fspec\u002Frequirements.md](templates\u002Fdocs\u002Fspec\u002Frequirements.md) | `docs\u002Fspec\u002Frequirements.md`: Tasks requirements, including a per-platform child (iOS and Android notification permission) | Workflow step 9 |\n| [templates\u002Fdocs\u002Fspec\u002Fdecisions.md](templates\u002Fdocs\u002Fspec\u002Fdecisions.md) | `docs\u002Fspec\u002Fdecisions.md`: an open decision with options and default, and a settled one | Workflow step 9 |\n| [templates\u002Fdocs\u002Fspec\u002Fout-of-scope.md](templates\u002Fdocs\u002Fspec\u002Fout-of-scope.md) | `docs\u002Fspec\u002Fout-of-scope.md`: what this version does not build | Workflow step 9 |\n| [templates\u002Fcontracts\u002Fspec.json](templates\u002Fcontracts\u002Fspec.json) | `contracts\u002Fspec.json`: the ID scheme, filled with the defaults | Workflow step 9, or when the app uses other prefixes |\n| [templates\u002Fcontracts\u002Fspec.schema.json](templates\u002Fcontracts\u002Fspec.schema.json) | `contracts\u002Fspec.schema.json`: JSON Schema of the contract | With the contract |\n| `scripts\u002Fspec-lookup.mjs` | Prints spec entries verbatim (`REQ-4 SCR-2 spec 1.1`), `--list [--kind]`, `--brief`, `--from`; fails on unknown IDs with the nearest ones | Workflow steps 1 to 4, whenever a spec line is quoted |\n| `scripts\u002Fcheck-spec-refs.mjs` | Checks the spec (headings, unique IDs, fields, routes, defaults, reference patterns) and every citation in files and commits (dangling IDs, sections, name pairs, tracing, excluded work) | Workflow step 8 and the definition of done |\n| `scripts\u002Flib\u002Fspec-model.mjs` | Reads the contract and the spec entries (shared by both scripts) | When changing a script |\n| `scripts\u002Fselftest.mjs` | Proves both scripts pass the shipped templates and catch each planted bug | After changing a script or a template |\n| `scripts\u002Fcheck-lib.mjs` | Shared script helper, synced from the library (do not edit here) | Never by hand |\n| `assets\u002Frequirement-ref.json` | The default requirement-reference pattern of the commit rules, synced from git-commits-and-reporting's `scripts\u002Fgit\u002Frequirement-ref.json`; used when the app has no copy and no `requirementRef` | Never by hand (synced) |\n| `assets\u002Fshared.json` | Declares the shared files this skill copies in | When adding a shared file |\n| `tests\u002Fbases\u002Fapp\u002F` | A minimal Tasks app the fixtures add to the shipped templates | When changing the fixtures |\n| `tests\u002Ffixtures\u002F` | Overlay cases on the templates: good, pass, bad (one per rule) and error | When adding a rule to a script |\n\n## Related skills\n\n- `tdd-workflow` - turns a quoted entry into the first failing test; its history check reads the same IDs.\n- `git-commits-and-reporting` - commit bodies, `Spec-Change:` trailers, reports and the request format for questions.\n- `screen-contracts` - how each screen named in the spec is built (states, testIDs).\n- `design-visual-parity` - proves a built screen matches its approved design baseline; the spec says what it shows.\n- `navigation-and-routing` - the route files that screen entries name.\n- `e2e-maestro` - the flows that trace screens and requirements on both platforms.\n- `react-native-conventions-index` - which skill to load for a task.\n",{"name":5,"description":7},"main","41a0e66d4d09de5b46e6537f59a97c7192473486","skills\u002Fspec-traceability",2,"https:\u002F\u002Fgithub.com\u002Fzakariaf\u002FReactNative-Skills","https:\u002F\u002Fzakaria.dev\u002FReactNative-Skills\u002F","https:\u002F\u002Fgithub.com\u002Fzakariaf","https:\u002F\u002Fzakaria.dev","Seniore Software Engineer","2026-10-22 07:05:00",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add zakariaf\u002FReactNative-Skills --skill spec-traceability",{"tool":40,"command":41},"bunx","bunx skills add zakariaf\u002FReactNative-Skills --skill spec-traceability",{"tool":43,"command":44},"pnpm","pnpm dlx skills add zakariaf\u002FReactNative-Skills --skill spec-traceability","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fzakariaf\u002FReactNative-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fspec-traceability\u002FSKILL.md",true,[48,54,58,64,68,72,78,82,86,90,94,98,102,106,110,114,118,122,126,130,136,140,144,148,152,156,160,164,168,172,176],{"path":49,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":52,"sourceHtmlUrl":53},"assets\u002Frequirement-ref.json","ASSET","资产文件",624,"https:\u002F\u002Fgithub.com\u002Fzakariaf\u002FReactNative-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fspec-traceability\u002Fassets\u002Frequirement-ref.json",{"path":55,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":56,"sourceHtmlUrl":57},"assets\u002Fshared.json",175,"https:\u002F\u002Fgithub.com\u002Fzakariaf\u002FReactNative-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fspec-traceability\u002Fassets\u002Fshared.json",{"path":59,"resourceType":60,"resourceTypeDesc":61,"sizeBytes":62,"sourceHtmlUrl":63},"examples\u002Fspec-citations.md","REFERENCE","参考文档",5309,"https:\u002F\u002Fgithub.com\u002Fzakariaf\u002FReactNative-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fspec-traceability\u002Fexamples\u002Fspec-citations.md",{"path":65,"resourceType":60,"resourceTypeDesc":61,"sizeBytes":66,"sourceHtmlUrl":67},"references\u002Fquestions-and-decisions.md",7347,"https:\u002F\u002Fgithub.com\u002Fzakariaf\u002FReactNative-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fspec-traceability\u002Freferences\u002Fquestions-and-decisions.md",{"path":69,"resourceType":60,"resourceTypeDesc":61,"sizeBytes":70,"sourceHtmlUrl":71},"references\u002Fspec-format.md",14002,"https:\u002F\u002Fgithub.com\u002Fzakariaf\u002FReactNative-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fspec-traceability\u002Freferences\u002Fspec-format.md",{"path":73,"resourceType":74,"resourceTypeDesc":75,"sizeBytes":76,"sourceHtmlUrl":77},"scripts\u002Fcheck-lib.mjs","SCRIPT","脚本",119923,"https:\u002F\u002Fgithub.com\u002Fzakariaf\u002FReactNative-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fspec-traceability\u002Fscripts\u002Fcheck-lib.mjs",{"path":79,"resourceType":74,"resourceTypeDesc":75,"sizeBytes":80,"sourceHtmlUrl":81},"scripts\u002Fcheck-spec-refs.mjs",24907,"https:\u002F\u002Fgithub.com\u002Fzakariaf\u002FReactNative-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fspec-traceability\u002Fscripts\u002Fcheck-spec-refs.mjs",{"path":83,"resourceType":74,"resourceTypeDesc":75,"sizeBytes":84,"sourceHtmlUrl":85},"scripts\u002Flib\u002Fspec-model.mjs",16182,"https:\u002F\u002Fgithub.com\u002Fzakariaf\u002FReactNative-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fspec-traceability\u002Fscripts\u002Flib\u002Fspec-model.mjs",{"path":87,"resourceType":74,"resourceTypeDesc":75,"sizeBytes":88,"sourceHtmlUrl":89},"scripts\u002Fselftest.mjs",663,"https:\u002F\u002Fgithub.com\u002Fzakariaf\u002FReactNative-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fspec-traceability\u002Fscripts\u002Fselftest.mjs",{"path":91,"resourceType":74,"resourceTypeDesc":75,"sizeBytes":92,"sourceHtmlUrl":93},"scripts\u002Fspec-lookup.mjs",7797,"https:\u002F\u002Fgithub.com\u002Fzakariaf\u002FReactNative-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fspec-traceability\u002Fscripts\u002Fspec-lookup.mjs",{"path":95,"resourceType":60,"resourceTypeDesc":61,"sizeBytes":96,"sourceHtmlUrl":97},"templates\u002Fcontracts\u002Fspec.json",1104,"https:\u002F\u002Fgithub.com\u002Fzakariaf\u002FReactNative-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fspec-traceability\u002Ftemplates\u002Fcontracts\u002Fspec.json",{"path":99,"resourceType":60,"resourceTypeDesc":61,"sizeBytes":100,"sourceHtmlUrl":101},"templates\u002Fcontracts\u002Fspec.schema.json",3556,"https:\u002F\u002Fgithub.com\u002Fzakariaf\u002FReactNative-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fspec-traceability\u002Ftemplates\u002Fcontracts\u002Fspec.schema.json",{"path":103,"resourceType":60,"resourceTypeDesc":61,"sizeBytes":104,"sourceHtmlUrl":105},"templates\u002Fdocs\u002Fspec\u002Fdecisions.md",451,"https:\u002F\u002Fgithub.com\u002Fzakariaf\u002FReactNative-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fspec-traceability\u002Ftemplates\u002Fdocs\u002Fspec\u002Fdecisions.md",{"path":107,"resourceType":60,"resourceTypeDesc":61,"sizeBytes":108,"sourceHtmlUrl":109},"templates\u002Fdocs\u002Fspec\u002Fnon-negotiables.md",1722,"https:\u002F\u002Fgithub.com\u002Fzakariaf\u002FReactNative-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fspec-traceability\u002Ftemplates\u002Fdocs\u002Fspec\u002Fnon-negotiables.md",{"path":111,"resourceType":60,"resourceTypeDesc":61,"sizeBytes":112,"sourceHtmlUrl":113},"templates\u002Fdocs\u002Fspec\u002Fout-of-scope.md",491,"https:\u002F\u002Fgithub.com\u002Fzakariaf\u002FReactNative-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fspec-traceability\u002Ftemplates\u002Fdocs\u002Fspec\u002Fout-of-scope.md",{"path":115,"resourceType":60,"resourceTypeDesc":61,"sizeBytes":116,"sourceHtmlUrl":117},"templates\u002Fdocs\u002Fspec\u002FREADME.md",2337,"https:\u002F\u002Fgithub.com\u002Fzakariaf\u002FReactNative-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fspec-traceability\u002Ftemplates\u002Fdocs\u002Fspec\u002FREADME.md",{"path":119,"resourceType":60,"resourceTypeDesc":61,"sizeBytes":120,"sourceHtmlUrl":121},"templates\u002Fdocs\u002Fspec\u002Frequirements.md",1766,"https:\u002F\u002Fgithub.com\u002Fzakariaf\u002FReactNative-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fspec-traceability\u002Ftemplates\u002Fdocs\u002Fspec\u002Frequirements.md",{"path":123,"resourceType":60,"resourceTypeDesc":61,"sizeBytes":124,"sourceHtmlUrl":125},"templates\u002Fdocs\u002Fspec\u002Fscreens.md",1178,"https:\u002F\u002Fgithub.com\u002Fzakariaf\u002FReactNative-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fspec-traceability\u002Ftemplates\u002Fdocs\u002Fspec\u002Fscreens.md",{"path":127,"resourceType":60,"resourceTypeDesc":61,"sizeBytes":128,"sourceHtmlUrl":129},"tests\u002Fbases\u002Fapp\u002Fpackage.json",41,"https:\u002F\u002Fgithub.com\u002Fzakariaf\u002FReactNative-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fspec-traceability\u002Ftests\u002Fbases\u002Fapp\u002Fpackage.json",{"path":131,"resourceType":132,"resourceTypeDesc":133,"sizeBytes":134,"sourceHtmlUrl":135},"tests\u002Fbases\u002Fapp\u002Fsrc\u002Ffeatures\u002Ftasks\u002Ftasks-screen.tsx","OTHER","其他",192,"https:\u002F\u002Fgithub.com\u002Fzakariaf\u002FReactNative-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fspec-traceability\u002Ftests\u002Fbases\u002Fapp\u002Fsrc\u002Ffeatures\u002Ftasks\u002Ftasks-screen.tsx",{"path":137,"resourceType":60,"resourceTypeDesc":61,"sizeBytes":138,"sourceHtmlUrl":139},"tests\u002Ffixtures\u002Fcheck-spec-refs\u002FCASES.json",17343,"https:\u002F\u002Fgithub.com\u002Fzakariaf\u002FReactNative-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fspec-traceability\u002Ftests\u002Ffixtures\u002Fcheck-spec-refs\u002FCASES.json",{"path":141,"resourceType":60,"resourceTypeDesc":61,"sizeBytes":142,"sourceHtmlUrl":143},"tests\u002Ffixtures\u002Fcheck-spec-refs\u002Fgood\u002Fmutation.json",735,"https:\u002F\u002Fgithub.com\u002Fzakariaf\u002FReactNative-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fspec-traceability\u002Ftests\u002Ffixtures\u002Fcheck-spec-refs\u002Fgood\u002Fmutation.json",{"path":145,"resourceType":60,"resourceTypeDesc":61,"sizeBytes":146,"sourceHtmlUrl":147},"tests\u002Ffixtures\u002Fcheck-spec-refs\u002Fgood\u002Foverlay\u002F.maestro\u002Fadd-task.yaml",122,"https:\u002F\u002Fgithub.com\u002Fzakariaf\u002FReactNative-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fspec-traceability\u002Ftests\u002Ffixtures\u002Fcheck-spec-refs\u002Fgood\u002Foverlay\u002F.maestro\u002Fadd-task.yaml",{"path":149,"resourceType":60,"resourceTypeDesc":61,"sizeBytes":150,"sourceHtmlUrl":151},"tests\u002Ffixtures\u002Fcheck-spec-refs\u002Fgood\u002Foverlay\u002Fdocs\u002Fnotes.md",339,"https:\u002F\u002Fgithub.com\u002Fzakariaf\u002FReactNative-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fspec-traceability\u002Ftests\u002Ffixtures\u002Fcheck-spec-refs\u002Fgood\u002Foverlay\u002Fdocs\u002Fnotes.md",{"path":153,"resourceType":60,"resourceTypeDesc":61,"sizeBytes":154,"sourceHtmlUrl":155},"tests\u002Ffixtures\u002Fcheck-spec-refs\u002Fgood\u002Foverlay\u002Fscripts\u002Fgit\u002Fcommit-message-samples.json",86,"https:\u002F\u002Fgithub.com\u002Fzakariaf\u002FReactNative-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fspec-traceability\u002Ftests\u002Ffixtures\u002Fcheck-spec-refs\u002Fgood\u002Foverlay\u002Fscripts\u002Fgit\u002Fcommit-message-samples.json",{"path":157,"resourceType":74,"resourceTypeDesc":75,"sizeBytes":158,"sourceHtmlUrl":159},"tests\u002Ffixtures\u002Fcheck-spec-refs\u002Fgood\u002Foverlay\u002Fsrc\u002Ffeatures\u002Ftasks\u002Fadd-task.test.ts",643,"https:\u002F\u002Fgithub.com\u002Fzakariaf\u002FReactNative-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fspec-traceability\u002Ftests\u002Ffixtures\u002Fcheck-spec-refs\u002Fgood\u002Foverlay\u002Fsrc\u002Ffeatures\u002Ftasks\u002Fadd-task.test.ts",{"path":161,"resourceType":60,"resourceTypeDesc":61,"sizeBytes":162,"sourceHtmlUrl":163},"tests\u002Ffixtures\u002Fcheck-spec-refs\u002FSUITE.json",71,"https:\u002F\u002Fgithub.com\u002Fzakariaf\u002FReactNative-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fspec-traceability\u002Ftests\u002Ffixtures\u002Fcheck-spec-refs\u002FSUITE.json",{"path":165,"resourceType":60,"resourceTypeDesc":61,"sizeBytes":166,"sourceHtmlUrl":167},"tests\u002Ffixtures\u002Fspec-lookup\u002FCASES.json",2444,"https:\u002F\u002Fgithub.com\u002Fzakariaf\u002FReactNative-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fspec-traceability\u002Ftests\u002Ffixtures\u002Fspec-lookup\u002FCASES.json",{"path":169,"resourceType":60,"resourceTypeDesc":61,"sizeBytes":170,"sourceHtmlUrl":171},"tests\u002Ffixtures\u002Fspec-lookup\u002Fgood\u002FARGS.txt",43,"https:\u002F\u002Fgithub.com\u002Fzakariaf\u002FReactNative-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fspec-traceability\u002Ftests\u002Ffixtures\u002Fspec-lookup\u002Fgood\u002FARGS.txt",{"path":173,"resourceType":60,"resourceTypeDesc":61,"sizeBytes":174,"sourceHtmlUrl":175},"tests\u002Ffixtures\u002Fspec-lookup\u002Fgood\u002FEXPECT.txt",332,"https:\u002F\u002Fgithub.com\u002Fzakariaf\u002FReactNative-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fspec-traceability\u002Ftests\u002Ffixtures\u002Fspec-lookup\u002Fgood\u002FEXPECT.txt",{"path":177,"resourceType":60,"resourceTypeDesc":61,"sizeBytes":178,"sourceHtmlUrl":179},"tests\u002Ffixtures\u002Fspec-lookup\u002FSUITE.json",52,"https:\u002F\u002Fgithub.com\u002Fzakariaf\u002FReactNative-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fspec-traceability\u002Ftests\u002Ffixtures\u002Fspec-lookup\u002FSUITE.json",[181,188,194,201,208,215],{"skillNo":182,"name":183,"nameZh":6,"description":184,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":185,"categories":186,"keywords":187,"publishedAt":19},"01M7F2S4KZG97D21GEJ2GKKYK1","demo","Planted skill folder (never scanned).","https:\u002F\u002Fgithub.com\u002Fzakariaf\u002FReactNative-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fweb-support\u002Ftests\u002Fbases\u002Fapp\u002Fskills\u002Fdemo\u002FSKILL.md",[],[],{"skillNo":189,"name":183,"nameZh":6,"description":190,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":191,"categories":192,"keywords":193,"publishedAt":19},"01M7F2S1F4ATZ49909EDKWA9E6","Planted installed skill (its files must never be scanned).","https:\u002F\u002Fgithub.com\u002Fzakariaf\u002FReactNative-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fweb-support\u002Ftests\u002Fbases\u002Fapp\u002F.agents\u002Fskills\u002Fdemo\u002FSKILL.md",[],[],{"skillNo":195,"name":196,"nameZh":6,"description":197,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":198,"categories":199,"keywords":200,"publishedAt":19},"01M7F2RXGPZJ5Q1FV2HQ1PJ6AX","web-support","Ships the web build of an Expo app: platform files, APIs missing in react-native-web, expo-sqlite headers. Use when adding web, a .web.tsx file or expo export --platform web. Not for responsive layout (adaptive-layout).","https:\u002F\u002Fgithub.com\u002Fzakariaf\u002FReactNative-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fweb-support\u002FSKILL.md",[],[],{"skillNo":202,"name":203,"nameZh":6,"description":204,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":205,"categories":206,"keywords":207,"publishedAt":19},"01M7F2RQ43JFA4QFWQEHBET08G","value-objects-money-and-units","Stores money as ISO 4217 minor units, quantities in canonical units, instants as epoch ms. Use when adding a price, currency, tax, split, unit or timestamp, or a total is a cent off. Not for calendar days (dates-streaks-and-statistics).","https:\u002F\u002Fgithub.com\u002Fzakariaf\u002FReactNative-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fvalue-objects-money-and-units\u002FSKILL.md",[],[],{"skillNo":209,"name":210,"nameZh":6,"description":211,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":212,"categories":213,"keywords":214,"publishedAt":19},"01M7F2RHR7H8VVZDP16FJNJV11","unit-and-component-tests","Sets up Jest, checks unit, component and route tests (RNTL 14, renderWithProviders, SDK mocks, fakes, fast-check, Stryker). Use when writing a test or mock, or Jest fails or flakes. Not for goldens (golden-and-snapshot-tests).","https:\u002F\u002Fgithub.com\u002Fzakariaf\u002FReactNative-Skills\u002Fblob\u002Fmain\u002Fskills\u002Funit-and-component-tests\u002FSKILL.md",[],[],{"skillNo":216,"name":217,"nameZh":6,"description":218,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":219,"categories":220,"keywords":221,"publishedAt":19},"01M7F2RAEDWQ6H4514HFRWJAE6","ui-states-and-feedback","Builds loading, empty, failed and offline states, delayed skeletons, toasts, banners, confirms, Undo. Use when a screen loads data, shows a spinner, toast, retry or delete prompt. Not for failure values (error-handling-typed-results).","https:\u002F\u002Fgithub.com\u002Fzakariaf\u002FReactNative-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fui-states-and-feedback\u002FSKILL.md",[],[]]