How do I install the Ns Best Practices skill?

Run npx skillmds@latest add nextstage-brasil/ns-best-practices in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Ns Best Practices safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Ns Best Practices?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Ns Best Practices free to use?

Yes. Installing skills from SkillMD is free. This skill is licensed under Apache-2.

Who published Ns Best Practices?

nextstage-brasil (@nextstage-brasil) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Ns Best Practices by nextstage-brasil

Name: Ns Best Practices
Author: nextstage-brasil

Ns Best Practices

(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).

File contents

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

Scope — web app surface, API gateway, static assets, or prototype/.
Baseline — read references/checklist.md; tick only applicable sections (offline security/compat/a11y).
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).
Scan — configs (nginx, Vite, Next, Laravel middleware, etc.); no stack assume.
Report — findings table: severity, location (file:line when possible), recommendation, effort.
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

---name: ns-best-practicesdescription: (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---# Best PracticesFocused **quality + security hygiene** pass — not substitute for senior code review or visual design direction.## Session bootSee `../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` |## Workflow1. **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

Frequently asked questions