メニュー
Monorepo structure, package conventions, version synchronization, and publishing workflow. Use when adding packages, modifying project structure, or managing versions.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | eserstack-monorepo |
| description | Monorepo structure, package conventions, version synchronization, and publishing workflow. Use when adding packages, modifying project structure, or managing versions. |
Multi-language monorepo: Deno/TypeScript packages (JSR/npm) + Go services.
pkg/@eserstack/<name>/ with deno.json, mod.ts, mod.test.tsdeno task cli codebase versions <patch|minor|major>deno publish), npm secondary (only @eserstack/cli)deno task validate to check entire monorepomod.ts (or main.ts for CLIs)*.test.ts co-located with source, benchmarks: *.bench.ts.ts filesexports and publish.include in each deno.json@eserstack/standards is the foundation — change carefullyGo code lives in apps/ajan/ with independent git-tag versioning.
make go-ok for Go-only validationgo-practices skillSee rules.md for package conventions, adding packages, and templates.
JavaScript/TypeScript conventions: ES modules, Deno runtime, React patterns, async/await, and type handling. Use when writing .ts, .tsx, or .js files, configuring imports, or building React components.
Development tooling: Deno runtime, JSR package registry, deno.json and package.json configuration, and editor settings. Use when setting up projects, choosing packages, or configuring build tools.
Agent roles, safety rules, file ownership, and cross-package change protocol. Use when AI agents work on this codebase, plan multi-package changes, or need boundary guidance.
Security practices: secrets in env vars, input validation, SSRF prevention, error sanitization, and production hardening. Use when handling authentication, secrets, user input, or preparing production deployments.
System architecture: ES modules, hexagonal architecture, project structure, ADRs, and testing strategy. Use when designing systems, planning directory layout, writing ADRs, or reviewing architecture.
CI/CD operations: GitHub Actions, Kubernetes, ArgoCD, and CI timeout configuration. Use when configuring pipelines, debugging deployments, or working with GitHub Actions. Do NOT use for general development workflow.