メニュー
Generate friendly greetings in multiple languages with cultural context. Use when creating welcome messages, international greetings, or multilingual user interfaces.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Create ASCII wireframes, user flow diagrams, and cross-cutting specifications for UI/UX visualization. Use PROACTIVELY when user mentions wireframe, UI design, UX flow, screen layout, screen design, user flow, or asks to visualize screens. Examples: <example>Context: User needs screen design user: 'Create wireframes for this feature' assistant: 'I will use designing-wireframes skill' <commentary>Triggered by wireframe request</commentary></example> <example>Context: After requirements are detailed user: 'Let me design the screens' assistant: 'I will use designing-wireframes skill' <commentary>Triggered by screen design request</commentary></example>
Plan and create GitHub Issues with agile/scrum methodology. Analyze requirements, identify parallel work, manage dependencies, and suggest git worktree strategies. Use PROACTIVELY when creating tickets, planning sprints, breaking down features, organizing issues, identifying parallel tasks, managing dependencies, or working with GitHub Issues, scrum, agile planning, ticket breakdown, worktree planning. Examples: <example>Context: User wants to plan implementation user: 'チケットを作っていこう' assistant: 'I will use agile-ticket-planner skill' <commentary>Triggered by ticket creation request</commentary></example> <example>Context: User has requirements user: 'この要件をIssueに分割して' assistant: 'I will use agile-ticket-planner skill' <commentary>Triggered by issue breakdown request</commentary></example>
Clarify ambiguous requirements through structured questioning and produce detailed, implementation-ready specifications. Acts as PdM to identify unclear points and resolve them via AskUserQuestion. Use PROACTIVELY when user mentions requirements, specs, PRD, refine, detail, clarify requirements, or asks to detail/refine app ideas. Also trigger when the user is about to jump into implementation with a vague or incomplete spec — even if they haven't explicitly asked to "refine" anything. Examples: <example>Context: User has rough idea user: 'Help me refine this app spec' assistant: 'I will use refining-requirements skill' <commentary>Triggered by spec refinement request</commentary></example> <example>Context: User jumps to implementation with vague spec user: 'Let me start building this feature' assistant: 'I will use refining-requirements skill first to clarify the requirements' <commentary>Proactively triggered before ambiguous implementation</commentary></example> <example>Context: Planning phase user: 'Let
Design UI/UX concepts for apps and web services through systematic research and questioning. Use PROACTIVELY when designing app interfaces, determining visual direction, creating design systems, choosing color schemes, or establishing UX patterns. Examples: <example>Context: User wants to design an app user: 'UI/UXのデザインコンセプトを決めたい' assistant: 'I will use ui-ux-designing skill' <commentary>Triggered by design concept request</commentary></example> <example>Context: User building new feature user: 'この機能の見た目どうしよう' assistant: 'I will use ui-ux-designing skill' <commentary>Triggered by visual design question</commentary></example>
Author a concise, self-contained prompt to hand to Claude Code's /goal command in a separate, unattended session. Researches the target project (CLAUDE.md, dev rules, baseline build/test state, existing patterns) and drafts a goal with measurable done-criteria, transcript-verifiable checks, scope + anti-cheat constraints, and stop rules. Outputs to chat by default; externalizes bulky context to ~/.claude/goal-prompts/<slug>/ only when inlining would bloat it. Decides autonomously, asking only when a goal-defining axis is genuinely ambiguous. Use PROACTIVELY when the user mentions /goal, goal prompt, ゴールプロンプト, /goal に渡す, 自走/無人実行させたい, unattended run, 完了条件を決めて goal を回す, or setting up a long-running autonomous Claude session. Examples: <example>Context: User wants an unattended run user: '/goal に渡すプロンプトを作って' assistant: 'I will use authoring-goal-prompts skill' <commentary>goal-prompt authoring request</commentary></example>
Claude Code ベストプラクティスの対話形式セットアップウィザード。Use PROACTIVELY when setting up new projects, configuring Claude Code, adding agents/rules/hooks, or when user mentions "bootstrap", "setup claude", "configure claude code", "add agents", "add rules", "セットアップ", "初期設定", "ブートストラップ". Examples: <example>Context: User wants to set up Claude Code user: 'Claude Codeをセットアップしたい' assistant: 'I will use bootstrapping-claudecode skill' <commentary>Triggered by setup request</commentary></example>
| name | greeting-generator |
| description | Generate friendly greetings in multiple languages with cultural context. Use when creating welcome messages, international greetings, or multilingual user interfaces. |
A simple skill that demonstrates the basic structure of a Claude Code skill. This skill generates friendly greetings in various languages with appropriate cultural context.
Use this skill when:
When generating greetings:
Language: Japanese
Formality: Formal
Context: Business meeting
Greeting: おはようございます (Ohayou gozaimasu)
Translation: Good morning
Cultural Note: Used until around 10-11 AM. Appropriate for business settings.
Alternative: こんにちは (Konnichiwa) - for afternoon greetings
Language: Spanish
Formality: Informal
Context: Friends meeting
Greeting: ¡Hola! ¿Qué tal?
Translation: Hi! How's it going?
Cultural Note: Very casual, perfect for friends and peers.
Alternative: ¡Buenos días! - more formal morning greeting
When this skill is activated:
Ask the user about:
Generate:
Always provide:
Never: