メニュー
Convention for inline callout markers in prose and artefact files. Reference-only — not auto-loaded. Load explicitly when writing or reviewing documents that follow bew's personal notes style.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Token-efficient man page reading. Load when looking up CLI tool docs, flags, options, usage examples, config formats. Do NOT use bash to run `man` directly without loading this skill first.
Load when user asks to create, update, edit, or refactor any OpenCode (OC) artefact: skills, agents, commands, tools, plugins, or snippets — including modifying an existing one. Triggers examples: "create skill to …", "draft a command to …", "add Y to OC cmd Z", "edit the W agent", "write a plugin to …", "create a tool for …", "update crafter skill". Guides user through discovery, drafting, and iterative refinement.
Methodology for drafting technical design specs. Load when asked to write, draft, or refine a spec, design doc, architecture note, RFC, or similar document for a system, API, protocol, or subsystem.
Load ONLY when user explicitly invokes /reflect-friction or directly asks to review session friction (e.g. "review friction", "what went wrong", "where did you push back"). Do NOT auto-load speculatively.
General script writing guidelines: structure, naming, error handling, and organization. Language-agnostic. Auto-load when writing or reviewing any script. Language-specific skills (write-script-bash, write-script-bats) build on top of this.
Load whenever new files or directories are created in a git repo — via write, bash, or any other tool. Ensures `git_track_new_file` is called so new files are git-tracked for the user.
| name | bew-inline-callout-style |
| description | Convention for inline callout markers in prose and artefact files. Reference-only — not auto-loaded. Load explicitly when writing or reviewing documents that follow bew's personal notes style. |
Callout markers draw attention to secondary info that should stand out in prose. Use when careful reader might otherwise miss or skip the info. No hard limit on count — if callouts appear frequently, prose likely needs rewriting rather than more markers.
Common keywords and intended semantics:
NOTE: — context or secondary info reader should not miss; doesn't block progress.IMPORTANT: — hard constraint. Must be followed to produce correct output.WARNING: — risk. Bad outcome if ignored.TIP: — actionable shortcut or best practice. Use rarely.TRADEOFF: — competing forces with no single right answer; surfaces the tension.List above is not exhaustive. Use other UPPERCASE keywords when none fit, as
long as keyword clearly signals nature of callout (e.g. CONTEXT:, CAVEAT:,
ASSUMPTION:). Prefer established keywords when they fit.
WARNING: not **WARNING:**.(KEYWORD: ...): must be single line. Can appear inline
within another paragraph without blank line separator.Multi-line WARNING — blank line ends callout:
WARNING: Avoid `.opencode/skills/` for team repos — it locks the skill to
OpenCode only and blocks non-OC contributors.
This line is no longer part of the warning.
Parenthesized IMPORTANT inline in a paragraph:
Present the draft as a fenced block labeled with the artefact type.
(IMPORTANT: Always use 4 backticks so nested code blocks don't break formatting.)
Ask: *Does this match what you had in mind?*