project-skill-generating

スター1

フォーク0

更新日2026年5月4日 12:37

Use when creating or updating project-specific Codex skills for create-vibe-start, especially skills stored under .agents/skills with concise SKILL.md instructions and progressively loaded reference files.

インストール

Codex または Claude でインストールこの Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。

ソース

bichikim

bichikim/create-vibe-start

GitHub リポジトリを開く Creator のリポジトリを見る

ダウンロード

Project Skill Generating

Core Workflow

Create project-specific skills under .agents/skills/<skill-name>/.
Put the required frontmatter and essential workflow in SKILL.md.
Write concise, action-oriented instructions that tell the agent what to do.
Split deeper guidance into reference files under references/.
Link each reference file from SKILL.md with when to read it.
Keep the first-read content focused on trigger, scope, file layout, and the next action.
Use positive instructions such as Create, Use, Write, Split, Link, Validate, and Report.

Skill Layout

.agents/skills/<skill-name>/
  SKILL.md
  references/
    authoring.md
    validation.md

Progressive Reading

For detailed authoring rules, read references/authoring.md.
For review and validation steps, read references/validation.md.

Completion

Validate that SKILL.md has name and description frontmatter.
Confirm referenced files exist at the paths listed in SKILL.md.
Report the created or updated skill path and the reference files added.

このリポジトリの他の Skills

同じリポジトリ

skill-diet

bichikim/create-vibe-start

Reduce an existing Codex skill to its minimum useful form, extract on-demand context into linked sibling files, or decide that the skill should be deleted. Use when the user asks to diet, slim, trim, simplify, minimize, reevaluate, or remove bloat from a skill while preserving its trigger behavior, tone, safety constraints, and practical usefulness.

2026-08-021

new-pr

bichikim/create-vibe-start

Create a GitHub pull request from the current branch—commit uncommitted changes, push, and open a PR against main with an auto-generated title and Summary/Testing body sections.

2026-08-021

unit-test

bichikim/create-vibe-start

Use when adding or updating unit tests for create-vibe-start CLI modules, especially Vitest tests that must isolate prompts, shell commands, platform detection, and package imports from real external resources.

2026-08-021

critical-review

bichikim/create-vibe-start

Review code for correctness risks, maintainability, security, and lifecycle issues with severity-tagged findings.

2026-05-171

update-pr

bichikim/create-vibe-start

Update an existing GitHub pull request for the current branch—commit and push latest changes, then refresh the PR title and body from the full diff against main.

2026-05-171

deep-interview

bichikim/create-vibe-start

Interview the user with Socratic questions to turn an ambiguous request into actionable requirements. Use when the user asks for a deep-interview, requirement clarification, or help organizing their thoughts, or when the goal, scope, constraints, or definition of done are unclear. Do not use when the request is already concrete, or for low-value work like typo fixes, small config tweaks, or test top-ups.

2026-05-131

name	project-skill-generating
description	Use when creating or updating project-specific Codex skills for create-vibe-start, especially skills stored under .agents/skills with concise SKILL.md instructions and progressively loaded reference files.

Project Skill Generating

Core Workflow

Create project-specific skills under .agents/skills/<skill-name>/.
Put the required frontmatter and essential workflow in SKILL.md.
Write concise, action-oriented instructions that tell the agent what to do.
Split deeper guidance into reference files under references/.
Link each reference file from SKILL.md with when to read it.
Keep the first-read content focused on trigger, scope, file layout, and the next action.
Use positive instructions such as Create, Use, Write, Split, Link, Validate, and Report.

Skill Layout

.agents/skills/<skill-name>/
  SKILL.md
  references/
    authoring.md
    validation.md

Progressive Reading

For detailed authoring rules, read references/authoring.md.
For review and validation steps, read references/validation.md.

Completion

Validate that SKILL.md has name and description frontmatter.
Confirm referenced files exist at the paths listed in SKILL.md.
Report the created or updated skill path and the reference files added.