Guide · Agent skill
How to use the Coding Standards (Japanese) agent skill
Updated · written with AI from the project's own documentation and checked against our catalogue data
This skill is a written style guide in Japanese that tells an AI coding agent how to write and review TypeScript, JavaScript, React and Node.js code. Once it is installed, the agent follows these conventions when it writes or reviews matching code, using good and bad examples as reference. This guide walks through what the skill changes, how to install it, how to trigger it and what to keep in mind.
Quick start
- 1Download the ZIP. Get the coding-standards ZIP from this page and unzip it. It contains SKILL.md.
- 2Choose a location. Put the folder in ~/.claude/skills/ for personal use, or in a project's .claude/skills/ folder.
- 3Or upload in the Claude apps. In the Claude apps, go to Settings → Capabilities → Skills and upload the skill.
- 4Ask a TypeScript or React question. Make a request about TypeScript, JavaScript, React or Node.js code in plain language.
- 5Review the output. Check the code against the PASS examples and your own project rules before using it.
What does the coding-standards skill make the agent do?
An agent skill is a set of instructions that an AI assistant loads when a task matches it. This skill contains a general coding standard covering readable naming, simple design (KISS, DRY, YAGNI), immutability, error handling, async patterns, typing, React components and hooks, REST API conventions, input validation with zod, file naming, comments and performance.
The skill does not run anything itself. It only changes the guidance the agent uses, so the agent is more likely to write code in the conventions described in the file.
- Prefer descriptive variable and function names, such as verb-noun function names.
- Use spread syntax instead of mutating objects and arrays.
- Handle errors in async functions and run independent promises with Promise.all.
- Use explicit types instead of any, and functional state updates in React.
- Follow the REST and zod validation patterns shown in the file.
How do I install the coding-standards skill?
Download the ZIP from this page and unzip it. The package contains a single file, SKILL.md. Place the unzipped folder in one of these locations:
- Personal skills: ~/.claude/skills/ so it is available in all your projects.
- Project skills: the .claude/skills/ folder inside a specific project.
- Claude apps: upload the skill under Settings → Capabilities → Skills.
How do I trigger the skill with natural requests?
You do not need a special command. Ask for TypeScript, JavaScript, React or Node.js code in ordinary language, and the agent can apply the standard when the request matches the skill's description. Mentioning the topic directly makes a match more likely.
- Write a React button component in TypeScript following our coding standards.
- Review this TypeScript function for naming, immutability and error handling.
- Design a REST endpoint for listing markets with query parameters and zod validation.
- Refactor this useEffect so the state updates use the functional form.
What does the output look like in practice?
The skill marks guidance with PASS (good) and FAIL (bad) examples. When the agent writes code, it should aim for the PASS style; when it reviews code, it can point to FAIL patterns it sees. The examples are written in Japanese comments and English code, and the file includes examples for typing, error responses and JSDoc comments.
What does the skill need, and what are the safety notes?
The listing states that the skill requires nothing beyond itself, does not run scripts and does not use the network. The only file is SKILL.md, so there is no executable code to review beyond the guidance text.
Because the content is guidance, the agent may still produce code that conflicts with your project. Check its output against your own tests and tooling before merging.
What tips help the skill work well?
Results depend on how closely your project matches the skill's assumptions. The file assumes a Next.js-style App Router layout, so projects with a different structure may need adjustments in the request.
- If your project has its own style guide, tell the agent which rules take priority, because the two may conflict.
- Name the file or folder in your request so the agent applies the conventions to the right code.
- Use the skill for review as well as writing, since it lists concrete bad patterns to look for.
What people use it for
- Writing a new React component with typed props and a clear structure.
- Reviewing a TypeScript pull request for vague names, mutation and missing error handling.
- Designing REST endpoints for a Next.js-style web app.
- Adding zod validation to an API route's request body.
- Creating a shared, Japanese-language baseline for code review in a team.
Frequently asked questions
How do I install the coding-standards agent skill?
Download the ZIP from this page and unzip it. Put the folder in ~/.claude/skills/ for personal use or in a project's .claude/skills/ folder. In the Claude apps, you can instead upload it under Settings → Capabilities → Skills.
Does the coding-standards skill need anything else installed?
The listing states that it requires nothing else. It contains only SKILL.md, does not run scripts and does not use the network.
Is the coding-standards skill free?
The source material gives the licence as MIT. It does not list pricing, so check the licence text for the terms that apply.
What languages and frameworks does this skill cover?
It covers TypeScript, JavaScript, React and Node.js, with examples in the Next.js App Router style. The file does not cover languages outside the JavaScript ecosystem.
Can I use this skill if my project already has a style guide?
Be careful. The listing says these rules may conflict with an established project style guide, so tell the agent which rules take priority.
Why isn't my agent using the coding-standards skill?
Check that the folder containing SKILL.md is in ~/.claude/skills/ or the project's .claude/skills/ folder. Then make your request mention TypeScript, JavaScript, React or Node.js explicitly so it matches the skill.
New agent skills, repos and AI tools — every week
The best new skills and open-source projects, the fastest-growing repos, and one free prompt. Five minutes to read. Unsubscribe anytime.
Our verdict
Use this skill if you want an AI assistant to write or review TypeScript and React code in a consistent style, especially if your team wants a shared Japanese-language baseline. Pick something else if your project has its own established style guide, if you are not a programmer, or if your work is outside the JavaScript ecosystem.
Download the skill