[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M753VGF1KWQ0MXSCJ6FX64WE":3,"skill-same:01M753VGF1KWQ0MXSCJ6FX64WE":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":28,"commitSha":29,"skillDirectory":30,"forksCount":14,"repositoryHtmlUrl":31,"repositoryHomepageUrl":6,"ownerHtmlUrl":32,"ownerBlogUrl":33,"ownerDescription":34,"updatedAt":35,"install":36,"resources":49},"01M753VGF1KWQ0MXSCJ6FX64WE","no-workarounds",null,"Enforce root-cause fixes over workarounds, hacks, and symptom patches in all software engineering tasks. Use when debugging issues, fixing bugs, resolving test failures, planning solutions, making architectural decisions, or reviewing code changes. Activates gate functions that detect and reject common workaround patterns such as type assertions, lint suppressions, error swallowing, timing hacks, and monkey patches. Don't use for trivial formatting changes or documentation-only edits.","haryelramalho\u002Fskills","haryelramalho","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F38708454?v=4","01M753ESC6XNS6GXGV5X9YMKGA","Haryel Ramalho","01M753ESCSPRNDTEJRVRYY1VJ0",0,"MIT","https:\u002F\u002Fgithub.com\u002Fharyelramalho\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fcurated\u002Fno-workarounds\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: no-workarounds\ndescription: Enforce root-cause fixes over workarounds, hacks, and symptom patches in all software engineering tasks. Use when debugging issues, fixing bugs, resolving test failures, planning solutions, making architectural decisions, or reviewing code changes. Activates gate functions that detect and reject common workaround patterns such as type assertions, lint suppressions, error swallowing, timing hacks, and monkey patches. Don't use for trivial formatting changes or documentation-only edits.\nmetadata:\n  author: Pedro Nauck\n  github: https:\u002F\u002Fgithub.com\u002Fpedronauck\n  repository: https:\u002F\u002Fgithub.com\u002Fpedronauck\u002Fskills\n---\n# No Workarounds\n\n## The Fundamental Law\n\n```\nA WORKAROUND IS A LIE TOLD TO THE COMPILER.\nIt makes the symptom disappear while the disease spreads.\n```\n\nA workaround is any change that makes a problem stop manifesting without addressing why the problem exists. Workarounds are not fixes. They are deferred failures with compound interest.\n\n**Philosophical foundation:** Read `references\u002Fphilosophical-foundations.md` for the engineering principles behind this skill, drawn from Toyota's Jidoka, Fowler's Technical Debt Quadrant, Torvalds' \"good taste,\" and the Broken Windows Theory.\n\n## The Workaround Detection Gate\n\n```\nBEFORE writing or proposing ANY fix:\n\n1. STATE the problem clearly\n2. ASK: \"Why does this problem exist?\" (not \"How do I make it stop?\")\n3. TRACE to root cause (use systematic-debugging skill)\n4. ASK: \"Does my proposed fix address the ROOT CAUSE?\"\n5. ASK: \"Would this fix be necessary if the code were correct?\"\n6. ASK: \"Am I silencing a signal or fixing a source?\"\n\nIF any answer reveals symptom-patching:\n  STOP — Redesign the fix to address root cause\n\nIF root cause is in external code or truly unfixable:\n  Document why, add defensive validation, and mark with WORKAROUND comment\n  (See \"The Escape Valve\" section below)\n```\n\n## The Seven Categories of Workarounds\n\n### Category 1 — TYPE: Type System Evasion\n\n**The signal being silenced:** The type system is telling the code is wrong.\n\n```typescript\n\u002F\u002F WORKAROUND: Lying to the compiler\nconst value = response.data as UserProfile;\nconst config = {} as AppConfig;\nfunction process(input: any) { ... }\n\n\u002F\u002F PROPER FIX: Make types truthful\nconst value: UserProfile | undefined = response.data;\nif (!value) throw new Error(\"Missing user profile\");\n\nconst config: AppConfig = { theme: \"light\", locale: \"en\" };\n\nfunction process(input: UserProfile) { ... }\n```\n\n**Gate function:**\n\n```\nBEFORE using `as`, `any`, `unknown` cast, or `!` (non-null assertion):\n  Ask: \"Why doesn't the type match?\"\n\n  IF the data shape is genuinely unknown:\n    Use runtime validation (Schema, Zod, or type guards)\n  IF the type is wrong:\n    Fix the type definition\n  IF the API returns unexpected shape:\n    Fix the API contract or add a validation layer\n  NEVER use type assertions to bypass compiler errors\n```\n\n### Category 2 — LINT: Lint and Warning Suppression\n\n**The signal being silenced:** Static analysis found a real problem.\n\n```typescript\n\u002F\u002F WORKAROUND: Shooting the messenger\n\u002F\u002F eslint-disable-next-line @typescript-eslint\u002Fno-unused-vars\nconst result = fetchData();\n\n\u002F\u002F @ts-ignore\nsomeFunction(wrongArgs);\n\n\u002F\u002F @ts-expect-error - TODO fix later\nbrokenCall();\n\n\u002F\u002F PROPER FIX: Fix what the linter found\nfetchData(); \u002F\u002F Remove unused binding\n\nsomeFunction(correctArgs); \u002F\u002F Fix the arguments\n```\n\n**Gate function:**\n\n```\nBEFORE adding eslint-disable, @ts-ignore, @ts-expect-error, or any suppression:\n  Ask: \"What rule is being violated and WHY?\"\n\n  IF the code genuinely violates the rule:\n    Fix the code, not the linter\n  IF the rule is wrong for this codebase:\n    Disable the rule in config (globally), not inline\n  IF it's a third-party type issue:\n    File an issue, add a minimal typed wrapper\n  NEVER suppress a warning without understanding it\n```\n\n### Category 3 — SWALLOW: Error Swallowing\n\n**The signal being silenced:** Something failed and the code pretends it didn't.\n\n```typescript\n\u002F\u002F WORKAROUND: Pretending errors don't exist\ntry {\n  await saveData(payload);\n} catch {\n  \u002F\u002F silently ignore\n}\n\ntry {\n  result = JSON.parse(input);\n} catch {\n  result = {}; \u002F\u002F default to empty - hides corrupt data\n}\n\n\u002F\u002F PROPER FIX: Handle errors meaningfully\ntry {\n  await saveData(payload);\n} catch (error) {\n  logger.error(\"Failed to save data\", { error, payload });\n  throw new SaveError(\"Data save failed\", { cause: error });\n}\n\nconst parsed = Schema.decodeUnknownSync(PayloadSchema)(input);\n\u002F\u002F Throws descriptive error if input is invalid\n```\n\n**Gate function:**\n\n```\nBEFORE writing a catch block:\n  Ask: \"What specific errors can occur here?\"\n  Ask: \"What should happen when each error occurs?\"\n\n  IF the answer is \"ignore it\":\n    STOP — Ignoring errors hides bugs\n  IF the answer is \"log it\":\n    Log AND propagate or handle meaningfully\n  IF the answer is \"use a default\":\n    Ensure the default is SAFE and the failure is LOGGED\n  NEVER write an empty catch block\n  NEVER catch Exception\u002FError broadly without re-throwing specific types\n```\n\n### Category 4 — TIMING: Timing and Lifecycle Hacks\n\n**The signal being silenced:** Code runs in the wrong order or at the wrong time.\n\n```typescript\n\u002F\u002F WORKAROUND: Racing against the clock\nsetTimeout(() => {\n  element.focus();\n}, 100);\n\nawait new Promise((resolve) => setTimeout(resolve, 500));\n\u002F\u002F \"wait for state to settle\"\n\nawait retry(() => checkCondition(), { times: 10, delay: 200 });\n\u002F\u002F retry loop hiding a race condition\n\n\u002F\u002F PROPER FIX: Fix the lifecycle\n\u002F\u002F Use framework-native lifecycle hooks\nuseEffect(() => {\n  if (ref.current) ref.current.focus();\n}, [isVisible]);\n\n\u002F\u002F Use proper event-driven coordination\nawait waitForEvent(emitter, \"ready\");\n\n\u002F\u002F Use condition-based polling (not blind retries)\nawait waitUntil(() => service.isReady(), {\n  timeout: 5000,\n  message: \"Service failed to become ready\",\n});\n```\n\n**Gate function:**\n\n```\nBEFORE adding setTimeout, delay, sleep, or retry loops:\n  Ask: \"WHY is the timing wrong?\"\n  Ask: \"What event signals that the system is ready?\"\n\n  IF there's an event or callback available:\n    Use it instead of arbitrary delays\n  IF the ordering is wrong:\n    Fix the initialization order\n  IF it's a test timing issue:\n    Use condition-based waiting, never arbitrary sleeps\n  NEVER use setTimeout(fn, 0) to \"fix\" rendering issues\n  NEVER use arbitrary delays to \"wait for things to settle\"\n```\n\n### Category 5 — PATCH: Monkey Patching and Runtime Mutation\n\n**The signal being silenced:** The API doesn't do what the code needs.\n\n```typescript\n\u002F\u002F WORKAROUND: Mutating things you don't own\nArray.prototype.customMethod = function () { ... };\nObject.defineProperty(window, \"fetch\", { value: customFetch });\nlibrary.internals._privateMethod = replacement;\n\n\u002F\u002F PROPER FIX: Composition over mutation\nfunction customOperation\u003CT>(arr: T[]): T[] { ... }\nconst wrappedFetch = createFetchWrapper(window.fetch);\nconst adapter = new LibraryAdapter(library);\n```\n\n**Gate function:**\n\n```\nBEFORE modifying prototypes, globals, or third-party internals:\n  Ask: \"Does the library provide an extension point?\"\n\n  IF yes: Use the official extension mechanism\n  IF no: Wrap with composition\u002Fadapter pattern\n  IF the library is broken: File issue, fork, or find alternative\n  NEVER modify objects the code doesn't own\n```\n\n### Category 6 — SCATTER: Defensive Duplication\n\n**The signal being silenced:** The data is unreliable at its source.\n\n```typescript\n\u002F\u002F WORKAROUND: Checking everywhere because source is broken\nfunction renderUser(user: User) {\n  const name = user?.name ?? user?.displayName ?? \"Unknown\";\n  const email = user?.email ?? user?.contacts?.email ?? \"\";\n  const id = user?.id ?? user?.userId ?? user?._id ?? \"\";\n  \u002F\u002F ... 20 more optional chains\n}\n\n\u002F\u002F PROPER FIX: Validate once at the boundary\nconst user = Schema.decodeUnknownSync(UserSchema)(rawData);\n\u002F\u002F user is now guaranteed to have correct shape\n\nfunction renderUser(user: User) {\n  \u002F\u002F No defensive checks needed — schema validated at entry\n  return `${user.name} (${user.email})`;\n}\n```\n\n**Gate function:**\n\n```\nBEFORE adding optional chaining (?.) or nullish coalescing (??) deeply:\n  Ask: \"Why might this value be missing?\"\n  Ask: \"Where does this data enter the system?\"\n\n  IF data is unvalidated at entry:\n    Add validation at the boundary, remove defensive checks downstream\n  IF the type allows undefined but shouldn't:\n    Fix the type to be non-optional\n  IF it's truly optional:\n    Handle the None\u002Fundefined case explicitly at the nearest decision point\n  NEVER scatter optional chains as a substitute for proper validation\n```\n\n### Category 7 — CLONE: Copy-Paste Adaptation\n\n**The signal being silenced:** The abstraction doesn't fit but the developer forces it.\n\n```typescript\n\u002F\u002F WORKAROUND: Copy and \"adapt\" (badly)\n\u002F\u002F Copied from UserService and changed 3 lines\nfunction createProject(data: ProjectData) {\n  \u002F\u002F 200 lines, 95% identical to createUser\n  \u002F\u002F but with subtle bugs from incomplete adaptation\n}\n\n\u002F\u002F PROPER FIX: Extract shared pattern or write fresh\n\u002F\u002F Option A: Extract the common pattern\nfunction createEntity\u003CT>(schema: Schema\u003CT>, repo: Repository\u003CT>) {\n  return (data: T) => pipe(\n    Schema.decode(schema)(data),\n    Effect.flatMap(repo.insert),\n  );\n}\n\n\u002F\u002F Option B: Write purpose-built code\nfunction createProject(data: ProjectData) {\n  \u002F\u002F Clean, focused implementation for projects\n}\n```\n\n**Gate function:**\n\n```\nBEFORE copying code and modifying it:\n  Ask: \"Am I copying because the pattern is the same or because I'm lazy?\"\n\n  IF the pattern is genuinely the same:\n    Extract a shared abstraction first, then use it\n  IF the pattern is similar but different:\n    Write purpose-built code — similar-looking code with different intent\n    should NOT be forced into the same abstraction\n  NEVER copy-paste more than 5 lines without questioning why\n```\n\n## The Compound Cost\n\nA workaround that saves 30 minutes today costs 30 hours when copied to 5 places, debugged 3 times, and confused 4 developers over 6 months. The interest rate on workarounds is predatory.\n\n## Red Flags — STOP and Rethink\n\nCatch these thought patterns and STOP:\n\n| Thought                                      | What It Means                        |\n| -------------------------------------------- | ------------------------------------ |\n| \"Just add `as any` to make it compile\"       | TYPE — Type system evasion           |\n| \"Disable the lint rule for this line\"        | LINT — Warning suppression           |\n| \"Wrap it in try-catch and ignore the error\"  | SWALLOW — Error swallowing           |\n| \"Add a setTimeout to fix the timing\"         | TIMING — Lifecycle hack              |\n| \"Override the prototype\u002Fglobal\"              | PATCH — Monkey patching              |\n| \"Add `?.` everywhere just to be safe\"        | SCATTER — Defensive duplication      |\n| \"Copy this code and change a few things\"     | CLONE — Copy-paste adaptation        |\n| \"It works, don't touch it\"                   | Fear masking a fragile workaround    |\n| \"We'll fix it properly later\"                | Later never comes                    |\n| \"It's just temporary\"                        | Nothing is more permanent            |\n\n## The Escape Valve\n\nNot every problem can be fixed at root cause. When a workaround is genuinely unavoidable:\n\n```\nREQUIRED conditions (ALL must be true):\n  1. Root cause is in external code the team does not control\n  2. The proper fix requires upstream changes with uncertain timeline\n  3. The business impact of NOT shipping exceeds the technical debt cost\n  4. The workaround is ISOLATED (does not leak into other code)\n\nIF all conditions are met:\n  1. Mark with explicit comment: \u002F\u002F WORKAROUND: [reason] — see [issue-link]\n  2. File a tracking issue for removal\n  3. Add a test that verifies the workaround behavior\n  4. Add a test that will FAIL when the upstream fix lands (canary test)\n  5. Set a review date (max 90 days)\n\nIF any condition is NOT met:\n  Fix the root cause. No exceptions.\n```\n\n## Common Rationalizations\n\n| Excuse                                         | Reality                                                      |\n| ---------------------------------------------- | ------------------------------------------------------------ |\n| \"It's just a small workaround\"                 | Small workarounds become big patterns when copied             |\n| \"We don't have time for the proper fix\"        | Workarounds cost MORE time in debugging and maintenance       |\n| \"The type system is too strict\"                | The type system found a real bug — listen to it               |\n| \"Nobody will copy this\"                        | Every workaround in a codebase gets copied within 3 months   |\n| \"It's behind a feature flag\"                   | Feature flags don't expire — the workaround becomes permanent |\n| \"The test passes\"                              | A passing test with a workaround tests the workaround, not the code |\n| \"I'll create a tech debt ticket\"               | 93% of tech debt tickets are never resolved                  |\n| \"The external library forces this\"             | Use The Escape Valve process above, with all 5 requirements  |\n\n## The Bottom Line\n\n```\nEvery workaround is a bet that nobody will ever need to understand this code again.\nThat bet always loses.\n\nFix the disease, not the symptom.\nFix the source, not the signal.\nFix the code, not the compiler message.\n```\n\n**For the detailed catalog of 30+ specific workaround patterns with before\u002Fafter code:** Read `references\u002Fworkaround-catalog.md`.\n\n**For the philosophical and engineering foundations:** Read `references\u002Fphilosophical-foundations.md`.\n","# No Workarounds\n\n## The Fundamental Law\n\n```\nA WORKAROUND IS A LIE TOLD TO THE COMPILER.\nIt makes the symptom disappear while the disease spreads.\n```\n\nA workaround is any change that makes a problem stop manifesting without addressing why the problem exists. Workarounds are not fixes. They are deferred failures with compound interest.\n\n**Philosophical foundation:** Read `references\u002Fphilosophical-foundations.md` for the engineering principles behind this skill, drawn from Toyota's Jidoka, Fowler's Technical Debt Quadrant, Torvalds' \"good taste,\" and the Broken Windows Theory.\n\n## The Workaround Detection Gate\n\n```\nBEFORE writing or proposing ANY fix:\n\n1. STATE the problem clearly\n2. ASK: \"Why does this problem exist?\" (not \"How do I make it stop?\")\n3. TRACE to root cause (use systematic-debugging skill)\n4. ASK: \"Does my proposed fix address the ROOT CAUSE?\"\n5. ASK: \"Would this fix be necessary if the code were correct?\"\n6. ASK: \"Am I silencing a signal or fixing a source?\"\n\nIF any answer reveals symptom-patching:\n  STOP — Redesign the fix to address root cause\n\nIF root cause is in external code or truly unfixable:\n  Document why, add defensive validation, and mark with WORKAROUND comment\n  (See \"The Escape Valve\" section below)\n```\n\n## The Seven Categories of Workarounds\n\n### Category 1 — TYPE: Type System Evasion\n\n**The signal being silenced:** The type system is telling the code is wrong.\n\n```typescript\n\u002F\u002F WORKAROUND: Lying to the compiler\nconst value = response.data as UserProfile;\nconst config = {} as AppConfig;\nfunction process(input: any) { ... }\n\n\u002F\u002F PROPER FIX: Make types truthful\nconst value: UserProfile | undefined = response.data;\nif (!value) throw new Error(\"Missing user profile\");\n\nconst config: AppConfig = { theme: \"light\", locale: \"en\" };\n\nfunction process(input: UserProfile) { ... }\n```\n\n**Gate function:**\n\n```\nBEFORE using `as`, `any`, `unknown` cast, or `!` (non-null assertion):\n  Ask: \"Why doesn't the type match?\"\n\n  IF the data shape is genuinely unknown:\n    Use runtime validation (Schema, Zod, or type guards)\n  IF the type is wrong:\n    Fix the type definition\n  IF the API returns unexpected shape:\n    Fix the API contract or add a validation layer\n  NEVER use type assertions to bypass compiler errors\n```\n\n### Category 2 — LINT: Lint and Warning Suppression\n\n**The signal being silenced:** Static analysis found a real problem.\n\n```typescript\n\u002F\u002F WORKAROUND: Shooting the messenger\n\u002F\u002F eslint-disable-next-line @typescript-eslint\u002Fno-unused-vars\nconst result = fetchData();\n\n\u002F\u002F @ts-ignore\nsomeFunction(wrongArgs);\n\n\u002F\u002F @ts-expect-error - TODO fix later\nbrokenCall();\n\n\u002F\u002F PROPER FIX: Fix what the linter found\nfetchData(); \u002F\u002F Remove unused binding\n\nsomeFunction(correctArgs); \u002F\u002F Fix the arguments\n```\n\n**Gate function:**\n\n```\nBEFORE adding eslint-disable, @ts-ignore, @ts-expect-error, or any suppression:\n  Ask: \"What rule is being violated and WHY?\"\n\n  IF the code genuinely violates the rule:\n    Fix the code, not the linter\n  IF the rule is wrong for this codebase:\n    Disable the rule in config (globally), not inline\n  IF it's a third-party type issue:\n    File an issue, add a minimal typed wrapper\n  NEVER suppress a warning without understanding it\n```\n\n### Category 3 — SWALLOW: Error Swallowing\n\n**The signal being silenced:** Something failed and the code pretends it didn't.\n\n```typescript\n\u002F\u002F WORKAROUND: Pretending errors don't exist\ntry {\n  await saveData(payload);\n} catch {\n  \u002F\u002F silently ignore\n}\n\ntry {\n  result = JSON.parse(input);\n} catch {\n  result = {}; \u002F\u002F default to empty - hides corrupt data\n}\n\n\u002F\u002F PROPER FIX: Handle errors meaningfully\ntry {\n  await saveData(payload);\n} catch (error) {\n  logger.error(\"Failed to save data\", { error, payload });\n  throw new SaveError(\"Data save failed\", { cause: error });\n}\n\nconst parsed = Schema.decodeUnknownSync(PayloadSchema)(input);\n\u002F\u002F Throws descriptive error if input is invalid\n```\n\n**Gate function:**\n\n```\nBEFORE writing a catch block:\n  Ask: \"What specific errors can occur here?\"\n  Ask: \"What should happen when each error occurs?\"\n\n  IF the answer is \"ignore it\":\n    STOP — Ignoring errors hides bugs\n  IF the answer is \"log it\":\n    Log AND propagate or handle meaningfully\n  IF the answer is \"use a default\":\n    Ensure the default is SAFE and the failure is LOGGED\n  NEVER write an empty catch block\n  NEVER catch Exception\u002FError broadly without re-throwing specific types\n```\n\n### Category 4 — TIMING: Timing and Lifecycle Hacks\n\n**The signal being silenced:** Code runs in the wrong order or at the wrong time.\n\n```typescript\n\u002F\u002F WORKAROUND: Racing against the clock\nsetTimeout(() => {\n  element.focus();\n}, 100);\n\nawait new Promise((resolve) => setTimeout(resolve, 500));\n\u002F\u002F \"wait for state to settle\"\n\nawait retry(() => checkCondition(), { times: 10, delay: 200 });\n\u002F\u002F retry loop hiding a race condition\n\n\u002F\u002F PROPER FIX: Fix the lifecycle\n\u002F\u002F Use framework-native lifecycle hooks\nuseEffect(() => {\n  if (ref.current) ref.current.focus();\n}, [isVisible]);\n\n\u002F\u002F Use proper event-driven coordination\nawait waitForEvent(emitter, \"ready\");\n\n\u002F\u002F Use condition-based polling (not blind retries)\nawait waitUntil(() => service.isReady(), {\n  timeout: 5000,\n  message: \"Service failed to become ready\",\n});\n```\n\n**Gate function:**\n\n```\nBEFORE adding setTimeout, delay, sleep, or retry loops:\n  Ask: \"WHY is the timing wrong?\"\n  Ask: \"What event signals that the system is ready?\"\n\n  IF there's an event or callback available:\n    Use it instead of arbitrary delays\n  IF the ordering is wrong:\n    Fix the initialization order\n  IF it's a test timing issue:\n    Use condition-based waiting, never arbitrary sleeps\n  NEVER use setTimeout(fn, 0) to \"fix\" rendering issues\n  NEVER use arbitrary delays to \"wait for things to settle\"\n```\n\n### Category 5 — PATCH: Monkey Patching and Runtime Mutation\n\n**The signal being silenced:** The API doesn't do what the code needs.\n\n```typescript\n\u002F\u002F WORKAROUND: Mutating things you don't own\nArray.prototype.customMethod = function () { ... };\nObject.defineProperty(window, \"fetch\", { value: customFetch });\nlibrary.internals._privateMethod = replacement;\n\n\u002F\u002F PROPER FIX: Composition over mutation\nfunction customOperation\u003CT>(arr: T[]): T[] { ... }\nconst wrappedFetch = createFetchWrapper(window.fetch);\nconst adapter = new LibraryAdapter(library);\n```\n\n**Gate function:**\n\n```\nBEFORE modifying prototypes, globals, or third-party internals:\n  Ask: \"Does the library provide an extension point?\"\n\n  IF yes: Use the official extension mechanism\n  IF no: Wrap with composition\u002Fadapter pattern\n  IF the library is broken: File issue, fork, or find alternative\n  NEVER modify objects the code doesn't own\n```\n\n### Category 6 — SCATTER: Defensive Duplication\n\n**The signal being silenced:** The data is unreliable at its source.\n\n```typescript\n\u002F\u002F WORKAROUND: Checking everywhere because source is broken\nfunction renderUser(user: User) {\n  const name = user?.name ?? user?.displayName ?? \"Unknown\";\n  const email = user?.email ?? user?.contacts?.email ?? \"\";\n  const id = user?.id ?? user?.userId ?? user?._id ?? \"\";\n  \u002F\u002F ... 20 more optional chains\n}\n\n\u002F\u002F PROPER FIX: Validate once at the boundary\nconst user = Schema.decodeUnknownSync(UserSchema)(rawData);\n\u002F\u002F user is now guaranteed to have correct shape\n\nfunction renderUser(user: User) {\n  \u002F\u002F No defensive checks needed — schema validated at entry\n  return `${user.name} (${user.email})`;\n}\n```\n\n**Gate function:**\n\n```\nBEFORE adding optional chaining (?.) or nullish coalescing (??) deeply:\n  Ask: \"Why might this value be missing?\"\n  Ask: \"Where does this data enter the system?\"\n\n  IF data is unvalidated at entry:\n    Add validation at the boundary, remove defensive checks downstream\n  IF the type allows undefined but shouldn't:\n    Fix the type to be non-optional\n  IF it's truly optional:\n    Handle the None\u002Fundefined case explicitly at the nearest decision point\n  NEVER scatter optional chains as a substitute for proper validation\n```\n\n### Category 7 — CLONE: Copy-Paste Adaptation\n\n**The signal being silenced:** The abstraction doesn't fit but the developer forces it.\n\n```typescript\n\u002F\u002F WORKAROUND: Copy and \"adapt\" (badly)\n\u002F\u002F Copied from UserService and changed 3 lines\nfunction createProject(data: ProjectData) {\n  \u002F\u002F 200 lines, 95% identical to createUser\n  \u002F\u002F but with subtle bugs from incomplete adaptation\n}\n\n\u002F\u002F PROPER FIX: Extract shared pattern or write fresh\n\u002F\u002F Option A: Extract the common pattern\nfunction createEntity\u003CT>(schema: Schema\u003CT>, repo: Repository\u003CT>) {\n  return (data: T) => pipe(\n    Schema.decode(schema)(data),\n    Effect.flatMap(repo.insert),\n  );\n}\n\n\u002F\u002F Option B: Write purpose-built code\nfunction createProject(data: ProjectData) {\n  \u002F\u002F Clean, focused implementation for projects\n}\n```\n\n**Gate function:**\n\n```\nBEFORE copying code and modifying it:\n  Ask: \"Am I copying because the pattern is the same or because I'm lazy?\"\n\n  IF the pattern is genuinely the same:\n    Extract a shared abstraction first, then use it\n  IF the pattern is similar but different:\n    Write purpose-built code — similar-looking code with different intent\n    should NOT be forced into the same abstraction\n  NEVER copy-paste more than 5 lines without questioning why\n```\n\n## The Compound Cost\n\nA workaround that saves 30 minutes today costs 30 hours when copied to 5 places, debugged 3 times, and confused 4 developers over 6 months. The interest rate on workarounds is predatory.\n\n## Red Flags — STOP and Rethink\n\nCatch these thought patterns and STOP:\n\n| Thought                                      | What It Means                        |\n| -------------------------------------------- | ------------------------------------ |\n| \"Just add `as any` to make it compile\"       | TYPE — Type system evasion           |\n| \"Disable the lint rule for this line\"        | LINT — Warning suppression           |\n| \"Wrap it in try-catch and ignore the error\"  | SWALLOW — Error swallowing           |\n| \"Add a setTimeout to fix the timing\"         | TIMING — Lifecycle hack              |\n| \"Override the prototype\u002Fglobal\"              | PATCH — Monkey patching              |\n| \"Add `?.` everywhere just to be safe\"        | SCATTER — Defensive duplication      |\n| \"Copy this code and change a few things\"     | CLONE — Copy-paste adaptation        |\n| \"It works, don't touch it\"                   | Fear masking a fragile workaround    |\n| \"We'll fix it properly later\"                | Later never comes                    |\n| \"It's just temporary\"                        | Nothing is more permanent            |\n\n## The Escape Valve\n\nNot every problem can be fixed at root cause. When a workaround is genuinely unavoidable:\n\n```\nREQUIRED conditions (ALL must be true):\n  1. Root cause is in external code the team does not control\n  2. The proper fix requires upstream changes with uncertain timeline\n  3. The business impact of NOT shipping exceeds the technical debt cost\n  4. The workaround is ISOLATED (does not leak into other code)\n\nIF all conditions are met:\n  1. Mark with explicit comment: \u002F\u002F WORKAROUND: [reason] — see [issue-link]\n  2. File a tracking issue for removal\n  3. Add a test that verifies the workaround behavior\n  4. Add a test that will FAIL when the upstream fix lands (canary test)\n  5. Set a review date (max 90 days)\n\nIF any condition is NOT met:\n  Fix the root cause. No exceptions.\n```\n\n## Common Rationalizations\n\n| Excuse                                         | Reality                                                      |\n| ---------------------------------------------- | ------------------------------------------------------------ |\n| \"It's just a small workaround\"                 | Small workarounds become big patterns when copied             |\n| \"We don't have time for the proper fix\"        | Workarounds cost MORE time in debugging and maintenance       |\n| \"The type system is too strict\"                | The type system found a real bug — listen to it               |\n| \"Nobody will copy this\"                        | Every workaround in a codebase gets copied within 3 months   |\n| \"It's behind a feature flag\"                   | Feature flags don't expire — the workaround becomes permanent |\n| \"The test passes\"                              | A passing test with a workaround tests the workaround, not the code |\n| \"I'll create a tech debt ticket\"               | 93% of tech debt tickets are never resolved                  |\n| \"The external library forces this\"             | Use The Escape Valve process above, with all 5 requirements  |\n\n## The Bottom Line\n\n```\nEvery workaround is a bet that nobody will ever need to understand this code again.\nThat bet always loses.\n\nFix the disease, not the symptom.\nFix the source, not the signal.\nFix the code, not the compiler message.\n```\n\n**For the detailed catalog of 30+ specific workaround patterns with before\u002Fafter code:** Read `references\u002Fworkaround-catalog.md`.\n\n**For the philosophical and engineering foundations:** Read `references\u002Fphilosophical-foundations.md`.\n",{"name":5,"metadata":24,"description":7},{"author":25,"github":26,"repository":27},"Pedro Nauck","https:\u002F\u002Fgithub.com\u002Fpedronauck","https:\u002F\u002Fgithub.com\u002Fpedronauck\u002Fskills","main","a5b533be2d244bbf3e5606e851742f0e0ba99423","skills\u002Fcurated\u002Fno-workarounds","https:\u002F\u002Fgithub.com\u002Fharyelramalho\u002Fskills","https:\u002F\u002Fgithub.com\u002Fharyelramalho","linkedin.com\u002Fin\u002Fharyelramalho\u002F","Software Engineer @ SKORR •  Former Vice President of the Junior Computer Association - TecnoJr","2026-07-16 01:34:58",{"source":8,"skillName":5,"commands":37,"prompt":47,"zipAvailable":48},[38,41,44],{"tool":39,"command":40},"npx","npx skills add haryelramalho\u002Fskills --skill no-workarounds",{"tool":42,"command":43},"bunx","bunx skills add haryelramalho\u002Fskills --skill no-workarounds",{"tool":45,"command":46},"pnpm","pnpm dlx skills add haryelramalho\u002Fskills --skill no-workarounds","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fharyelramalho\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fcurated\u002Fno-workarounds\u002FSKILL.md",true,[50,56],{"path":51,"resourceType":52,"resourceTypeDesc":53,"sizeBytes":54,"sourceHtmlUrl":55},"references\u002Fphilosophical-foundations.md","REFERENCE","参考文档",7592,"https:\u002F\u002Fgithub.com\u002Fharyelramalho\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fcurated\u002Fno-workarounds\u002Freferences\u002Fphilosophical-foundations.md",{"path":57,"resourceType":52,"resourceTypeDesc":53,"sizeBytes":58,"sourceHtmlUrl":59},"references\u002Fworkaround-catalog.md",14160,"https:\u002F\u002Fgithub.com\u002Fharyelramalho\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fcurated\u002Fno-workarounds\u002Freferences\u002Fworkaround-catalog.md",[61,68,75,82,89,96],{"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":19},"01M753YDMKSDB7320THEQ2CVW5","to-prompt-opus","Use when preparing or rewriting prompts for Claude Opus 4.8, Anthropic API agents, XML-structured prompts, long-context document work, coding agents, research synthesis, frontend\u002Fdesign tasks, or model-specific prompt optimization. Do not use for GPT\u002FOpenAI prompts or raw context packaging without Opus-specific tuning.","https:\u002F\u002Fgithub.com\u002Fharyelramalho\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fmine\u002Fto-prompt-opus\u002FSKILL.md",[],[],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":19},"01M753YAP95W4K2MCEAEEAV6YA","to-prompt-gpt","Use when preparing or rewriting prompts for GPT-5.5, OpenAI API agents, Responses workflows, coding agents, research synthesis, support assistants, or model-specific prompt optimization. Do not use for Claude\u002FOpus prompts or raw context packaging without GPT-specific tuning.","https:\u002F\u002Fgithub.com\u002Fharyelramalho\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fmine\u002Fto-prompt-gpt\u002FSKILL.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":19},"01M753Y700AZ0GVJDNW9Q1Q54F","plan-refactor-qa","Plans and runs qa-report before executing Compozy refactor tasks. Use when the user provides a refactor or issue slug and wants Codex to inspect the matching .compozy\u002Ftasks directory, related PRD\u002FTechSpec\u002FADR\u002Ftask artifacts, affected code, and existing tests, then invoke $qa-report with a repository-grounded prompt. Do not use to run tests, execute qa-execution, implement code, or perform post-refactor verification.","https:\u002F\u002Fgithub.com\u002Fharyelramalho\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fmine\u002Fplan-refactor-qa\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":19},"01M753XZENG0Z8S2ET75EM8CGB","multi-tool-branch-review","Orchestrates a multi-tool branch review of the current git branch against a base branch. By default it runs two independent thermo-nuclear maintainability audits, one on Codex GPT-5.5 xhigh and one on Claude Opus xhigh, then consolidates the findings into a single remediation plan via writing-plans. If the user explicitly asks for native reviews, it can add the Claude native review pass, the Codex native review pass, or both. Use when the user wants a deep cross-model review of a branch or PR before merge, or asks to review this branch with multiple tools or models. Encodes known infra failure modes and their fixes (missing Claude ACP adapter, Codex MCP auth hangs, false-positive report files, long jobs orphaned inside subagents). Do not use for reviewing a single uncommitted snippet, for non-git work, for running only one reviewer, or when the user only wants a quick lint or test run.","https:\u002F\u002Fgithub.com\u002Fharyelramalho\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fmine\u002Fmulti-tool-branch-review\u002FSKILL.md",[],[],{"skillNo":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":93,"categories":94,"keywords":95,"publishedAt":19},"01M753XQM40XCK55BH5WPA88EW","create-pr-with-template","Create a GitHub Pull Request with gh CLI and prefer repository PR templates automatically. Use this whenever the user asks to open\u002Fcreate a PR, especially when template compliance is needed. If multiple templates exist, ask the user which template to use.","https:\u002F\u002Fgithub.com\u002Fharyelramalho\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fmine\u002Fcreate-pr-with-template\u002FSKILL.md",[],[],{"skillNo":97,"name":98,"nameZh":6,"description":99,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":100,"categories":101,"keywords":102,"publishedAt":19},"01M753XJMBJ8VFPRCDCC1JJ9G4","ui-craft","Provides guardrails for user-facing UI work: usability heuristics, accessibility floors, design-system discipline, component states, microcopy, motion, dark mode, responsive behavior, and human-AI UX. Use when designing, generating, reviewing, or refactoring visible product surfaces such as components, pages, dashboards, forms, dialogs, loading\u002Fempty\u002Ferror states, or AI interfaces. Do not use for backend-only work, infrastructure, CLI\u002FTUI design, or pure documentation editing.","https:\u002F\u002Fgithub.com\u002Fharyelramalho\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fcurated\u002Fui-craft\u002FSKILL.md",[],[]]