code-style
Code style rules for readable, maintainable implementation. Load this skill always when writing or editing code, and whenever the user asks about code style, refactoring shape, function/file size, object-oriented structure, helper ordering, or comments. For Frappe-specific work, prefer frappe-app-dev.
Datos de origen
- Repositorio
- frappe/skills
- Última actividad en el origen
- 12 de agosto de 2026 a las 06:32
- Idioma detectado de SKILL.md
- inglés
- Estrellas
- 146
- Forks
- 46
Opciones de instalación
De forma predeterminada está seleccionado el prompt que primero revisa el origen. Puedes cambiar a un comando directo o descargar una copia local.
Revisa los archivos de origen
Lee SKILL.md y los archivos complementarios que muestra SkillsMP antes de decidir si quieres instalarlo.
Mostrando SKILL.md
SKILL.md
Instrucciones de origen · Vista previa de solo lectura- name
- code-style
- description
- Code style rules for readable, maintainable implementation. Load this skill always when writing or editing code, and whenever the user asks about code style, refactoring shape, function/file size, object-oriented structure, helper ordering, or comments. For Frappe-specific work, prefer frappe-app-dev.
# Code Style Rules
- Keep functions small. Split when a function has multiple jobs or needs sections to be readable.
- Keep files under 300 lines when practical. Split by responsibility, not by arbitrary layer.
- Prefer object-oriented code over scattered functions.
- Put higher-order/public functions near the top of the file; keep low-level utilities at the bottom.
- Write terse, simple English comments. Explain why something is surprising; do not narrate obvious code.
- Do not add abstractions until there are repeated concrete uses.
Ver en GitHub