メニュー
Prompt template for exploring open-source code (extracted from paint/note). User will refine later.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
REQUIRED for end-user customization of Linux desktop, window manager, or system config. Use when editing ~/.config/hypr/, ~/.config/waybar/, ~/.config/walker/, ~/.config/alacritty/, ~/.config/kitty/, ~/.config/ghostty/, ~/.config/mako/, or ~/.config/omarchy/. Triggers: Hyprland, window rules, animations, keybindings, monitors, gaps, borders, blur, opacity, waybar, walker, terminal config, themes, wallpaper, night light, idle, lock screen, screenshots, layer rules, workspace settings, display config, and user-facing omarchy commands. Excludes Omarchy source development in ~/.local/share/omarchy/ and omarchy-dev-* workflows.
REQUIRED when the user explicitly says "buddy", "task-buddy", or "verify-buddy" (or plurals "buddies", "task-buddies", "verify-buddies", and close variants like "use buddy", "run a task-buddy", "do a verify-buddy", "run 4 verify-buddies"). Do not trigger on generic phrases like "second opinion", "external review", "another model", or "GPT" -- only on the literal terms buddy / task-buddy / verify-buddy (and their plurals).
Conventions for creating or modifying personal scripts in ~/workspace/conf/bin. Trigger when adding, editing, or discussing scripts in the bin directory.
Create, refine, review, merge, and archive project plan files. Use when the task is about planning work, naming plan files, creating new plan documents under ./plan, or archiving completed plans into ./plan-archive.
Prompt template for exploring open-source code (extracted from paint/note). User will refine later.
Prompt template for exploring open-source code (extracted from paint/note). User will refine later.
| name | explore-opensource-application-impl |
| description | Prompt template for exploring open-source code (extracted from paint/note). User will refine later. |
I'm studying this application to understand how it's built and learn from its design decisions. Explain the following to me in clear, educational terms. Assume I'm a systems programmer comfortable with C and low-level graphics but unfamiliar with this specific codebase.
## High-Level Architecture
- What does this application do and what problem does it solve?
- What are the major subsystems/modules and how do they communicate?
- Draw me an ASCII diagram of the overall architecture.
## Build & Dependencies
- What are the external dependencies and what role does each play?
- How is the build system structured? What are the build targets?
- What platforms are supported and how is portability handled?
## Core Loop
- What does the main loop look like? Walk me through one frame/cycle.
- How is state managed across the application?
- How does it handle input, and how does input flow into the rest of the system?
## Rendering / Output
- How does it get pixels on screen? What graphics API or abstraction does it use?
- How is drawing organized (immediate mode, retained, scene graph, command buffer)?
- Where are the hot paths and what performance considerations are visible in the code?
## Data Model
- What are the core data structures that represent the user's work/content?
- How is data serialized for saving/loading? What file format is used?
- How is undo/redo implemented, if at all?
## UI
- How is the UI built? Custom, immediate-mode, toolkit?
- How are layout and event handling structured?
- How does the UI layer interact with the core data model?
## Design Patterns & Takeaways
- What are the most interesting or unusual design decisions in this codebase?
- What patterns here could I reuse in my own projects?
- Where are the rough edges or known limitations?