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

default-conventions-hd

Enforce React/Next.js component structure, prop naming, and TypeScript interface conventions.

1|1|Updated Apr 9, 2026
Search Tags:#typescript#frontend#react#conventions#nextjs#code-review#style-guide
One-click install
npx skills add https://github.com/kangmomin/harness-plugins --skill default-conventions-hd
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: default-conventions-hd
Source: https://github.com/kangmomin/harness-plugins/tree/main/plugins/hyeondongs-harness/skills/default-conventions-hd
Command: npx skills add https://github.com/kangmomin/harness-plugins --skill default-conventions-hd

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The guidelines provide a standardized set of rules for frontend development and code reviews, reducing ambiguity and ensuring consistent quality across React/Next.js projects.

Core Features & Use Cases

  • Consistent component structure, naming conventions, and TypeScript interfaces across teams.
  • Clear reviewer expectations during PRs, CI checks, and code reviews to improve maintainability.
  • Applicable to local development workflows, component libraries, and project scaffolding for React/Next.js applications.

Quick Start

Review and apply the conventions when starting a new feature or reviewing pull requests.

Frequently Asked Questions about default-conventions-hd

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

FAQPage Schema
What are standard React component structure conventions for scalable frontend apps?▼

Standard React conventions enforce consistent component layouts, prop naming, and TypeScript interfaces to reduce ambiguity and ensure maintainable code across teams. Applying these rules during development and code reviews improves overall project quality.

How do I standardize TypeScript interfaces and prop naming in Next.js projects?▼

You can standardize TypeScript interfaces and prop naming by applying documented frontend conventions during local development and PR reviews. This enforces consistent component structures and reduces ambiguity across React and Next.js applications.

Does this code review style guide work with existing React and Next.js workflows?▼

Yes, these frontend conventions integrate directly into existing React and Next.js workflows. You can apply the rules during local development, CI checks, and pull request reviews to enforce consistent code quality without disrupting your process.

When do I need to enforce frontend conventions for component libraries?▼

You need frontend conventions for component libraries when multiple teams require consistent TypeScript interfaces and prop naming. Enforcing these rules during project scaffolding and code reviews ensures maintainability and reduces ambiguity across scalable React applications.

What is the best way to set reviewer expectations for React pull requests?▼

The best way to set reviewer expectations is to apply standardized frontend conventions for component structure and TypeScript interfaces during PRs. Clear code review guidelines ensure consistent quality and maintainability across React and Next.js projects.

Related Skills

Explore More Software Engineering Skills→
GemachDAOGemachDAO
4

gdex-ui-install-setup

Scaffold a React or Next.js project with a GDEX SDK provider.

Official
Intermediate
shidax-corpshidax-corp

Create GitHub Issues and Pull Requests

Create and manage GitHub Issues and Pull Requests via the GitHub CLI.

Official
Intermediate
SandroBeatzSandroBeatz

lint-check

Run ESLint and TypeScript type checking on a codebase.

Community
Intermediate
forgivesam168forgivesam168
2

frontend-patterns

Implement reusable React and Next.js component patterns for scalable frontend architectures.

Community
Intermediate