[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7EVKQJ4M2HE2MZTAZAM62W2":3,"skill-same:01M7EVKQJ4M2HE2MZTAZAM62W2":60},{"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":40,"commitSha":41,"skillDirectory":42,"forksCount":14,"repositoryHtmlUrl":43,"repositoryHomepageUrl":43,"ownerHtmlUrl":44,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":45,"install":46,"resources":59},"01M7EVKQJ4M2HE2MZTAZAM62W2","cross-platform-contract-propagation-audit",null,"Use when auditing whether a field, enum, flag, or API contract propagates consistently across storage, services, clients, analytics, and tests.","Mr-Nobody-Anonymous\u002FAll-skills","Mr-Nobody-Anonymous","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F184253119?v=4","01M7AEXFJHKTYQW5R0ZCQQTWFV","anonymous","01M7C00M3GQR4QKP9GZA42GFAK",0,"MIT","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fdevelopment\u002Fcross-platform-contract-propagation-audit\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: cross-platform-contract-propagation-audit\ndescription: \"Use when auditing whether a field, enum, flag, or API contract propagates consistently across storage, services, clients, analytics, and tests.\"\ncategory: development\nrisk: safe\nsource: self\nsource_type: self\ndate_added: \"2026-08-18\"\nauthor: Whxuan0701\ntags: [contract-audit, cross-platform, api, schema, feature-flags]\ntools: [claude, cursor, gemini, codex]\n---\n\n# Cross-Platform Contract Propagation Audit\n\n## Overview\n\nAudit a contract change from its source through every transformation and consumer before release. Treat a field that exists in one schema as incomplete until its meaning, defaults, wire behavior, rollout controls, client handling, analytics, and tests are proven across all relevant paths.\n\nThis is a read-only evidence workflow. It reports propagation gaps; it does not implement them.\n\n## When to Use This Skill\n\n- Use when adding or changing a field, enum value, status, capability, or feature flag shared by multiple components.\n- Use when database, backend, API, Web, Android, iOS, jobs, events, or analytics may interpret the same value differently.\n- Use when a change must preserve existing records, older clients, or a default-off rollout.\n- Use when a change looks complete in one endpoint but may be missing from alternate entry points or generated models.\n\n## How It Works\n\n### Step 1: Write the semantic contract\n\nBefore tracing files, state the business invariant and define every observable state. Distinguish values that languages and serializers often collapse:\n\n| State | Questions to answer |\n|---|---|\n| missing | Is the property absent on the wire or in an old record? |\n| `null` | Is it unknown, inherited, unsupported, or invalid? |\n| `false` or zero | Is this an explicit disabled value or a default? |\n| `true` or non-zero | What behavior becomes available? |\n| unknown enum | Must old consumers ignore, preserve, or reject it? |\n\nRecord compatibility requirements, ownership, rollout condition, and the exact user-visible or system behavior for each state. Do not accept `optional`, `nullable`, and `default false` as equivalent without evidence.\n\n### Step 2: Enumerate the propagation graph\n\nList every relevant node before judging completeness:\n\n```text\nsource of truth\n  -> persistence and migration\n  -> domain model and mapper\n  -> service or policy computation\n  -> every API, event, cache, and job projection\n  -> generated or handwritten client model\n  -> client state and presentation logic\n  -> analytics and operational observability\n  -> tests, rollout, and rollback checks\n```\n\nInclude alternate read\u002Fwrite endpoints, list\u002Fdetail projections, background consumers, offline caches, admin surfaces, older app versions, and feature-flag evaluation points when they are in scope. Mark a node `not applicable` only with a reason.\n\n### Step 3: Trace evidence edge by edge\n\nFor each edge, cite the producer, transformation, consumer, and test using file paths, symbols, schema names, or other inspectable evidence. Assign one status:\n\n| Status | Meaning |\n|---|---|\n| `proven` | Producer and consumer agree, with direct evidence and relevant test coverage. |\n| `partial` | Some paths or states agree, but coverage is incomplete. |\n| `missing` | A required propagation edge or consumer is absent. |\n| `conflict` | Two layers implement different semantics. |\n| `unknown` | Evidence is unavailable or ambiguous. |\n| `not_applicable` | The layer is outside scope, with a stated reason. |\n\nDo not upgrade `likely`, convention, type compatibility, or a framework default to `proven`. A declaration proves shape, not runtime mapping or behavior.\n\n### Step 4: Check the high-risk boundaries\n\nInspect these boundaries explicitly:\n\n- **Migration and existing data:** default, backfill, nullability, rollback, mixed-version reads and writes.\n- **Domain mapping:** missing\u002Fnull coercion, enum fallbacks, validation, derived values, serialization symmetry.\n- **Fan-out surfaces:** list and detail DTOs, events, caches, jobs, search indexes, SDKs, and alternate API versions.\n- **Client compatibility:** missing and explicit-null decoding, unknown enums, generated-model drift, cached payloads, release or minified builds.\n- **Rollout control:** flag default, evaluation location, cohort consistency, kill switch, and behavior when stored data disagrees with the flag.\n- **Analytics:** offered, rendered, attempted, succeeded, and failed events carry enough contract and version context to join reliably.\n\n### Step 5: Build a state-by-path test matrix\n\nCross the semantic states from Step 1 with every material path from Step 2. At minimum, include existing-data defaults, enabled and disabled values, flag on and off, alternate endpoints, current clients, and representative older clients.\n\nFor each cell, record the expected result, evidence, and status. A unit test at one layer does not prove an end-to-end cell. Use `unknown` for unexecuted cells.\n\n### Step 6: Decide against explicit release gates\n\nDerive gates from the stated contract, not from intuition. A release is blocked when an edge or compatibility invariant that the contract explicitly requires is `missing`, `conflict`, or `unknown`, or when rollback cannot contain the new behavior. Use `inconclusive` only when the release contract itself is absent or ambiguous, so the audit cannot determine which edges or invariants are required. Do not downgrade a known required but unproven gate from `blocked` to `inconclusive`.\n\nReturn the smallest verification or repair set that would change the verdict. Keep implementation suggestions separate from proven findings.\n\n## Example\n\nFor a nullable `can_complete` field that should expose an action only when both the stored capability and server flag are true:\n\n```text\nInvariant: show action = (feature_flag == on) AND (can_complete == true)\n\nPath                                      Status    Evidence\nDB null -> domain false -> detail API     partial   mapper exists; null case untested\nDB true + flag off -> detail API          unknown   flag branch not tested\nDB true + flag on -> list API             missing   list DTO omits field\nmissing field -> Web hidden               proven    client test covers missing\nexplicit null -> Android hidden           unknown   decoder behavior untested\nimpression -> click attribution           missing   click event lacks capability\u002Fcohort\n\nVerdict: blocked by the missing list projection and incomplete flag enforcement;\nolder-client and explicit-null compatibility remain unverified.\n```\n\n## Best Practices\n\n- Start from behavior and state semantics, then trace code; do not start from a filename guess.\n- Search for field names, serialized aliases, enum values, DTOs, mappers, flags, and analytics events.\n- Cite negative searches with their scope and revision; absence claims require a bounded search.\n- Separate source-of-truth behavior from client presentation and telemetry.\n- Verify all entry points that can produce the same user-visible state.\n- Keep findings reproducible: contract, revision, evidence, status, impact, and next check.\n\n## Limitations\n\n- Static evidence cannot prove runtime configuration, deployed schema state, generated-code freshness, or client behavior that was not exercised.\n- Repository access may omit private services, analytics schemas, remote flags, or older released clients; mark those edges `unknown`.\n- This skill finds propagation and semantic gaps, not every security, performance, or product-design defect.\n- A complete graph does not prove the underlying business rule is correct.\n\n## Security & Safety Notes\n\n- Keep the audit read-only unless the user separately authorizes implementation or runtime testing.\n- Redact production records, credentials, user identifiers, and sensitive payload fields from evidence.\n- Do not enable flags, mutate data, publish schemas, or exercise production actions merely to fill an evidence gap.\n\n## Common Pitfalls\n\n- **Problem:** The field exists in the database and one response, so the change is called complete.\n  **Solution:** Trace every projection and consumer, including alternate endpoints and events.\n- **Problem:** Missing, null, and false are treated as the same state.\n  **Solution:** Define and test each state at every serialization boundary.\n- **Problem:** Type declarations are treated as runtime proof.\n  **Solution:** Require mapping, decoding, behavior, and test evidence before using `proven`.\n- **Problem:** The feature flag hides UI but not data or alternate APIs.\n  **Solution:** Map every flag evaluation point and test stored-value\u002Fflag combinations.\n- **Problem:** A green unit test suite is presented as cross-platform coverage.\n  **Solution:** Build the state-by-path matrix and preserve unexecuted cells as `unknown`.\n\n## Related Skills\n\n- `@api-analyzer` - Validate the correctness of an individual API request.\n- `@spec-to-code-compliance` - Compare formal blockchain specifications with implementations.\n- `@technical-change-tracker` - Record implementation progress and handoff state across sessions.\n","# Cross-Platform Contract Propagation Audit\n\n## Overview\n\nAudit a contract change from its source through every transformation and consumer before release. Treat a field that exists in one schema as incomplete until its meaning, defaults, wire behavior, rollout controls, client handling, analytics, and tests are proven across all relevant paths.\n\nThis is a read-only evidence workflow. It reports propagation gaps; it does not implement them.\n\n## When to Use This Skill\n\n- Use when adding or changing a field, enum value, status, capability, or feature flag shared by multiple components.\n- Use when database, backend, API, Web, Android, iOS, jobs, events, or analytics may interpret the same value differently.\n- Use when a change must preserve existing records, older clients, or a default-off rollout.\n- Use when a change looks complete in one endpoint but may be missing from alternate entry points or generated models.\n\n## How It Works\n\n### Step 1: Write the semantic contract\n\nBefore tracing files, state the business invariant and define every observable state. Distinguish values that languages and serializers often collapse:\n\n| State | Questions to answer |\n|---|---|\n| missing | Is the property absent on the wire or in an old record? |\n| `null` | Is it unknown, inherited, unsupported, or invalid? |\n| `false` or zero | Is this an explicit disabled value or a default? |\n| `true` or non-zero | What behavior becomes available? |\n| unknown enum | Must old consumers ignore, preserve, or reject it? |\n\nRecord compatibility requirements, ownership, rollout condition, and the exact user-visible or system behavior for each state. Do not accept `optional`, `nullable`, and `default false` as equivalent without evidence.\n\n### Step 2: Enumerate the propagation graph\n\nList every relevant node before judging completeness:\n\n```text\nsource of truth\n  -> persistence and migration\n  -> domain model and mapper\n  -> service or policy computation\n  -> every API, event, cache, and job projection\n  -> generated or handwritten client model\n  -> client state and presentation logic\n  -> analytics and operational observability\n  -> tests, rollout, and rollback checks\n```\n\nInclude alternate read\u002Fwrite endpoints, list\u002Fdetail projections, background consumers, offline caches, admin surfaces, older app versions, and feature-flag evaluation points when they are in scope. Mark a node `not applicable` only with a reason.\n\n### Step 3: Trace evidence edge by edge\n\nFor each edge, cite the producer, transformation, consumer, and test using file paths, symbols, schema names, or other inspectable evidence. Assign one status:\n\n| Status | Meaning |\n|---|---|\n| `proven` | Producer and consumer agree, with direct evidence and relevant test coverage. |\n| `partial` | Some paths or states agree, but coverage is incomplete. |\n| `missing` | A required propagation edge or consumer is absent. |\n| `conflict` | Two layers implement different semantics. |\n| `unknown` | Evidence is unavailable or ambiguous. |\n| `not_applicable` | The layer is outside scope, with a stated reason. |\n\nDo not upgrade `likely`, convention, type compatibility, or a framework default to `proven`. A declaration proves shape, not runtime mapping or behavior.\n\n### Step 4: Check the high-risk boundaries\n\nInspect these boundaries explicitly:\n\n- **Migration and existing data:** default, backfill, nullability, rollback, mixed-version reads and writes.\n- **Domain mapping:** missing\u002Fnull coercion, enum fallbacks, validation, derived values, serialization symmetry.\n- **Fan-out surfaces:** list and detail DTOs, events, caches, jobs, search indexes, SDKs, and alternate API versions.\n- **Client compatibility:** missing and explicit-null decoding, unknown enums, generated-model drift, cached payloads, release or minified builds.\n- **Rollout control:** flag default, evaluation location, cohort consistency, kill switch, and behavior when stored data disagrees with the flag.\n- **Analytics:** offered, rendered, attempted, succeeded, and failed events carry enough contract and version context to join reliably.\n\n### Step 5: Build a state-by-path test matrix\n\nCross the semantic states from Step 1 with every material path from Step 2. At minimum, include existing-data defaults, enabled and disabled values, flag on and off, alternate endpoints, current clients, and representative older clients.\n\nFor each cell, record the expected result, evidence, and status. A unit test at one layer does not prove an end-to-end cell. Use `unknown` for unexecuted cells.\n\n### Step 6: Decide against explicit release gates\n\nDerive gates from the stated contract, not from intuition. A release is blocked when an edge or compatibility invariant that the contract explicitly requires is `missing`, `conflict`, or `unknown`, or when rollback cannot contain the new behavior. Use `inconclusive` only when the release contract itself is absent or ambiguous, so the audit cannot determine which edges or invariants are required. Do not downgrade a known required but unproven gate from `blocked` to `inconclusive`.\n\nReturn the smallest verification or repair set that would change the verdict. Keep implementation suggestions separate from proven findings.\n\n## Example\n\nFor a nullable `can_complete` field that should expose an action only when both the stored capability and server flag are true:\n\n```text\nInvariant: show action = (feature_flag == on) AND (can_complete == true)\n\nPath                                      Status    Evidence\nDB null -> domain false -> detail API     partial   mapper exists; null case untested\nDB true + flag off -> detail API          unknown   flag branch not tested\nDB true + flag on -> list API             missing   list DTO omits field\nmissing field -> Web hidden               proven    client test covers missing\nexplicit null -> Android hidden           unknown   decoder behavior untested\nimpression -> click attribution           missing   click event lacks capability\u002Fcohort\n\nVerdict: blocked by the missing list projection and incomplete flag enforcement;\nolder-client and explicit-null compatibility remain unverified.\n```\n\n## Best Practices\n\n- Start from behavior and state semantics, then trace code; do not start from a filename guess.\n- Search for field names, serialized aliases, enum values, DTOs, mappers, flags, and analytics events.\n- Cite negative searches with their scope and revision; absence claims require a bounded search.\n- Separate source-of-truth behavior from client presentation and telemetry.\n- Verify all entry points that can produce the same user-visible state.\n- Keep findings reproducible: contract, revision, evidence, status, impact, and next check.\n\n## Limitations\n\n- Static evidence cannot prove runtime configuration, deployed schema state, generated-code freshness, or client behavior that was not exercised.\n- Repository access may omit private services, analytics schemas, remote flags, or older released clients; mark those edges `unknown`.\n- This skill finds propagation and semantic gaps, not every security, performance, or product-design defect.\n- A complete graph does not prove the underlying business rule is correct.\n\n## Security & Safety Notes\n\n- Keep the audit read-only unless the user separately authorizes implementation or runtime testing.\n- Redact production records, credentials, user identifiers, and sensitive payload fields from evidence.\n- Do not enable flags, mutate data, publish schemas, or exercise production actions merely to fill an evidence gap.\n\n## Common Pitfalls\n\n- **Problem:** The field exists in the database and one response, so the change is called complete.\n  **Solution:** Trace every projection and consumer, including alternate endpoints and events.\n- **Problem:** Missing, null, and false are treated as the same state.\n  **Solution:** Define and test each state at every serialization boundary.\n- **Problem:** Type declarations are treated as runtime proof.\n  **Solution:** Require mapping, decoding, behavior, and test evidence before using `proven`.\n- **Problem:** The feature flag hides UI but not data or alternate APIs.\n  **Solution:** Map every flag evaluation point and test stored-value\u002Fflag combinations.\n- **Problem:** A green unit test suite is presented as cross-platform coverage.\n  **Solution:** Build the state-by-path matrix and preserve unexecuted cells as `unknown`.\n\n## Related Skills\n\n- `@api-analyzer` - Validate the correctness of an individual API request.\n- `@spec-to-code-compliance` - Compare formal blockchain specifications with implementations.\n- `@technical-change-tracker` - Record implementation progress and handoff state across sessions.\n",{"name":5,"risk":24,"tags":25,"tools":31,"author":36,"source":37,"category":38,"date_added":39,"description":7,"source_type":37},"safe",[26,27,28,29,30],"contract-audit","cross-platform","api","schema","feature-flags",[32,33,34,35],"claude","cursor","gemini","codex","Whxuan0701","self","development","2026-08-18","main","2d1750717747097b602acf30bd09a7cbd4b4c6ea","awesome_skills\u002Fdevelopment\u002Fcross-platform-contract-propagation-audit","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous","2026-11-09 11:45:36",{"source":8,"skillName":5,"commands":47,"prompt":57,"zipAvailable":58},[48,51,54],{"tool":49,"command":50},"npx","npx skills add Mr-Nobody-Anonymous\u002FAll-skills --skill cross-platform-contract-propagation-audit",{"tool":52,"command":53},"bunx","bunx skills add Mr-Nobody-Anonymous\u002FAll-skills --skill cross-platform-contract-propagation-audit",{"tool":55,"command":56},"pnpm","pnpm dlx skills add Mr-Nobody-Anonymous\u002FAll-skills --skill cross-platform-contract-propagation-audit","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fdevelopment\u002Fcross-platform-contract-propagation-audit\u002FSKILL.md",true,[],[61,69,76,83,90,97],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":68},"01M7FFFZPC2025JQQHPHDX154J","dei-assessment","Assess diversity, equity, and inclusion with metrics. TRIGGERS - Use when user needs help with dei-assessment related tasks.","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fhr-people\u002Fdei-assessment\u002FSKILL.md",[],[],"2026-11-16 10:05:34",{"skillNo":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"publishedAt":68},"01M7FFFWN8H4WA7A6Y398QKB6J","dei-action-plan","Create DEI action plans with goals and initiatives. TRIGGERS - Use when user needs help with dei-action-plan related tasks.","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fhr-people\u002Fdei-action-plan\u002FSKILL.md",[],[],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":68},"01M7FFFSHTM0QZRVZ2NRJTJ0PY","culture-fit-assessment","Design culture add assessment processes. TRIGGERS - Use when user needs help with culture-fit-assessment related tasks.","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fhr-people\u002Fculture-fit-assessment\u002FSKILL.md",[],[],{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":68},"01M7FFFMA12RKEQA38KHJSXXPS","cowork-to-code-bridge","Use an already-installed, independently verified cowork-to-code bridge to run narrowly approved actions on the user's own macOS, Linux, or WSL2 machine through a local file queue.","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fhr-people\u002Fcowork-to-code-bridge\u002FSKILL.md",[],[],{"skillNo":91,"name":92,"nameZh":6,"description":93,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":94,"categories":95,"keywords":96,"publishedAt":68},"01M7FFFH1F6M8YRGW5V487GH1K","counter-offer-response","Draft counter-offer responses for retention. TRIGGERS - Use when user needs help with counter-offer-response related tasks.","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fhr-people\u002Fcounter-offer-response\u002FSKILL.md",[],[],{"skillNo":98,"name":99,"nameZh":6,"description":100,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":101,"categories":102,"keywords":103,"publishedAt":68},"01M7FFFDGEHV8Y7J9N40HZXW52","continuous-feedback-system","Design continuous feedback systems. TRIGGERS - Use when user needs help with continuous-feedback-system related tasks.","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fhr-people\u002Fcontinuous-feedback-system\u002FSKILL.md",[],[]]