app-standards
All modes that write scripts or code follow these app standards for communication, modularization, simplification, naming conventions
Best use case
app-standards is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
All modes that write scripts or code follow these app standards for communication, modularization, simplification, naming conventions
Teams using app-standards should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/app-standards/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How app-standards Compares
| Feature / Agent | app-standards | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
All modes that write scripts or code follow these app standards for communication, modularization, simplification, naming conventions
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Standards-all-modes instructions
### Communication
Be brief; don't echo user requests.
### Modularization
**Scope**: Critical for Python, JS, and logic files.
- **Exception**: Do NOT apply this to CSS.
**Hard Limit**:
- **Enforce** a maximum of **450 lines of code** per file.
- **Split** larger files: Create more files with fewer functions rather than exceeding this limit.
**Utility Strategy**:
- **Extract** logic liberally into utility folders.
- **Naming Convention**: Use `utils/` or `utils_db/`.
### Naming Conventions: Domain-First
**Rationale**: Group related code by **Domain** (Subject) first, then **Specific** (Action/Qualifier).
#### Core Pattern
**Invert the standard naming order**:
- **Bad**: `{specific}_{domain}` (e.g., `edit_user`)
- **Good**: `{domain}_{specific}` (e.g., `user_edit`)
**Casing Rules**:
- **snake_case**: Files, functions, variables, DB tables/columns.
- **PascalCase**: Classes.
#### Transformation Examples
| Type | Old Pattern | **New Pattern (Target)** | Note |
| **Files** | `admin_dashboard_utils.py` | `dashboard_utils_admin.py` | Domain is `dashboard` |
| **Functions** | `edit_user` | `user_edit` | Domain is `user` |
| **Classes** | `AdminPerson` | `PersonAdmin` | Better: Use `Person` w/ type param |
#### Scope & Restrictions
**When to Apply**:
- **New Code**: **Always** apply this pattern.
- **Existing Code**: Apply **only** if you are already actively editing the file.
**Do NOT rename without explicit approval**:
- **Public APIs**: HTTP routes, library exports, CLI flags.
- **Database**: Tables and columns (requires migration).
- **Standards**: `__init__.py`, `setUp()`, `settings.py` (Django).
#### Refactoring Checklist
**If you rename a symbol, you MUST fix all references.**
Before finishing, verify:
1. [ ] **Imports**: Updated in all other files?
2. [ ] **Calls**: Function/Class usage updated everywhere?
3. [ ] **Tests**: Do tests still pass?
4. [ ] **Docs**: Updated docstrings/comments?
5. [ ] **VS Code**: No errors in the Problems panel?Related Skills
dev_standards_skill
Development standards and architecture management skill. Enforces modular design, low coupling, clean code practices, and maintains project architecture graph for quick context understanding. Language-agnostic, works with TypeScript, Python, Go, Rust, Java, and more. Use when starting development tasks, refactoring, or analyzing project structure.
custom-project-standards
Hệ thống tiêu chuẩn dự án đa năng (Standard Platform). Hỗ trợ Frontend, Backend, DevOps với nhiều tùy chọn ngôn ngữ/framework.
coding-standards
Provides coding standards for React Native — performance patterns, consistency rules, and clean React architecture. Use when writing, modifying, or reviewing code.
cc-skill-coding-standards
Universal coding standards, best practices, and patterns for TypeScript, JavaScript, React, and Node.js development.
android-dev-standards
Standards, architecture patterns, and best practices for Android app development with Kotlin, Jetpack Compose, and Android Jetpack libraries using clean architecture and MVVM. Use for any Android coding, review, refactor, or design task, especially when acting as an AI coding agent that must follow established project conventions.
actionable-review-format-standards
Standardized output format for code reviews with severity labels, file:line references, and fix code snippets. Use when generating review reports that need consistent, actionable feedback structure.
accessibility-standards
Implement WCAG 2.1 accessibility standards for Vue 3 apps. Use when adding ARIA labels, keyboard navigation, screen reader support, or checking color contrast. Mentions "accessibility", "ARIA", "keyboard nav", "screen reader", or "color contrast".
code-standards
Setup universal code quality standards in your project. Use when the user wants to generate coding standards files (CLAUDE.md, AGENTS.md, GEMINI.md, etc.) or mentions 'code standards', 'code review setup', or similar intent in any language.
academic-writing-standards
Expert knowledge of academic writing standards for peer-reviewed papers, including citation integrity, style compliance, clarity, and scientific writing best practices. Use when reviewing or editing academic manuscripts, papers, or research documentation.
arweave-standards
GitHub repository skill for ArweaveTeam/arweave-standards
spring-boot-rest-api-standards
Provides REST API design standards and best practices for Spring Boot projects. Use when creating or reviewing REST endpoints, DTOs, error handling, pagination, security headers, HATEOAS and architecture patterns.
NestJS API Standards
Response wrapping, pagination, and error standardization.