[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M718WN7KGP7RM2M1VR93VKQJ":3,"skill-same:01M718WN7KGP7RM2M1VR93VKQJ":93},{"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":36,"linkOnly":37,"markdownContent":38,"markdownBody":39,"frontMatter":40,"refName":41,"commitSha":42,"skillDirectory":43,"forksCount":44,"repositoryHtmlUrl":45,"repositoryHomepageUrl":6,"ownerHtmlUrl":46,"ownerBlogUrl":47,"ownerDescription":6,"updatedAt":48,"install":49,"resources":62},"01M718WN7KGP7RM2M1VR93VKQJ","oma-translation",null,"Context-aware translation and localization for UI strings, documentation, marketing copy, and prose. Preserves meaning, register, terminology, placeholders, structure, and natural target-language phrasing.","vasceannie\u002Fslopgate","vasceannie","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F20271133?v=4","01M718RGA8VV2EF22XJEMXVQ0Q","Travis Vasceannie","01M718RGB0GWSXBBZBN67Q6NHQ",1,"MIT","https:\u002F\u002Fgithub.com\u002Fvasceannie\u002Fslopgate\u002Fblob\u002Fmaster\u002F.agents\u002Fskills\u002Foma-translation\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35],"oma translation","translation","language","prose","copy","terminology","for","register","target","context","ui","localization","marketing","structure","documentation","meaning","strings","2026-11-10 10:12:30",false,"---\nname: oma-translation\ndescription: Context-aware translation and localization for UI strings,\n  documentation, marketing copy, and prose. Preserves meaning, register,\n  terminology, placeholders, structure, and natural target-language phrasing.\n---\n\n# Translation - Context-Aware Localization\n\n## Scheduling\n\n### Goal\nTranslate, review, or adapt multilingual content faithfully and naturally while preserving the\nparts that must remain exact: placeholders, code, links, formatting, terminology, and file\nstructure.\n\n### Intent signature\n- Translate, localize, review a translation, adapt copy, or create a glossary\u002Fstyle guide.\n- Update target-language files after the source changed.\n\n### When to use\n- UI strings, error messages, locale files, documentation, reports, marketing copy, and prose.\n- Review of existing translations for accuracy, register, terminology, or naturalness.\n\n### When NOT to use\n- i18n infrastructure, locale registration, or key extraction -> use the relevant development skill.\n- Date\u002Fpluralization APIs or other code-level localization -> use the owning code-domain skill.\n\n### Expected inputs\n- Source text, target language or locale, content type, and requested output mode.\n- Existing locale files, glossary, surrounding context, and optional author sample.\n- Placeholder and formatting constraints when the source is structured.\n\n### Expected outputs\n- Natural target-language text or evidence-backed review findings.\n- Exact preservation of placeholders, code spans, links, headings, list structure, and locale keys.\n- Translator notes only for meaningful ambiguity or necessary cultural explanation.\n\n### Dependencies\n- Target profile: `resources\u002Flang\u002F{code}.md`, if one exists.\n- `resources\u002Ftranslation-rubric.md` for substantive content or review.\n- `resources\u002Fanti-ai-patterns.md` when prose needs style review.\n- Existing siblings and glossary when translating into a project.\n\n### Control-flow features\n- Branches by UI batch versus prose, profile availability, locale variant, ambiguity, and review mode.\n- Loads only the target profile and references required for the content type.\n- Edits files only when the user asked for file changes.\n\n## Structural Flow\n\n### Entry\n1. Identify source, target locale, content type, and whether this is translate, review, or diff-sync.\n2. Preserve exact tokens first: placeholders, code, URLs, keys, and structural markers.\n3. Load the target profile if available; read sibling translations when the target is in a project.\n\n### Scenes\n1. **PREPARE**: Resolve locale, output mode, target audience, and protected syntax.\n2. **ACQUIRE**: Read the target profile, relevant siblings, glossary, and source context. For prose or review, load the rubric; load anti-AI patterns only when style review is needed.\n3. **REASON**: Determine meaning, register, terminology, cultural references, and any ambiguity. Decide whether an idiom should be interpreted, substituted, or retained.\n4. **ACT**: Write natural target-language text. Match established project patterns without adding meaning, opinion, or personality.\n5. **VERIFY**: Check protected syntax and structure. For substantive text, check meaning, terminology, register, and target-language naturalness against the rubric.\n6. **FINALIZE**: Return the requested text, patch, or review with only supported findings.\n\n### Transitions\n- A profile exists -> load it; its target-language rules take precedence over shared guidance.\n- A locale variant is required -> resolve it before drafting.\n- No profile exists -> use shared guidance and note that limit once; do not borrow another language's rules.\n- A short independent UI string with established siblings -> use protected-syntax and sibling checks; the full prose review is optional.\n- Long prose, documentation, marketing copy, mixed tables\u002Fcode, or review mode -> use the rubric.\n- Ambiguous meaning that changes the result -> ask one targeted question or flag the choice.\n- Diff-sync -> modify only source-touched equivalents, located by headings and surrounding context, not line number.\n\n### Failure and recovery\n| Failure | Recovery |\n|---|---|\n| Missing target context | Use the source register and state the assumption, unless the ambiguity changes meaning |\n| Conflicting literal wording and project convention | Follow the established target convention and explain a material difference |\n| Placeholder or structure mismatch | Revise before emitting or applying a patch |\n| Missing profile | Use shared guidance and identify the coverage limit once |\n| Unclear cultural reference | Add a concise note only when the target audience needs it |\n\n### Exit\n- Success: the text is faithful, natural, structurally safe, and checked in proportion to content risk.\n- Partial: unresolved ambiguity or missing context is stated without inventing an answer.\n\n### Language profile loading\n\nResolve the BCP 47 primary subtag and load one matching profile when present:\n\n| Target | Profile |\n|---|---|\n| Korean | `resources\u002Flang\u002Fko.md` |\n| Japanese | `resources\u002Flang\u002Fja.md` |\n| Chinese | `resources\u002Flang\u002Fzh.md`; resolve the declared variant |\n| English | `resources\u002Flang\u002Fen.md` |\n| Other | no profile; use shared guidance |\n\nProfiles define typography, register, and target-language checks. Shared guidance explains common\nrisks. A profile wins if they conflict. Add a new profile from `resources\u002Flang\u002F_template.md` only\nwhen the task is to extend this skill.\n\n### Translation method\n\n1. Read for meaning, intended effect, domain terms, and protected syntax. Identify figurative\n   wording as **interpret**, **substitute**, or **retain**. Do not add a new metaphor or remove an\n   intentional one without a reason.\n2. Choose register from the source, target audience, and sibling translations. Apply\n   `translation_voice` from `.agents\u002Foma-config.yaml` only as a rhythm\u002Fformality preference:\n   `formal`, `balanced` (default), or `interpreter`. It never overrides meaning or target norms.\n3. Reconstruct in the target language. Change word order, split or merge sentences, and omit\n   implied subjects only when the target language calls for it.\n4. Preserve author style only where it belongs: prose, dialogue, adaptation, or explicitly\n   user-authored documentation. Match observable rhythm and diction, never add facts, stance,\n   jokes, first person, or stronger emotion.\n\n### Verification\n\nAlways check:\n\n- Every placeholder, code span, identifier, URL, and locale key is unchanged.\n- Headings, links, table rows, list nesting, and code blocks retain their structure.\n- The target follows its profile's typography and register rules.\n- Existing siblings are matched when they establish terminology or UI style.\n\nFor substantive content and review mode, also check the rubric: meaning, naturalness,\nterminology, register, cultural fit, and emotional force. Use anti-AI patterns as a diagnostic,\nnot a demand to make prose decorative or to remove intentional source style.\n\n### Review mode\n\nReview from evidence, not from an expectation that every draft is machine-translated. Record zero\nfindings when no material defect is confirmed. Separate:\n\n- **Accuracy or safety defects**: changed meaning, broken placeholder, incorrect term, or wrong register.\n- **Supported style findings**: a concrete target-language issue with a reason and proposed fix.\n- **Preferences**: optional alternatives that do not make the existing translation wrong.\n\nDo not rewrite a sound translation merely to produce findings.\n\n### Batch and diff-sync work\n\nFor batches, read the complete set first, translate values only, and maintain one terminology and\nregister decision. Verify placeholders and key structure across the set.\n\nFor diff-sync, map each source hunk by heading and surrounding context. Touch only the affected\ntarget section; leave unrelated text byte-identical. State updated sections, skipped cosmetic\nhunks, and material terminology decisions.\n\n### Output formats\n\nFor a single text, present the translation and brief notes for ambiguities or adaptations. For\nfiles, preserve the input format and modify only requested values. For review, show the original,\nthe suggested revision only when warranted, and the evidence for each finding.\n\n## Logical Operations\n\n### Actions\n| Action | SSL primitive | Evidence |\n|---|---|---|\n| Resolve locale and mode | `SELECT` | User request and file context |\n| Read profile and siblings conditionally | `READ` | Target profile, glossary, nearby translations |\n| Protect syntax and structure | `VALIDATE` | Source tokens and structural markers |\n| Infer meaning and register | `INFER` | Source, audience, project convention |\n| Translate or revise | `WRITE` | Target text or requested file patch |\n| Review substantive content | `VALIDATE` | Rubric and concrete findings |\n| Report result and limits | `NOTIFY` | Translation, patch, or review |\n\n### Tools and instruments\n- Native search\u002Fread for local source and sibling translations.\n- Configured `code_intelligence` capability when available for code-context navigation; native\n  search\u002Fread when it is unavailable or times out.\n- Target profile, rubric, anti-AI patterns, and language-template resources as selected above.\n\n### Canonical workflow path\n1. Resolve target locale and protect exact syntax.\n2. Load the one applicable language profile and relevant siblings; load rubric\u002Fstyle resources only\n   for substantive content or review.\n3. Infer meaning, register, terminology, and figurative-language handling.\n4. Draft in natural target order and project style.\n5. Verify exact syntax and structure, then review substantive content against the rubric.\n6. Emit the requested translation, patch, or evidence-backed review. State a missing-profile or\n   context limitation when material.\n\n### Resource scope\n| Scope | Resource target |\n|---|---|\n| `LOCAL_FS` | Source\u002Ftarget files, glossaries, language profiles |\n| `CODEBASE` | Sibling translations and code context |\n| `PROCESS` | Native search and syntax checks |\n| `MEMORY` | Locale, terminology, register, protected syntax, unresolved ambiguity |\n\n### Effects and side effects\n- Produces translated text or review findings.\n- Changes locale\u002Fdocs files only when explicitly requested.\n- Retains source structure, identifiers, and placeholders.\n\n### Guardrails\n1. Preserve meaning, protected syntax, and file structure before stylistic preference.\n2. Do not invent facts, opinions, emotional emphasis, examples, citations, or personality.\n3. Do not use a different language's profile as a substitute.\n4. Do not change untouched sections during diff-sync.\n5. Do not claim completion of a check that the available source cannot support.\n\n## References\n\n- Translation rubric: `resources\u002Ftranslation-rubric.md` (load for substantive content or review)\n- Style diagnostics: `resources\u002Fanti-ai-patterns.md` (load when prose style needs review)\n- Target profiles: `resources\u002Flang\u002F{ko,ja,zh,en}.md` (load one matching profile)\n- Profile template: `resources\u002Flang\u002F_template.md` (only when adding a profile)\n- Shared context loading: `..\u002F_shared\u002Fcore\u002Fcontext-loading.md`\n- Shared quality principles: `..\u002F_shared\u002Fcore\u002Fquality-principles.md`","# Translation - Context-Aware Localization\n\n## Scheduling\n\n### Goal\nTranslate, review, or adapt multilingual content faithfully and naturally while preserving the\nparts that must remain exact: placeholders, code, links, formatting, terminology, and file\nstructure.\n\n### Intent signature\n- Translate, localize, review a translation, adapt copy, or create a glossary\u002Fstyle guide.\n- Update target-language files after the source changed.\n\n### When to use\n- UI strings, error messages, locale files, documentation, reports, marketing copy, and prose.\n- Review of existing translations for accuracy, register, terminology, or naturalness.\n\n### When NOT to use\n- i18n infrastructure, locale registration, or key extraction -> use the relevant development skill.\n- Date\u002Fpluralization APIs or other code-level localization -> use the owning code-domain skill.\n\n### Expected inputs\n- Source text, target language or locale, content type, and requested output mode.\n- Existing locale files, glossary, surrounding context, and optional author sample.\n- Placeholder and formatting constraints when the source is structured.\n\n### Expected outputs\n- Natural target-language text or evidence-backed review findings.\n- Exact preservation of placeholders, code spans, links, headings, list structure, and locale keys.\n- Translator notes only for meaningful ambiguity or necessary cultural explanation.\n\n### Dependencies\n- Target profile: `resources\u002Flang\u002F{code}.md`, if one exists.\n- `resources\u002Ftranslation-rubric.md` for substantive content or review.\n- `resources\u002Fanti-ai-patterns.md` when prose needs style review.\n- Existing siblings and glossary when translating into a project.\n\n### Control-flow features\n- Branches by UI batch versus prose, profile availability, locale variant, ambiguity, and review mode.\n- Loads only the target profile and references required for the content type.\n- Edits files only when the user asked for file changes.\n\n## Structural Flow\n\n### Entry\n1. Identify source, target locale, content type, and whether this is translate, review, or diff-sync.\n2. Preserve exact tokens first: placeholders, code, URLs, keys, and structural markers.\n3. Load the target profile if available; read sibling translations when the target is in a project.\n\n### Scenes\n1. **PREPARE**: Resolve locale, output mode, target audience, and protected syntax.\n2. **ACQUIRE**: Read the target profile, relevant siblings, glossary, and source context. For prose or review, load the rubric; load anti-AI patterns only when style review is needed.\n3. **REASON**: Determine meaning, register, terminology, cultural references, and any ambiguity. Decide whether an idiom should be interpreted, substituted, or retained.\n4. **ACT**: Write natural target-language text. Match established project patterns without adding meaning, opinion, or personality.\n5. **VERIFY**: Check protected syntax and structure. For substantive text, check meaning, terminology, register, and target-language naturalness against the rubric.\n6. **FINALIZE**: Return the requested text, patch, or review with only supported findings.\n\n### Transitions\n- A profile exists -> load it; its target-language rules take precedence over shared guidance.\n- A locale variant is required -> resolve it before drafting.\n- No profile exists -> use shared guidance and note that limit once; do not borrow another language's rules.\n- A short independent UI string with established siblings -> use protected-syntax and sibling checks; the full prose review is optional.\n- Long prose, documentation, marketing copy, mixed tables\u002Fcode, or review mode -> use the rubric.\n- Ambiguous meaning that changes the result -> ask one targeted question or flag the choice.\n- Diff-sync -> modify only source-touched equivalents, located by headings and surrounding context, not line number.\n\n### Failure and recovery\n| Failure | Recovery |\n|---|---|\n| Missing target context | Use the source register and state the assumption, unless the ambiguity changes meaning |\n| Conflicting literal wording and project convention | Follow the established target convention and explain a material difference |\n| Placeholder or structure mismatch | Revise before emitting or applying a patch |\n| Missing profile | Use shared guidance and identify the coverage limit once |\n| Unclear cultural reference | Add a concise note only when the target audience needs it |\n\n### Exit\n- Success: the text is faithful, natural, structurally safe, and checked in proportion to content risk.\n- Partial: unresolved ambiguity or missing context is stated without inventing an answer.\n\n### Language profile loading\n\nResolve the BCP 47 primary subtag and load one matching profile when present:\n\n| Target | Profile |\n|---|---|\n| Korean | `resources\u002Flang\u002Fko.md` |\n| Japanese | `resources\u002Flang\u002Fja.md` |\n| Chinese | `resources\u002Flang\u002Fzh.md`; resolve the declared variant |\n| English | `resources\u002Flang\u002Fen.md` |\n| Other | no profile; use shared guidance |\n\nProfiles define typography, register, and target-language checks. Shared guidance explains common\nrisks. A profile wins if they conflict. Add a new profile from `resources\u002Flang\u002F_template.md` only\nwhen the task is to extend this skill.\n\n### Translation method\n\n1. Read for meaning, intended effect, domain terms, and protected syntax. Identify figurative\n   wording as **interpret**, **substitute**, or **retain**. Do not add a new metaphor or remove an\n   intentional one without a reason.\n2. Choose register from the source, target audience, and sibling translations. Apply\n   `translation_voice` from `.agents\u002Foma-config.yaml` only as a rhythm\u002Fformality preference:\n   `formal`, `balanced` (default), or `interpreter`. It never overrides meaning or target norms.\n3. Reconstruct in the target language. Change word order, split or merge sentences, and omit\n   implied subjects only when the target language calls for it.\n4. Preserve author style only where it belongs: prose, dialogue, adaptation, or explicitly\n   user-authored documentation. Match observable rhythm and diction, never add facts, stance,\n   jokes, first person, or stronger emotion.\n\n### Verification\n\nAlways check:\n\n- Every placeholder, code span, identifier, URL, and locale key is unchanged.\n- Headings, links, table rows, list nesting, and code blocks retain their structure.\n- The target follows its profile's typography and register rules.\n- Existing siblings are matched when they establish terminology or UI style.\n\nFor substantive content and review mode, also check the rubric: meaning, naturalness,\nterminology, register, cultural fit, and emotional force. Use anti-AI patterns as a diagnostic,\nnot a demand to make prose decorative or to remove intentional source style.\n\n### Review mode\n\nReview from evidence, not from an expectation that every draft is machine-translated. Record zero\nfindings when no material defect is confirmed. Separate:\n\n- **Accuracy or safety defects**: changed meaning, broken placeholder, incorrect term, or wrong register.\n- **Supported style findings**: a concrete target-language issue with a reason and proposed fix.\n- **Preferences**: optional alternatives that do not make the existing translation wrong.\n\nDo not rewrite a sound translation merely to produce findings.\n\n### Batch and diff-sync work\n\nFor batches, read the complete set first, translate values only, and maintain one terminology and\nregister decision. Verify placeholders and key structure across the set.\n\nFor diff-sync, map each source hunk by heading and surrounding context. Touch only the affected\ntarget section; leave unrelated text byte-identical. State updated sections, skipped cosmetic\nhunks, and material terminology decisions.\n\n### Output formats\n\nFor a single text, present the translation and brief notes for ambiguities or adaptations. For\nfiles, preserve the input format and modify only requested values. For review, show the original,\nthe suggested revision only when warranted, and the evidence for each finding.\n\n## Logical Operations\n\n### Actions\n| Action | SSL primitive | Evidence |\n|---|---|---|\n| Resolve locale and mode | `SELECT` | User request and file context |\n| Read profile and siblings conditionally | `READ` | Target profile, glossary, nearby translations |\n| Protect syntax and structure | `VALIDATE` | Source tokens and structural markers |\n| Infer meaning and register | `INFER` | Source, audience, project convention |\n| Translate or revise | `WRITE` | Target text or requested file patch |\n| Review substantive content | `VALIDATE` | Rubric and concrete findings |\n| Report result and limits | `NOTIFY` | Translation, patch, or review |\n\n### Tools and instruments\n- Native search\u002Fread for local source and sibling translations.\n- Configured `code_intelligence` capability when available for code-context navigation; native\n  search\u002Fread when it is unavailable or times out.\n- Target profile, rubric, anti-AI patterns, and language-template resources as selected above.\n\n### Canonical workflow path\n1. Resolve target locale and protect exact syntax.\n2. Load the one applicable language profile and relevant siblings; load rubric\u002Fstyle resources only\n   for substantive content or review.\n3. Infer meaning, register, terminology, and figurative-language handling.\n4. Draft in natural target order and project style.\n5. Verify exact syntax and structure, then review substantive content against the rubric.\n6. Emit the requested translation, patch, or evidence-backed review. State a missing-profile or\n   context limitation when material.\n\n### Resource scope\n| Scope | Resource target |\n|---|---|\n| `LOCAL_FS` | Source\u002Ftarget files, glossaries, language profiles |\n| `CODEBASE` | Sibling translations and code context |\n| `PROCESS` | Native search and syntax checks |\n| `MEMORY` | Locale, terminology, register, protected syntax, unresolved ambiguity |\n\n### Effects and side effects\n- Produces translated text or review findings.\n- Changes locale\u002Fdocs files only when explicitly requested.\n- Retains source structure, identifiers, and placeholders.\n\n### Guardrails\n1. Preserve meaning, protected syntax, and file structure before stylistic preference.\n2. Do not invent facts, opinions, emotional emphasis, examples, citations, or personality.\n3. Do not use a different language's profile as a substitute.\n4. Do not change untouched sections during diff-sync.\n5. Do not claim completion of a check that the available source cannot support.\n\n## References\n\n- Translation rubric: `resources\u002Ftranslation-rubric.md` (load for substantive content or review)\n- Style diagnostics: `resources\u002Fanti-ai-patterns.md` (load when prose style needs review)\n- Target profiles: `resources\u002Flang\u002F{ko,ja,zh,en}.md` (load one matching profile)\n- Profile template: `resources\u002Flang\u002F_template.md` (only when adding a profile)\n- Shared context loading: `..\u002F_shared\u002Fcore\u002Fcontext-loading.md`\n- Shared quality principles: `..\u002F_shared\u002Fcore\u002Fquality-principles.md`",{"name":5,"description":7},"master","5fab8004af1390aa17b3447f2780766c8bf2482c",".agents\u002Fskills\u002Foma-translation",0,"https:\u002F\u002Fgithub.com\u002Fvasceannie\u002Fslopgate","https:\u002F\u002Fgithub.com\u002Fvasceannie","thingswithstuff.io","2026-11-10 23:25:49",{"source":8,"skillName":5,"commands":50,"prompt":60,"zipAvailable":61},[51,54,57],{"tool":52,"command":53},"npx","npx skills add vasceannie\u002Fslopgate --skill oma-translation",{"tool":55,"command":56},"bunx","bunx skills add vasceannie\u002Fslopgate --skill oma-translation",{"tool":58,"command":59},"pnpm","pnpm dlx skills add vasceannie\u002Fslopgate --skill oma-translation","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fvasceannie\u002Fslopgate\u002Fblob\u002Fmaster\u002F.agents\u002Fskills\u002Foma-translation\u002FSKILL.md",true,[63,69,73,77,81,85,89],{"path":64,"resourceType":65,"resourceTypeDesc":66,"sizeBytes":67,"sourceHtmlUrl":68},"resources\u002Fanti-ai-patterns.md","REFERENCE","参考文档",16807,"https:\u002F\u002Fgithub.com\u002Fvasceannie\u002Fslopgate\u002Fblob\u002Fmaster\u002F.agents\u002Fskills\u002Foma-translation\u002Fresources\u002Fanti-ai-patterns.md",{"path":70,"resourceType":65,"resourceTypeDesc":66,"sizeBytes":71,"sourceHtmlUrl":72},"resources\u002Flang\u002F_template.md",2912,"https:\u002F\u002Fgithub.com\u002Fvasceannie\u002Fslopgate\u002Fblob\u002Fmaster\u002F.agents\u002Fskills\u002Foma-translation\u002Fresources\u002Flang\u002F_template.md",{"path":74,"resourceType":65,"resourceTypeDesc":66,"sizeBytes":75,"sourceHtmlUrl":76},"resources\u002Flang\u002Fen.md",7831,"https:\u002F\u002Fgithub.com\u002Fvasceannie\u002Fslopgate\u002Fblob\u002Fmaster\u002F.agents\u002Fskills\u002Foma-translation\u002Fresources\u002Flang\u002Fen.md",{"path":78,"resourceType":65,"resourceTypeDesc":66,"sizeBytes":79,"sourceHtmlUrl":80},"resources\u002Flang\u002Fja.md",9059,"https:\u002F\u002Fgithub.com\u002Fvasceannie\u002Fslopgate\u002Fblob\u002Fmaster\u002F.agents\u002Fskills\u002Foma-translation\u002Fresources\u002Flang\u002Fja.md",{"path":82,"resourceType":65,"resourceTypeDesc":66,"sizeBytes":83,"sourceHtmlUrl":84},"resources\u002Flang\u002Fko.md",14237,"https:\u002F\u002Fgithub.com\u002Fvasceannie\u002Fslopgate\u002Fblob\u002Fmaster\u002F.agents\u002Fskills\u002Foma-translation\u002Fresources\u002Flang\u002Fko.md",{"path":86,"resourceType":65,"resourceTypeDesc":66,"sizeBytes":87,"sourceHtmlUrl":88},"resources\u002Flang\u002Fzh.md",8247,"https:\u002F\u002Fgithub.com\u002Fvasceannie\u002Fslopgate\u002Fblob\u002Fmaster\u002F.agents\u002Fskills\u002Foma-translation\u002Fresources\u002Flang\u002Fzh.md",{"path":90,"resourceType":65,"resourceTypeDesc":66,"sizeBytes":91,"sourceHtmlUrl":92},"resources\u002Ftranslation-rubric.md",4891,"https:\u002F\u002Fgithub.com\u002Fvasceannie\u002Fslopgate\u002Fblob\u002Fmaster\u002F.agents\u002Fskills\u002Foma-translation\u002Fresources\u002Ftranslation-rubric.md",[94,126,153,190,215,236],{"skillNo":95,"name":96,"nameZh":6,"description":97,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":98,"categories":99,"keywords":105,"publishedAt":36},"01M71951JDWCYMS8GDC2C7395D","type-strictness","Enforce strict type compliance by eliminating `Any` types and `# type: ignore` comments. Use when:\n(1) Editing code that contains `Any` as a type annotation\n(2) Code has `# type: ignore` or `# pyright: ignore` comments\n(3) User requests type fixes or type strictness enforcement\n(4) Importing from untyped third-party libraries\n(5) User asks to \"fix types\", \"remove Any\", or \"add proper typing\"\n(6) Pyrefly or mypy reports type errors that need resolution\n(7) Code review reveals weak typing patterns\nFollows hierarchical resolution: codebase inference → type stubs → library inspection → type guards → casting (last resort).","https:\u002F\u002Fgithub.com\u002Fvasceannie\u002Fslopgate\u002Fblob\u002Fmaster\u002Fbundle\u002Fshared\u002Fskills\u002Ftype-strictness\u002FSKILL.md",[100],{"categoryNo":101,"categoryName":102,"taxonomyType":103,"taxonomyTypeDesc":104},"01JBSEEDCAT000000000000007","代码审查","SCENARIO","使用场景",[106,107,108,109,110,111,112,113,114,115,116,117,118,119,120,121,122,123,124,125],"type","type strictness","typing","types","remove","code review","fix","errors","inspection","when","code","review","reports","libraries","casting","pyrefly","mypy","pyright","library","patterns",{"skillNo":127,"name":128,"nameZh":6,"description":129,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":130,"categories":131,"keywords":136,"publishedAt":36},"01M7194XGBQXSE7Y5BZ4K5CSTK","slopgate-test-extender","Extend Python test suites with parametrization, fixture reuse, and quality enforcement. Use when asked to add tests, extend existing tests, improve test coverage, consolidate duplicate tests, fix test quality issues, or when Slopgate reports untested-production-code, missing test references, or coverage gaps. Triggers on requests like \"add tests for X\", \"extend these tests\", \"parametrize tests\", \"consolidate tests\", \"fix test quality\", \"improve test coverage\", \"write tests for this function\", \"test this module\", \"behavior tests\", \"integration tests\", \"missing tests\", \"coverage holes\", \"untested code\", or when a hook denies with test-related findings.","https:\u002F\u002Fgithub.com\u002Fvasceannie\u002Fslopgate\u002Fblob\u002Fmaster\u002Fbundle\u002Fshared\u002Fskills\u002Fslopgate-test-extender\u002FSKILL.md",[132,133],{"categoryNo":101,"categoryName":102,"taxonomyType":103,"taxonomyTypeDesc":104},{"categoryNo":134,"categoryName":135,"taxonomyType":103,"taxonomyTypeDesc":104},"01JBSEEDCAT000000000000008","测试与质量",[137,138,139,140,141,112,142,143,144,145,146,147,115,116,148,149,118,150,151,152],"slopgate test extender","test","coverage","fixture","testing","issues","write tests","improve","only","cleanup","loop","candidate","consolidate","references","opencode","orchestrator",{"skillNo":154,"name":155,"nameZh":6,"description":156,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":157,"categories":158,"keywords":174,"publishedAt":36},"01M7194RMVQS5YJJ4ZEFXX20VS","slopgate-intelligent-coding-patterns","Pattern-selection playbook for agents editing code with complex branching, stateful parsers\u002Fworkflows, duplicated skeletons, policy checks, or ordered transforms. Load before refactoring if\u002Felif dispatch chains, boolean-flag state machines, repeated validation predicates, parallel provider\u002Flanguage implementations, or regex\u002Fcontent transformation pipelines. Also load when asked to \"apply a design pattern\", \"which pattern should I use here\", \"refactor this switch statement\", \"replace if-elif chain\", \"state machine pattern\", \"strategy pattern\", \"template method\", \"pipeline pattern\", \"specification pattern\", \"dispatch table\", \"guard clause refactor\", \"reduce cyclomatic complexity\", or when Slopgate fires PY-CODE-014, PY-CODE-017, PY-CODE-018, QUALITY-LINT-001, or PY-QUALITY-010. Use with behavior-locking tests and avoid pattern theater for simple one-off code.","https:\u002F\u002Fgithub.com\u002Fvasceannie\u002Fslopgate\u002Fblob\u002Fmaster\u002Fbundle\u002Fshared\u002Fskills\u002Fslopgate-intelligent-coding-patterns\u002FSKILL.md",[159,160,163,166,171],{"categoryNo":101,"categoryName":102,"taxonomyType":103,"taxonomyTypeDesc":104},{"categoryNo":161,"categoryName":162,"taxonomyType":103,"taxonomyTypeDesc":104},"01JBSEEDCAT000000000000015","视觉设计",{"categoryNo":164,"categoryName":165,"taxonomyType":103,"taxonomyTypeDesc":104},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":167,"categoryName":168,"taxonomyType":169,"taxonomyTypeDesc":170},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",{"categoryNo":172,"categoryName":173,"taxonomyType":169,"taxonomyTypeDesc":170},"01JBSEEDCAT000000000000032","设计师",[175,176,125,177,178,179,180,181,182,183,184,185,186,145,146,187,188,115,189,116],"coding patterns","slopgate intelligent coding patterns","coding","stateful","complexity","branch","which","chain","parsers","pipeline","selection","design","utility","workflows","reduce",{"skillNo":191,"name":192,"nameZh":6,"description":193,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":194,"categories":195,"keywords":198,"publishedAt":36},"01M7194KTXBM85GB0W7JKFQD55","slopgate-hygiene-orchestrator","Orchestrate systematic elimination of linter warnings and errors across Python, TypeScript, and Rust codebases. Use when asked to \"clean up lints\", \"fix all warnings\", \"run hygiene\", \"eliminate type errors\", \"orchestrate code quality fixes\", \"fix lint errors\", \"resolve quality gate failures\", \"pass CI checks\", \"reduce tech debt\", \"refactor to pass hooks\", or when a Slopgate hook denies with QUALITY-LINT-001, PY-CODE-017, PY-CODE-018, or any collector finding. This skill coordinates multiple code-hygiene-enforcer agents working in parallel on non-conflicting file groupings, tracks progress persistently via JSON exports, and loops until all issues are resolved. CRITICAL: Never run linters directly—always use `slopgate lint check` as the primary gate, discover project-specific tools from config files, and export findings to JSON for tracking.","https:\u002F\u002Fgithub.com\u002Fvasceannie\u002Fslopgate\u002Fblob\u002Fmaster\u002Fbundle\u002Fshared\u002Fskills\u002Fslopgate-hygiene-orchestrator\u002FSKILL.md",[196,197],{"categoryNo":101,"categoryName":102,"taxonomyType":103,"taxonomyTypeDesc":104},{"categoryNo":164,"categoryName":165,"taxonomyType":103,"taxonomyTypeDesc":104},[199,200,152,201,112,202,203,204,205,206,146,189,207,208,209,210,211,212,213,214],"slopgate hygiene orchestrator","hygiene","project","ci","local","clean","never run","files","run","lint check","systematic","config","typescript","debt","quality-gates","hook",{"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":223,"publishedAt":36},"01M7194G50FZYXXT8VNK360RPA","slopgate-code-smell-utility-locator","Autoactivate when code-smell hooks or reviews mention feature envy, thin wrappers, duplicate helpers, duplicate code,\nscattered helpers, builders\u002Ffactories\u002Fconfig\u002Fconstants\u002Fdataclass reuse, PY-CODE-012, PY-CODE-013, QUALITY-LINT-001,\nor repeated slopgate code-quality denials. Also load when asked to \"find existing helpers\", \"consolidate utilities\",\n\"search for duplicate code\", \"where is this already implemented\", \"reuse existing logic\", \"don't duplicate this\",\n\"find similar functions\", \"utility inventory\", \"code smell radar\", or before adding new helpers\u002Fwrappers so agents can\nfind existing shared utilities and consolidate instead of duplicating.","https:\u002F\u002Fgithub.com\u002Fvasceannie\u002Fslopgate\u002Fblob\u002Fmaster\u002Fbundle\u002Fshared\u002Fskills\u002Fslopgate-code-smell-utility-locator\u002FSKILL.md",[221,222],{"categoryNo":101,"categoryName":102,"taxonomyType":103,"taxonomyTypeDesc":104},{"categoryNo":167,"categoryName":168,"taxonomyType":169,"taxonomyTypeDesc":170},[187,224,116,225,139,226,227,228,229,145,230,115,231,149,151,232,233,210,234,235],"slopgate code smell utility locator","shared","reviews","inventory","search","hooks","new","coordination","radar","code-quality","Utilities","dataclass",{"skillNo":237,"name":238,"nameZh":6,"description":239,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":240,"categories":241,"keywords":244,"publishedAt":36},"01M7194AWG1Q37F9756H4SFDH9","slopgate-code-hygiene-refactor","Recovery playbook for Slopgate and project quality failures. Load after hook\u002Flint denials such as PY-CODE-017 flat sibling modules, PY-CODE-018 oversized modules, QUALITY-LINT-001 post-edit quality backstops, PY-QUALITY-010 magic numbers \u002F repeated literals, PY-CODE-012\u002FPY-CODE-013 smell findings, type-suppression bans, duplicate helpers, or repeated hygiene retry loops. Also load when asked to \"refactor this module\", \"split this file\", \"extract a class\", \"reduce complexity\", \"fix god class\", \"flatten module hierarchy\", \"move code to a package\", \"extract helpers\", \"consolidate duplicates\", \"replace magic numbers with constants\", or when a hook blocks an edit with structural complaints. Focuses on preserving public APIs while refactoring toward packages, cohesive modules, typed seams, and focused tests.","https:\u002F\u002Fgithub.com\u002Fvasceannie\u002Fslopgate\u002Fblob\u002Fmaster\u002Fbundle\u002Fshared\u002Fskills\u002Fslopgate-code-hygiene-refactor\u002FSKILL.md",[242,243],{"categoryNo":101,"categoryName":102,"taxonomyType":103,"taxonomyTypeDesc":104},{"categoryNo":167,"categoryName":168,"taxonomyType":169,"taxonomyTypeDesc":170},[245,246,116,247,200,248,179,249,250,201,251,227,252,112,145,187,115,189,231,149],"code hygiene","slopgate code hygiene refactor","refactor","modules","duplicates","retry","move","structural"]