メニュー
Write code following SOLID design principles with good information hiding. Use when writing or reviewing code for architecture, class design, or module organization.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Annotate a sourdough bake log in Grafana. Use when asked to add Grafana annotations from a Zephyr bake log, build the annotation CLI, or update the bake log grafana section.
Understand the Zephyr sourdough bake tagging scheme. Use when working with Zephyr bake logs, finding which bake log corresponds to a Zephyr key, reading Zephyr voice memo entries to extract bake events, routing Zephyr entries from any document to their bake logs, or building the Grafana dashboard links for a bake log.
Create a research note from a rough question. Cleans the question, splits into separate files if multiple questions, adds an answer and Google search links. Use when the user has a question they want documented as a note.
Search shell history using atuin. Use when the user mentions searching shell history, finding a past command, or recalling a URL or tool invocation from the terminal.
Reformat a recipe file using consistent style rules. Use when the user wants to clean up or standardize a recipe note in the vault, or create a new recipe note from a URL.
Create a structured Obsidian vault note from a YouTube video transcript — fetches captions with timestamps, cleans the text, divides into sections, adds a TOC and per-section video links, uploads the thumbnail to Imgur, and commits. Use when the user shares a YouTube URL and wants a full transcript note in the vault.
| name | solid-principles |
| description | Write code following SOLID design principles with good information hiding. Use when writing or reviewing code for architecture, class design, or module organization. |
Follow SOLID design principles and maintain good information hiding:
Individual code files should strive to stay under 200 lines. This is a goal, not a strict limit — justified outliers are fine.
Decompose extensive logic into multiple discrete files rather than accumulating lines in a single file. This promotes information hiding and keeps modules focused and comprehensible.
When writing code, consider:
