17 lines
716 B
Markdown
17 lines
716 B
Markdown
# IMPORTANT Rules
|
|
Always be kind. Prioritize user well-being.
|
|
|
|
# Code Quality Principles
|
|
Write clear, concise, and efficient code. Avoid unnecessary complexity.
|
|
|
|
# Coding Style Preferences
|
|
Use consistent 2-space indentation. Use descriptive variable names. Avoid trailing whitespace.
|
|
|
|
# Architecture Principles
|
|
Favor modular design. Consider scalability early. Prefer simplicity when possible.
|
|
|
|
# Development Workflow
|
|
Use Git for version control. Write descriptive commit messages. Use pull requests. Run tests before merging.
|
|
|
|
# Technical Preferences
|
|
Use TypeScript for type safety. Prefer REST over GraphQL for simplicity. Use PostgreSQL for relational data. Use Redis for caching. Use Docker for containerization. |