[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6NQ74C8EKMSABDNN4T6TFBD":3,"skill-same:01M6NQ74C8EKMSABDNN4T6TFBD":201},{"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":46,"commitSha":47,"skillDirectory":48,"forksCount":14,"repositoryHtmlUrl":49,"repositoryHomepageUrl":6,"ownerHtmlUrl":50,"ownerBlogUrl":51,"ownerDescription":6,"updatedAt":52,"install":53,"resources":66},"01M6NQ74C8EKMSABDNN4T6TFBD","project-ployglot-project-scafford",null,"Scaffold a polyglot library project as TypeScript + Python twin packages under `packages\u002Fts\u002F` + `packages\u002Fpy\u002F`, with a shared `SPEC.md`, cross-language `tests\u002Fparity\u002Ffixtures.json`, side-by-side `examples\u002Fsdk\u002F` + `examples\u002Fapi\u002F` documentation, per-package `Makefile`, and a root orchestrator that exposes `make ci`. Open-source friendly — no organization-specific paths or scopes baked in. Use when starting a new polyglot library, porting a single-language library to a twin, or auditing\u002Fregularizing an existing two-language repo against the canonical layout.","carlosmarte\u002Fai-agent-artifacts","carlosmarte","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F3478576?v=4","01M6NPRTEXZG86XJXMGQ05A24X","Carlos Marte","01M6NPRTK4A6A4Q8CMWMH1ZY7W",0,"MIT","https:\u002F\u002Fgithub.com\u002Fcarlosmarte\u002Fai-agent-artifacts\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fproject-ployglot-project-scafford\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38],"project ployglot project scafford","project","only","\u003Cslug>","scope","false","dry","layout","shared","organization","documentation","orchestrator","read","Bash","makefile","open","api","ci","run","packages","2026-11-10 10:12:30",false,"---\nname: project-ployglot-project-scafford\ndescription: Scaffold a polyglot library project as TypeScript + Python twin packages under `packages\u002Fts\u002F` + `packages\u002Fpy\u002F`, with a shared `SPEC.md`, cross-language `tests\u002Fparity\u002Ffixtures.json`, side-by-side `examples\u002Fsdk\u002F` + `examples\u002Fapi\u002F` documentation, per-package `Makefile`, and a root orchestrator that exposes `make ci`. Open-source friendly — no organization-specific paths or scopes baked in. Use when starting a new polyglot library, porting a single-language library to a twin, or auditing\u002Fregularizing an existing two-language repo against the canonical layout.\ntier: project\nallowed-tools: Read, Write, Edit, Glob, Grep, Bash, AskUserQuestion\nargument-hint: \"\u003Cslug> [--scope @your-org] [--ts-only|--py-only|--both] [--dry-run]\"\ndisable-model-invocation: false\n---\n\n# Polyglot Project Scaffold (TS + Python twins)\n\nGenerate the canonical layout for a polyglot library that ships as two\nlanguage twins — TypeScript (`packages\u002Fts\u002F`) and Python (`packages\u002Fpy\u002F`) —\ngoverned by a single behavioral spec and proven by a shared cross-language\nparity fixture.\n\nThe shape is intentionally open-source-friendly: no internal organization\nscopes, no agent-runtime paths, no plan-tree dependencies. Every file\nwritten is something a downstream user can publish to npm + PyPI or fork\ninto their own repo.\n\n## When to use this skill\n\n- Starting a new library and you want it to have **TypeScript + Python**\n  surfaces from day one with parity enforced by tests, not vibes.\n- Porting a single-language library to a twin (e.g. you have the TS but\n  want the Python twin) and want the cross-language scaffolding —\n  `SPEC.md`, parity fixtures, `examples\u002F{sdk,api}\u002F`, root `Makefile` —\n  in place before the port.\n- Auditing or normalizing an existing two-language repo: comparing the\n  current state against `references\u002Freference-structure.md` and writing\n  the missing load-bearing files.\n\nSkip when:\n\n- The work needs more than two languages, or a non-library shape (CLI,\n  service, multi-package monorepo). Use a different skill for those.\n- The repo is already a polyglot SDK with full client\u002Ftransport\u002F\n  middleware\u002Fretry layering — that's the SDK paradigms canon, not a\n  library scaffold. Use `sdk-paradigms-scaffold` instead.\n- You have a feature\u002Fstory\u002Ftask plan tree and want plan-driven\n  implementation — use `implement-polyglot-project-plan` (sibling skill,\n  not part of this open-source pattern).\n\n## Reference structure\n\nThe canonical layout this skill produces:\n\n```\n\u003Crepo-root>\u002F\n├── README.md                       # repo intro + per-language quick start\n├── SPEC.md                         # canonical behavior — both ports MUST conform\n├── LICENSE                         # MIT (or user-supplied)\n├── Makefile                        # root orchestrator: ci, ci-ts, ci-py, clean\n├── package.json                    # npm workspace marker (workspaces: [\"packages\u002Fts\"])\n├── pyproject.toml                  # Python layout marker (no build, points at packages\u002Fpy)\n├── .gitignore                      # Node + Python + IDE\u002FOS + env ignores\n├── .agent.md                       # LLM entry reference (root index)\n├── .agent.json                     # machine-readable counterpart of .agent.md\n├── .agents\u002F\n│   └── parity.md                   # twin drift catalog + intentional asymmetries\n├── packages\u002F\n│   ├── ts\u002F\n│   │   ├── package.json            # the publishable npm package\n│   │   ├── tsconfig.json           # strict TS config\n│   │   ├── Makefile                # help\u002Finstall\u002Fci-install\u002Ftest\u002Flint\u002Fbuild\u002Fpack\u002Fclean\u002Fdistclean\u002Fci\n│   │   ├── .agent.md               # per-package LLM skill file\n│   │   ├── src\u002F\n│   │   │   └── index.ts            # public surface — re-exports only\n│   │   └── test\u002F\n│   │       ├── smoke.test.ts       # the package loads + exports the surface\n│   │       └── parity.test.ts      # consumes ..\u002F..\u002Ftests\u002Fparity\u002Ffixtures.json\n│   └── py\u002F\n│       ├── pyproject.toml          # the publishable PyPI package\n│       ├── Makefile                # uv-aware; falls back to pip+pytest on bare runners\n│       ├── README.md               # 1-line pointer to the TS twin\n│       ├── .agent.md               # per-package LLM skill file\n│       ├── \u003Csnake_pkg>\u002F\n│       │   ├── __init__.py         # public surface — re-exports only\n│       │   └── py.typed            # PEP 561 marker\n│       └── tests\u002F\n│           ├── __init__.py\n│           ├── _helpers.py         # env-isolation utilities for tests\n│           ├── test_smoke.py       # the package loads + exports the surface\n│           └── test_parity.py      # consumes ..\u002F..\u002Ftests\u002Fparity\u002Ffixtures.json\n├── tests\u002F\n│   └── parity\u002F\n│       └── fixtures.json           # shared cross-language behavior fixtures\n└── examples\u002F\n    ├── README.md\n    ├── sdk\u002F\n    │   ├── README.md               # programmatic embedding scenarios\n    │   └── 01-\u003Cscenario>.md        # side-by-side TS + Python code per scenario\n    └── api\u002F\n        ├── README.md               # per-function contract reference\n        └── 01-\u003Centry>.md           # signature, inputs, errors per entry\n```\n\nSee `references\u002Freference-structure.md` for the field-by-field inventory.\n\n## Placeholders\n\nTemplates use these placeholders. Resolve every one before writing:\n\n| Placeholder      | Meaning                                                | Example                       |\n| ---------------- | ------------------------------------------------------ | ----------------------------- |\n| `\u003Cslug>`         | Kebab-case package name (used for npm + PyPI names)    | `my-lib`                      |\n| `\u003Csnake_pkg>`    | Python module directory \u002F import name                  | `my_lib`                      |\n| `\u003Cscope>`        | Optional npm scope (drop for a flat name)              | `@your-org` or empty          |\n| `\u003Crepo-name>`    | Top-level repo folder name                             | `my-lib`                      |\n| `\u003Cauthor>`       | Author name in package metadata                        | `Jane Doe`                    |\n| `\u003Csubject>`      | One-phrase domain descriptor for README\u002FSPEC intros    | `concise tagline of behavior` |\n| `\u003Csurface-list>` | Comma-separated public symbols (used in `.agent.md`)   | `doThing, doOtherThing, ...`  |\n\nConventions:\n\n- `\u003Cslug>` and the npm name match directly. With a scope, the npm name is\n  `\u003Cscope>\u002F\u003Cslug>` (e.g. `@your-org\u002F\u003Cslug>`). Without a scope, both\n  npm and PyPI publish as `\u003Cslug>`.\n- `\u003Csnake_pkg>` is the Python import name — always derive it from `\u003Cslug>`\n  by replacing dashes with underscores.\n- The user can freely change these post-scaffold; this skill picks\n  defaults so the repo boots immediately.\n\n## Workflow\n\n### Step 1 — Resolve scaffold parameters\n\n1. Accept `$ARGUMENTS` of the form `\u003Cslug> [--scope @your-org] [--ts-only|--py-only|--both] [--dry-run]`.\n2. If `\u003Cslug>` is missing, ask via `AskUserQuestion`. Validate it is\n   kebab-case (`^[a-z][a-z0-9-]*$`); reject otherwise with a clear\n   error.\n3. Derive `\u003Csnake_pkg>` from `\u003Cslug>` (`s\u002F-\u002F_\u002Fg`).\n4. Resolve `\u003Cscope>`: explicit `--scope` flag wins; otherwise leave\n   empty (publishes as flat `\u003Cslug>`).\n5. Default to `--both` packages. Honor `--ts-only` \u002F `--py-only` to\n   skip the other tree.\n6. Confirm with the user before writing: print the resolved\n   placeholders + the file list this run will write.\n\n### Step 2 — Inspect the working directory\n\n1. Run `Glob` on the cwd. If the directory is empty (or contains only\n   `.git\u002F`, `LICENSE`, `README.md`), proceed to a fresh scaffold.\n2. If `packages\u002Fts\u002F` or `packages\u002Fpy\u002F` already exist, do **not** overwrite.\n   Walk the layout in `references\u002Freference-structure.md` and report\n   missing files — write **only** the missing ones, leaving existing\n   files untouched.\n3. If the repo is clearly not a polyglot library candidate (has its own\n   `src\u002F`, monorepo manifest, foreign workspace shape), stop and ask.\n\n### Step 3 — Write root files\n\nIn this order, from `references\u002Ftemplates\u002F`:\n\n1. `root-README.md` → `README.md`\n2. `root-SPEC.md` → `SPEC.md` (intentionally a stub — the user fills the\n   behavior; the structure is what this skill provides)\n3. `root-LICENSE` → `LICENSE` (skip if already present)\n4. `root-Makefile` → `Makefile`\n5. `root-package.json` → `package.json`\n6. `root-pyproject.toml` → `pyproject.toml`\n7. `root-gitignore` → `.gitignore`\n8. `root-agent.md` → `.agent.md`\n9. `root-agent.json` → `.agent.json`\n10. `root-agents-parity.md` → `.agents\u002Fparity.md`\n\nIf `--ts-only`, the root `package.json` is still written (it's the\nworkspace marker). If `--py-only`, write a minimal `package.json` with\nempty `workspaces` so the root remains valid; the user can drop it\nlater.\n\n### Step 4 — Write per-package files\n\nFor TypeScript (when `--both` or `--ts-only`):\n\n| Source                                     | Target                                  |\n| ------------------------------------------ | --------------------------------------- |\n| `packages-ts\u002Fpackage.json`                 | `packages\u002Fts\u002Fpackage.json`              |\n| `packages-ts\u002Ftsconfig.json`                | `packages\u002Fts\u002Ftsconfig.json`             |\n| `packages-ts\u002FMakefile`                     | `packages\u002Fts\u002FMakefile`                  |\n| `packages-ts\u002Fagent.md`                     | `packages\u002Fts\u002F.agent.md`                 |\n| `packages-ts\u002Fsrc-index.ts`                 | `packages\u002Fts\u002Fsrc\u002Findex.ts`              |\n| `packages-ts\u002Ftest-smoke.test.ts`           | `packages\u002Fts\u002Ftest\u002Fsmoke.test.ts`        |\n| `packages-ts\u002Ftest-parity.test.ts`          | `packages\u002Fts\u002Ftest\u002Fparity.test.ts`       |\n\nFor Python (when `--both` or `--py-only`):\n\n| Source                                       | Target                                              |\n| -------------------------------------------- | --------------------------------------------------- |\n| `packages-py\u002Fpyproject.toml`                 | `packages\u002Fpy\u002Fpyproject.toml`                        |\n| `packages-py\u002FMakefile`                       | `packages\u002Fpy\u002FMakefile`                              |\n| `packages-py\u002FREADME.md`                      | `packages\u002Fpy\u002FREADME.md`                             |\n| `packages-py\u002Fagent.md`                       | `packages\u002Fpy\u002F.agent.md`                             |\n| `packages-py\u002Fsnake_pkg-__init__.py`          | `packages\u002Fpy\u002F\u003Csnake_pkg>\u002F__init__.py`               |\n| `packages-py\u002Fsnake_pkg-py.typed`             | `packages\u002Fpy\u002F\u003Csnake_pkg>\u002Fpy.typed` (empty file)     |\n| `packages-py\u002Ftests-__init__.py`              | `packages\u002Fpy\u002Ftests\u002F__init__.py` (empty file)        |\n| `packages-py\u002Ftests-_helpers.py`              | `packages\u002Fpy\u002Ftests\u002F_helpers.py`                     |\n| `packages-py\u002Ftests-test_smoke.py`            | `packages\u002Fpy\u002Ftests\u002Ftest_smoke.py`                   |\n| `packages-py\u002Ftests-test_parity.py`           | `packages\u002Fpy\u002Ftests\u002Ftest_parity.py`                  |\n\n### Step 5 — Write parity + examples scaffolding\n\n| Source                                       | Target                                  |\n| -------------------------------------------- | --------------------------------------- |\n| `tests-parity\u002Ffixtures.json`                 | `tests\u002Fparity\u002Ffixtures.json`            |\n| `examples\u002FREADME.md`                         | `examples\u002FREADME.md`                    |\n| `examples\u002Fsdk-README.md`                     | `examples\u002Fsdk\u002FREADME.md`                |\n| `examples\u002Fapi-README.md`                     | `examples\u002Fapi\u002FREADME.md`                |\n\nThe `examples\u002Fsdk\u002F01-\u003Cscenario>.md` and `examples\u002Fapi\u002F01-\u003Centry>.md`\nfiles are deliberately not auto-generated — they describe **specific\nbehavior** of the user's library, which this skill does not know.\nThe `examples\u002F{sdk,api}\u002FREADME.md` files include a \"How to add a new\nexample\" section the user follows.\n\n### Step 6 — Verify the scaffold boots\n\nAfter writing, run a smoke check:\n\n```bash\nmake ci-install\nmake ci\n```\n\nThe first run will fail at the parity test (the fixtures file is a\nstub) and may fail at the smoke test (the public surface is empty).\nThat is expected — the skill produces a structurally complete repo,\nnot a behaviorally complete one. Report the failure clearly so the\nuser knows what to fill in next:\n\n1. Edit `SPEC.md` to define the behavior contract.\n2. Implement the public surface in `packages\u002Fts\u002Fsrc\u002Findex.ts` and\n   `packages\u002Fpy\u002F\u003Csnake_pkg>\u002F__init__.py` (or sub-modules they\n   re-export).\n3. Replace the placeholder fixture in `tests\u002Fparity\u002Ffixtures.json`\n   with cases that exercise the surface in both languages.\n4. Add scenario files under `examples\u002Fsdk\u002F` and `examples\u002Fapi\u002F`.\n\n### Step 7 — Report\n\nEmit a short summary:\n\n- Resolved placeholders (`\u003Cslug>`, `\u003Csnake_pkg>`, `\u003Cscope>`).\n- Files written (count, grouped by tree).\n- Files skipped because they already existed.\n- Smoke result (`make ci-install` exit, `make ci` exit, with the\n  expected stub-failure note if applicable).\n- Next-step checklist (the four-step \"fill in\" list from Step 6).\n\n## Hard rules\n\n- **Never write organization-specific or host-machine-absolute paths\n  into a scaffolded file.** This skill is open-source. Use relative\n  paths and generic scope placeholders. Do not embed `\u002FUsers\u002F...`\n  paths anywhere in template output.\n- **Never overwrite an existing file** without confirming first. The\n  scaffold is additive — if `pyproject.toml` already exists, leave\n  it alone and report the skip.\n- **Never collapse the twin layout** even if the user only wants one\n  language today. Write the full root scaffold so the second twin can\n  be added later without restructuring.\n- **Never invent the SPEC.** The skill writes a `SPEC.md` stub that\n  documents the *structure* of a spec (function inventory table,\n  algorithm section, drift table). Concrete behavior is the user's\n  job — do not put fake behavior in there.\n- **Never skip parity-test wiring.** Even with empty fixtures, both\n  `parity.test.ts` and `test_parity.py` must be written so adding a\n  fixture entry later is the only required step to expand parity\n  coverage.\n- **Do not push, publish, tag, or open PRs** unless the user\n  explicitly asks.\n\n## Inputs and arguments\n\n- `$ARGUMENTS` shape: `\u003Cslug> [--scope @your-org] [--ts-only|--py-only|--both] [--dry-run]`\n- `--scope` — optional npm scope. Without it, the npm name is the bare\n  `\u003Cslug>`.\n- `--ts-only` \u002F `--py-only` — write only one language tree. Default\n  is both. The root scaffold (`Makefile`, `package.json`,\n  `pyproject.toml`, `SPEC.md`, etc.) is always written.\n- `--dry-run` — print the resolved placeholders and the source →\n  target file map without calling `Write`. Useful to confirm the\n  layout before committing to a scaffold.\n\n## Examples\n\nAll examples below use `\u003Cyour-slug>` as the placeholder for whatever\nkebab-case name the user picks. Substitute it in real invocations.\n\n**Bootstrap a fresh polyglot library, both languages, no scope:**\n\n```\n\u002Fployglot-project-scafford \u003Cyour-slug>\n```\n\nWrites the full layout. `package.json` declares the npm name as\n`\u003Cyour-slug>`. `pyproject.toml` declares the PyPI name as\n`\u003Cyour-slug>`. Python module derives by replacing dashes with\nunderscores.\n\n**Bootstrap with an npm scope:**\n\n```\n\u002Fployglot-project-scafford \u003Cyour-slug> --scope @your-org\n```\n\n`package.json` becomes `@your-org\u002F\u003Cyour-slug>`; PyPI name stays the\nunscoped `\u003Cyour-slug>` (PyPI has no scopes).\n\n**Add the Python twin to an existing TS-only repo:**\n\n```\n\u002Fployglot-project-scafford \u003Cyour-slug> --py-only\n```\n\nSkill detects the existing `packages\u002Fts\u002F` and only writes the\n`packages\u002Fpy\u002F` tree, the Python-side entries in `tests\u002Fparity\u002F`, and\nthe Python columns in `examples\u002F`. Existing root files are left alone.\n\n**Preview before writing:**\n\n```\n\u002Fployglot-project-scafford \u003Cyour-slug> --dry-run\n```\n\nPrints the source → target map for ~25 files and the resolved\nplaceholder values, without touching the disk.\n\n## See also\n\n- `references\u002Freference-structure.md` — field-by-field inventory of the\n  layout (what each file is for, why it exists).\n- `references\u002Ftemplates\u002FREADME.md` — the source → target-path map and\n  placeholder substitution rules.\n- Sibling skills: `sdk-paradigms` (canon for richer SDK shapes than a\n  pure library), `ployglot-agentmd-usages` (regenerates `.agent.md`\n  index after the surface evolves).\n","# Polyglot Project Scaffold (TS + Python twins)\n\nGenerate the canonical layout for a polyglot library that ships as two\nlanguage twins — TypeScript (`packages\u002Fts\u002F`) and Python (`packages\u002Fpy\u002F`) —\ngoverned by a single behavioral spec and proven by a shared cross-language\nparity fixture.\n\nThe shape is intentionally open-source-friendly: no internal organization\nscopes, no agent-runtime paths, no plan-tree dependencies. Every file\nwritten is something a downstream user can publish to npm + PyPI or fork\ninto their own repo.\n\n## When to use this skill\n\n- Starting a new library and you want it to have **TypeScript + Python**\n  surfaces from day one with parity enforced by tests, not vibes.\n- Porting a single-language library to a twin (e.g. you have the TS but\n  want the Python twin) and want the cross-language scaffolding —\n  `SPEC.md`, parity fixtures, `examples\u002F{sdk,api}\u002F`, root `Makefile` —\n  in place before the port.\n- Auditing or normalizing an existing two-language repo: comparing the\n  current state against `references\u002Freference-structure.md` and writing\n  the missing load-bearing files.\n\nSkip when:\n\n- The work needs more than two languages, or a non-library shape (CLI,\n  service, multi-package monorepo). Use a different skill for those.\n- The repo is already a polyglot SDK with full client\u002Ftransport\u002F\n  middleware\u002Fretry layering — that's the SDK paradigms canon, not a\n  library scaffold. Use `sdk-paradigms-scaffold` instead.\n- You have a feature\u002Fstory\u002Ftask plan tree and want plan-driven\n  implementation — use `implement-polyglot-project-plan` (sibling skill,\n  not part of this open-source pattern).\n\n## Reference structure\n\nThe canonical layout this skill produces:\n\n```\n\u003Crepo-root>\u002F\n├── README.md                       # repo intro + per-language quick start\n├── SPEC.md                         # canonical behavior — both ports MUST conform\n├── LICENSE                         # MIT (or user-supplied)\n├── Makefile                        # root orchestrator: ci, ci-ts, ci-py, clean\n├── package.json                    # npm workspace marker (workspaces: [\"packages\u002Fts\"])\n├── pyproject.toml                  # Python layout marker (no build, points at packages\u002Fpy)\n├── .gitignore                      # Node + Python + IDE\u002FOS + env ignores\n├── .agent.md                       # LLM entry reference (root index)\n├── .agent.json                     # machine-readable counterpart of .agent.md\n├── .agents\u002F\n│   └── parity.md                   # twin drift catalog + intentional asymmetries\n├── packages\u002F\n│   ├── ts\u002F\n│   │   ├── package.json            # the publishable npm package\n│   │   ├── tsconfig.json           # strict TS config\n│   │   ├── Makefile                # help\u002Finstall\u002Fci-install\u002Ftest\u002Flint\u002Fbuild\u002Fpack\u002Fclean\u002Fdistclean\u002Fci\n│   │   ├── .agent.md               # per-package LLM skill file\n│   │   ├── src\u002F\n│   │   │   └── index.ts            # public surface — re-exports only\n│   │   └── test\u002F\n│   │       ├── smoke.test.ts       # the package loads + exports the surface\n│   │       └── parity.test.ts      # consumes ..\u002F..\u002Ftests\u002Fparity\u002Ffixtures.json\n│   └── py\u002F\n│       ├── pyproject.toml          # the publishable PyPI package\n│       ├── Makefile                # uv-aware; falls back to pip+pytest on bare runners\n│       ├── README.md               # 1-line pointer to the TS twin\n│       ├── .agent.md               # per-package LLM skill file\n│       ├── \u003Csnake_pkg>\u002F\n│       │   ├── __init__.py         # public surface — re-exports only\n│       │   └── py.typed            # PEP 561 marker\n│       └── tests\u002F\n│           ├── __init__.py\n│           ├── _helpers.py         # env-isolation utilities for tests\n│           ├── test_smoke.py       # the package loads + exports the surface\n│           └── test_parity.py      # consumes ..\u002F..\u002Ftests\u002Fparity\u002Ffixtures.json\n├── tests\u002F\n│   └── parity\u002F\n│       └── fixtures.json           # shared cross-language behavior fixtures\n└── examples\u002F\n    ├── README.md\n    ├── sdk\u002F\n    │   ├── README.md               # programmatic embedding scenarios\n    │   └── 01-\u003Cscenario>.md        # side-by-side TS + Python code per scenario\n    └── api\u002F\n        ├── README.md               # per-function contract reference\n        └── 01-\u003Centry>.md           # signature, inputs, errors per entry\n```\n\nSee `references\u002Freference-structure.md` for the field-by-field inventory.\n\n## Placeholders\n\nTemplates use these placeholders. Resolve every one before writing:\n\n| Placeholder      | Meaning                                                | Example                       |\n| ---------------- | ------------------------------------------------------ | ----------------------------- |\n| `\u003Cslug>`         | Kebab-case package name (used for npm + PyPI names)    | `my-lib`                      |\n| `\u003Csnake_pkg>`    | Python module directory \u002F import name                  | `my_lib`                      |\n| `\u003Cscope>`        | Optional npm scope (drop for a flat name)              | `@your-org` or empty          |\n| `\u003Crepo-name>`    | Top-level repo folder name                             | `my-lib`                      |\n| `\u003Cauthor>`       | Author name in package metadata                        | `Jane Doe`                    |\n| `\u003Csubject>`      | One-phrase domain descriptor for README\u002FSPEC intros    | `concise tagline of behavior` |\n| `\u003Csurface-list>` | Comma-separated public symbols (used in `.agent.md`)   | `doThing, doOtherThing, ...`  |\n\nConventions:\n\n- `\u003Cslug>` and the npm name match directly. With a scope, the npm name is\n  `\u003Cscope>\u002F\u003Cslug>` (e.g. `@your-org\u002F\u003Cslug>`). Without a scope, both\n  npm and PyPI publish as `\u003Cslug>`.\n- `\u003Csnake_pkg>` is the Python import name — always derive it from `\u003Cslug>`\n  by replacing dashes with underscores.\n- The user can freely change these post-scaffold; this skill picks\n  defaults so the repo boots immediately.\n\n## Workflow\n\n### Step 1 — Resolve scaffold parameters\n\n1. Accept `$ARGUMENTS` of the form `\u003Cslug> [--scope @your-org] [--ts-only|--py-only|--both] [--dry-run]`.\n2. If `\u003Cslug>` is missing, ask via `AskUserQuestion`. Validate it is\n   kebab-case (`^[a-z][a-z0-9-]*$`); reject otherwise with a clear\n   error.\n3. Derive `\u003Csnake_pkg>` from `\u003Cslug>` (`s\u002F-\u002F_\u002Fg`).\n4. Resolve `\u003Cscope>`: explicit `--scope` flag wins; otherwise leave\n   empty (publishes as flat `\u003Cslug>`).\n5. Default to `--both` packages. Honor `--ts-only` \u002F `--py-only` to\n   skip the other tree.\n6. Confirm with the user before writing: print the resolved\n   placeholders + the file list this run will write.\n\n### Step 2 — Inspect the working directory\n\n1. Run `Glob` on the cwd. If the directory is empty (or contains only\n   `.git\u002F`, `LICENSE`, `README.md`), proceed to a fresh scaffold.\n2. If `packages\u002Fts\u002F` or `packages\u002Fpy\u002F` already exist, do **not** overwrite.\n   Walk the layout in `references\u002Freference-structure.md` and report\n   missing files — write **only** the missing ones, leaving existing\n   files untouched.\n3. If the repo is clearly not a polyglot library candidate (has its own\n   `src\u002F`, monorepo manifest, foreign workspace shape), stop and ask.\n\n### Step 3 — Write root files\n\nIn this order, from `references\u002Ftemplates\u002F`:\n\n1. `root-README.md` → `README.md`\n2. `root-SPEC.md` → `SPEC.md` (intentionally a stub — the user fills the\n   behavior; the structure is what this skill provides)\n3. `root-LICENSE` → `LICENSE` (skip if already present)\n4. `root-Makefile` → `Makefile`\n5. `root-package.json` → `package.json`\n6. `root-pyproject.toml` → `pyproject.toml`\n7. `root-gitignore` → `.gitignore`\n8. `root-agent.md` → `.agent.md`\n9. `root-agent.json` → `.agent.json`\n10. `root-agents-parity.md` → `.agents\u002Fparity.md`\n\nIf `--ts-only`, the root `package.json` is still written (it's the\nworkspace marker). If `--py-only`, write a minimal `package.json` with\nempty `workspaces` so the root remains valid; the user can drop it\nlater.\n\n### Step 4 — Write per-package files\n\nFor TypeScript (when `--both` or `--ts-only`):\n\n| Source                                     | Target                                  |\n| ------------------------------------------ | --------------------------------------- |\n| `packages-ts\u002Fpackage.json`                 | `packages\u002Fts\u002Fpackage.json`              |\n| `packages-ts\u002Ftsconfig.json`                | `packages\u002Fts\u002Ftsconfig.json`             |\n| `packages-ts\u002FMakefile`                     | `packages\u002Fts\u002FMakefile`                  |\n| `packages-ts\u002Fagent.md`                     | `packages\u002Fts\u002F.agent.md`                 |\n| `packages-ts\u002Fsrc-index.ts`                 | `packages\u002Fts\u002Fsrc\u002Findex.ts`              |\n| `packages-ts\u002Ftest-smoke.test.ts`           | `packages\u002Fts\u002Ftest\u002Fsmoke.test.ts`        |\n| `packages-ts\u002Ftest-parity.test.ts`          | `packages\u002Fts\u002Ftest\u002Fparity.test.ts`       |\n\nFor Python (when `--both` or `--py-only`):\n\n| Source                                       | Target                                              |\n| -------------------------------------------- | --------------------------------------------------- |\n| `packages-py\u002Fpyproject.toml`                 | `packages\u002Fpy\u002Fpyproject.toml`                        |\n| `packages-py\u002FMakefile`                       | `packages\u002Fpy\u002FMakefile`                              |\n| `packages-py\u002FREADME.md`                      | `packages\u002Fpy\u002FREADME.md`                             |\n| `packages-py\u002Fagent.md`                       | `packages\u002Fpy\u002F.agent.md`                             |\n| `packages-py\u002Fsnake_pkg-__init__.py`          | `packages\u002Fpy\u002F\u003Csnake_pkg>\u002F__init__.py`               |\n| `packages-py\u002Fsnake_pkg-py.typed`             | `packages\u002Fpy\u002F\u003Csnake_pkg>\u002Fpy.typed` (empty file)     |\n| `packages-py\u002Ftests-__init__.py`              | `packages\u002Fpy\u002Ftests\u002F__init__.py` (empty file)        |\n| `packages-py\u002Ftests-_helpers.py`              | `packages\u002Fpy\u002Ftests\u002F_helpers.py`                     |\n| `packages-py\u002Ftests-test_smoke.py`            | `packages\u002Fpy\u002Ftests\u002Ftest_smoke.py`                   |\n| `packages-py\u002Ftests-test_parity.py`           | `packages\u002Fpy\u002Ftests\u002Ftest_parity.py`                  |\n\n### Step 5 — Write parity + examples scaffolding\n\n| Source                                       | Target                                  |\n| -------------------------------------------- | --------------------------------------- |\n| `tests-parity\u002Ffixtures.json`                 | `tests\u002Fparity\u002Ffixtures.json`            |\n| `examples\u002FREADME.md`                         | `examples\u002FREADME.md`                    |\n| `examples\u002Fsdk-README.md`                     | `examples\u002Fsdk\u002FREADME.md`                |\n| `examples\u002Fapi-README.md`                     | `examples\u002Fapi\u002FREADME.md`                |\n\nThe `examples\u002Fsdk\u002F01-\u003Cscenario>.md` and `examples\u002Fapi\u002F01-\u003Centry>.md`\nfiles are deliberately not auto-generated — they describe **specific\nbehavior** of the user's library, which this skill does not know.\nThe `examples\u002F{sdk,api}\u002FREADME.md` files include a \"How to add a new\nexample\" section the user follows.\n\n### Step 6 — Verify the scaffold boots\n\nAfter writing, run a smoke check:\n\n```bash\nmake ci-install\nmake ci\n```\n\nThe first run will fail at the parity test (the fixtures file is a\nstub) and may fail at the smoke test (the public surface is empty).\nThat is expected — the skill produces a structurally complete repo,\nnot a behaviorally complete one. Report the failure clearly so the\nuser knows what to fill in next:\n\n1. Edit `SPEC.md` to define the behavior contract.\n2. Implement the public surface in `packages\u002Fts\u002Fsrc\u002Findex.ts` and\n   `packages\u002Fpy\u002F\u003Csnake_pkg>\u002F__init__.py` (or sub-modules they\n   re-export).\n3. Replace the placeholder fixture in `tests\u002Fparity\u002Ffixtures.json`\n   with cases that exercise the surface in both languages.\n4. Add scenario files under `examples\u002Fsdk\u002F` and `examples\u002Fapi\u002F`.\n\n### Step 7 — Report\n\nEmit a short summary:\n\n- Resolved placeholders (`\u003Cslug>`, `\u003Csnake_pkg>`, `\u003Cscope>`).\n- Files written (count, grouped by tree).\n- Files skipped because they already existed.\n- Smoke result (`make ci-install` exit, `make ci` exit, with the\n  expected stub-failure note if applicable).\n- Next-step checklist (the four-step \"fill in\" list from Step 6).\n\n## Hard rules\n\n- **Never write organization-specific or host-machine-absolute paths\n  into a scaffolded file.** This skill is open-source. Use relative\n  paths and generic scope placeholders. Do not embed `\u002FUsers\u002F...`\n  paths anywhere in template output.\n- **Never overwrite an existing file** without confirming first. The\n  scaffold is additive — if `pyproject.toml` already exists, leave\n  it alone and report the skip.\n- **Never collapse the twin layout** even if the user only wants one\n  language today. Write the full root scaffold so the second twin can\n  be added later without restructuring.\n- **Never invent the SPEC.** The skill writes a `SPEC.md` stub that\n  documents the *structure* of a spec (function inventory table,\n  algorithm section, drift table). Concrete behavior is the user's\n  job — do not put fake behavior in there.\n- **Never skip parity-test wiring.** Even with empty fixtures, both\n  `parity.test.ts` and `test_parity.py` must be written so adding a\n  fixture entry later is the only required step to expand parity\n  coverage.\n- **Do not push, publish, tag, or open PRs** unless the user\n  explicitly asks.\n\n## Inputs and arguments\n\n- `$ARGUMENTS` shape: `\u003Cslug> [--scope @your-org] [--ts-only|--py-only|--both] [--dry-run]`\n- `--scope` — optional npm scope. Without it, the npm name is the bare\n  `\u003Cslug>`.\n- `--ts-only` \u002F `--py-only` — write only one language tree. Default\n  is both. The root scaffold (`Makefile`, `package.json`,\n  `pyproject.toml`, `SPEC.md`, etc.) is always written.\n- `--dry-run` — print the resolved placeholders and the source →\n  target file map without calling `Write`. Useful to confirm the\n  layout before committing to a scaffold.\n\n## Examples\n\nAll examples below use `\u003Cyour-slug>` as the placeholder for whatever\nkebab-case name the user picks. Substitute it in real invocations.\n\n**Bootstrap a fresh polyglot library, both languages, no scope:**\n\n```\n\u002Fployglot-project-scafford \u003Cyour-slug>\n```\n\nWrites the full layout. `package.json` declares the npm name as\n`\u003Cyour-slug>`. `pyproject.toml` declares the PyPI name as\n`\u003Cyour-slug>`. Python module derives by replacing dashes with\nunderscores.\n\n**Bootstrap with an npm scope:**\n\n```\n\u002Fployglot-project-scafford \u003Cyour-slug> --scope @your-org\n```\n\n`package.json` becomes `@your-org\u002F\u003Cyour-slug>`; PyPI name stays the\nunscoped `\u003Cyour-slug>` (PyPI has no scopes).\n\n**Add the Python twin to an existing TS-only repo:**\n\n```\n\u002Fployglot-project-scafford \u003Cyour-slug> --py-only\n```\n\nSkill detects the existing `packages\u002Fts\u002F` and only writes the\n`packages\u002Fpy\u002F` tree, the Python-side entries in `tests\u002Fparity\u002F`, and\nthe Python columns in `examples\u002F`. Existing root files are left alone.\n\n**Preview before writing:**\n\n```\n\u002Fployglot-project-scafford \u003Cyour-slug> --dry-run\n```\n\nPrints the source → target map for ~25 files and the resolved\nplaceholder values, without touching the disk.\n\n## See also\n\n- `references\u002Freference-structure.md` — field-by-field inventory of the\n  layout (what each file is for, why it exists).\n- `references\u002Ftemplates\u002FREADME.md` — the source → target-path map and\n  placeholder substitution rules.\n- Sibling skills: `sdk-paradigms` (canon for richer SDK shapes than a\n  pure library), `ployglot-agentmd-usages` (regenerates `.agent.md`\n  index after the surface evolves).\n",{"name":5,"tier":20,"description":7,"allowed-tools":44,"argument-hint":45,"disable-model-invocation":40},"Read, Write, Edit, Glob, Grep, Bash, AskUserQuestion","\u003Cslug> [--scope @your-org] [--ts-only|--py-only|--both] [--dry-run]","main","b78f8878258c912b66be9d4b56b316515e44c728",".claude\u002Fskills\u002Fproject-ployglot-project-scafford","https:\u002F\u002Fgithub.com\u002Fcarlosmarte\u002Fai-agent-artifacts","https:\u002F\u002Fgithub.com\u002Fcarlosmarte","http:\u002F\u002Fcarlosmarte.me\u002F","2026-08-25 00:53:46",{"source":8,"skillName":5,"commands":54,"prompt":64,"zipAvailable":65},[55,58,61],{"tool":56,"command":57},"npx","npx skills add carlosmarte\u002Fai-agent-artifacts --skill project-ployglot-project-scafford",{"tool":59,"command":60},"bunx","bunx skills add carlosmarte\u002Fai-agent-artifacts --skill project-ployglot-project-scafford",{"tool":62,"command":63},"pnpm","pnpm dlx skills add carlosmarte\u002Fai-agent-artifacts --skill project-ployglot-project-scafford","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fcarlosmarte\u002Fai-agent-artifacts\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fproject-ployglot-project-scafford\u002FSKILL.md",true,[67,73,77,81,85,89,93,97,101,107,110,113,117,121,125,129,133,137,141,145,149,153,157,161,165,169,173,177,181,185,189,193,197],{"path":68,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":71,"sourceHtmlUrl":72},"references\u002Freference-structure.md","REFERENCE","参考文档",10599,"https:\u002F\u002Fgithub.com\u002Fcarlosmarte\u002Fai-agent-artifacts\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fproject-ployglot-project-scafford\u002Freferences\u002Freference-structure.md",{"path":74,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":75,"sourceHtmlUrl":76},"references\u002Ftemplates\u002Fexamples\u002Fapi-README.md",1470,"https:\u002F\u002Fgithub.com\u002Fcarlosmarte\u002Fai-agent-artifacts\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fproject-ployglot-project-scafford\u002Freferences\u002Ftemplates\u002Fexamples\u002Fapi-README.md",{"path":78,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":79,"sourceHtmlUrl":80},"references\u002Ftemplates\u002Fexamples\u002FREADME.md",834,"https:\u002F\u002Fgithub.com\u002Fcarlosmarte\u002Fai-agent-artifacts\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fproject-ployglot-project-scafford\u002Freferences\u002Ftemplates\u002Fexamples\u002FREADME.md",{"path":82,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":83,"sourceHtmlUrl":84},"references\u002Ftemplates\u002Fexamples\u002Fsdk-README.md",1190,"https:\u002F\u002Fgithub.com\u002Fcarlosmarte\u002Fai-agent-artifacts\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fproject-ployglot-project-scafford\u002Freferences\u002Ftemplates\u002Fexamples\u002Fsdk-README.md",{"path":86,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":87,"sourceHtmlUrl":88},"references\u002Ftemplates\u002Fpackages-py\u002Fagent.md",1354,"https:\u002F\u002Fgithub.com\u002Fcarlosmarte\u002Fai-agent-artifacts\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fproject-ployglot-project-scafford\u002Freferences\u002Ftemplates\u002Fpackages-py\u002Fagent.md",{"path":90,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":91,"sourceHtmlUrl":92},"references\u002Ftemplates\u002Fpackages-py\u002FMakefile",3415,"https:\u002F\u002Fgithub.com\u002Fcarlosmarte\u002Fai-agent-artifacts\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fproject-ployglot-project-scafford\u002Freferences\u002Ftemplates\u002Fpackages-py\u002FMakefile",{"path":94,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":95,"sourceHtmlUrl":96},"references\u002Ftemplates\u002Fpackages-py\u002Fpyproject.toml",1104,"https:\u002F\u002Fgithub.com\u002Fcarlosmarte\u002Fai-agent-artifacts\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fproject-ployglot-project-scafford\u002Freferences\u002Ftemplates\u002Fpackages-py\u002Fpyproject.toml",{"path":98,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":99,"sourceHtmlUrl":100},"references\u002Ftemplates\u002Fpackages-py\u002FREADME.md",442,"https:\u002F\u002Fgithub.com\u002Fcarlosmarte\u002Fai-agent-artifacts\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fproject-ployglot-project-scafford\u002Freferences\u002Ftemplates\u002Fpackages-py\u002FREADME.md",{"path":102,"resourceType":103,"resourceTypeDesc":104,"sizeBytes":105,"sourceHtmlUrl":106},"references\u002Ftemplates\u002Fpackages-py\u002Fsnake_pkg-__init__.py","SCRIPT","脚本",312,"https:\u002F\u002Fgithub.com\u002Fcarlosmarte\u002Fai-agent-artifacts\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fproject-ployglot-project-scafford\u002Freferences\u002Ftemplates\u002Fpackages-py\u002Fsnake_pkg-__init__.py",{"path":108,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":14,"sourceHtmlUrl":109},"references\u002Ftemplates\u002Fpackages-py\u002Fsnake_pkg-py.typed","https:\u002F\u002Fgithub.com\u002Fcarlosmarte\u002Fai-agent-artifacts\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fproject-ployglot-project-scafford\u002Freferences\u002Ftemplates\u002Fpackages-py\u002Fsnake_pkg-py.typed",{"path":111,"resourceType":103,"resourceTypeDesc":104,"sizeBytes":14,"sourceHtmlUrl":112},"references\u002Ftemplates\u002Fpackages-py\u002Ftests-__init__.py","https:\u002F\u002Fgithub.com\u002Fcarlosmarte\u002Fai-agent-artifacts\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fproject-ployglot-project-scafford\u002Freferences\u002Ftemplates\u002Fpackages-py\u002Ftests-__init__.py",{"path":114,"resourceType":103,"resourceTypeDesc":104,"sizeBytes":115,"sourceHtmlUrl":116},"references\u002Ftemplates\u002Fpackages-py\u002Ftests-_helpers.py",802,"https:\u002F\u002Fgithub.com\u002Fcarlosmarte\u002Fai-agent-artifacts\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fproject-ployglot-project-scafford\u002Freferences\u002Ftemplates\u002Fpackages-py\u002Ftests-_helpers.py",{"path":118,"resourceType":103,"resourceTypeDesc":104,"sizeBytes":119,"sourceHtmlUrl":120},"references\u002Ftemplates\u002Fpackages-py\u002Ftests-test_parity.py",1576,"https:\u002F\u002Fgithub.com\u002Fcarlosmarte\u002Fai-agent-artifacts\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fproject-ployglot-project-scafford\u002Freferences\u002Ftemplates\u002Fpackages-py\u002Ftests-test_parity.py",{"path":122,"resourceType":103,"resourceTypeDesc":104,"sizeBytes":123,"sourceHtmlUrl":124},"references\u002Ftemplates\u002Fpackages-py\u002Ftests-test_smoke.py",484,"https:\u002F\u002Fgithub.com\u002Fcarlosmarte\u002Fai-agent-artifacts\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fproject-ployglot-project-scafford\u002Freferences\u002Ftemplates\u002Fpackages-py\u002Ftests-test_smoke.py",{"path":126,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":127,"sourceHtmlUrl":128},"references\u002Ftemplates\u002Fpackages-ts\u002Fagent.md",1278,"https:\u002F\u002Fgithub.com\u002Fcarlosmarte\u002Fai-agent-artifacts\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fproject-ployglot-project-scafford\u002Freferences\u002Ftemplates\u002Fpackages-ts\u002Fagent.md",{"path":130,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":131,"sourceHtmlUrl":132},"references\u002Ftemplates\u002Fpackages-ts\u002FMakefile",2701,"https:\u002F\u002Fgithub.com\u002Fcarlosmarte\u002Fai-agent-artifacts\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fproject-ployglot-project-scafford\u002Freferences\u002Ftemplates\u002Fpackages-ts\u002FMakefile",{"path":134,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":135,"sourceHtmlUrl":136},"references\u002Ftemplates\u002Fpackages-ts\u002Fpackage.json",760,"https:\u002F\u002Fgithub.com\u002Fcarlosmarte\u002Fai-agent-artifacts\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fproject-ployglot-project-scafford\u002Freferences\u002Ftemplates\u002Fpackages-ts\u002Fpackage.json",{"path":138,"resourceType":103,"resourceTypeDesc":104,"sizeBytes":139,"sourceHtmlUrl":140},"references\u002Ftemplates\u002Fpackages-ts\u002Fsrc-index.ts",304,"https:\u002F\u002Fgithub.com\u002Fcarlosmarte\u002Fai-agent-artifacts\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fproject-ployglot-project-scafford\u002Freferences\u002Ftemplates\u002Fpackages-ts\u002Fsrc-index.ts",{"path":142,"resourceType":103,"resourceTypeDesc":104,"sizeBytes":143,"sourceHtmlUrl":144},"references\u002Ftemplates\u002Fpackages-ts\u002Ftest-parity.test.ts",1943,"https:\u002F\u002Fgithub.com\u002Fcarlosmarte\u002Fai-agent-artifacts\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fproject-ployglot-project-scafford\u002Freferences\u002Ftemplates\u002Fpackages-ts\u002Ftest-parity.test.ts",{"path":146,"resourceType":103,"resourceTypeDesc":104,"sizeBytes":147,"sourceHtmlUrl":148},"references\u002Ftemplates\u002Fpackages-ts\u002Ftest-smoke.test.ts",547,"https:\u002F\u002Fgithub.com\u002Fcarlosmarte\u002Fai-agent-artifacts\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fproject-ployglot-project-scafford\u002Freferences\u002Ftemplates\u002Fpackages-ts\u002Ftest-smoke.test.ts",{"path":150,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":151,"sourceHtmlUrl":152},"references\u002Ftemplates\u002Fpackages-ts\u002Ftsconfig.json",571,"https:\u002F\u002Fgithub.com\u002Fcarlosmarte\u002Fai-agent-artifacts\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fproject-ployglot-project-scafford\u002Freferences\u002Ftemplates\u002Fpackages-ts\u002Ftsconfig.json",{"path":154,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":155,"sourceHtmlUrl":156},"references\u002Ftemplates\u002FREADME.md",5473,"https:\u002F\u002Fgithub.com\u002Fcarlosmarte\u002Fai-agent-artifacts\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fproject-ployglot-project-scafford\u002Freferences\u002Ftemplates\u002FREADME.md",{"path":158,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":159,"sourceHtmlUrl":160},"references\u002Ftemplates\u002Froot-agent.json",833,"https:\u002F\u002Fgithub.com\u002Fcarlosmarte\u002Fai-agent-artifacts\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fproject-ployglot-project-scafford\u002Freferences\u002Ftemplates\u002Froot-agent.json",{"path":162,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":163,"sourceHtmlUrl":164},"references\u002Ftemplates\u002Froot-agent.md",2122,"https:\u002F\u002Fgithub.com\u002Fcarlosmarte\u002Fai-agent-artifacts\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fproject-ployglot-project-scafford\u002Freferences\u002Ftemplates\u002Froot-agent.md",{"path":166,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":167,"sourceHtmlUrl":168},"references\u002Ftemplates\u002Froot-agents-parity.md",1565,"https:\u002F\u002Fgithub.com\u002Fcarlosmarte\u002Fai-agent-artifacts\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fproject-ployglot-project-scafford\u002Freferences\u002Ftemplates\u002Froot-agents-parity.md",{"path":170,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":171,"sourceHtmlUrl":172},"references\u002Ftemplates\u002Froot-gitignore",351,"https:\u002F\u002Fgithub.com\u002Fcarlosmarte\u002Fai-agent-artifacts\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fproject-ployglot-project-scafford\u002Freferences\u002Ftemplates\u002Froot-gitignore",{"path":174,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":175,"sourceHtmlUrl":176},"references\u002Ftemplates\u002Froot-LICENSE",1067,"https:\u002F\u002Fgithub.com\u002Fcarlosmarte\u002Fai-agent-artifacts\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fproject-ployglot-project-scafford\u002Freferences\u002Ftemplates\u002Froot-LICENSE",{"path":178,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":179,"sourceHtmlUrl":180},"references\u002Ftemplates\u002Froot-Makefile",1021,"https:\u002F\u002Fgithub.com\u002Fcarlosmarte\u002Fai-agent-artifacts\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fproject-ployglot-project-scafford\u002Freferences\u002Ftemplates\u002Froot-Makefile",{"path":182,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":183,"sourceHtmlUrl":184},"references\u002Ftemplates\u002Froot-package.json",325,"https:\u002F\u002Fgithub.com\u002Fcarlosmarte\u002Fai-agent-artifacts\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fproject-ployglot-project-scafford\u002Freferences\u002Ftemplates\u002Froot-package.json",{"path":186,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":187,"sourceHtmlUrl":188},"references\u002Ftemplates\u002Froot-pyproject.toml",334,"https:\u002F\u002Fgithub.com\u002Fcarlosmarte\u002Fai-agent-artifacts\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fproject-ployglot-project-scafford\u002Freferences\u002Ftemplates\u002Froot-pyproject.toml",{"path":190,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":191,"sourceHtmlUrl":192},"references\u002Ftemplates\u002Froot-README.md",1940,"https:\u002F\u002Fgithub.com\u002Fcarlosmarte\u002Fai-agent-artifacts\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fproject-ployglot-project-scafford\u002Freferences\u002Ftemplates\u002Froot-README.md",{"path":194,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":195,"sourceHtmlUrl":196},"references\u002Ftemplates\u002Froot-SPEC.md",2076,"https:\u002F\u002Fgithub.com\u002Fcarlosmarte\u002Fai-agent-artifacts\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fproject-ployglot-project-scafford\u002Freferences\u002Ftemplates\u002Froot-SPEC.md",{"path":198,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":199,"sourceHtmlUrl":200},"references\u002Ftemplates\u002Ftests-parity\u002Ffixtures.json",440,"https:\u002F\u002Fgithub.com\u002Fcarlosmarte\u002Fai-agent-artifacts\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fproject-ployglot-project-scafford\u002Freferences\u002Ftemplates\u002Ftests-parity\u002Ffixtures.json",[202,229,269,297,320,347],{"skillNo":203,"name":204,"nameZh":6,"description":205,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":206,"categories":207,"keywords":208,"publishedAt":39},"01M6NQ7MN7FKWQE3CKRWKVAC9K","validation_handoff","Forces the agent to conclude its response by generating a strict validation checklist and outlining pending actions, focusing heavily on defensive execution and edge-case testing.","https:\u002F\u002Fgithub.com\u002Fcarlosmarte\u002Fai-agent-artifacts\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fvalidation_handoff\u002FSKILL.md",[],[209,210,211,212,213,214,215,216,217,218,219,220,221,222,223,224,225,226,227,228],"handoff","validation","validation handoff","testing","architecture","edge","actions","refactor","execution","system","implementation","checklist","feature implementation","feature","end","case","defensive","hook","at","pending",{"skillNo":230,"name":231,"nameZh":6,"description":232,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":233,"categories":234,"keywords":251,"publishedAt":39},"01M6NQ6VJVPM37YA73T8BCD3VF","playwright-ui-locator","Auto-heal Playwright tests after a frontend developer changes a div's class, id, or other selector. Catches a failing Playwright test, captures the old vs new DOM tree, finds the element that drifted, derives the most stable replacement locator, and proposes the fix as a GitHub pull request (confident heals) or files a GitHub issue (ambiguous \u002F element-removed cases) — never editing the working tree directly. Trigger when Playwright tests fail with \"locator resolved to 0 elements\", \"Timeout waiting for selector\", or after a UI refactor \u002F class rename \u002F Tailwind cleanup broke previously-passing tests.","https:\u002F\u002Fgithub.com\u002Fcarlosmarte\u002Fai-agent-artifacts\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fplaywright-test-gh-auto-heal-ui-locator\u002FSKILL.md",[235,240,243,246],{"categoryNo":236,"categoryName":237,"taxonomyType":238,"taxonomyTypeDesc":239},"01JBSEEDCAT000000000000007","代码审查","SCENARIO","使用场景",{"categoryNo":241,"categoryName":242,"taxonomyType":238,"taxonomyTypeDesc":239},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":244,"categoryName":245,"taxonomyType":238,"taxonomyTypeDesc":239},"01JBSEEDCAT000000000000009","前端开发",{"categoryNo":247,"categoryName":248,"taxonomyType":249,"taxonomyTypeDesc":250},"01JBSEEDCAT000000000000032","设计师","PROFESSION","适用职业",[252,253,254,255,256,257,32,31,258,259,260,261,262,263,264,265,266,24,267,268],"playwright","ui","playwright ui locator","frontend","cleanup","Tailwind","write","edit","fix","snapshot","auto","never","issue","files","rename","element","request",{"skillNo":270,"name":271,"nameZh":6,"description":272,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":273,"categories":274,"keywords":278,"publishedAt":39},"01M6NQ6BCW05C6Y6VRV0RBQD1V","org-learn-context-window","Distill the current conversation into a reusable command or skill artifact. Use when the user wants to capture a workflow they just executed (create a reusable slash command) or formalize a resolution\u002Fmistake\u002Fcorrection into a reusable skill so the same class of issue never recurs.","https:\u002F\u002Fgithub.com\u002Fcarlosmarte\u002Fai-agent-artifacts\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Forg-learn-context-window\u002FSKILL.md",[275],{"categoryNo":276,"categoryName":277,"taxonomyType":238,"taxonomyTypeDesc":239},"01JBSEEDCAT000000000000023","Skill与智能体开发",[279,280,281,282,283,284,285,286,287,288,289,290,291,263,264,292,293,294,295,296],"learn","context","org","window","org learn context window","workflow","create","just","capture","distill","command","user","use","reusable","conversation","artifact","resolution","skill artifact",{"skillNo":298,"name":299,"nameZh":6,"description":300,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":301,"categories":302,"keywords":304,"publishedAt":39},"01M6NQ66NFPQM1PDBHP1B2G82X","org-agent-skill-creator","Scaffold and validate scope-aware agent skills (company, enterprise, org, team, project, application). Use when the user asks to create a new agent skill, generate a SKILL.md file, scaffold a skill directory, or validate that existing skill directories meet SKILL_SPEC.md (frontmatter, naming rules, structure, scope\u002Ftier).","https:\u002F\u002Fgithub.com\u002Fcarlosmarte\u002Fai-agent-artifacts\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Forg-agent-skill-creator\u002FSKILL.md",[303],{"categoryNo":276,"categoryName":277,"taxonomyType":238,"taxonomyTypeDesc":239},[305,306,281,307,308,309,285,310,311,312,313,291,314,315,20,23,316,317,318,319],"skill creator","agent skill","agent skill creator","creator","org agent skill creator","file","Enterprise","team","Rules","structure","new agent","directories","Existing","company","Meet",{"skillNo":321,"name":322,"nameZh":6,"description":323,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":324,"categories":325,"keywords":329,"publishedAt":39},"01M6NQ5VSH5M682YMYDF9H9KFE","app-workshop-session-pdf-recap-next","Extract content from a workshop session PDF and produce a structured recap focused on (1) what was learned, (2) next steps, and (3) possible enhancements. Ingests a single PDF file path, parses session material (slides, transcripts, exercises, Q&A), and emits a Markdown report with Learning Recap, Next Steps, and Enhancement Opportunities sections with page-level traceability. Use when the user asks to \"summarize a workshop\", \"recap a training PDF\", \"pull next steps from a session deck\", or provides a workshop\u002Fseminar\u002Ftutorial PDF and wants a learn-and-act summary.","https:\u002F\u002Fgithub.com\u002Fcarlosmarte\u002Fai-agent-artifacts\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fapp-workshop-session-pdf-recap-next\u002FSKILL.md",[326],{"categoryNo":327,"categoryName":328,"taxonomyType":238,"taxonomyTypeDesc":239},"01JBSEEDCAT000000000000002","文档处理",[330,331,332,333,334,335,336,279,337,338,339,340,341,342,291,343,24,344,345,346],"PDF","recap","session","next","app","app workshop session pdf recap next","training","pull","produce","learning","slides","page","tutorial","deck","material","traceability","next steps",{"skillNo":348,"name":349,"nameZh":6,"description":350,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":351,"categories":352,"keywords":354,"publishedAt":39},"01M6NQ5NFNK613NR7FM8HPAJ74","app-workshop-recaps-consolidate","Consolidate multiple workshop-session recap Markdown files (typically produced by the workshop-session-pdf-recap-next skill) into a single unified report. Merges and deduplicates learnings across sessions and emits six sections — Consolidated Recap, Follow-ups, Action Items, Next Steps, Possible Enhancements, and Industry \u002F External Viewpoint. The last section supplements the attendees' material with current external perspective via web research. Use when the user has a set of per-session recap files and wants one portfolio-level summary with an outside-in lens (\"consolidate these recaps\", \"merge my workshop notes\", \"cross-session summary\", \"roll up action items\").","https:\u002F\u002Fgithub.com\u002Fcarlosmarte\u002Fai-agent-artifacts\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fapp-workshop-recaps-consolidate\u002FSKILL.md",[353],{"categoryNo":327,"categoryName":328,"taxonomyType":238,"taxonomyTypeDesc":239},[355,334,356,330,357,358,32,359,331,360,361,265,362,333,363,24,364,346,365,366],"consolidate","app workshop recaps consolidate","notes","SET","markdown","portfolio","up","learnings","across","lens","follow-ups","websearch"]