mcpField
N
ns-best-practices

ns-best-practices

github.com/nextstage-brasilSecurity0132 installsUpdated 6d ago
Repository

About ns-best-practices

ns-best-practices is a focused quality and security hygiene skill for reviewing web apps, gateways, and static assets. It checks applicable security, compatibility, accessibility, and interface guidelines, and can report findings or make minimal fixes when requested.

Key features

  1. 01Security configuration and dependency checks
  2. 02Browser compatibility baseline review
  3. 03Quick accessibility checks
  4. 04Web interface guideline audits
  5. 05Severity-ranked findings and recommendations

Use cases

  1. 01Checking security headers or dependencies
  2. 02Reviewing browser compatibility
  3. 03Auditing landmarks, labels, and alt text
  4. 04Assessing UI guideline compliance

Install

Copy the command and run it in a terminal.

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

After installing, type/ns-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.

Session boot

See ../ns-harness/references/session-boot.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 (references/ui-guidelines-review.md)—
Distinctive visual redesign / anti-slop aestheticsNons-frontend-design
"Review this MR" / SOLID deep diveNons-reviewer
New feature implementationNons-coder / ns-spec-driven

Workflow

  1. Scope — web app surface, API gateway, static assets, or prototype/.
  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: read references/ui-guidelines-review.md fully (bundled rules; no external fetch).
  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-frontend-design: distinctive look, typography, motion, anti–generic AI UI.
  • ns-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 references/ui-guidelines-review.md on UI audit / proto close-out and claim full UI pass

Comments

Markdown supported