メニュー
How to scaffold a new OwlMeans Common project — the @owlmeans/create-app CLI (npm/bun/yarn create), its flags, what it generates, and the manual alternative. Use when asked to create/bootstrap/start a new OwlMeans app or set up a fresh project.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
PK-based supervisor authentication — a development-only login where a holder of one of the project's trusted private keys mints a token for any user id/email (registering them on first use), bypassing external IdPs. Primary use is end-to-end tests. Covers appendSupervisorAuth (server + web), the supervisor plugin, and the @owlmeans/test-ui helpers. Use when wiring or testing supervisor auth.
How to use @owlmeans/web-auth — web client auth plugins that register into @owlmeans/client-auth/manager. Currently ships the development-only PK-based supervisor login form (appendSupervisorAuth). Auto-invoked when importing @owlmeans/web-auth.
Discovery-first, reuse-first workflow for OwlMeans projects. Use BEFORE planning or building any feature, before proposing a third-party library or a custom solution, and after writing code. Find an existing @owlmeans/* package or existing code first; extend before writing new; simplify what you write.
Discovery-first, reuse-first workflow for OwlMeans projects. Use BEFORE planning or building any feature, before proposing a third-party library or a custom solution, and after writing code. Find an existing @owlmeans/* package or existing code first; extend before writing new; simplify what you write.
How to scaffold a new OwlMeans Common project — the @owlmeans/create-app CLI (npm/bun/yarn create), its flags, what it generates, and the manual alternative. Use when asked to create/bootstrap/start a new OwlMeans app or set up a fresh project.
How to use @owlmeans/api — HTTP client service (axios-based) used to call entrypoints across services. Auto-invoked when importing the API service or when ctx.entrypoint(...).call() under the hood is involved.
| name | scaffolding |
| description | How to scaffold a new OwlMeans Common project — the @owlmeans/create-app CLI (npm/bun/yarn create), its flags, what it generates, and the manual alternative. Use when asked to create/bootstrap/start a new OwlMeans app or set up a fresh project. |
| user-invocable | true |
| scope | general |
Two paths produce the same minimal fullstack project (common + api + web, shadcn UI
navigation/layout, no auth, a session-scoped in-memory resource). The full reference is
docs/getting-started.md; the framework shape is [[getting-started]].
@owlmeans/create-app (one command)npm create @owlmeans/app@latest my-app
bun create @owlmeans/app my-app
yarn create @owlmeans/app my-app
npx @owlmeans/create-app my-app
By default it copies the template, runs git init, installs dependencies, and deploys agent
guidance into the project via [[bun]]-installed @owlmeans/agent-skills (.claude/skills/ +
.github/instructions/).
Flags: --name <name>, --pm <bun|npm|yarn> (default bun), --no-install, --no-skills,
--no-git, --yes/-y, --help.
Then run:
cd my-app && bun run dev # API :3000, web :3001
When an agent should use this: the user asks to start/bootstrap/create a new OwlMeans app from
nothing. Prefer it over hand-writing boilerplate. After it runs, point the user at the Session
screen and docs/getting-started.md.
Follow Option B in docs/getting-started.md: create the bun
workspace, then common (shared entrypoints/schemas/config), api (@owlmeans/server-app +
appendStaticResource handlers + main), and web (@owlmeans/web-panel + shadcn @-provided
primitives + layout/nav/screens). Finish with npx @owlmeans/agent-skills to add agent guidance.
my-app/
├── package.json # bun workspaces: sources/*
├── CLAUDE.md # agent context: memory + skill directives + project-purpose placeholder
├── .github/
│ ├── copilot-instructions.md # same directives for Copilot
│ └── memory/MEMORY.md # starter memory index
├── .claude/memory/MEMORY.md # starter memory index
├── sources/common/ # consts, types, schemas, config, modules (entrypoints)
├── sources/api/ # context.ts (appendStaticResource), app/session/*, modules.ts, index.ts
└── sources/web/ # vite + tailwind v4, components/ui/*, layout, nav, screens, render.tsx
The session demo stores items in @owlmeans/static-resource, namespaced by a client-generated
sid kept in localStorage — no database, no authentication. See [[static-resource]],
[[server-app]], [[web-panel]].
CLAUDE.md and .github/copilot-instructions.md carry the same memory and skill directives as a
real OwlMeans project, plus a project-purpose placeholder (<!-- OWLMEANS:PROJECT-PURPOSE -->).
On the first agent session that block instructs the agent to ask the user what the project is for and
replace it in both files. The deployed skills include the general management skills
[[skill-authoring]], [[agent-memory]] and the mandatory [[reuse-code]] (find an existing @owlmeans/*
package or code before proposing third-party libraries or custom solutions) so the project can grow its own guidance.
CLAUDE.md and .github/copilot-instructions.md reference [[reuse-code]] as mandatory. After adding any
@owlmeans/* dependency, re-run npx @owlmeans/agent-skills — discovery scans every
node_modules/@owlmeans in the workspace (root and nested under sources/*), so package-specific
skills are picked up even though bun nests them.