Agent skill

Coding Standards

by mrzmyr in mrzmyr/pixy-mood-tracker-app

A skill your agent uses when writing, reviewing, or refactoring TypeScript

MITAuto-check passedDevelopment

Install Coding Standards

skills CLI
$ npx skills add mrzmyr/pixy-mood-tracker-app --skill coding-standards -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install mrzmyr/pixy-mood-tracker-app coding-standards --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/mrzmyr/pixy-mood-tracker-app.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/coding-standards .claude/skills/coding-standards && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
coding-standards
GitHub stars
153
Token cost
~2.2k tokens
SKILL.md length
638 words
Files
1
Skills in repo
7
Repo updated
First seen
Licence
MIT

At a glance

A skill your agent uses when writing, reviewing, or refactoring TypeScript

  • Refactoring TypeScript
  • SKILL.md covers Principles, Function Calls, Branch Bodies and Error Logging, plus 7 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
  • Tasks that involve Code quality

What it does

Coding Standards is an agent skill from mrzmyr/pixy-mood-tracker-app. Use when writing, reviewing, or refactoring TypeScript

Its SKILL.md is about 2.2k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Development, covering Code quality and Refactoring. It works with TypeScript. The repository describes itself as: Minimalistic app to track your mood within one pixel a day. The licence is MIT.

When your agent uses it

  • Refactoring TypeScript
  • Tasks that involve Code quality
  • Tasks that involve Refactoring

Example prompts

  • “/coding-standards”

What it can do on your machine

Read from SKILL.md and the folder at commit 700546b. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are typescript).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Coding Standards loads about 2.2k tokens when it runs. Until then it costs about 18 tokens; SKILL.md has 638 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~18
When it runs · the whole SKILL.md, loaded when a task matches
~2.2k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from mrzmyr/pixy-mood-tracker-app at commit 700546b, republished under its MIT licence (© mrzmyr). 638 words, ~2,175 tokens.

Download SKILL.mdSave it as .claude/skills/coding-standards/SKILL.md (or your agent's skills folder).
name
coding-standards
description
Use when writing, reviewing, or refactoring TypeScript

Coding Standards

Principles

  • No backward compatibility. Remove obsolete paths instead of adding compatibility layers, fallbacks, or migrations.
  • Simplest thing that fully works. Choose the simplest implementation that meets the current requirements. Avoid speculative abstractions, configuration, and indirection.
  • Grow in layers. Start with the smallest version that works end to end, and add each capability on top of something that already works. Never trade a working product for unfinished complexity.
  • Modular by default. Keep components separate and concerns clearly divided.
  • Use existing dependencies first. Reach for what the project already has before writing your own implementation or adding a package. Do not assume a library lacks a capability without checking its docs and types.
  • Prefer established libraries. Use well-maintained libraries when they reduce complexity or improve reliability. Do not reimplement common functionality without a clear reason.
  • Decide for the long term. Do not accept a stopgap that only works for now and is meant to be replaced later.

Function Calls

  • Prefer named parameters over positional parameters.
  • Use an object argument when a function takes multiple values, optional values, or values whose meaning is not obvious from type alone.

✅ Use

ts
getUsers({ pageSize, pageIndex });

const tool = stripPrefix({
  value: ctx.toolName,
  prefix: prefix,
});

❌ Avoid

ts
getUsers(pageSize, pageIndex);

stripPrefix(ctx.toolName, prefix);

Branch Bodies

Avoid ternaries that stand in for a branch. Oxlint rejects nested ternaries; simple ternaries still need judgment.

Error Logging

Every real error path must use the project's structured error helper. This includes thrown errors, returned HTTP/OAuth/JSON errors, and error logs.

Structured errors must include:

  • status
  • message
  • why
  • fix

The fields must be specific enough for an operator or developer to understand what happened, why it happened, and what action resolves it.

✅ Use

ts
throw createError({
  status: 502,
  message: "OAuth metadata request failed",
  why: `The provider returned status ${response.status} while loading OAuth metadata`,
  fix: "Verify the OAuth provider is reachable and the issuer configuration is correct",
});

❌ Avoid

ts
throw new Error(`OAuth metadata request failed with ${response.status}`);

Boolean Names

Boolean-returning functions must be prefixed with a boolean-style verb.

Use prefixes like:

  • is
  • has
  • can
  • should
  • was
  • will

✅ Use

ts
function isAllowed({ userId }: { userId: string }): boolean {
  return userId.length > 0;
}

❌ Avoid ambiguous boolean names

ts
function allowed(userId: string): boolean {
  return userId.length > 0;
}

Function Names

Function names should be short and start with an action verb. Prefer verb + subject.

Use verbs like:

  • get
  • set
  • create
  • update
  • delete
  • fetch
  • load
  • parse
  • format
  • increase
  • decrease

✅ Use

ts
getAttrs();
increaseRetries();
formatName();

❌ Avoid noun-only or abbreviated names when the function performs an action

ts
baseAttr();
retryCount();
displayName();

✅ Use one-word function names when the word is the complete, intentional API and reads clearly at the call site, especially for small DSL-style helpers or result builders

ts
success();
error();
text();
Show full SKILL.md (280 more words)Show less

Local File Name Context

Use the file name as naming context. Do not repeat the domain already supplied by the file path or file name unless it removes ambiguity at the call site.

✅ Use

ts
// data-analysis.ts
export function getSandbox() {
  // ...
}

❌ Avoid

ts
// data-analysis.ts
export function getDataAnalysisSandbox() {
  // ...
}
  • Prefer shorter local names when the module boundary already supplies the noun
  • Use longer names only when exported APIs are commonly imported into contexts where the shorter name would be unclear

Fallbacks

  • Question your usage of fallbacks (e.g. environment variables overrides).

✅ Use

ts
const DATABASE_URL = process.env.DATABASE_URL;

if (!DATABASE_URL) {
  throw createError({
    status: 500,
    message: "DATABASE_URL is required",
    why: "DATABASE_URL was not set in the environment",
    fix: "Set DATABASE_URL before starting the service",
  });
}

❌ Avoid

ts
const DATABASE_URL =
  process.env.DATABASE_URL ??
  process.env.LEGACY_DATABASE_URL ??
  "postgres://localhost:5432/app";

Regex Pattern Matching

  • Question your usage of pattern matching via regex.

✅ Use

ts
async function readOnlyQuery({ db, query }) {
  const result = await db.explainQuery({ query });

  if (result.statementType !== "SELECT") {
    // throw structured error
  }

  return query;
}

❌ Avoid

ts
function readOnlyQuery(query) {
  const sql = String(query).trim().replace(/;+\s*$/, "");
  if (!/^(select|with|explain)\b/i.test(sql)) throw new Error("read only only");
  if (/\b(insert|update|delete|drop|alter|create)\b/i.test(sql)) throw new Error("mutating sql");
  return sql;
}

JSDoc Comments

  • Oxlint enforces JSDoc presence on exported declarations.
  • You must write a JSDoc comment for each public method and each public property of an exported class.
  • Write the JSDoc comment on the original declaration. Do not write a JSDoc comment for a re-export.
  • Write a JSDoc comment for internal code only when the code is complex.
  • Write the invariant, the limitation, or the constraint that the TypeScript types cannot show.
  • Do not describe how the code operates. Do not write the TypeScript types again in the comment. Do not use @inheritDoc or @inherit.
  • In the @returns tag, write the typed errors that the function can return. These errors include Result types and tagged errors.
  • Use the @throws tag only if one of these is true:
    • The throw shows a defect that the program cannot correct.
    • The framework makes the throw necessary.
    • The path is a temporary notYetImplemented path.
  • Write a JSDoc comment for each field of a complex object type that you export.

✅ Good

ts
/**
 * Parse an email address from untrusted input.
 *
 * The input is trimmed and lower-cased before validation. Construct values
 * only through this function; the brand makes raw strings unusable where an
 * {@link EmailAddress} is required.
 *
 * @param input - The untrusted string to parse.
 * @returns A parsed {@link EmailAddress}, or {@link InvalidEmailAddress} when
 *   the input is invalid.
 */
export function parse(input: string): Result<EmailAddress, InvalidEmailAddress> {
  // ...
}

/** Input required to evaluate a boolean flag for a single user. */
export type BooleanFlagInput = {
  /** The feature flag key to evaluate. */
  readonly flagKey: string;
  /** The user's email, used as both context key and email attribute. */
  readonly userEmail: string;
  /** The value returned when the flag cannot be evaluated. */
  readonly defaultValue: boolean;
};

❌ Bad

ts
/**
 * Parses input.
 *
 * @inheritDoc
 * @param input - string
 * @returns Result<EmailAddress, InvalidEmailAddress>
 */
export function parse(input: string): Result<EmailAddress, InvalidEmailAddress> {
  // ...
}

export type BooleanFlagInput = {
  readonly flagKey: string;
  readonly userEmail: string;
  readonly defaultValue: boolean;
};

Comments on Edge Cases

  • When fixing edge cases, add a comment explaining and add links to the relevant documentation.

✅ Good

ts
/**
 * Context window of {@link MODEL_ID}. Declared here because this model is
 * unlisted in the gateway catalog, so the build cannot resolve compaction
 * metadata. Keep it in sync when the model changes.
 * See https://example.com/docs/agent-config
 */
export const MODEL_CONTEXT_WINDOW_TOKENS = 1_000_000;

❌ Bad

ts
export const MODEL_CONTEXT_WINDOW_TOKENS = 1_000_000;

✅ Good

ts
/**
 * Terminal assistant message held until the turn ends.
 *
 * `message.completed` fires inside the step that produced it, before that
 * step's `step.completed` reports usage. Posting there would render a footer
 * whose cost is always missing on a single-step turn, so delivery waits for
 * `turn.completed`. See https://example.com/docs/sessions
 */
const pendingChannelResponse = defineState<PendingChannelResponse | null>(
  "my-agent.pending-channel-response",
  () => null,
);

❌ Bad

ts
const pendingChannelResponse = defineState<PendingChannelResponse | null>(
  "my-agent.pending-channel-response",
  () => null,
);

© mrzmyr, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .agents/skills/coding-standards of mrzmyr/pixy-mood-tracker-app.

Open the folder on GitHubat commit 700546b

Compare with similar skills

Coding Standards next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Coding Standards compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Coding Standards this skillmrzmyr/pixy-mood-tracker-app153—~2.2kAutomated safety check: PassMIT
DRY Refactoring With jscpdkucherenko/jscpd6.4k—~2.1kAutomated safety check: PassMIT
Qovery Console StandardsQovery/console227—~924Automated safety check: PassMIT
jscpd Duplicate Code Detectorkucherenko/jscpd6.4k—~4.5kAutomated safety check: PassMIT
Typescript Best Practicesjwynia/agent-skills169—~2.5kAutomated safety check: PassMIT
Clean Testsertugrul-dmr/clean-code-skills197—~1.4kAutomated safety check: PassMIT

Similar skills

  • Removes copy-paste duplication found by jscpd, starting with exact clones and hotspots, then renamed and near-miss copies, using proven refactoring strategies.

    6.4k GitHub stars~2.1k tokensUpdated today
    DevelopmentAuto-check passed
  • Qovery Console coding standards, architecture guidelines, naming conventions, testing practices, and development workflows.

    227 GitHub stars~924 tokensUpdated today
    DevelopmentAuto-check passed
  • Finds duplicated code in 220+ languages with jscpd, reports exact, renamed and near-miss clones in a compact agent-friendly format and measures duplication.

    6.4k GitHub stars~4.5k tokensUpdated today
    DevelopmentAuto-check passed
  • Typescript Best Practices

    jwynia/agent-skills

    Guide AI agents through TypeScript coding best practices including type safety, error handling, code organization, and architecture patterns.

    169 GitHub stars~2.5k tokensUpdated 7 mo ago
    DevelopmentAuto-check passed
  • Clean Tests

    ertugrul-dmr/clean-code-skills

    A skill your agent uses when writing, fixing, editing, or refactoring TypeScript tests.

    197 GitHub stars~1.4k tokensUpdated 5 mo ago
    DevelopmentAuto-check passed
  • Code Reviewer

    LeoYeAI/openclaw-master-skills

    Code review automation for TypeScript, JavaScript, Python, Go, Swift, Kotlin.

    2.2k GitHub starsUsed in 1 repo~1.2k tokens
    DevelopmentAuto-check passed

More from mrzmyr/pixy-mood-tracker-app

  • Competitor Analysis

    mrzmyr/pixy-mood-tracker-app

    Competitor analysis for Pixy (or any mobile app) from public App Store and Google Play data, no API keys.

    153 GitHub stars~1.4k tokensUpdated yesterday
    Auto-check passed
  • PR Proof

    mrzmyr/pixy-mood-tracker-app

    Upload screenshots or videos to a PR body. An agent skill from mrzmyr/pixy-mood-tracker-app.

    153 GitHub stars~571 tokensUpdated yesterday
    Auto-check passed
  • Run App

    mrzmyr/pixy-mood-tracker-app

    Build, install, and run the app on a device. An agent skill from mrzmyr/pixy-mood-tracker-app.

    153 GitHub stars~893 tokensUpdated yesterday
    Auto-check passed
  • Add Testers

    mrzmyr/pixy-mood-tracker-app

    Add beta testers for Pixy on Android and iOS. An agent skill from mrzmyr/pixy-mood-tracker-app.

    153 GitHub stars~229 tokensUpdated yesterday
    Auto-check passed
  • Test PR

    mrzmyr/pixy-mood-tracker-app

    Run changed e2e flows for a pull request and note the result.

    153 GitHub stars~391 tokensUpdated yesterday
    Auto-check passed
  • Babysit PR

    mrzmyr/pixy-mood-tracker-app

    Monitor a pull request until review comments and CI are handled.

    153 GitHub stars~189 tokensUpdated yesterday
    Auto-check passed

Works with

Categories

Questions about Coding Standards

What does Coding Standards do?

A skill your agent uses when writing, reviewing, or refactoring TypeScript. Coding Standards is an agent skill from mrzmyr/pixy-mood-tracker-app.

When should I use Coding Standards?

Coding Standards fits situations like: refactoring TypeScript; tasks that involve Code quality; tasks that involve Refactoring.

How do I install Coding Standards in Claude Code?

Run `npx skills add mrzmyr/pixy-mood-tracker-app --skill coding-standards -a claude-code`. Or copy the skill folder (.agents/skills/coding-standards in mrzmyr/pixy-mood-tracker-app) into .claude/skills/coding-standards in your project. Claude Code loads it when a task matches its description.

How do I install Coding Standards in Codex?

Run `npx skills add mrzmyr/pixy-mood-tracker-app --skill coding-standards -a codex`. Or copy the skill folder (.agents/skills/coding-standards in mrzmyr/pixy-mood-tracker-app) into .agents/skills/coding-standards in your project. Codex loads it when a task matches its description.

Can I use Coding Standards in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add mrzmyr/pixy-mood-tracker-app --skill coding-standards -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/coding-standards, .gemini/skills/coding-standards, .github/skills/coding-standards and .opencode/skills/coding-standards in your project.

What does Coding Standards need to run?

SKILL.md names no scripts, command-line tools or credentials: Coding Standards is instructions for the agent only.

Does Coding Standards access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Coding Standards safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Coding Standards use?

Coding Standards is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Coding Standards use?

About 2.2k tokens (SKILL.md is roughly 8.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Coding Standards?

Skills that share tags, products or a category with Coding Standards: DRY Refactoring With jscpd (kucherenko/jscpd, 6.4k stars), Qovery Console Standards (Qovery/console, 227 stars), jscpd Duplicate Code Detector (kucherenko/jscpd, 6.4k stars) and Typescript Best Practices (jwynia/agent-skills, 169 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Coding Standards?

mrzmyr (a GitHub user) maintains it in mrzmyr/pixy-mood-tracker-app, which has 153 GitHub stars. The repository holds 7 skills in this directory. The repository was last updated on October 8, 2026.

Source: mrzmyr/pixy-mood-tracker-app on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.