Create Saleor Package
saleor/apps
Scaffold a new shared package in the saleor-apps monorepo under ./packages/.
Scaffold a new workspace package in the c15t monorepo. An agent skill from c15t/c15t.
Install Creating A Package
$ npx skills add c15t/c15t --skill creating-a-package -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install c15t/c15t creating-a-package --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/c15t/c15t.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/creating-a-package .claude/skills/creating-a-package && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "creating-a-package" agent skill from https://github.com/c15t/c15t/tree/canary/.agents/skills/creating-a-package into .claude/skills/creating-a-package/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "creating-a-package", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/c15t/c15t/tree/canary/.agents/skills/creating-a-packageType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add c15t/c15t --skill creating-a-package -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install c15t/c15t creating-a-package --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/c15t/c15t.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/creating-a-package .agents/skills/creating-a-package && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "creating-a-package" agent skill from https://github.com/c15t/c15t/tree/canary/.agents/skills/creating-a-package into .agents/skills/creating-a-package/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "creating-a-package", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add c15t/c15t --skill creating-a-package -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install c15t/c15t creating-a-package --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/c15t/c15t.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/creating-a-package .cursor/skills/creating-a-package && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "creating-a-package" agent skill from https://github.com/c15t/c15t/tree/canary/.agents/skills/creating-a-package into .cursor/skills/creating-a-package/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "creating-a-package", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/c15t/c15t.git --path .agents/skills/creating-a-package--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add c15t/c15t --skill creating-a-package -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install c15t/c15t creating-a-package --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/c15t/c15t.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/creating-a-package .gemini/skills/creating-a-package && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "creating-a-package" agent skill from https://github.com/c15t/c15t/tree/canary/.agents/skills/creating-a-package into .gemini/skills/creating-a-package/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "creating-a-package", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install c15t/c15t creating-a-packageInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add c15t/c15t --skill creating-a-package -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/c15t/c15t.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/creating-a-package .github/skills/creating-a-package && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "creating-a-package" agent skill from https://github.com/c15t/c15t/tree/canary/.agents/skills/creating-a-package into .github/skills/creating-a-package/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "creating-a-package", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add c15t/c15t --skill creating-a-package -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install c15t/c15t creating-a-package --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/c15t/c15t.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/creating-a-package .opencode/skills/creating-a-package && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "creating-a-package" agent skill from https://github.com/c15t/c15t/tree/canary/.agents/skills/creating-a-package into .opencode/skills/creating-a-package/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "creating-a-package", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
creating-a-package- GitHub stars
- 1.9k
- Token cost
- ~913 tokens
- SKILL.md length
- 366 words
- Files
- 1
- Skills in repo
- 8
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Scaffold a new workspace package in the c15t monorepo. An agent skill from c15t/c15t.
- Works in 10 steps: Directory: packages/ (auto-included by… → package.json — match the house shape → rslib.config.ts: ESM + CJS,… → …
- Adding a package under packages/
- SKILL.md covers Checklist and Verify
- Calls bun, tsc and vitest
What it does
Creating A Package is an agent skill from c15t/c15t. Scaffold a new workspace package in the c15t monorepo. Use when adding a package under packages/, wiring up rslib builds, vitest, turbo, exports maps, or deciding whether a package joins the linked changeset group.
Its SKILL.md is about 910 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Testing & QA, covering Unit testing and Monorepo tooling. It works with Vitest and TypeScript. The repository describes itself as: The Developer-First Cookie Banner. The licence is Apache-2.0.
When your agent uses it
- Adding a package under packages/
- Wiring up rslib builds
- Deciding whether a package joins the linked changeset group
Example prompts
- “/creating-a-package”
Workflow steps
10 steps, taken from the first numbered list in SKILL.md.
- Directory: packages/ (auto-included by the root workspaces globs). Kebab-case file names throughout — Biome errors otherwise.
- package.json — match the house shape
- rslib.config.ts: ESM + CJS, dts.distPath: './dist-types' on the ESM lib only, source.exclude for test globs, getRsdoctorPlugins() from…
- tsconfig.json: extend @c15t/typescript-config/base.json (or next.json/node.json). Don't relax strictness.
- vitest.config.ts: extend @c15t/vitest-config base config; add the package to root vitest.workspace.ts if it should run in the workspace…
- turbo.json: the generic build/test/lint tasks cover most packages. Add a package-specific entry only if outputs differ (e.g. bundled docs…
- Changesets: decide whether it joins the linked group in .changeset/config.json (core SDK packages that must version together) or versions…
- README: user-facing published packages get a generated README.md — create readme.json (see packages/react/readme.json) and run bun run…
- Bundled docs (only for user-facing SDK packages): add a config entry in scripts/generate-package-docs.ts and include "AGENTS.md", "docs"…
- knip.json: add one if the package has intentional unused-export patterns; run bun run knip to check.
What it can do on your machine
Read from SKILL.md and the folder at commit f2b2318. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
buntscvitest
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Creating A Package loads about 913 tokens when it runs. Until then it costs about 58 tokens; SKILL.md has 366 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from c15t/c15t at commit f2b2318, republished under its Apache-2.0 licence (© c15t). 366 words, ~913 tokens.
Download SKILL.mdSave it as
.claude/skills/creating-a-package/SKILL.md (or your agent's skills folder).- name
- creating-a-package
- description
- Scaffold a new workspace package in the c15t monorepo. Use when adding a package under packages/, wiring up rslib builds, vitest, turbo, exports maps, or deciding whether a package joins the linked changeset group.
Creating a c15t Package
Copy the shape of an existing package rather than inventing one. packages/logger is the minimal template; packages/core shows prebuild/version generation and bundled docs; packages/react shows subpath exports, CSS entrypoints, and browser tests.
Checklist
Directory:
packages/<name>(auto-included by the rootworkspacesglobs). Kebab-case file names throughout — Biome errors otherwise.package.json — match the house shape:
"name": "@c15t/<name>", sameversionas the linked group if it will join it,"type": "module","sideEffects": falsewhere true, Apache-2.0 license,repository.directoryset.- Exports map pointing at build output:
json "exports": { ".": { "types": "./dist-types/index.d.ts", "import": "./dist/index.js", "require": "./dist/index.cjs" } }, "main": "./dist/index.cjs", "module": "./dist/index.js", "types": "./dist-types/index.d.ts", "files": ["dist", "dist-types"] - Standard scripts (copy from logger):
build(rslib +normalize-dist-types.mjs),dev(rslib watch,--no-dts --no-clean),check-types(tsc --noEmit),lint(bun biome lint ./src),fmt,test(vitest run, add--passWithNoTestsuntil tests exist). Core SDK packages additionally runprepack(bun ../../scripts/verify-package-artifacts.ts) — add it if the package ships to end users. - Workspace deps use
"workspace:*". Dev deps include@c15t/typescript-configand, if tested,@c15t/vitest-config.
rslib.config.ts: ESM + CJS,
dts.distPath: './dist-types'on the ESM lib only,source.excludefor test globs,getRsdoctorPlugins()from../shared/rslib-utils. If the package needs a runtime version string, add theprebuildgenversion script like core (src/version.tsis generated — gitignore it).tsconfig.json: extend
@c15t/typescript-config/base.json(ornext.json/node.json). Don't relax strictness.vitest.config.ts: extend
@c15t/vitest-configbase config; add the package to rootvitest.workspace.tsif it should run in the workspace suite. Browser tests followpackages/react/vitest.config.ts(@vitest/browser-playwright, Chromium).turbo.json: the generic
build/test/linttasks cover most packages. Add a package-specific entry only if outputs differ (e.g. bundled docs addAGENTS.md+docs/**to build outputs) or the demo should watch it (@c15t/example-demo#dev.with).Changesets: decide whether it joins the
linkedgroup in.changeset/config.json(core SDK packages that must version together) or versions independently (utilities like logger/schema/ui).README: user-facing published packages get a generated
README.md— createreadme.json(seepackages/react/readme.json) and runbun run generate:readmes; don't hand-write README.md. Internal utility packages (like schema/ui today) may skip it.Bundled docs (only for user-facing SDK packages): add a config entry in
scripts/generate-package-docs.tsand include"AGENTS.md", "docs"infilesplus abuild:docsscript.knip.json: add one if the package has intentional unused-export patterns; run
bun run knipto check.
Show full SKILL.md (1 more words)Show less
Verify
bun install
bun turbo run build check-types lint test --filter=@c15t/<name>
bun pm pack --dry-run --cwd packages/<name>© c15t, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in .agents/skills/creating-a-package of c15t/c15t.
Open the folder on GitHubat commit f2b2318
Compare with similar skills
Creating A Package next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Creating A Package this skillc15t/c15t | 1.9k | — | ~913 | Automated safety check: Pass | Apache-2.0 | |
| Create Saleor Packagesaleor/apps | 162 | — | ~608 | Automated safety check: Pass | Custom licence | |
| Effect TStellahq/opensession | 392 | — | ~3.7k | Automated safety check: Pass | MIT | |
| Ever Worksever-works/ever-works | 158 | — | ~2.2k | Automated safety check: Pass | AGPL-3.0 | |
| Typescript Idiomsirahardianto/awesome-agv | 157 | — | ~6.1k | Automated safety check: Pass | MIT | |
| Vue Idiomsirahardianto/awesome-agv | 157 | — | ~6k | Automated safety check: Pass | MIT |
Similar skills
Effect TS
tellahq/opensession
Write idiomatic Effect v4 TypeScript verified against the pinned effect@4.0.0-rc.112 source.
Ever Works
ever-works/ever-works
Repo-specific guide to the Ever Works monorepo (ever-works/ever-works) — its pnpm + Turborepo layout, the per-workspace test runners (Jest vs Vitest vs Playwright), file-naming and import-alias…
Typescript Idioms
irahardianto/awesome-agv
TypeScript strict typing: type narrowing, discriminated unions, Zod runtime validation, generic utility types, and Vitest testing.
Vue Idioms
irahardianto/awesome-agv
Vue 3 Composition API patterns: <script setup syntax, reactive state with Pinia stores, reusable composables, and Vitest component testing.
Test Writing Workflow
iOfficeAI/AionUi
Sets the test-writing workflow for the repository: risk-first scenario lists, behavior-focused Vitest tests, a full run before each commit and a coverage target.
More from c15t/c15t
All 8 skills in this repoC15t
c15t/c15t
Work with c15t consent management docs, APIs, and integrations for Next.js, React, and JavaScript.
Releasing
c15t/c15t
Version and release c15t packages with Changesets. An agent skill from c15t/c15t.
Writing Docs
c15t/c15t
Author or edit c15t documentation in docs//.mdx — the source for both the c15t.com site and the docs bundled into published packages.
Leadtype
c15t/c15t
Work with the leadtype package for MDX components, remark plugins, MDX-to-markdown conversion, llms.txt generation, and docs linting.
C15t Backend Docs
c15t/c15t
Read and search the @c15t/backend documentation. An agent skill from c15t/c15t.
C15t Docs
c15t/c15t
Read and search the c15t documentation. An agent skill from c15t/c15t.
Related
Works with
Categories
Questions about Creating A Package
What does Creating A Package do?
Scaffold a new workspace package in the c15t monorepo. An agent skill from c15t/c15t. Creating A Package is an agent skill from c15t/c15t. Scaffold a new workspace package in the c15t monorepo.
When should I use Creating A Package?
Creating A Package fits situations like: adding a package under packages/; wiring up rslib builds; deciding whether a package joins the linked changeset group.
How do I install Creating A Package in Claude Code?
Run `npx skills add c15t/c15t --skill creating-a-package -a claude-code`. Or copy the skill folder (.agents/skills/creating-a-package in c15t/c15t) into .claude/skills/creating-a-package in your project. Claude Code loads it when a task matches its description.
How do I install Creating A Package in Codex?
Run `npx skills add c15t/c15t --skill creating-a-package -a codex`. Or copy the skill folder (.agents/skills/creating-a-package in c15t/c15t) into .agents/skills/creating-a-package in your project. Codex loads it when a task matches its description.
Can I use Creating A Package in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add c15t/c15t --skill creating-a-package -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/creating-a-package, .gemini/skills/creating-a-package, .github/skills/creating-a-package and .opencode/skills/creating-a-package in your project.
What does Creating A Package need to run?
Going by SKILL.md and its folder, Creating A Package needs the command-line tools its instructions call (bun, tsc and vitest).
Does Creating A Package access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Creating A Package safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Creating A Package use?
Creating A Package is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Creating A Package use?
About 913 tokens (SKILL.md is roughly 3.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Creating A Package?
Skills that share tags, products or a category with Creating A Package: Create Saleor Package (saleor/apps, 162 stars), Effect TS (tellahq/opensession, 392 stars), Ever Works (ever-works/ever-works, 158 stars) and Typescript Idioms (irahardianto/awesome-agv, 157 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Creating A Package?
c15t (a GitHub organization) maintains it in c15t/c15t, which has 1,931 GitHub stars. The repository holds 8 skills in this directory. The repository was last updated on October 6, 2026.
Source: c15t/c15t on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.