Skip to main content

code-quality

Coding style standards, security guidelines, and accessibility requirements. Use when (1) Writing new code, (2) Reviewing code for style/security, (3) Implementing UI/UX features, (4) Addressing security concerns, (5) Ensuring accessibility compliance. Covers naming conventions, formatting, security best practices (no secrets/PII), accessibility standards (semantic HTML, keyboard nav), and responsive design. Use when this capability is needed.

설치로 이동

소스 정보

저장소
tomevault-io/skills-registry
최근 소스 활동
2026년 4월 28일 22:53
감지된 SKILL.md 언어
영어
스타
1
포크
0

설치 방법

기본적으로 소스를 먼저 확인하는 Prompt가 선택됩니다. 직접 명령으로 전환하거나 로컬 사본을 다운로드할 수도 있습니다.

소스 파일 검토

설치 여부를 결정하기 전에 SKILL.md와 SkillsMP에 표시된 보조 파일을 읽어 보세요.

파일 탐색기
2 개 파일

SKILL.md 표시 중

SKILL.md
소스 지침 · 읽기 전용 미리보기
name
code-quality
description
Coding style standards, security guidelines, and accessibility requirements. Use when (1) Writing new code, (2) Reviewing code for style/security, (3) Implementing UI/UX features, (4) Addressing security concerns, (5) Ensuring accessibility compliance. Covers naming conventions, formatting, security best practices (no secrets/PII), accessibility standards (semantic HTML, keyboard nav), and responsive design. Use when this capability is needed.
metadata
{"author":"ainative-studio"}
# Code Quality Standards ## Coding Style * **Naming:** camelCase for vars/functions; PascalCase for classes/types * **Formatting:** 4-space indentation; target ≤80 chars (wrap thoughtfully) * **Comments:** Meaningful, current; delete stale comments * **Security:** Never log secrets/PII; validate inputs; least privilege by default * **Errors/Logs:** Explicit error types; structured logs by level; actionable messages ## Accessibility & UX Quality * Favor semantic roles/labels; keyboard nav and focus order must work * Include responsive checks at **375, 768, 1024, 1440** with notes/screenshots * Use deterministic test IDs; avoid brittle CSS/XPath ## Security & Compliance Guardrails * No real credentials in code, tests, or screenshots * Use test accounts/fixtures; redact secrets * Follow least-privilege and input validation * Document threat considerations in PR when relevant ## Reference Files See `references/coding-style.md` for detailed style guide, formatting rules, comment standards. See `references/security-checklist.md` for security validation checklist, threat modeling, PII handling. See `references/accessibility-standards.md` for WCAG compliance, semantic HTML patterns, keyboard nav testing. --- > Converted and distributed by [TomeVault](https://tomevault.io/claim/ainative-studio) — claim your Tome and manage your conversions. <!-- tomevault:4.0:skill_md:2026-04-14 -->
GitHub에서 보기