skills.rest
kangmomin
kangmominCOMMUNITY
Explore all skills by this author →
GitHub

default-conventions

Standardizes Be-Harness plugin development guidelines with YAML frontmatter and project overrides.

1|1|Updated Apr 9, 2026
Search Tags:#development#claude#plugin#conventions#coding-standards#overrides
One-click install
npx skills add https://github.com/kangmomin/harness-plugins --skill default-conventions
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: default-conventions
Source: https://github.com/kangmomin/harness-plugins/tree/main/be-harness/skills/default-conventions
Command: npx skills add https://github.com/kangmomin/harness-plugins --skill default-conventions

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Be-harness guidelines provide a universal baseline for CLAUDE-based plugin development, solving the problem of inconsistency across plugins and projects by codifying common conventions.

Core Features & Use Cases

  • Surgical-change mindset: enforce minimal, well-scoped changes per commit.
  • Project overrides: allow local overrides via CLAUDE.md and OVERRIDES.md at the project root.
  • Project-wide consistency: align with profile's projectConventions and be-harness common docs.
  • Use Case: teams standardize plugin development for predictable behavior across minmos-harness and hyeondongs-harness.

Quick Start

Update CLAUDE.md and the project's projectConventions to apply the universal be-harness guidelines.

Frequently Asked Questions about default-conventions

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I standardize coding conventions across multiple CLAUDE-based plugin projects?▼

Project overrides are applied by updating CLAUDE.md and projectConventions at the project root, allowing local OVERRIDES.md files to align universal be-harness guidelines with specific project needs.

What is the surgical-change mindset in CLAUDE plugin development?▼

YAML frontmatter must include name and description fields to standardize be-harness plugin identification and align with projectConventions across core plugins and overrides.

How do I configure local overrides for be-harness guidelines?▼

Optional directories supported by be-harness conventions include scripts, references, and assets folders, providing structured locations for supplementary plugin development files alongside the standardized YAML frontmatter.

Does be-harness support project-specific overrides for CLAUDE plugins?▼

Be-harness guidelines are designed for teams standardizing CLAUDE-based plugin development, providing a universal baseline that ensures predictable behavior across minmos-harness and hyeondongs-harness environments.

Related Skills

Explore More Software Engineering Skills→
EhraxEhrax

using-git-worktrees

Creates isolated git worktrees for feature work with verified ignore rules and project setup.

Community
Advanced
kgadekkgadek

Plugin Settings

Configure per-project plugin behavior via YAML frontmatter in .claude/plugin-name.local.md.

Community
Intermediate
kangmominkangmomin
1

commit-hard-push

Commit repository changes and push to remote despite protected branches.

Community
Intermediate
sraloffsraloff
2

wordpress-legacy

Enforce WordPress coding standards and security practices for themes and plugins.

Community
Intermediate