[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7BK7KJDKZ3BNWNZ9GV5WZE8":3,"skill-same:01M7BK7KJDKZ3BNWNZ9GV5WZE8":53},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":29,"ownerHtmlUrl":30,"ownerBlogUrl":6,"ownerDescription":31,"updatedAt":32,"install":33,"resources":46},"01M7BK7KJDKZ3BNWNZ9GV5WZE8","setup-ts-deep-modules",null,"Wire dependency-cruiser into a TypeScript repo so each package is a deep module, with implementation hidden in subfolders and reachable only through its entry-point files. User-invoked.","fderuiter\u002Fagy-skills","fderuiter","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F127706008?v=4","01M6C40AWP9EPQBS3EG0RF5DRD","Frederick de Ruiter","01M7BK63K60DTR50H82SAHMYHK",1,"MIT","https:\u002F\u002Fgithub.com\u002Ffderuiter\u002Fagy-skills\u002Fblob\u002Fmain\u002Fskills\u002Fengineering\u002Fsetup-ts-deep-modules\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: setup-ts-deep-modules\ndescription: Wire dependency-cruiser into a TypeScript repo so each package is a deep module, with implementation hidden in subfolders and reachable only through its entry-point files. User-invoked.\n---\n\n# Setup TS Deep Modules\n\nMake every package in this repo a **deep module**: a lot of behaviour behind a small interface. A package's public surface is its **entry points** (the files at the package root), and everything in its subfolders is hidden. This skill installs [dependency-cruiser](https:\u002F\u002Fgithub.com\u002Fsverweij\u002Fdependency-cruiser) and the rules that make the entry points the only way in, then proves the rules bite.\n\nFor the vocabulary (deep module, interface, seam, depth), call the Skill tool with \"codebase-design\" and use its language throughout.\n\n## The shape this enforces\n\n```\nsrc\u002Fpackages\u002F\n  \u003Cname>\u002F\n    index.ts        ← an entry point (public). Import this from outside.\n    client.ts       ← another entry point. Packages may expose SEVERAL.\n    lib\u002F            ← implementation: hidden from outside, free to import each other.\n    tests\u002F          ← co-located tests + fixtures (a subfolder, so private).\n```\n\nThe public surface is the package's **root files**, not one designated `index.ts`. By convention implementation lives in `lib\u002F` and tests in `tests\u002F`, giving every package the same two-folder shape. The rule itself is general, though: *anything* in *any* subfolder is private, so you never extend the config to add a folder.\n\nFive rules, all `error`:\n\n1. **Entry-point boundary from app**: code outside a package (app code or root code) may import only that package's entry points (its root files), never anything in its subfolders.\n2. **Entry-point boundary across packages**: a package's own files import each other freely, but may reach other packages only through their entry points, never their subfolder internals.\n3. **Tests through the entry points**: files under `\u003Cpkg>\u002Ftests\u002F` may import any package's entry points and their own `tests\u002F` fixtures, but never any package's subfolder internals (not even their own). Integration tests across packages are fine; deep imports are not.\n4. **Tests folder is private**: files under `\u003Cpkg>\u002Ftests\u002F` are reachable only from test files; application code may not import test fixtures.\n5. **No cycles**: no dependency cycles.\n\n**Entry points, not a barrel.** Because the public surface is *every* root file, a package can expose several small entry points (`index.ts`, `client.ts`, `server.ts`) instead of funnelling everything through one giant `index.ts`. Barrel files that re-export a whole subtree are discouraged; keep entry points small and hide implementation in subfolders.\n\nLayering (which packages may depend on which) is a *different* concern and is left as a commented stub in the config for this repo to fill in.\n\n## Steps\n\n### 1. Detect the environment\n\n- **Package manager**: `pnpm-lock.yaml` → pnpm, `yarn.lock` → yarn, `bun.lockb` → bun, else npm. Use it for every command below (`pnpm`\u002F`yarn`\u002F`npm run`\u002F`bunx`).\n- **TypeScript and module setup**:\n  - Check `package.json` for `\"type\": \"module\"` (ESM).\n  - Inspect `tsconfig.json` (or root solution \u002F base tsconfig) for `moduleResolution` (`NodeNext`, `Node16`, `Bundler`, `Node`) and path mappings (`compilerOptions.paths`).\n  - Check if project references (`references: [...]`) or monorepo workspaces are used.\n- **Packages root**: if `src\u002Fpackages` exists use `src\u002Fpackages`, else `packages` or `src\u002F`. Confirm the choice with the user if the repo already has a different obvious convention.\n- **Existing config**: check for a `.dependency-cruiser.*` file. If one exists, do **not** overwrite it: merge the five rules and resolver options in, and tell the user what you added.\n- **Upstream verification**: When encountering non-standard bundler plugins, path aliases, or experimental TypeScript options, use `search_web` and `read_url_content` to inspect upstream `dependency-cruiser` documentation and release notes for the exact `enhancedResolveOptions` syntax.\n\n**Done when:** package manager, TypeScript module setup, packages root, and existing-config status are all known.\n\n### 2. Install dependency-cruiser\n\nInstall `dependency-cruiser` as a devDependency with the detected package manager.\n\n**Done when:** `dependency-cruiser` is in `devDependencies`.\n\n### 3. Write the config\n\nCopy [`dependency-cruiser.config.cjs`](.\u002Fdependency-cruiser.config.cjs) to the repo root as `.dependency-cruiser.cjs`.\n\n- Set `PACKAGES_ROOT` to the root detected in step 1.\n- Set `options.tsConfig.fileName` to point to the repo's `tsconfig.json` (or the root solution config that resolves path aliases and references).\n- Ensure `options.enhancedResolveOptions` includes modern TypeScript extensions (`.ts`, `.tsx`, `.d.ts`, `.js`, `.jsx`, `.mjs`, `.cjs`, `.json`) and export conditions (`exportsFields: [\"exports\"]`, `conditionNames: [\"import\", \"require\", \"node\", \"default\", \"types\"]`).\n\nThe rules are path-depth based and extension-agnostic, so nothing else needs adapting.\n\n**Done when:** `.dependency-cruiser.cjs` exists with the correct `PACKAGES_ROOT`, resolver options, and the five forbidden rules.\n\n### 4. Wire it into the checks\n\n- Add a `lint:boundaries` script in `package.json`: `depcruise \u003Cpackages-root>` (or `depcruise src`).\n- Fold it into the repo's umbrella check command, the one that already runs typecheck (e.g. a `check` \u002F `ci` \u002F `validate` script). Do **not** touch `tsconfig` or add path aliases solely for boundary linting.\n- If there is no umbrella script, add `lint:boundaries` and tell the user to include it in CI.\n\n**Done when:** `lint:boundaries` exists and runs as part of the same command as typecheck.\n\n### 5. Scaffold the example package\n\nCreate a committed `\u003Cpackages-root>\u002Fexample\u002F` as a copy-me template:\n\n- `index.ts` is an entry point. Export one function that delegates to an internal file (so the package is visibly *deep*, not a pass-through). If using NodeNext ESM resolution, use explicit relative extensions (such as `.\u002Flib\u002Fimpl.js`).\n- `lib\u002Fimpl.ts`: an internal file in a **subfolder**, imported by `index.ts`, not reachable from outside.\n- `tests\u002Fexample.test.ts` imports **only** `..\u002Findex` (or `..\u002Findex.js` under NodeNext) and asserts against the public function.\n\nTell the user this is a starter template to copy or delete.\n\n**Done when:** the example package exists, exposes its behaviour through a root entry point, and hides `impl` in a subfolder.\n\n### 6. Prove the rules bite\n\nThis is the completion criterion for the whole skill: a config that doesn't fail on a violation is worthless.\n\n1. Run `lint:boundaries`. It must **pass** on the clean example.\n2. Temporarily add a deep import to `tests\u002Fexample.test.ts` (e.g. `import { thing } from \"..\u002Flib\u002Fimpl\"` or `..\u002Flib\u002Fimpl.js`). Run `lint:boundaries` again; it must **fail** with `tests-through-entrypoints`.\n3. Revert the deep import. Run once more, and it must **pass**.\n\n**Done when:** you have observed a pass, then a fail on the deep import, then a pass again. If step 2 does not fail, the rules are not wired correctly, so fix before finishing.\n\n### 7. Document the convention\n\nWrite a `README.md` **in the packages folder** (`\u003Cpackages-root>\u002FREADME.md`, next to the packages it governs) covering: the `src\u002Fpackages\u002F\u003Cname>\u002F` layout (entry points at the root, `lib\u002F` for implementation, `tests\u002F` for tests), \"import only through a package's entry points (its root files)\", and how to run `lint:boundaries`. **Discourage barrel files** explicitly: expose several small entry points instead of re-exporting a whole subtree through one index. Keep it to the copy-me snippet plus the rules in one paragraph each.\n\nThen add a **context pointer** to it from the repo's agent-instructions file (`AGENTS.md` if present, else `CLAUDE.md`, creating `AGENTS.md` if neither exists). One line is enough, e.g. `Packages are deep modules: see [src\u002Fpackages\u002FREADME.md](.\u002Fsrc\u002Fpackages\u002FREADME.md) before adding or importing one.` This is what makes an agent discover the boundary rule instead of tripping over it.\n\n**Done when:** `\u003Cpackages-root>\u002FREADME.md` exists and discourages barrels, and the repo's `AGENTS.md`\u002F`CLAUDE.md` links to it.\n\n## Notes\n\n- The config's `$1` back-references (dependency-cruiser's group matching) are what let a package reach its own internals while outsiders cannot. Do not flatten them into separate per-package rules.\n- Public vs private is decided by **depth**: a package's root files are entry points; anything in a subfolder is private. The conventional subfolders are `lib\u002F` (implementation) and `tests\u002F`, but the rule does not hardcode them: any subfolder is private, so a new folder never needs a config change. Adding an entry point is just adding a root file (no barrel).\n- Packages are **flat**: one tier of immediate children under the root. A package's internals may nest as deep as you like; a package may not contain another package.\n- Use `.cjs` (not `.js`) so the config's `module.exports` works even in `\"type\": \"module\"` repos.\n- In TypeScript ESM projects using `NodeNext` or `Node16`, source code imports write `.js` extensions while files on disk are `.ts`. Dependency-cruiser resolves these specifiers to the underlying TypeScript files via `tsConfig` and `enhancedResolveOptions`.\n","# Setup TS Deep Modules\n\nMake every package in this repo a **deep module**: a lot of behaviour behind a small interface. A package's public surface is its **entry points** (the files at the package root), and everything in its subfolders is hidden. This skill installs [dependency-cruiser](https:\u002F\u002Fgithub.com\u002Fsverweij\u002Fdependency-cruiser) and the rules that make the entry points the only way in, then proves the rules bite.\n\nFor the vocabulary (deep module, interface, seam, depth), call the Skill tool with \"codebase-design\" and use its language throughout.\n\n## The shape this enforces\n\n```\nsrc\u002Fpackages\u002F\n  \u003Cname>\u002F\n    index.ts        ← an entry point (public). Import this from outside.\n    client.ts       ← another entry point. Packages may expose SEVERAL.\n    lib\u002F            ← implementation: hidden from outside, free to import each other.\n    tests\u002F          ← co-located tests + fixtures (a subfolder, so private).\n```\n\nThe public surface is the package's **root files**, not one designated `index.ts`. By convention implementation lives in `lib\u002F` and tests in `tests\u002F`, giving every package the same two-folder shape. The rule itself is general, though: *anything* in *any* subfolder is private, so you never extend the config to add a folder.\n\nFive rules, all `error`:\n\n1. **Entry-point boundary from app**: code outside a package (app code or root code) may import only that package's entry points (its root files), never anything in its subfolders.\n2. **Entry-point boundary across packages**: a package's own files import each other freely, but may reach other packages only through their entry points, never their subfolder internals.\n3. **Tests through the entry points**: files under `\u003Cpkg>\u002Ftests\u002F` may import any package's entry points and their own `tests\u002F` fixtures, but never any package's subfolder internals (not even their own). Integration tests across packages are fine; deep imports are not.\n4. **Tests folder is private**: files under `\u003Cpkg>\u002Ftests\u002F` are reachable only from test files; application code may not import test fixtures.\n5. **No cycles**: no dependency cycles.\n\n**Entry points, not a barrel.** Because the public surface is *every* root file, a package can expose several small entry points (`index.ts`, `client.ts`, `server.ts`) instead of funnelling everything through one giant `index.ts`. Barrel files that re-export a whole subtree are discouraged; keep entry points small and hide implementation in subfolders.\n\nLayering (which packages may depend on which) is a *different* concern and is left as a commented stub in the config for this repo to fill in.\n\n## Steps\n\n### 1. Detect the environment\n\n- **Package manager**: `pnpm-lock.yaml` → pnpm, `yarn.lock` → yarn, `bun.lockb` → bun, else npm. Use it for every command below (`pnpm`\u002F`yarn`\u002F`npm run`\u002F`bunx`).\n- **TypeScript and module setup**:\n  - Check `package.json` for `\"type\": \"module\"` (ESM).\n  - Inspect `tsconfig.json` (or root solution \u002F base tsconfig) for `moduleResolution` (`NodeNext`, `Node16`, `Bundler`, `Node`) and path mappings (`compilerOptions.paths`).\n  - Check if project references (`references: [...]`) or monorepo workspaces are used.\n- **Packages root**: if `src\u002Fpackages` exists use `src\u002Fpackages`, else `packages` or `src\u002F`. Confirm the choice with the user if the repo already has a different obvious convention.\n- **Existing config**: check for a `.dependency-cruiser.*` file. If one exists, do **not** overwrite it: merge the five rules and resolver options in, and tell the user what you added.\n- **Upstream verification**: When encountering non-standard bundler plugins, path aliases, or experimental TypeScript options, use `search_web` and `read_url_content` to inspect upstream `dependency-cruiser` documentation and release notes for the exact `enhancedResolveOptions` syntax.\n\n**Done when:** package manager, TypeScript module setup, packages root, and existing-config status are all known.\n\n### 2. Install dependency-cruiser\n\nInstall `dependency-cruiser` as a devDependency with the detected package manager.\n\n**Done when:** `dependency-cruiser` is in `devDependencies`.\n\n### 3. Write the config\n\nCopy [`dependency-cruiser.config.cjs`](.\u002Fdependency-cruiser.config.cjs) to the repo root as `.dependency-cruiser.cjs`.\n\n- Set `PACKAGES_ROOT` to the root detected in step 1.\n- Set `options.tsConfig.fileName` to point to the repo's `tsconfig.json` (or the root solution config that resolves path aliases and references).\n- Ensure `options.enhancedResolveOptions` includes modern TypeScript extensions (`.ts`, `.tsx`, `.d.ts`, `.js`, `.jsx`, `.mjs`, `.cjs`, `.json`) and export conditions (`exportsFields: [\"exports\"]`, `conditionNames: [\"import\", \"require\", \"node\", \"default\", \"types\"]`).\n\nThe rules are path-depth based and extension-agnostic, so nothing else needs adapting.\n\n**Done when:** `.dependency-cruiser.cjs` exists with the correct `PACKAGES_ROOT`, resolver options, and the five forbidden rules.\n\n### 4. Wire it into the checks\n\n- Add a `lint:boundaries` script in `package.json`: `depcruise \u003Cpackages-root>` (or `depcruise src`).\n- Fold it into the repo's umbrella check command, the one that already runs typecheck (e.g. a `check` \u002F `ci` \u002F `validate` script). Do **not** touch `tsconfig` or add path aliases solely for boundary linting.\n- If there is no umbrella script, add `lint:boundaries` and tell the user to include it in CI.\n\n**Done when:** `lint:boundaries` exists and runs as part of the same command as typecheck.\n\n### 5. Scaffold the example package\n\nCreate a committed `\u003Cpackages-root>\u002Fexample\u002F` as a copy-me template:\n\n- `index.ts` is an entry point. Export one function that delegates to an internal file (so the package is visibly *deep*, not a pass-through). If using NodeNext ESM resolution, use explicit relative extensions (such as `.\u002Flib\u002Fimpl.js`).\n- `lib\u002Fimpl.ts`: an internal file in a **subfolder**, imported by `index.ts`, not reachable from outside.\n- `tests\u002Fexample.test.ts` imports **only** `..\u002Findex` (or `..\u002Findex.js` under NodeNext) and asserts against the public function.\n\nTell the user this is a starter template to copy or delete.\n\n**Done when:** the example package exists, exposes its behaviour through a root entry point, and hides `impl` in a subfolder.\n\n### 6. Prove the rules bite\n\nThis is the completion criterion for the whole skill: a config that doesn't fail on a violation is worthless.\n\n1. Run `lint:boundaries`. It must **pass** on the clean example.\n2. Temporarily add a deep import to `tests\u002Fexample.test.ts` (e.g. `import { thing } from \"..\u002Flib\u002Fimpl\"` or `..\u002Flib\u002Fimpl.js`). Run `lint:boundaries` again; it must **fail** with `tests-through-entrypoints`.\n3. Revert the deep import. Run once more, and it must **pass**.\n\n**Done when:** you have observed a pass, then a fail on the deep import, then a pass again. If step 2 does not fail, the rules are not wired correctly, so fix before finishing.\n\n### 7. Document the convention\n\nWrite a `README.md` **in the packages folder** (`\u003Cpackages-root>\u002FREADME.md`, next to the packages it governs) covering: the `src\u002Fpackages\u002F\u003Cname>\u002F` layout (entry points at the root, `lib\u002F` for implementation, `tests\u002F` for tests), \"import only through a package's entry points (its root files)\", and how to run `lint:boundaries`. **Discourage barrel files** explicitly: expose several small entry points instead of re-exporting a whole subtree through one index. Keep it to the copy-me snippet plus the rules in one paragraph each.\n\nThen add a **context pointer** to it from the repo's agent-instructions file (`AGENTS.md` if present, else `CLAUDE.md`, creating `AGENTS.md` if neither exists). One line is enough, e.g. `Packages are deep modules: see [src\u002Fpackages\u002FREADME.md](.\u002Fsrc\u002Fpackages\u002FREADME.md) before adding or importing one.` This is what makes an agent discover the boundary rule instead of tripping over it.\n\n**Done when:** `\u003Cpackages-root>\u002FREADME.md` exists and discourages barrels, and the repo's `AGENTS.md`\u002F`CLAUDE.md` links to it.\n\n## Notes\n\n- The config's `$1` back-references (dependency-cruiser's group matching) are what let a package reach its own internals while outsiders cannot. Do not flatten them into separate per-package rules.\n- Public vs private is decided by **depth**: a package's root files are entry points; anything in a subfolder is private. The conventional subfolders are `lib\u002F` (implementation) and `tests\u002F`, but the rule does not hardcode them: any subfolder is private, so a new folder never needs a config change. Adding an entry point is just adding a root file (no barrel).\n- Packages are **flat**: one tier of immediate children under the root. A package's internals may nest as deep as you like; a package may not contain another package.\n- Use `.cjs` (not `.js`) so the config's `module.exports` works even in `\"type\": \"module\"` repos.\n- In TypeScript ESM projects using `NodeNext` or `Node16`, source code imports write `.js` extensions while files on disk are `.ts`. Dependency-cruiser resolves these specifiers to the underlying TypeScript files via `tsConfig` and `enhancedResolveOptions`.\n",{"name":5,"description":7},"main","97b7a56459bd17362bf4f075d60d92c1ae6cce33","skills\u002Fengineering\u002Fsetup-ts-deep-modules",0,"https:\u002F\u002Fgithub.com\u002Ffderuiter\u002Fagy-skills","https:\u002F\u002Ffderuiter.github.io\u002Fagy-skills\u002F","https:\u002F\u002Fgithub.com\u002Ffderuiter","Clinical Data Specialist at @Bright-Research \r\n\r\nInterests in Photogrammetry, Data Analytics + Pipelines, Mathematics, and AI\u002FML.\r\n\r\nPython, Rust, TS.","2026-08-29 02:26:25",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add fderuiter\u002Fagy-skills --skill setup-ts-deep-modules",{"tool":39,"command":40},"bunx","bunx skills add fderuiter\u002Fagy-skills --skill setup-ts-deep-modules",{"tool":42,"command":43},"pnpm","pnpm dlx skills add fderuiter\u002Fagy-skills --skill setup-ts-deep-modules","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Ffderuiter\u002Fagy-skills\u002Fblob\u002Fmain\u002Fskills\u002Fengineering\u002Fsetup-ts-deep-modules\u002FSKILL.md",true,[47],{"path":48,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":51,"sourceHtmlUrl":52},"dependency-cruiser.config.cjs","SCRIPT","脚本",3765,"https:\u002F\u002Fgithub.com\u002Ffderuiter\u002Fagy-skills\u002Fblob\u002Fmain\u002Fskills\u002Fengineering\u002Fsetup-ts-deep-modules\u002Fdependency-cruiser.config.cjs",[54,61,68,75,82,89],{"skillNo":55,"name":56,"nameZh":6,"description":57,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":58,"categories":59,"keywords":60,"publishedAt":19},"01M7BK91P025C72NSC9NZTS4JF","writing-shape","Shape raw material into an article paragraph by paragraph, arguing format choices along the way.","https:\u002F\u002Fgithub.com\u002Ffderuiter\u002Fagy-skills\u002Fblob\u002Fmain\u002Fskills\u002Fproductivity\u002Fwriting-shape\u002FSKILL.md",[],[],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":19},"01M7BK908F7QPQST3FKHAAVE87","writing-fragments","Mine raw writing fragments with no structure yet, capturing ideas into a single quarry file.","https:\u002F\u002Fgithub.com\u002Ffderuiter\u002Fagy-skills\u002Fblob\u002Fmain\u002Fskills\u002Fproductivity\u002Fwriting-fragments\u002FSKILL.md",[],[],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":19},"01M7BK8YJEBD31HR3GTYATQ6ZA","writing-for-agents","Writing documents for agents. Use when creating or editing skills, or modifying AGENTS.md or CLAUDE.md.","https:\u002F\u002Fgithub.com\u002Ffderuiter\u002Fagy-skills\u002Fblob\u002Fmain\u002Fskills\u002Fproductivity\u002Fwriting-for-agents\u002FSKILL.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":19},"01M7BK8WWERTYDTVVE95VMKZ2J","writing-beats","Assemble raw material into a narrative journey of beats, grounding concepts before leaning on them.","https:\u002F\u002Fgithub.com\u002Ffderuiter\u002Fagy-skills\u002Fblob\u002Fmain\u002Fskills\u002Fproductivity\u002Fwriting-beats\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":19},"01M7BK8VT41ZSQVB6TFM2KZRBZ","wait-what","Stop. That last message did not land: re-pitch it.","https:\u002F\u002Fgithub.com\u002Ffderuiter\u002Fagy-skills\u002Fblob\u002Fmain\u002Fskills\u002Fproductivity\u002Fwait-what\u002FSKILL.md",[],[],{"skillNo":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":93,"categories":94,"keywords":95,"publishedAt":19},"01M7BK8T2V1J99DXH22Q304T4S","to-questionnaire","Turn a decision you can't fully answer into a questionnaire for someone else to fill in.","https:\u002F\u002Fgithub.com\u002Ffderuiter\u002Fagy-skills\u002Fblob\u002Fmain\u002Fskills\u002Fproductivity\u002Fto-questionnaire\u002FSKILL.md",[],[]]