react-coding-standards
React & TypeScript coding standards
This skill applies company coding standards expressed as Avoid (anti-patterns) and Prefer (recommended patterns) to in-code patterns only. For file and folder naming and structure, use react-files-structure-standards.
Source of truth (priority order)
When resolving standards, use this order:
- Project tooling: ESLint config (
eslint.config.js/.eslintrc*), TypeScript config (tsconfig.json,tsconfig.app.json). Runyarn lintornpm run lint; fix auto-fixable issues first. - Reference files in
references/(see table below) for Avoid/Prefer rules and examples. - Reference codebase (if provided): e.g. a frontend app under the same org — use it to infer naming, structure, and patterns (hooks returning data only,
FunctionComponent+ destructured props,*.utils.ts/*.store.ts, test style with Vitest or Jest).
Reference categories
Standards are defined in the references/ folder. Load these files when you need the exact Avoid/Prefer rules and examples:
| Category | File | Scope |
|---|---|---|
| Coding patterns | references/common-coding-patterns.md | TypeScript (types, control flow, errors, enums, destructuring, etc.) |
More from lichens-innovation/skills
react-single-responsibility
Strategies to simplify components, hooks, and methods: decomposition order (utilities, hooks, sub-components), early returns, control flow, parameter design, and code smell fixes. Use when the user says: ungodify this method/function/component, simplify this method/function/component, make this method/function/component less complex; or when refactoring a large component, hook, or function, reducing complexity, applying single responsibility, or asking how to simplify a component, hook, or method.
30generate-pr-description
Generates pull request descriptions by comparing current branch with parent branch. Creates semantic commit-style PR titles and fills PR templates. Use when the user asks to generate PR description, prepare pull request, or create merge request description. The user may include ticket IDs in the request (e.g. tickets: NN-123, TB-456) from the company tracking system; treat those as the related issue IDs for the PR.
28review-staged-changes
Reviews staged git changes for code quality, maintainability, readability, and potential regressions. Verifies changes make sense in context, improve maintainability, enhance readability, and don't introduce side effects. Use when reviewing staged changes, examining git diffs, or when the user asks to review modifications before committing.
25hello-world
This skill welcomes users in ASCII art with OS information. Use when the user says 'hello' or 'hi'.
20typescript-and-react-guidelines
|
10single-responsibility
|
6