mcpField
N
ns-code-best-practices

ns-code-best-practices

github.com/nextstage-brasilSecurity054 installsUpdated 5d ago
Repository

About ns-code-best-practices

A focused quality and security hygiene skill for web apps, APIs, and static assets. It checks applicable security, compatibility, and accessibility concerns, then reports findings or makes minimal fixes when requested.

Key features

  1. 01Security configuration and dependency checks
  2. 02Browser compatibility review
  3. 03Accessibility quick checks
  4. 04Guideline-based UI audits
  5. 05Findings with severity and recommendations

Use cases

  1. 01Checking security headers and CSP
  2. 02Sweeping dependencies for known CVEs
  3. 03Reviewing web accessibility basics
  4. 04Auditing UI against guidelines

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/nextstage-brasil/skills --skill ns-code-best-practices

After installing, type/ns-code-best-practicesin Claude Code to confirm it loaded.

Bundled files

References and scripts installed along with SKILL.md.

evals/
evals.json
references/
checklist.md
ui-guidelines-review.md

Details

From the project README

Best Practices

Focused quality + security hygiene pass — not substitute for senior code review or visual design direction.

Harness discovery

See ../ns-harness/references/harness-discovery.md. Read architecture-rules.md + security-related harness rules.

When to use

RequestThis skillUse instead
Security headers / CSP / HSTSYes—
Dependency audit / known CVE sweepYes—
Browser compatibility baselineYes—
Accessibility quick pass (landmarks, alt, labels)Yes—
"Review my UI" / Web Interface Guidelines / UX a11y auditYes (guidelines fetch)—
Distinctive visual redesign / anti-slop aestheticsNons-code-frontend-design
"Review this MR" / SOLID deep diveNons-code-reviewer
New feature implementationNons-code-coder / ns-spec-driven

Workflow

  1. Scope — web app surface, API gateway, static assets, or {product_root}/prototype/; confirm {product_root}.
  2. Baseline — read references/checklist.md; tick only applicable sections (offline security/compat/a11y).
  3. Guidelines — UI/a11y/UX audit or invoker is ns-proto-creator close-out: follow references/ui-guidelines-review.md (WebFetch required).
  4. Scan — configs (nginx, Vite, Next, Laravel middleware, etc.); no stack assume.
  5. Report — findings table: severity, location (file:line when possible), recommendation, effort.
  6. Fix — minimal safe diffs when user asked implement; else report only.

Overlap with other skills

  • This skill: cross-cutting hygiene + Web Interface Guidelines compliance.
  • ns-code-frontend-design: distinctive look, typography, motion, anti–generic AI UI.
  • ns-code-reviewer: change-specific SOLID, tests, maintainability on diff.

Delivery may use sequentially — face skills route explicit.

Forbidden

  • Declare production secure without evidence
  • Break existing integrations without calling out risk
  • Replace threat modeling for high-risk domains (escalate to human)
  • Skip guidelines fetch on UI audit / proto close-out and claim full UI pass

Comments

Markdown supported