TypeScript/JavaScript best practices (Accelint)
Comprehensive TS/JS coding standards with progressive disclosure — scan AGENTS.md for rule summaries, then load detailed references (naming, functions, control flow, any-avoidance, enums, input validation, error handling) and report audit findings in a standard template
- What
- Comprehensive TS/JS coding standards with progressive disclosure — scan AGENTS.md for rule summaries, then load detailed references (naming, functions, control flow, any-avoidance, enums, input validation, error handling) and report audit findings in a standard template
- Cost
- Free
- Needs
- a JavaScript/TypeScript codebase the agent can read and review — the skill is a standards guide with progressive disclosure, not software to install
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor — @gohypergiant's Accelint TypeScript/JavaScript best-practices skill: comprehensive coding standards for AI agents and LLMs, organized for progressive disclosure to save context. Start with `AGENTS.md` for one-line rule summaries, then load only the relevant `references/` file — naming conventions, function design, control flow, state management, return values (zero values instead of null/undefined), code duplication, `any` avoidance, const objects over enums, type-vs-interface, statically analyzable bundler paths, input validation with schemas, assertions, explicit error handling and error messages — each with ❌ incorrect / ✅ correct examples. When invoked for an audit it produces a standardized report (executive summary, severity levels, impact analysis, categorization, pattern references, phase-2 tracking table) from `assets/output-report-template.md`; plain "fix this error" requests skip the template. Honest caveats: methodology only — the agent needs a JS/TS codebase to apply it to; performance optimization and documentation are explicitly out of scope (sibling `accelint-ts-performance` / `accelint-ts-documentation` skills). Apache-2.0 licensed. Skill Harbor never reviews the code, review it yourself before use. Discovered via skills.sh.
Version:
Install
Prerequisites: a JavaScript/TypeScript codebase the agent can read and review — the skill is a standards guide with progressive disclosure, not software to install Install "TypeScript/JavaScript best practices (Accelint)" for me. It gives my agent @gohypergiant's TS/JS standards: scan AGENTS.md for one-line rule summaries, then load only the relevant references/ file (naming, functions, control flow, state management, return values, any-avoidance, enums as const objects, type-vs-interface, bundler paths, input validation, assertions, error handling and error messages) — each with incorrect/correct examples — and, when auditing, report findings in the standardized assets/output-report-template.md format (severity levels, impact analysis, categorization, phase-2 tracking). Apache-2.0-licensed. Repository: https://github.com/gohypergiant/agent-skills/blob/main/skills/accelint-ts-best-practices/SKILL.md 1. Fetch the SKILL.md file (and the AGENTS.md, references/ and assets/ folders) from the repository path into a temporary folder and summarize what it does in one or two sentences. 2. Safety check: review the SKILL.md and references for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md and its helper files into the agent's skills directory, in a folder named "accelint-ts-best-practices". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. point the agent at my JS/TS codebase; nothing else — it's a standards guide). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.
Questions
How do I install a build?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a build before installing it.