Repository Guidelines

Project Structure & Module Organization

This repository publishes reusable agent skills. The root README.md is the English catalog and README.ko.md its Korean translation. Store each skill in skills/<skill-name>/ with SKILL.md and an English README.md; add README.ko.md for bilingual documentation. Keep focused guidance in references/, for example skills/create-component/references/styling.md.

Skill and Documentation Conventions

Use lowercase kebab-case for directory and skill names. Keep the name in a skill's YAML frontmatter aligned with its directory. Write direct Markdown; organize SKILL.md around purpose, activation conditions, workflow, outputs, and guardrails. Link reference files using relative paths.

Keep translated READMEs aligned with English examples, paths, and installation commands. Do not claim tooling or behavior absent from this repository.

README Skill Catalog Updates

When asked to update or refresh the README, first explore skills/ to identify the current skill directories and their documentation. Update the Skills section in README.md and the 스킬 목록 section in README.ko.md using the existing per-skill format: a linked heading, a GitHub NOTE information quote, key capabilities, activation conditions, and a fenced installation command.

List entries in ascending English alphabetical order by skill directory name. For example, create-component comes before monospec-kit. Add newly found skills, remove catalog entries for deleted skills, and ensure each link points to the correct language-specific skill README.

Use this entry shape in the English README; translate the labels and summary for README.ko.md while preserving the same structure:

### [<skill-name>](skills/<skill-name>/README.md)
> [!NOTE]
> <Short skill description.>

**Key capabilities**:

- <Capability 1>
- <Capability 2>
- <Capability 3>

**Use when**:

- <Activation condition 1>
- <Activation condition 2>

**Install**:

```sh
npx skills add https://github.com/monegit/agent-skills --skill <skill-name>
```

---

Build, Test, and Development Commands

There is no application build, package manifest, linter, or automated test suite. Use lightweight documentation checks before submitting changes:

rg --files skills
git diff --check
git diff -- README.md README.ko.md skills/<skill-name>

These commands confirm files, detect whitespace errors, and focus review.

Testing Guidelines

Treat each skill's written workflow as its test contract. Verify referenced files, repository paths, and output locations; consider both new and existing resource paths and document edge-case guardrails.

Commit & Pull Request Guidelines

• Use the action-first format: <verb>(<skill-name>): <concise scope>.
• Use one of these verbs:
  • add for a new skill, document, or capability.
  • update for a change to an existing skill or document.
  • remove for removing a skill, document, or capability.
• Use the scope to name the concrete features or rules changed. When a commit changes multiple meaningful behaviors, include each distinguishing change in the scope.
  • For example: update(create-component): enforce styles and prohibit children usage.
• Keep commits focused.

Pull requests should summarize user-facing changes, list modified skills, describe validation, and include before/after examples when behavior or output changes.