Skip to content

Jorgut/dev-patterns-reference

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

2 Commits
 
 
 
 
 
 
 
 

Repository files navigation

Developer Patterns Reference

A consolidated collection of development patterns, best practices, and reference guides across multiple tech stacks. Originally crafted as AI coding assistant skills — now published as plain reference documents.

Positioning

This repository is a reference library, not an executable agent skill package.

It is meant to preserve reusable engineering judgment in a format that is easy for humans and AI coding agents to inspect. Individual documents may later be promoted into dedicated SKILL.md packages, but the repository itself should remain a stable, searchable source of development patterns.

Use it when you need:

  • A quick reminder of proven implementation patterns
  • A checklist before designing or reviewing a feature
  • Source material for creating or improving agent skills
  • Team onboarding notes for common backend, frontend, testing, security, and DevOps practices

Do not use it as:

  • A drop-in replacement for framework documentation
  • A dependency or installable package
  • A canonical security standard without project-specific review
  • A source of live compatibility guarantees for rapidly changing libraries

Contents

patterns/
├── backend/
│   ├── backend-patterns.md     # Node.js/Express API patterns
│   ├── coding-standards.md     # TypeScript/JS/React coding standards
│   ├── jpa-patterns.md         # JPA/Hibernate entity & query patterns
│   └── postgres-patterns.md    # PostgreSQL optimization & schema design
├── frameworks/
│   ├── django-patterns.md      # Django architecture & DRF patterns
│   ├── springboot-patterns.md  # Spring Boot layered architecture
│   ├── golang-patterns.md      # Idiomatic Go patterns
│   ├── python-patterns.md      # Pythonic idioms & PEP 8
│   ├── java-coding-standards.md # Java/Spring Boot coding conventions
│   └── clickhouse-io.md        # ClickHouse analytical queries
├── frontend/
│   └── frontend-patterns.md    # React/Next.js/state management
├── testing/
│   ├── python-testing.md       # pytest, fixtures, mocking, parametrization
│   ├── golang-testing.md       # Table-driven tests, benchmarks, fuzzing
│   ├── cpp-testing.md          # GoogleTest/CTest configuration
│   ├── django-tdd.md           # pytest-django, factory_boy, coverage
│   ├── springboot-tdd.md       # JUnit 5, Mockito, Testcontainers
│   └── tdd-workflow.md         # TDD methodology (framework-agnostic)
├── security/
│   ├── django-security.md      # CSRF, XSS, SQL injection prevention
│   └── springboot-security.md  # Spring Security authn/authz
└── devops/
    ├── django-verification.md  # Django deployment readiness
    ├── springboot-verification.md # Spring Boot deployment readiness
    └── continuous-learning.md  # Extracting patterns from sessions

Usage

Read the relevant file when working with the corresponding technology. Each file is self-contained and can be used:

  • As a quick reference during development
  • As a guide for setting up new projects
  • As a checklist for code reviews
  • As onboarding material for new team members
  • As reference material when drafting focused agent skills

Maintenance Policy

Maintenance priority: medium.

This repository is worth keeping because it contains broad, reusable engineering knowledge, but it should be updated selectively rather than constantly.

Recommended update triggers:

  • A framework or language has a major release that changes common practice
  • A pattern becomes risky, deprecated, or misleading
  • A repeated project lesson deserves to be captured once and reused
  • A document is promoted into a dedicated skill and needs a back-reference

Recommended review cadence:

  • Quarterly scan for stale guidance
  • Ad-hoc updates after real project lessons
  • Annual pruning of duplicated or low-value notes

Promotion To Skills

Convert a document into a standalone skill only when it has:

  • A clear trigger condition
  • A repeatable workflow
  • Concrete checks or examples
  • Enough depth to guide an agent without extra context

Until then, keep the material here as reference documentation.

License

MIT

About

Consolidated collection of development patterns and best practices across multiple tech stacks

Topics

Resources

Stars

Watchers

Forks

Releases

Packages

Contributors