mirror of
https://github.com/affaan-m/everything-claude-code.git
synced 2026-02-08 07:33:08 +08:00
86b5a53e5d
* refactor(rules): restructure rules into common + language-specific directories - Split 8 flat rule files into common/, typescript/, python/, golang/ - common/ contains language-agnostic principles (no code examples) - typescript/ extracts TS/JS specifics (Zod, Playwright, Prettier hooks, etc.) - python/ adds Python rules (PEP 8, pytest, black/ruff, bandit) - golang/ adds Go rules (gofmt, table-driven tests, gosec, functional options) - Replace deprecated ultrathink with extended thinking documentation - Add README.md with installation guide and new-language template Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com> * Fix installation commands for rules Updated installation instructions to copy all rules to a single directory. * docs: update README.md to reflect new rules directory structure Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com> --------- Co-authored-by: Hor1zonZzz <Hor1zonZzz@users.noreply.github.com> Co-authored-by: Claude Opus 4.5 <noreply@anthropic.com>
32 lines
1022 B
Markdown
32 lines
1022 B
Markdown
# Common Patterns
|
|
|
|
## Skeleton Projects
|
|
|
|
When implementing new functionality:
|
|
1. Search for battle-tested skeleton projects
|
|
2. Use parallel agents to evaluate options:
|
|
- Security assessment
|
|
- Extensibility analysis
|
|
- Relevance scoring
|
|
- Implementation planning
|
|
3. Clone best match as foundation
|
|
4. Iterate within proven structure
|
|
|
|
## Design Patterns
|
|
|
|
### Repository Pattern
|
|
|
|
Encapsulate data access behind a consistent interface:
|
|
- Define standard operations: findAll, findById, create, update, delete
|
|
- Concrete implementations handle storage details (database, API, file, etc.)
|
|
- Business logic depends on the abstract interface, not the storage mechanism
|
|
- Enables easy swapping of data sources and simplifies testing with mocks
|
|
|
|
### API Response Format
|
|
|
|
Use a consistent envelope for all API responses:
|
|
- Include a success/status indicator
|
|
- Include the data payload (nullable on error)
|
|
- Include an error message field (nullable on success)
|
|
- Include metadata for paginated responses (total, page, limit)
|