Skip to main content
skill CX Codex

ns-best-practices — Claude Code skill: what it does, how to install

ns-best-practices runs security header audits, checks basic accessibility, and reviews UI against Web Interface Guidelines. Generates structured findings with file locations.

Apache-2.0 154 installs updated 2026-10-24

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add nextstage-brasil/skills --skill ns-best-practices -a claude-code
Open on GitHub

What ns-best-practices does

The skill runs baseline security and interface hygiene checks across web apps, APIs, and static assets. It inspects setup files for Nginx, Vite, Next.js, or Laravel middleware without assuming a specific stack. Scans cover CSP, CORS, HSTS configurations, known CVE vulnerabilities, and accessibility essentials like alt text and labels.

The review workflow uses local files. It consults references/checklist.md and evaluates UI elements against bundled Web Interface Guidelines without fetching remote assets. Findings are compiled into a markdown table with severity rankings, exact file:line locations, recommendations, and effort estimates. By default, it stays in audit mode and only writes minimal diffs when asked.

It depends directly on ns-harness. The rules forbid declaring any deployment secure without evidence, meaning high-stakes threat modeling must still go to human engineers.

What it helps with

  • audit security headers including CSP, CORS, and HSTS
  • scan project dependencies for known CVE vulnerabilities
  • evaluate markup against accessibility basics like landmarks and labels
  • review interfaces against Vercel Web Interface Guidelines

Example prompts for the agent

  • Check our Nginx and Vite configs for missing security headers and CSP rules
  • Run a quick accessibility audit on the landing page forms
  • Review the prototype against Web Interface Guidelines and list findings

How to install ns-best-practices

1Skills CLI (Vercel)

npx skills add nextstage-brasil/skills --skill ns-best-practices -a claude-code

2Manually: put the files in place

~/.claude/skills/ns-best-practices/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/ns-best-practices/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about ns-best-practices

How to install ns-best-practices in Claude Code?

Run npx skills add nextstage-brasil/skills --skill ns-best-practices -a claude-code. The files install directly to ~/.claude/skills/ns-best-practices/SKILL.md.

What does ns-best-practices inspect?

It scans server headers, flags known CVEs in packages, validates accessibility tags, and tests UI against offline Web Interface Guidelines.

Can ns-best-practices replace deep threat modeling?

No. The skill is instructed never to declare production secure on its own and requires handing high-risk threat analysis over to human reviewers.

Source text

SKILL.md · Apache-2.0
---
name: ns-best-practices
description: "(NS) Security/compat/a11y + Vercel Web Interface Guidelines. Use when hardening security, fixing CSP/CORS/headers, reviewing UI / checking a11y / auditing UX, or Web Interface Guidelines — even without saying \"best practices\"; also ns-proto-creator close-out. Do NOT use for MR/SOLID (ns-reviewer), visual redesign (ns-frontend-design), or features (ns-coder / ns-spec-driven)."
license: Apache-2.0
metadata:
  author: nextstage-brasil
  version: "1.1"
depends:
  - ns-harness
---

# 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

| Request | This skill | Use instead |
| ------- | ---------- | ----------- |
| Security headers / CSP / HSTS | Yes | — |
| Dependency audit / known CVE sweep | Yes | — |
| Browser compatibility baseline | Yes | — |
| Accessibility quick pass (landmarks, alt, labels) | Yes | — |
| "Review my UI" / Web Interface Guidelines / UX a11y audit | Yes (`references/ui-guidelines-review.md`) | — |
| Distinctive visual redesign / anti-slop aesthetics | No | `ns-frontend-design` |
| "Review this MR" / SOLID deep dive | No | `ns-reviewer` |
| New feature implementation | No | `ns-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

© nextstage-brasil · Apache-2.0 · nextstage-brasil/skills

Similar skills

All skills for Security →

From the same set20

The whole set →
ns-project-manager ns-project-manager is a Claude Code skill that turns meeting transcripts and briefs into project artifacts, forecasts, and reports. CX Codex +1 185installs ns-langgraph-agents ns-langgraph-agents — a skill for Claude Code, Codex, Cursor and other platforms that guides LangGraph.js agent-api development from initial bootstrap through graph-spec sync. CX Codex +1 171installs ns-execution-gitlab-issue ns-execution-gitlab-issue executes GitLab issues end-to-end with worktree isolation, automated status changes, atomic delivery, and merge requests. CX Codex +1 165installs ns-requirements-enricher ns-requirements-enricher turns one GitLab issue or a pasted scope into an implementation brief for a coding agent, grounded in the existing code, with blocking questions kept in chat. CX Codex +1 163installs ns-investigator The ns-investigator skill for Claude Code reads stack traces, logs and failing tests, identifies the root cause and proposes a minimal fix without implementing it. CX Codex +1 153installs ns-frontend-design ns-frontend-design — a skill for Claude Code, Codex, Cursor and other agents that builds production UI with deliberate typography, hierarchy and motion. Activates on pages, components, dashboards, forms and analytics views. CX Codex +1 153installs ns-autonomous ns-autonomous — a skill for Claude Code, Codex, Cursor, Copilot and Gemini CLI that takes a local plan or pasted text and runs it autonomously inside an isolated worktree. CX Codex +1 152installs ns-e2e-tests The ns-e2e-tests skill structures Cypress end-to-end work across devices and keeps tests in a separate project. Use it when adding or refactoring specs. CX Codex +1 151installs

Project sponsors

Companies that keep this analytics open