@allthingsclaude/blueprints 0.3.0-beta.24 → 0.3.0-beta.25

package/content/agents/implement.md

@@ -128,6 +128,7 @@ For each task in the current phase:
 - Check git diff to review changes
 - Verify the change works as expected
 - **Convention adherence**: Does this code follow the patterns discovered in Step 1.5? If the project uses a specific styling method, did you use it? If there's an established feedback/notification system, did you use it instead of a raw alternative? If there's a custom hook or data fetching pattern, did you follow it?
+- **No inline styles**: Never add inline styles unless absolutely necessary (e.g., a dynamic value that can't be expressed as a class). If the project uses CSS modules, SCSS, Tailwind, or any other styling method — use that. Look at how existing components are styled and follow the same approach.
 - **Accessibility basics** (for UI tasks — modals, forms, dialogs, interactive elements): Labels associated with inputs, ARIA roles on overlays/modals, keyboard handling (Escape to close, focus trap in modals), visible focus indicators
 - **Data access patterns** (for tasks involving data fetching or transformation): No per-item queries inside loops or list iterations, batch operations where possible, efficient relationship loading
 
@@ -167,7 +168,8 @@ At the end of each phase:
    - No unnecessary duplication (e.g., identical handler functions across components that could be shared)
    - Consistent component structure and naming
    - If any inconsistencies are found, fix them before moving on
-5. **Ask user for approval** before moving to next phase:
+5. **DRY check**: Run `/dry` (or mentally audit the phase's code) to identify any repeated patterns, duplicated logic, or code that should be extracted into shared utilities, components, or constants. Fix any DRY violations before presenting to the user.
+6. **Ask user for approval** before moving to next phase:
 
 ```markdown
 🎯 **Phase 1 Complete**
@@ -193,7 +195,7 @@ At the end of each phase:
 Ready to commit this phase before moving to Phase 2? (yes/no/review)
 ```
 
-5. **Update STATE.md** after phase completion:
+7. **Update STATE.md** after phase completion:
    - **Always READ existing STATE.md first** to preserve `## Overview` table and `## Plans` sections
    - Update the `**Phase**` field in the header to the next phase number
    - Update the `**Status**` field if needed (keep `🚧 In Progress` during work, set `✅ Complete` when all phases done)

package/content/agents/parallelize.md

@@ -190,6 +190,8 @@ You are implementing Stream [N] of a parallelized plan execution.
 
 These are authoritative patterns from the existing codebase. Always follow them — never introduce a parallel approach for the same concern.
 
+**Inline styles**: Never add inline styles unless absolutely necessary (e.g., a truly dynamic value that can't be expressed as a class). Look at how existing components are styled and use the same approach.
+
 ## Important Context
 
 - Other streams are running in parallel
@@ -331,7 +333,17 @@ After type check and lint pass, review code from all streams for pattern alignme
 
 If any drift is found between streams, fix it to match the project's established conventions before reporting results.
 
-#### 5.4 Conflict Resolution
+#### 5.4 DRY Check
+
+After cross-stream consistency review, audit the combined code for DRY violations. Different agents may have independently created similar utilities, components, or patterns. Look for:
+- Duplicated helper functions or utilities across streams
+- Similar component patterns that could share a base
+- Repeated constants, types, or configurations
+- Any code that should be extracted into shared modules
+
+Fix violations before reporting results — consolidate duplicates into shared code.
+
+#### 5.5 Conflict Resolution
 
 If conflicts exist (shouldn't if partitioning was correct):
 1. Identify conflicting changes
@@ -339,7 +351,7 @@ If conflicts exist (shouldn't if partitioning was correct):
 3. Apply manual fix
 4. Document what happened
 
-#### 5.5 Update Plan
+#### 5.6 Update Plan
 
 Mark completed tasks in the plan document:
 

package/content/commands/implement.md

@@ -41,6 +41,7 @@ Launching the **implement agent** which will work independently in a separate co
 - ✅ Validate each phase before proceeding
 - ✅ Handle blockers (will pause and report)
 - ✅ Adapt plan if better approaches discovered
+- ✅ Run DRY checks after each phase to extract shared patterns
 - ✅ Return comprehensive summary when complete
 
 ### What You'll See

package/content/commands/kickoff.md

@@ -36,7 +36,7 @@ I'll work through this plan collaboratively with you:
 
 1. **Load & Review**: I'll load the plan and show you a summary
 2. **Environment Check**: Verify git status and project state
-3. **Convention Discovery**: Scan the codebase for established patterns (error handling, styling, state management, data fetching, test infrastructure) and share findings so we're aligned on which patterns to follow
+3. **Convention Discovery**: Scan the codebase for established patterns (error handling, styling, state management, data fetching, test infrastructure) and share findings so we're aligned on which patterns to follow. Look at how existing code is structured — never add inline styles unless absolutely necessary, always use the project's established styling method
 4. **Task Tracking**: Set up TodoWrite for all plan tasks
 5. **Step-by-Step**: Execute tasks one at a time with your input
 6. **Validation**: Run type checks and lints after each task
@@ -74,3 +74,5 @@ Then ask: "Ready to start implementing? Which phase should we tackle first?"
 Use TodoWrite to create todos for all tasks from the plan once user confirms.
 
 Then begin executing tasks step-by-step, staying in the main context, validating as you go.
+
+After completing each phase, run `/dry` to check if any repeated patterns or duplicated code should be extracted into shared utilities, components, or constants. Fix any DRY violations before moving to the next phase.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@allthingsclaude/blueprints",
-  "version": "0.3.0-beta.24",
+  "version": "0.3.0-beta.25",
   "description": "Claude Code commands and agents for enhanced AI-assisted development workflows",
   "type": "module",
   "main": "dist/index.js",