Awesome Vibecoding Claude Guide

This skill provides guidance for working with the awesome-vibecoding repository, a curated list of resources about Vibe Coding (AI-assisted programming). This is a documentation-only repository with automated translation workflows.

Project Structure

The repository follows this structure:

```

awesome-vibecoding/

├── README.md # English source (edit this only)

├── README.ko.md # Korean translation (auto-generated)

├── README.ja.md # Japanese translation (auto-generated)

├── docs/

│ ├── automation.md # How the automation works

│ └── workflows-and-templates.md

├── .claude/

│ ├── commands/translate.md # /translate skill

│ ├── hooks/translate-readme.sh

│ └── settings.json # PostToolUse hook config

└── .github/

├── workflows/

│ ├── weekly-update.yml # Weekly content update via Claude Code

│ └── issue-approval.yml # Issue-based resource addition

└── prompts/

├── weekly-update.md # Prompt for weekly updates

└── issue-approval.md # Prompt for issue processing

```

Instructions

When Editing Content

1. **ONLY edit README.md** — Never directly edit the translated files (README.ko.md, README.ja.md)

2. **Follow existing table formats** — Each section uses specific table structures that must be maintained

3. **Include links for all tools** — Use official GitHub repositories or product pages

4. **Run `/translate` after changes** — Regenerate Korean and Japanese translations after any README.md modifications

5. **Preserve markdown formatting** — Maintain consistent formatting across all edits

Translation Requirements

When the `/translate` command is invoked or when reviewing translations:

1. **Technical terms** — Keep in English (e.g., "Vibe Coding", "Claude Code", product names)

2. **URLs and links** — Never translate; keep exactly as-is

3. **Korean translations**:

- Add space after **bold text** followed by Korean characters

- Example: `**Vibe Coding** 리소스` not `**Vibe Coding**리소스`

4. **Japanese translations**:

- Use appropriate particles (は、を、に、で, etc.)

- Use natural Japanese phrasing

- Example: `**Vibe Coding** のリソース`

5. **Formatting** — Preserve all markdown formatting exactly (headings, lists, tables, bold, links)

Available Commands

GitHub Actions Workflows

The repository includes two automated workflows:

1. **weekly-update.yml** — Runs every Sunday, uses Perplexity MCP to discover new vibe coding tools and resources

2. **issue-approval.yml** — Triggered when the repository owner comments `/approve` on an issue, automatically adds the resource

Hook System

The repository uses a `PostToolUse` hook (`translate-readme.sh`) that monitors Edit/Write operations. When README.md is modified, it prompts to run `/translate` to keep translations in sync.

Adding New Resources

1. Add the resource to the appropriate section in **README.md** only

2. Follow the existing table format for that section

3. Include a descriptive title and working link

4. Run `/translate` to generate Korean and Japanese versions

5. Verify all three files are properly formatted before committing

Quality Checks

Before finalizing changes:

Notes