[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6DVMAP0FSRV5GJB98F5SA8A":3,"skill-same:01M6DVMAP0FSRV5GJB98F5SA8A":84},{"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":39,"linkOnly":40,"markdownContent":41,"markdownBody":42,"frontMatter":43,"refName":44,"commitSha":45,"skillDirectory":46,"forksCount":47,"repositoryHtmlUrl":48,"repositoryHomepageUrl":6,"ownerHtmlUrl":49,"ownerBlogUrl":50,"ownerDescription":6,"updatedAt":51,"install":52,"resources":65},"01M6DVMAP0FSRV5GJB98F5SA8A","cv-tailor",null,"ACTIVATE when producing or reworking a CV, a résumé or an ESN dossier de compétences for the French market, or when adapting one to a specific job posting or mission brief. ACTIVATE for 'refais mon CV', 'adapte mon CV à cette offre', 'dossier de compétences', 'mon CV fait trop de pages', 'mon CV ne passe pas les ATS', 'CV freelance', 'tailor my resume', 'ATS check'. Compiles the career-evidence referential into a two-page ATS-safe CV or a mission-by-mission dossier, applies parsing rules taken from vendor documentation rather than folklore, and can never emit a client name whose disclosure level forbids it. DO NOT use to build or update the underlying referential (see career:career-evidence), to rewrite a LinkedIn profile (see career:linkedin-profile), or to write a cover letter or a commercial proposal.","FabienSalles\u002Fclaude-marketplace","FabienSalles","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F937901?v=4","01M6DVJBD31CJKRB382FQFZ5FH","Fabien Salles","01M6DVJBQNY8Q18KJD1ESAD6TX",9,"MIT","https:\u002F\u002Fgithub.com\u002FFabienSalles\u002Fclaude-marketplace\u002Fblob\u002Fmain\u002Fplugins\u002Fcareer\u002Fskills\u002Fcv-tailor\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38],"cv tailor","cv","evidence","rewrite","posting","pages","do","french","activate","Market","brief","never","use","commercial","linkedin profile","check","linkedin","Rules","page","parsing","2026-11-10 10:12:30",false,"---\nname: cv-tailor\ndescription: \"ACTIVATE when producing or reworking a CV, a résumé or an ESN dossier de compétences for the French market, or when adapting one to a specific job posting or mission brief. ACTIVATE for 'refais mon CV', 'adapte mon CV à cette offre', 'dossier de compétences', 'mon CV fait trop de pages', 'mon CV ne passe pas les ATS', 'CV freelance', 'tailor my resume', 'ATS check'. Compiles the career-evidence referential into a two-page ATS-safe CV or a mission-by-mission dossier, applies parsing rules taken from vendor documentation rather than folklore, and can never emit a client name whose disclosure level forbids it. DO NOT use to build or update the underlying referential (see career:career-evidence), to rewrite a LinkedIn profile (see career:linkedin-profile), or to write a cover letter or a commercial proposal.\"\n---\n\n# CV Tailor\n\nCompile the `career-evidence` referential into a document aimed at one reader. **The\nreferential is the source and is never edited from here**: a fact missing at compile\ntime is a fact to capture upstream, not to invent downstream.\n\n## 1. Classify before writing\n\nNever produce a document before these four are settled. They decide length, structure,\nvocabulary and what may be named. Ask only for what cannot be read from the request.\n\n| | Values | Decides |\n|---|---|---|\n| **Reader** | intermediary (recruiter, ESN sales, RH) · technical decision-maker (CTO, tech lead) · training buyer | vocabulary, what leads |\n| **Artifact** | 2-page CV · dossier de compétences · per-posting variant | structure and length |\n| **Channel** | ATS form · direct email · freelance platform · ESN | parsing constraints, anonymisation |\n| **Target** | the role aimed at, in the market's own words | title, ordering, keyword set |\n\nThe reader is the axis most often collapsed. On the French market a large share of\ninbound goes through intermediaries who filter on vocabulary without reading the\ntechnology. The same evidence therefore compiles differently: a technical\ndecision-maker wants the problem and the architecture, an intermediary wants the\nrole title, the stack and the availability.\n\n## 2. Two artifacts, one source\n\nThese are different documents, not two lengths of the same one. Producing a compromise\nbetween them is the most common failure and it serves neither reader.\n\n**The CV — two pages, never three.** Beyond ten years of experience one page\nunder-delivers, and past two pages a measurable share of recruiters reject on sight.\nDetail the last five to seven years; condense everything before into a single dense\nblock. Structure: identity → headline and summary → key skills → selected engagements →\nearlier career → training and certifications.\n\n**The dossier de compétences — long, mission by mission.** The format French\nintermediaries expect, and the one they can re-skin. Roughly half the volume goes to\nengagements, each opening with client context before its outcomes. Detail on the last\nfive to seven years, micro-engagements grouped rather than listed one by one. See\n[references\u002Fdossier-competences.md](references\u002Fdossier-competences.md).\n\nCutting an eleven-page dossier down to two pages destroys the artifact intermediaries\nactually read. Compile both from the same referential instead.\n\n## 3. Aggregate what is repetitive, detail what is singular\n\nEngagements are the reason someone reads the document, so they carry the detail.\nRecurring activity is proved by its totals, not by its list: twenty-five training\nsessions become four lines, seven audits become three. The referential keeps every\nentry so the totals stay recomputable.\n\nAggregate training by course rather than by year — a reader wants to know what can be\ntaught, and a chronological cut exposes gaps that need a sentence rather than a table.\nPrefer participant counts over session counts when a course was delivered to large\ncohorts, and state the totals so nothing looks concealed.\n\nWhere a course or an offering is no longer sold, keep it in a separate line rather than\nfolding it into the headline figure.\n\n## 4. Disclosure is enforced, not advised\n\nBefore emitting any client name, read its `disclosure` in the referential.\n\n- `public` → the name may appear.\n- `sector-only` → emit `## Formulation publique` verbatim. Never the name, never the\n  product, never the acronym, never a domain narrow enough to identify the buyer.\n- `excluded` → the engagement contributes to totals, seniority and date continuity, and\n  to nothing else.\n\nIf a restricted entry has no `## Formulation publique`, stop and say so. Do not\nsanitise on the fly: judging what identifies a buyer in a narrow market is the person's\ncall, made once, upstream.\n\n## 5. Bullets\n\nOne formula, applied everywhere: **verb, then object with the technology named, then a\nfigure or a scope, on the same line**. The reader scans line starts, so the verb comes\nfirst and the figure never spills to the next line.\n\nWhere no figure exists, state the scope instead of inventing an outcome, and make the\nchallenge explicit so the bullet still carries weight. Two lines is the right density;\none is thin, three is the ceiling.\n\nEvery technology listed in the skills section must appear in at least one engagement\nbullet. A skill listed and never demonstrated is what reviewers call inflated duties,\nand it is one of the markers they read as machine-written. See\n[references\u002Fbullet-formulas.md](references\u002Fbullet-formulas.md).\n\n## 6. Keyword coverage is a floor\n\nExtract the posting's vocabulary, classify each term as covered, partial, gap or\nnot-applicable, and place what is missing where the corresponding filter reads it.\nTarget roughly three quarters coverage and stop there.\n\nFull coverage is a defect, not a goal. It means terms were claimed without evidence,\nand reviewers name keyword saturation as the first thing that makes a document read as\ngenerated. Write the acronym and its expansion once each. Never append a keyword block\nat the end of the document: it ties no term to a dated engagement and reads as stuffing.\n\nOn form-based channels, fill the skills and languages fields by hand. At least one\nmajor ATS never populates them from the uploaded file, so the filters a recruiter uses\nstay empty however good the document is.\n\n## 7. Gate before delivery\n\nRun these in order. The first three are mechanical and must pass.\n\n1. **Plain-text extraction.** Extract the text from the produced file and read it. That\n   is what a parser sees. Wrong order, merged columns or words that lost letters mean\n   the file is broken whatever it looks like on screen. Watch the `fi` `ff` `fl`\n   ligatures in French: *certification*, *profil*, *efficacité*, *qualifications*.\n2. **Parsing rules.** Single column, no tables, no text boxes, nothing in headers or\n   footers, contact details in the body, standard section headings, one date format,\n   text-layer file under 2.5 MB. Full list with sources:\n   [references\u002Fats-rules-fr.md](references\u002Fats-rules-fr.md).\n3. **Disclosure.** No restricted name anywhere in the output.\n4. **Dates.** No unexplained overlap, no unexplained gap, and consistency with the\n   LinkedIn profile — recruiters check both.\n5. **Human pass.** Read it aloud. Every verb should be one the person would actually\n   say. Vary bullet length deliberately; uniform rhythm is a tell.\n\nDo not compute or report an ATS score. No major vendor produces one a candidate could\naim at — scores come from the tools that sell them. Report findings, not a grade.\n\n## 8. Deliver with its diff\n\nShip the document plus what changed and why, section by section, one line per change.\nThe person accepts or rejects each one. A document rewritten in one block cannot be\nreviewed, only trusted.\n\nState explicitly what was left out and why: entries dropped for relevance, figures\nmissing upstream, sections aggregated. Silent truncation reads as full coverage.\n\n## Anti-patterns\n\n- **Compromising between the CV and the dossier.** Two readers, two artifacts.\n- **Reporting a score.** It measures the tool that computed it.\n- **Sanitising a restricted client on the fly** instead of stopping when the public\n  formulation is missing.\n- **Maximising keyword coverage.** Past the floor it is the marker reviewers reject on.\n- **Editing the referential from here.** Missing facts go upstream.\n- **Reordering engagements out of chronology** to put a relevant one first. Parsers and\n  readers both infer recency from position; move the bullets, not the entries.\n- **Reducing legibility to hit a page count.** A clean two pages beats a cramped one.\n","# CV Tailor\n\nCompile the `career-evidence` referential into a document aimed at one reader. **The\nreferential is the source and is never edited from here**: a fact missing at compile\ntime is a fact to capture upstream, not to invent downstream.\n\n## 1. Classify before writing\n\nNever produce a document before these four are settled. They decide length, structure,\nvocabulary and what may be named. Ask only for what cannot be read from the request.\n\n| | Values | Decides |\n|---|---|---|\n| **Reader** | intermediary (recruiter, ESN sales, RH) · technical decision-maker (CTO, tech lead) · training buyer | vocabulary, what leads |\n| **Artifact** | 2-page CV · dossier de compétences · per-posting variant | structure and length |\n| **Channel** | ATS form · direct email · freelance platform · ESN | parsing constraints, anonymisation |\n| **Target** | the role aimed at, in the market's own words | title, ordering, keyword set |\n\nThe reader is the axis most often collapsed. On the French market a large share of\ninbound goes through intermediaries who filter on vocabulary without reading the\ntechnology. The same evidence therefore compiles differently: a technical\ndecision-maker wants the problem and the architecture, an intermediary wants the\nrole title, the stack and the availability.\n\n## 2. Two artifacts, one source\n\nThese are different documents, not two lengths of the same one. Producing a compromise\nbetween them is the most common failure and it serves neither reader.\n\n**The CV — two pages, never three.** Beyond ten years of experience one page\nunder-delivers, and past two pages a measurable share of recruiters reject on sight.\nDetail the last five to seven years; condense everything before into a single dense\nblock. Structure: identity → headline and summary → key skills → selected engagements →\nearlier career → training and certifications.\n\n**The dossier de compétences — long, mission by mission.** The format French\nintermediaries expect, and the one they can re-skin. Roughly half the volume goes to\nengagements, each opening with client context before its outcomes. Detail on the last\nfive to seven years, micro-engagements grouped rather than listed one by one. See\n[references\u002Fdossier-competences.md](references\u002Fdossier-competences.md).\n\nCutting an eleven-page dossier down to two pages destroys the artifact intermediaries\nactually read. Compile both from the same referential instead.\n\n## 3. Aggregate what is repetitive, detail what is singular\n\nEngagements are the reason someone reads the document, so they carry the detail.\nRecurring activity is proved by its totals, not by its list: twenty-five training\nsessions become four lines, seven audits become three. The referential keeps every\nentry so the totals stay recomputable.\n\nAggregate training by course rather than by year — a reader wants to know what can be\ntaught, and a chronological cut exposes gaps that need a sentence rather than a table.\nPrefer participant counts over session counts when a course was delivered to large\ncohorts, and state the totals so nothing looks concealed.\n\nWhere a course or an offering is no longer sold, keep it in a separate line rather than\nfolding it into the headline figure.\n\n## 4. Disclosure is enforced, not advised\n\nBefore emitting any client name, read its `disclosure` in the referential.\n\n- `public` → the name may appear.\n- `sector-only` → emit `## Formulation publique` verbatim. Never the name, never the\n  product, never the acronym, never a domain narrow enough to identify the buyer.\n- `excluded` → the engagement contributes to totals, seniority and date continuity, and\n  to nothing else.\n\nIf a restricted entry has no `## Formulation publique`, stop and say so. Do not\nsanitise on the fly: judging what identifies a buyer in a narrow market is the person's\ncall, made once, upstream.\n\n## 5. Bullets\n\nOne formula, applied everywhere: **verb, then object with the technology named, then a\nfigure or a scope, on the same line**. The reader scans line starts, so the verb comes\nfirst and the figure never spills to the next line.\n\nWhere no figure exists, state the scope instead of inventing an outcome, and make the\nchallenge explicit so the bullet still carries weight. Two lines is the right density;\none is thin, three is the ceiling.\n\nEvery technology listed in the skills section must appear in at least one engagement\nbullet. A skill listed and never demonstrated is what reviewers call inflated duties,\nand it is one of the markers they read as machine-written. See\n[references\u002Fbullet-formulas.md](references\u002Fbullet-formulas.md).\n\n## 6. Keyword coverage is a floor\n\nExtract the posting's vocabulary, classify each term as covered, partial, gap or\nnot-applicable, and place what is missing where the corresponding filter reads it.\nTarget roughly three quarters coverage and stop there.\n\nFull coverage is a defect, not a goal. It means terms were claimed without evidence,\nand reviewers name keyword saturation as the first thing that makes a document read as\ngenerated. Write the acronym and its expansion once each. Never append a keyword block\nat the end of the document: it ties no term to a dated engagement and reads as stuffing.\n\nOn form-based channels, fill the skills and languages fields by hand. At least one\nmajor ATS never populates them from the uploaded file, so the filters a recruiter uses\nstay empty however good the document is.\n\n## 7. Gate before delivery\n\nRun these in order. The first three are mechanical and must pass.\n\n1. **Plain-text extraction.** Extract the text from the produced file and read it. That\n   is what a parser sees. Wrong order, merged columns or words that lost letters mean\n   the file is broken whatever it looks like on screen. Watch the `fi` `ff` `fl`\n   ligatures in French: *certification*, *profil*, *efficacité*, *qualifications*.\n2. **Parsing rules.** Single column, no tables, no text boxes, nothing in headers or\n   footers, contact details in the body, standard section headings, one date format,\n   text-layer file under 2.5 MB. Full list with sources:\n   [references\u002Fats-rules-fr.md](references\u002Fats-rules-fr.md).\n3. **Disclosure.** No restricted name anywhere in the output.\n4. **Dates.** No unexplained overlap, no unexplained gap, and consistency with the\n   LinkedIn profile — recruiters check both.\n5. **Human pass.** Read it aloud. Every verb should be one the person would actually\n   say. Vary bullet length deliberately; uniform rhythm is a tell.\n\nDo not compute or report an ATS score. No major vendor produces one a candidate could\naim at — scores come from the tools that sell them. Report findings, not a grade.\n\n## 8. Deliver with its diff\n\nShip the document plus what changed and why, section by section, one line per change.\nThe person accepts or rejects each one. A document rewritten in one block cannot be\nreviewed, only trusted.\n\nState explicitly what was left out and why: entries dropped for relevance, figures\nmissing upstream, sections aggregated. Silent truncation reads as full coverage.\n\n## Anti-patterns\n\n- **Compromising between the CV and the dossier.** Two readers, two artifacts.\n- **Reporting a score.** It measures the tool that computed it.\n- **Sanitising a restricted client on the fly** instead of stopping when the public\n  formulation is missing.\n- **Maximising keyword coverage.** Past the floor it is the marker reviewers reject on.\n- **Editing the referential from here.** Missing facts go upstream.\n- **Reordering engagements out of chronology** to put a relevant one first. Parsers and\n  readers both infer recency from position; move the bullets, not the entries.\n- **Reducing legibility to hit a page count.** A clean two pages beats a cramped one.\n",{"name":5,"description":7},"main","479b264ec17cc5fafbf36287a1087472d3a386d3","plugins\u002Fcareer\u002Fskills\u002Fcv-tailor",2,"https:\u002F\u002Fgithub.com\u002FFabienSalles\u002Fclaude-marketplace","https:\u002F\u002Fgithub.com\u002FFabienSalles","https:\u002F\u002Ffabiensalles.com","2026-10-13 04:33:22",{"source":8,"skillName":5,"commands":53,"prompt":63,"zipAvailable":64},[54,57,60],{"tool":55,"command":56},"npx","npx skills add FabienSalles\u002Fclaude-marketplace --skill cv-tailor",{"tool":58,"command":59},"bunx","bunx skills add FabienSalles\u002Fclaude-marketplace --skill cv-tailor",{"tool":61,"command":62},"pnpm","pnpm dlx skills add FabienSalles\u002Fclaude-marketplace --skill cv-tailor","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FFabienSalles\u002Fclaude-marketplace\u002Fblob\u002Fmain\u002Fplugins\u002Fcareer\u002Fskills\u002Fcv-tailor\u002FSKILL.md",true,[66,72,76,80],{"path":67,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":70,"sourceHtmlUrl":71},"index.json","REFERENCE","参考文档",512,"https:\u002F\u002Fgithub.com\u002FDCx7C5\u002Fai-marketplace\u002Fblob\u002Fmain\u002Fskills\u002Fmalware-c2-adversary-monitor\u002Findex.json",{"path":73,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":74,"sourceHtmlUrl":75},"references\u002Fats-rules-fr.md",9093,"https:\u002F\u002Fgithub.com\u002FFabienSalles\u002Fclaude-marketplace\u002Fblob\u002Fmain\u002Fplugins\u002Fcareer\u002Fskills\u002Fcv-tailor\u002Freferences\u002Fats-rules-fr.md",{"path":77,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":78,"sourceHtmlUrl":79},"references\u002Fbullet-formulas.md",10348,"https:\u002F\u002Fgithub.com\u002FFabienSalles\u002Fclaude-marketplace\u002Fblob\u002Fmain\u002Fplugins\u002Fcareer\u002Fskills\u002Fcv-tailor\u002Freferences\u002Fbullet-formulas.md",{"path":81,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":82,"sourceHtmlUrl":83},"references\u002Fdossier-competences.md",6211,"https:\u002F\u002Fgithub.com\u002FFabienSalles\u002Fclaude-marketplace\u002Fblob\u002Fmain\u002Fplugins\u002Fcareer\u002Fskills\u002Fcv-tailor\u002Freferences\u002Fdossier-competences.md",[85,114,133,153,176,193],{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":96,"publishedAt":39},"01M6DW2YS1MGF65JNS1QQ15QHS","vitest-test-conventions","ACTIVATE when writing Vitest tests, creating test files, using vi.fn()\u002Fvi.mock()\u002Fvi.spyOn(), or test factories. ACTIVATE for 'Vitest', 'it.each', 'NestJS testing module', 'supertest', 'vi.fn', 'vi.mock', 'spyOn'. Provides Vitest\u002FNestJS-specific testing patterns; cross-language testing principles (DAMP, AAA, spy over mock, what NOT to test) live in craft:testing-principles. DO NOT use for: node:test files (a file importing node:test) or a project whose tests run under node --test (see node-test:node-test-conventions), TDD workflow\u002Fiterations (see vitest:vitest-tdd-workflow), PHP\u002FPHPUnit tests (see phpunit:php-test-conventions).","https:\u002F\u002Fgithub.com\u002FFabienSalles\u002Fclaude-marketplace\u002Fblob\u002Fmain\u002Fplugins\u002Fvitest\u002Fskills\u002Fvitest-test-conventions\u002FSKILL.md",[91],{"categoryNo":92,"categoryName":93,"taxonomyType":94,"taxonomyTypeDesc":95},"01JBSEEDCAT000000000000008","测试与质量","SCENARIO","使用场景",[97,98,99,100,101,102,103,104,105,106,31,107,108,27,25,109,110,111,112,113],"test","vitest","conventions","vitest test conventions","testing","writing","tdd","workflow","file","testing patterns","files","nestjs","project","tests","module","fn","testing principles",{"skillNo":115,"name":116,"nameZh":6,"description":117,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":118,"categories":119,"keywords":123,"publishedAt":39},"01M6DW2VFE6NPFCGQKQ68P1MVZ","vitest-tdd-workflow","ACTIVATE when building new features, endpoints, or user stories using TDD with Vitest in a TypeScript\u002FNestJS context. ACTIVATE for '\u002Ffeature-tdd-dev', 'TDD', 'red-green-refactor' in TS context. Provides Vitest\u002FNestJS-specific TDD examples and commands; cross-language TDD workflow (cross-layer iterations, RED-GREEN-REFACTOR, working app, bug-fix-first-test, mocks-hiding-bugs) lives in craft:tdd-workflow-principles. DO NOT use for: node:test files (a file importing node:test) or a project whose tests run under node --test (see node-test:node-test-conventions), test writing conventions (see vitest:vitest-test-conventions), PHP TDD (see phpunit:php-tdd-workflow).","https:\u002F\u002Fgithub.com\u002FFabienSalles\u002Fclaude-marketplace\u002Fblob\u002Fmain\u002Fplugins\u002Fvitest\u002Fskills\u002Fvitest-tdd-workflow\u002FSKILL.md",[120],{"categoryNo":121,"categoryName":122,"taxonomyType":94,"taxonomyTypeDesc":95},"01JBSEEDCAT000000000000023","Skill与智能体开发",[103,104,124,98,125,102,126,105,127,128,31,129,107,27,25,130,109,110,131,132],"tdd workflow","vitest tdd workflow","dev","examples","fix","red-green-refactor","green","feature","app",{"skillNo":134,"name":135,"nameZh":6,"description":136,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":137,"categories":138,"keywords":139,"publishedAt":39},"01M6DW2RGMQE10D8C5Z5MA2RMY","ts-refactoring","ACTIVATE when refactoring TypeScript code. ACTIVATE for 'refactor', 'extract', 'redesign', 'simplify', or 'clean up' in a TypeScript \u002F Node \u002F NestJS context. This skill provides TS-specific examples for the cross-language refactoring rules defined in craft:refactoring-principles. DO NOT use for: writing new features from scratch, general OOP patterns (see ts-oop).","https:\u002F\u002Fgithub.com\u002FFabienSalles\u002Fclaude-marketplace\u002Fblob\u002Fmain\u002Fplugins\u002Ftypescript\u002Fskills\u002Fts-refactoring\u002FSKILL.md",[],[140,141,102,142,143,127,144,145,36,146,147,31,148,149,150,108,151,27,25,152],"refactoring","ts refactoring","typescript","code","refactor","simplify","node","redesign","up","general","clean","craft","patterns",{"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":160,"publishedAt":39},"01M6DW2MHYXNBBVYEGB058Y48J","ts-ports-adapters","ACTIVATE when a TypeScript codebase with no dependency-injection container has to declare a port and wire its adapter — a repository, a clock, an id generator, an event dispatcher the domain depends on. ACTIVATE for 'port', 'adapter', 'SPI', 'dependency inversion' or 'composition root' in a codebase that wires its dependencies by hand. Covers: the port as a type of functions in the domain layer, the adapter as an object literal annotated with it, the handler that takes its dependencies first and its data second, the composition root in the infrastructure layer, and the in-memory stub that substitutes for the adapter in a unit test. DO NOT use for: NestJS, or any container-based DI with decorators and tokens (see nest-ddd-conventions), aggregate operations and smart constructors (see ddd-ts-fp), the Result type itself (see ts-functional).","https:\u002F\u002Fgithub.com\u002FFabienSalles\u002Fclaude-marketplace\u002Fblob\u002Fmain\u002Fplugins\u002Ftypescript\u002Fskills\u002Fts-ports-adapters\u002FSKILL.md",[159],{"categoryNo":92,"categoryName":93,"taxonomyType":94,"taxonomyTypeDesc":95},[161,162,163,97,164,165,31,166,167,108,168,27,25,169,170,171,172,173,174,175],"ports","ts ports adapters","memory","ddd","Composition","container","functions","Literal","dependency-injection","domain","tokens","as","type","id","adapter",{"skillNo":177,"name":178,"nameZh":6,"description":179,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":180,"categories":181,"keywords":182,"publishedAt":39},"01M6DW2GRXZFYT05HEDB26C9B8","ts-oop","ACTIVATE when designing TypeScript classes, and the value objects or collections modelled as classes, or when the user asks about object design, encapsulation, Tell Don't Ask, or Symbol.iterator. Provides TS-specific examples for the cross-language OOP rules defined in craft:oop-principles, plus TS-specific patterns (Symbol.iterator, branded types for primitive identifiers). DO NOT use for: a value object or an aggregate modelled as an immutable record rather than a class (see ddd-ts-fp), refactoring methodology (see ts-refactoring).","https:\u002F\u002Fgithub.com\u002FFabienSalles\u002Fclaude-marketplace\u002Fblob\u002Fmain\u002Fplugins\u002Ftypescript\u002Fskills\u002Fts-oop\u002FSKILL.md",[],[183,184,185,142,164,127,186,187,140,36,188,31,189,151,27,25,190,191,192,172],"oop","ts oop","design","methodology","immutable","ask","refactoring methodology","objects","record","collections",{"skillNo":194,"name":195,"nameZh":6,"description":196,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":197,"categories":198,"keywords":199,"publishedAt":39},"01M6DW2D26XG5MJMTP9MSE43S2","ts-layer-boundaries","ACTIVATE when wiring a Worker entry point, a Router, a controller, or a domain event consumer in a TypeScript CQRS codebase, or when deciding where a port belongs. ACTIVATE for 'composition root', 'layer boundary', 'ESLint zones', 'domain must not import infrastructure'. Covers: the *Worker.ts composition root, the curried consumer, Router wiring of command endpoints, the five-gesture controller, the domain-to-infrastructure import boundary enforced by ESLint, infrastructure-only ports, in-memory doubles for every port, the read-can-reach-write asymmetry, and read endpoints going through a domain handler. DO NOT use for: the port's own shape and adapter binding (see ts-ports-adapters), the Result type (see ts-functional), domain event structure (see ts-ddd-events).","https:\u002F\u002Fgithub.com\u002FFabienSalles\u002Fclaude-marketplace\u002Fblob\u002Fmain\u002Fplugins\u002Ftypescript\u002Fskills\u002Fts-layer-boundaries\u002FSKILL.md",[],[200,163,164,201,202,165,161,31,203,204,205,27,25,206,170,207,208,173,175,209],"ts layer boundaries","controller","boundary","router","only","endpoints","structure","cqrs","worker","import"]