tlc-claude-code 1.5.7 → 1.5.9

package/.claude/commands/tlc/build.md

@@ -2,6 +2,40 @@
 
 Write failing tests, then implement to make them pass.
 
+## Engineering Standards
+
+**Code like a senior engineer with 15+ years experience.** Every line should reflect:
+
+### Code Quality
+- **Clean Architecture**: Separate concerns. Domain logic never depends on infrastructure.
+- **SOLID Principles**: Single responsibility, open/closed, Liskov substitution, interface segregation, dependency inversion.
+- **DRY but not premature**: Extract only after 3+ repetitions. Duplication is better than wrong abstraction.
+- **Meaningful names**: Variables, functions, classes should reveal intent. No abbreviations except industry standards.
+- **Small functions**: Each function does ONE thing. If you need comments to explain sections, extract them.
+
+### Defensive Programming
+- **Validate at boundaries**: All external input (user, API, file) gets validated immediately.
+- **Fail fast**: Throw early with clear error messages. Don't let bad state propagate.
+- **Handle edge cases**: null, undefined, empty arrays, empty strings, zero, negative numbers.
+- **Type safety**: Use TypeScript strictly. No `any` except when interfacing with untyped libs.
+
+### Performance Awareness
+- **O(n) thinking**: Know the complexity of your algorithms. Avoid nested loops on large datasets.
+- **Lazy loading**: Don't fetch/compute until needed.
+- **Caching**: Identify expensive operations and cache appropriately.
+- **Database queries**: No N+1. Use joins, batch operations, proper indexes.
+
+### Security First
+- **Never trust input**: Sanitize, escape, parameterize.
+- **Least privilege**: Functions/modules only access what they need.
+- **No secrets in code**: Environment variables for all credentials.
+- **Audit trail**: Log security-relevant actions.
+
+### Testability
+- **Dependency injection**: Pass dependencies, don't import singletons.
+- **Pure functions**: Same input = same output. No hidden state.
+- **Mockable interfaces**: Code to interfaces, not implementations.
+
 ## What This Does
 
 1. **Write failing tests** for all tasks in the phase

package/.claude/commands/tlc/plan.md

@@ -2,6 +2,26 @@
 
 Research and create implementation plans with clear tasks.
 
+## Architectural Standards
+
+**Plan like a principal engineer designing for scale:**
+
+### Structure
+- **Layered architecture**: UI → Application → Domain → Infrastructure
+- **Bounded contexts**: Group related functionality, minimize coupling
+- **Dependency direction**: Always point inward (infrastructure depends on domain, never reverse)
+
+### Design Decisions
+- **Interface-first**: Define contracts before implementations
+- **Extension points**: Where will this need to grow? Plan for it.
+- **Error boundaries**: Where can failures occur? How are they handled?
+- **Data flow**: How does data enter, transform, and exit the system?
+
+### Task Breakdown
+- **Vertical slices**: Each task delivers testable, visible progress
+- **Risk-first**: Tackle unknowns and integrations early
+- **Dependencies explicit**: Mark what blocks what
+
 ## What This Does
 
 1. Researches how to implement the phase

package/.claude/commands/tlc/quick.md

@@ -2,6 +2,16 @@
 
 For ad-hoc tasks that don't need full phase planning, but still deserve tests.
 
+## Engineering Standards
+
+Even quick tasks follow senior engineer standards:
+- **Clean code**: Meaningful names, single responsibility, no magic values
+- **Defensive**: Validate input, handle edge cases, fail fast
+- **Secure**: No hardcoded secrets, sanitize user input
+- **Testable**: Pure functions, injected dependencies
+
+Quick doesn't mean sloppy. Every line should be production-ready.
+
 ## What This Does
 
 1. **Ask what you want to do**

package/.claude/commands/tlc/review.md

@@ -145,11 +145,35 @@ fi
 2. **Invoke each configured provider** (one chunk at a time if split):
 
 ```bash
-# For Codex (GPT-5.2) - use file attachment
-codex --print "Review this code diff for quality issues, bugs, security vulnerabilities, and test coverage. Respond with APPROVED or CHANGES_REQUESTED. File: /tmp/review-diff.patch"
-
-# For Gemini - use file attachment
-gemini --print "Review this code diff for quality and security issues. File: /tmp/review-diff.patch"
+# For Codex (GPT-5.2) - detailed review prompt
+codex --print "You are a senior code reviewer. Analyze this diff thoroughly:
+
+1. **Line-by-line Analysis**: Comment on specific lines with issues
+2. **Bugs**: Identify potential bugs, edge cases, null checks
+3. **Security**: SQL injection, XSS, command injection, auth issues
+4. **Performance**: N+1 queries, unnecessary loops, memory leaks
+5. **Code Quality**: Naming, duplication, complexity, SOLID principles
+6. **Test Coverage**: Are the changes properly tested?
+
+For each issue found:
+- File and line number
+- Severity (critical/high/medium/low)
+- What's wrong
+- How to fix it
+
+End with: APPROVED (no critical/high issues) or CHANGES_REQUESTED (has critical/high issues)
+
+File: /tmp/review-diff.patch"
+
+# For Gemini - detailed review prompt
+gemini --print "Review this code diff as a senior engineer. Provide:
+- Specific line-by-line feedback
+- Security vulnerabilities with file:line references
+- Performance concerns
+- Code quality issues
+- Missing test coverage
+
+Be thorough and specific. File: /tmp/review-diff.patch"
 ```
 
 **Large Diff Handling:**

package/.claude/commands/tlc/tlc.md

@@ -2,6 +2,18 @@
 
 One command. Context-aware. Visual dashboard.
 
+## Engineering Mindset
+
+**All TLC code generation follows senior engineer standards:**
+- Clean architecture with separated concerns
+- SOLID principles strictly applied
+- Defensive programming with validation at boundaries
+- Performance-aware (O(n) thinking, no N+1 queries)
+- Security-first (no secrets in code, sanitize all input)
+- Fully testable (dependency injection, pure functions)
+
+See `/tlc:build` for the complete engineering standards checklist.
+
 ## What This Does
 
 Launches the TLC dashboard - a visual interface showing project state, phases, tests, and next actions.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "tlc-claude-code",
-  "version": "1.5.7",
+  "version": "1.5.9",
   "description": "TLC - Test Led Coding for Claude Code",
   "bin": {
     "tlc": "./bin/tlc.js",