Add mix-and-match development patterns recipe for tasking Claude

[Copilot]

VibeScript enforces governance (what/where AI can modify) but lacks a system for defining coding style and practices (how AI writes code). Teams need consistent, reusable patterns for YAGNI, DRY, testing, documentation, etc. when tasking Claude.

Added Documentation

Core Pattern System (docs/development-patterns.md - 866 lines)

• YAGNI, DRY, SOLID with strict/moderate/relaxed variants
• Testing strategies (TDD, test-after, critical-path)
• Error handling (fail-fast, graceful degradation, result types)
• Documentation levels (full JSDoc, public APIs, self-documenting)
• Code organization (domain-driven, layer-based, feature-based)
• Pre-built bundles: "Strict & Safe", "Production Ready", "Move Fast", "Prototype/MVP"
• Production-Focused Directives: Comprehensive guidance for VibeScript's 5 new directives (security, performance, dependencies, observability, breaking) with examples at each pattern level

Quick Start Guide (docs/tasking-claude.md - 415 lines)

• Copy-paste task templates
• Pattern selection decision trees
• Troubleshooting matrix
• Pattern anti-combinations
• Integration notes for new production directives

Mad-Lib Template (.vibe/templates/claude-context.md.template - 230 lines)

• Checkbox-style pattern selection
• Project-specific rules, constraints, vocabulary
• Architectural decisions tracking
• Production directives section for security, performance, dependencies, observability, and breaking changes

Supporting Materials

• Real-world e-commerce API example (docs/example-setup.md - 378 lines)
• Print-friendly quick reference card (docs/patterns-quick-reference.md - 258 lines)

Total: 2,147 lines of comprehensive documentation

Usage Example

# .vibe/claude-context.md
Claude, use: Moderate YAGNI, Moderate DRY, TDD with 80% coverage,
JSDoc for public APIs, Fail-fast at boundaries, Atomic commits

Custom Rules:
- All DB queries use repository pattern
- API responses follow JSON:API spec
- No business logic in controllers

Then task Claude:

Claude, read .vibe/claude-context.md and implement user registration

or mix ad-hoc:

Claude, implement checkout flow using:
- Strict YAGNI (no speculation)
- High test coverage (80%+)
- Defense in depth security

Integration

• Merged with latest main branch changes (VibeScript 1.1.0 with 13 directives)
• Updated README.md with patterns section
• Updated .vibe/claude.instructions.md to reference pattern files
• All documentation updated to reflect 5 new production directives (security, performance, dependencies, observability, breaking)
• Provides pattern-level guidance (strict/moderate/relaxed) for each new directive
• 27+ cross-references between documentation files
• Complements existing VibeScript governance without code changes

Original prompt

Okay give claude a recipe of approaches to use when tasking. Such as YAGNI, DRY, etc. Common every day development patterns that when assigning Claude to a VibeScript powered project you can essentially mix and match or madlib Claude's starting instructions to conform to your expecations (or Claude can define starting expectations for future instances of himself).

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

[burtbyproxy]

There were changes to the main branch, please review and be sure your docs and everything line up with all of that.

[burtbyproxy]

There were changes on the main branch since you did this work, please update to cover that.

[Copilot]

There were changes to the main branch, please review and be sure your docs and everything line up with all of that.

Updated all documentation to align with main branch changes. Added comprehensive coverage of the 5 new production directives (security, performance, dependencies, observability, breaking) with examples at each pattern level. See commit 0dbb4af.

There were changes on the main branch since you did this work, please update to cover that.

Merged main branch and updated all documentation files to cover the new directives. Added "Production-Focused Directives" section to development-patterns.md with examples showing how to apply patterns at strict/moderate/relaxed levels for all 5 new directives. See commit 0dbb4af.