coding-standards

coding-standards is a skill for Claude Code from loulanyue/awesome-claude-notes. It costs 41 tokens per session (3,210 once invoked), scanned A, original, MIT.

A set of general coding standards and practical patterns for TypeScript, JavaScript, React, and Node.js. It covers readable naming, simple designs, avoiding repetition, and delaying unnecessary features.

In plain words
What is it for?
Use it when writing or reviewing TypeScript and JavaScript code, React components, Node.js services, and shared utility functions.
Why use it?
It helps keep code understandable and consistent as a project grows, while reducing duplicated logic and needless complexity.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the awesome-claude-notes plugin — 106 skills, 61 commands, 28 agents shipped together

Good fit Use it when writing or reviewing TypeScript and JavaScript code, React components…

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/loulanyue/awesome-claude-notes/coding-standards
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add loulanyue/awesome-claude-notes --skill coding-standards
Clone the repo
git clone --depth 1 https://github.com/loulanyue/awesome-claude-notes

Made for: Claude Code.

Or install awesome-claude-notes, the plugin that ships this one along with the rest of its 106 skills, 61 commands, 28 agents.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for coding-standards

README.md
[![agentmods](https://agentmods.dev/badge/skills/loulanyue/awesome-claude-notes/coding-standards.svg)](https://agentmods.dev/skills/loulanyue/awesome-claude-notes/coding-standards)
Your own site
<a href="https://agentmods.dev/skills/loulanyue/awesome-claude-notes/coding-standards"><img src="https://agentmods.dev/badge/skills/loulanyue/awesome-claude-notes/coding-standards.svg" alt="Measured on agentmods" height="20"></a>
Per session 41 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,210 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 1 finding. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00041 $0.03210
Opus 5 $0.00020 $0.01605
Sonnet 5 $0.00008 $0.00642
Haiku 4.5 $0.00004 $0.00321

Measured 2d ago against content hash 4f03b7bd8377, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

coding-standards scanned grade A with 1 finding against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

const response = await fetch(url)
docs/ja-JP/skills/coding-standards/SKILL.md · 537 lines

How it starts

The opening of the file, as written. The whole thing — 537 lines — stays where its author put it; the contents beside it link to each section on GitHub.

コーディング標準とベストプラクティス

すべてのプロジェクトに適用される汎用的なコーディング標準。

コード品質の原則

1. 可読性優先

  • コードは書くよりも読まれることが多い
  • 明確な変数名と関数名
  • コメントよりも自己文書化コードを優先
  • 一貫したフォーマット

2. KISS (Keep It Simple, Stupid)

  • 機能する最もシンプルなソリューションを採用
  • 過剰設計を避ける
  • 早すぎる最適化を避ける
  • 理解しやすさ > 巧妙なコード

3. DRY (Don't Repeat Yourself)

  • 共通ロジックを関数に抽出
  • 再利用可能なコンポーネントを作成
  • ユーティリティ関数をモジュール間で共有
  • コピー&ペーストプログラミングを避ける

4. YAGNI (You Aren't Gonna Need It)

  • 必要ない機能を事前に構築しない
  • 推測的な一般化を避ける
  • 必要なときのみ複雑さを追加
  • シンプルに始めて、必要に応じてリファクタリング

TypeScript/JavaScript標準

変数の命名

// ✅ GOOD: Descriptive names
const marketSearchQuery = 'election'
const isUserAuthenticated = true
const totalRevenue = 1000

// ❌ BAD: Unclear names
const q = 'election'
const flag = true
const x = 1000

関数の命名

// ✅ GOOD: Verb-noun pattern
async function fetchMarketData(marketId: string) { }
function calculateSimilarity(a: number[], b: number[]) { }
function isValidEmail(email: string): boolean { }

// ❌ BAD: Unclear or noun-only
async function market(id: string) { }
function similarity(a, b) { }
function email(e) { }

不変性パターン(重要)

// ✅ ALWAYS use spread operator
const updatedUser = {
  ...user,
  name: 'New Name'
}

const updatedArray = [...items, newItem]

// ❌ NEVER mutate directly
user.name = 'New Name'  // BAD
items.push(newItem)     // BAD

エラーハンドリング

// ✅ GOOD: Comprehensive error handling
async function fetchData(url: string) {
  try {
    const response = await fetch(url)

    if (!response.ok) {
      throw new Error(`HTTP ${response.status}: ${response.statusText}`)
    }

    return await response.json()
  } catch (error) {
    console.error('Fetch failed:', error)
    throw new Error('Failed to fetch data')
  }
}

// ❌ BAD: No error handling
async function fetchData(url) {
  const response = await fetch(url)
  return response.json()
}

Async/Awaitベストプラクティス

// ✅ GOOD: Parallel execution when possible
const [users, markets, stats] = await Promise.all([
  fetchUsers(),
  fetchMarkets(),
  fetchStats()
])

// ❌ BAD: Sequential when unnecessary
const users = await fetchUsers()
const markets = await fetchMarkets()
const stats = await fetchStats()

Read the full file on GitHub · 537 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 2d ago First seen · 537 lines · 41 tokens per session scan A 4f03b7bd8377

Subscribe to this mod's changes

coding-standards is a skill published in the GitHub repository loulanyue/awesome-claude-notes (270 stars, last pushed 3d ago), licensed MIT. It adds 41 tokens to every session and 3,210 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.

Related

Other skills, from other repositories

coding-standards

Universal coding standards, best practices, and patterns for TypeScript, JavaScript, React, and Node.js development.

shahidshabbir-se/my-pi-setup · 28 tokens

tanstack-form-composition

Migrate a React @tanstack/react-form codebase from the prop-drilled useForm + erased-form-type pattern to the official createFormHook composition API (useAppForm / withForm / field.X). Use when a project threads a form object (often cast to an any-erased type like ReactFormExtendedApi ) through field-wrapper…

suxrobGM/jobpilot · 158 tokens

react-dev

This skill should be used when building React components with TypeScript, typing hooks, handling events, or when React TypeScript, React 19, Server Components are mentioned. Covers type-safe patterns for React 18-19 including generic components, proper event typing, and routing integration (TanStack Router, React…

softaworks/agent-toolkit · 66 tokens

react-dev

Explicit /react-dev reference for advanced React/TypeScript typing and integration patterns. Do not auto-use for routine React implementation.

Dannykkh/skill-olympus · 29 tokens

react-component-development

Component patterns and best practices for React with TypeScript. Covers functional components, custom hooks, state management, composition patterns, error boundaries, server components, and form handling. Keywords: React component, hooks, state management, TypeScript component, custom hooks, Zustand, useReducer…

PMDevSolutions/Aurelius · 68 tokens

aio-xstate

Implement XState v5 state machines with strict patterns — setup().createMachine(), actors, and TypeScript typing. Use when working with finite state machines (FSM), statecharts, state diagrams, or the actor model in TypeScript. Covers @xstate/react integration (useMachine, useActor, useSelector), parallel states…

aiocean/claude-plugins · 103 tokens