Execute qualquer Skill no Manus
com um clique

Execute qualquer Skill no Manus com um clique

common-best-practices

Estrelas533

Forks154

Atualizado14 de julho de 2026 às 18:20

Enforce SOLID principles, guard-clause style, function size limits, and intention-revealing naming across all languages. Use when refactoring for readability, applying clean-code patterns, reviewing naming conventions, or reducing function complexity.

Instalação

Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.

Executar no Manus

Fonte

HoangNguyen0403

HoangNguyen0403/agent-skills-standard

Abrir repositório GitHub Ver repositórios do creator

Download

Executar no Manus

Ocupações relacionadasSOC

Baseado na classificação ocupacional SOC

Desenvolvedores de softwareInformática e Matemática·SOC 15-1252

Explorador de arquivos

3 arquivos

SKILL.md

readonly

name	common-best-practices
description	Enforce SOLID principles, guard-clause style, function size limits, and intention-revealing naming across all languages. Use when refactoring for readability, applying clean-code patterns, reviewing naming conventions, or reducing function complexity.
metadata	{"triggers":{"files":["*/.ts","*/.tsx","*/.go","*/.dart","*/.java","*/.kt","*/.swift","*/.py"],"keywords":["solid","kiss","dry","yagni","naming","conventions","refactor","clean code"]}}

Global Best Practices

Priority: P0 (CRITICAL)

Core Principles

SOLID: Follow SRP (One reason to change), OCP (Open to extension), LSP, ISP, DIP.
KISS/DRY/YAGNI: Favor readability. Abstract repeated logic. No " in case" code.
Naming: Use intention-revealing names (isUserAuthenticated > checkUser). Match language casing.

Code Hygiene

Size Limits: Functions < 30 lines. Services < 600 lines. Utils < 400 lines.
Early Returns: Use guard clauses. Avoid deep nesting.
Comments: Explain why, not what. Refactor bad code; don't comment it.
Input: Validate/sanitize all external inputs.

Anti-Patterns

No Hardcoded Constants: Use named config/env vars.
No Deep Nesting: Use guard clauses.
No Global State: Prefer dependency injection.
No Empty Catches: Always handle, log, or rethrow.

References

Code Structure Patterns — file/function organization
Effectiveness Guide — practical application examples

Mais deste repositório

mesmo repositório

common-code-review

HoangNguyen0403/agent-skills-standard

Conduct high-quality, persona-driven code reviews. Use when reviewing PRs, critiquing code quality, or analyzing changes for team feedback.

2026-07-14533

common-context-optimization

HoangNguyen0403/agent-skills-standard

Maximize context window efficiency, reduce latency, and prevent lost-in-middle issues through strategic masking and compaction. Use when token budgets are tight, tool outputs overflow the context, conversations drift from intent, or latency spikes from cache misses.

2026-07-14533

common-dast-tooling

HoangNguyen0403/agent-skills-standard

Standardize dynamic application security testing for backend APIs, frontend web apps, and mobile clients. Covers ZAP, Nuclei, Nikto, sqlmap, ffuf, browser automation, mobile proxy interception, and AI-driven curl probes. Use when advising on or running dynamic security scans on local/staging environments.

2026-07-14533

common-debugging

HoangNguyen0403/agent-skills-standard

Troubleshoot systematically using the Scientific Method. Use when debugging crashes, tracing errors, diagnosing unexpected behavior, or investigating exceptions.

2026-07-14533

common-documentation

HoangNguyen0403/agent-skills-standard

Write effective code comments, READMEs, and technical documentation following intent-first principles. Use when adding comments, writing docstrings, creating READMEs, or updating any documentation.

2026-07-14533

common-feedback-reporter

HoangNguyen0403/agent-skills-standard

Pre-write audit for skill violations: checks planned code against loaded skill anti-patterns before any file write. Use when writing Flutter/Dart/TS code or editing SKILL.md files with active project skills. Load as composite; on auto-fixed violation, also load +common/common-learning-log.

2026-07-14533

name	common-best-practices
description	Enforce SOLID principles, guard-clause style, function size limits, and intention-revealing naming across all languages. Use when refactoring for readability, applying clean-code patterns, reviewing naming conventions, or reducing function complexity.
metadata	{"triggers":{"files":["*/.ts","*/.tsx","*/.go","*/.dart","*/.java","*/.kt","*/.swift","*/.py"],"keywords":["solid","kiss","dry","yagni","naming","conventions","refactor","clean code"]}}

Global Best Practices

Priority: P0 (CRITICAL)

Core Principles

SOLID: Follow SRP (One reason to change), OCP (Open to extension), LSP, ISP, DIP.
KISS/DRY/YAGNI: Favor readability. Abstract repeated logic. No " in case" code.
Naming: Use intention-revealing names (isUserAuthenticated > checkUser). Match language casing.

Code Hygiene

Size Limits: Functions < 30 lines. Services < 600 lines. Utils < 400 lines.
Early Returns: Use guard clauses. Avoid deep nesting.
Comments: Explain why, not what. Refactor bad code; don't comment it.
Input: Validate/sanitize all external inputs.

Anti-Patterns

No Hardcoded Constants: Use named config/env vars.
No Deep Nesting: Use guard clauses.
No Global State: Prefer dependency injection.
No Empty Catches: Always handle, log, or rethrow.

References

Code Structure Patterns — file/function organization
Effectiveness Guide — practical application examples