coding-standards
Improve TypeScript, React, and API Code
Teams need consistent code quality guidance across TypeScript, JavaScript, React, Node.js, and APIs. This skill provides clear standards, review prompts, and practical examples for maintainable code.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "coding-standards" from https://skillstore.io/skills/sickn33-coding-standards.md and its manifest at https://skillstore.io/api/skills/sickn33-coding-standards/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.Your Agent should still show its plan and request any confirmation required by the security policy.
Agent-readable resources
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Test it
Using "coding-standards". A React component uses untyped props and updates state from stale values.
Expected outcome:
- Add explicit prop types so callers receive useful errors.
- Use functional state updates when the next value depends on the previous value.
- Keep rendering branches simple and avoid deeply nested conditions.
Using "coding-standards". An API endpoint returns different response shapes for success and failure.
Expected outcome:
The review recommends one response envelope, clear error messages, status-specific responses, and validation before business logic runs.
Using "coding-standards". A feature contains a long function that validates, transforms, and saves data.
Expected outcome:
The review suggests splitting validation, transformation, and persistence into named helpers, then adding tests for each behavior.
Security Audit
SafeAll 67 static findings are false positives from Markdown examples and illustrative TypeScript, React, API, testing, and performance snippets. No prompt injection, executable automation, data exfiltration, or system reconnaissance intent was found in SKILL.md.
Risk Factors
⚡ Contains scripts (1)
⚙️ External commands (53)
🌐 Network access (2)
Share & cite this report
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
Copy report link
https://skillstore.io/skills/sickn33-coding-standards/audits/4?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/sickn33-coding-standards?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/sickn33-coding-standards?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/sickn33-coding-standards/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/sickn33-coding-standards.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Academic citations (APA · BibTeX · CFF)
APA citation
affaan-m. (2026). coding-standards security audit report (audit version 4) [Author version 1.0]. Skillstore. https://skillstore.io/skills/sickn33-coding-standards/audits/4BibTeX citation
@techreport{affaan-m-sickn33-coding-standards-2026,
author = {affaan-m},
title = {coding-standards security audit report (audit version 4)},
institution = {Skillstore},
year = {2026},
number = {4},
url = {https://skillstore.io/skills/sickn33-coding-standards/audits/4},
note = {Author version 1.0}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "coding-standards security audit report (audit version 4)"
version: "1.0"
type: report
authors:
- name: "affaan-m"
date-released: "2026-07-06"
url: "https://skillstore.io/skills/sickn33-coding-standards/audits/4"
identifiers:
- type: other
value: "skillstore:sickn33-coding-standards:audit:4"
description: "Skillstore immutable audit report identifier"
Compare variants
2 installable variantsEach author remains a separate installable skill. The recommended variant is ranked by Skillstore evidence.
Why this variant is first
5minfutures-coding-standards
2026-08-21
sickn33-coding-standards
2026-08-21
Skillstore Score
Why this score Evidence Confidence: HighWhat You Can Build
Review pull requests
Check changed code for naming, type safety, immutability, error handling, and readable structure.
Create team standards
Turn broad quality principles into a shared checklist for frontend, backend, and API work.
Guide AI coding sessions
Ask an AI assistant to apply consistent patterns while editing TypeScript, React, or Node.js code.
Try These Prompts
Review this TypeScript or JavaScript code against the coding standards. Focus on naming, readability, immutability, types, and simple structure. List the highest priority fixes first.
Review this React component for prop typing, state updates, custom hook usage, conditional rendering, and maintainability. Suggest focused changes without changing behavior.
Review this API endpoint design for REST conventions, response consistency, input validation, error handling, and pagination. Explain which changes improve reliability.
Audit this feature against the full coding standards. Cover architecture, file organization, performance, tests, documentation, and code smells. Separate required fixes from optional improvements.
Best Practices
- Provide the code, framework, and project constraints before asking for review.
- Ask for prioritized findings when reviewing large changes or multiple files.
- Validate suggested refactors with tests, type checks, and team conventions.
Avoid
- Treating every example as mandatory architecture for every project.
- Requesting broad rewrites without explaining behavior that must remain stable.
- Skipping tests, type checks, and review after applying suggested changes.