versioning
Versioning
Semantic versioning rules and workflow for consistent releases.
Semver Rules
Format: MAJOR.MINOR.PATCH (e.g., 1.4.2)
| Bump | When | Examples |
|---|---|---|
| MAJOR | Breaking changes | API removed, incompatible changes, major rewrites |
| MINOR | New features (backward compatible) | New endpoint, new option, new capability |
| PATCH | Bug fixes (backward compatible) | Fix crash, fix typo, fix edge case |
Decision Tree
Is it a breaking change?
├── Yes → MAJOR
More from bfmcneill/agi-marketplace
psychology-foundations
Use when you need to understand WHY certain UX patterns work. Covers cognitive psychology, behavioral science, and neuroscience foundations that underpin satisfying experiences.
13progressive-disclosure
Use when designing interfaces with complex functionality, settings panels, or expert features. Covers layering information so beginners aren't overwhelmed and experts aren't held back.
7design-patterns
Use when refactoring code or designing flexible systems. Covers creational, structural, and behavioral patterns with Python examples.
6sveltekit-builder
Use when building SvelteKit apps with Svelte 5. Covers runes, SSR, forms, and stack patterns (Kysely, Better Auth, shadcn-svelte).
4agent-behavior
Use at the start of any coding session to establish activity tracking and working patterns. Defines how the agent should document its work and communicate progress.
3feedback-design
Use when building loading states, progress indicators, success confirmations, or error messages. Covers feedback loops and patterns that feel satisfying.
3