Template: Strengthen cs-design-python command and improve conventions guidance.

Address downstream feedback by: (1) Adding stronger practices guide compliance
enforcement with specific pattern examples for function signatures; (2) Adding
explicit language about implementations, especially for exceptions; (3) Removing
problematic text-editor MCP tools recommendations that Claude instances struggle
with. These changes ensure better adherence to project practices and cleaner
design-only outputs.

🤖 Generated with [Claude Code](https://claude.ai/code)

Co-Authored-By: Claude <noreply@anthropic.com>

Author: emcd

.auxiliary/configuration/claude/commands/cs-design-python.md

@@ -13,6 +13,7 @@ Stop and consult if:
 - Architectural decisions are needed instead of design specifications
 - Implementation details are requested instead of design specifications
 - Requirements analysis is needed instead of design specifications
+- User requests actual code implementations instead of specifications
 
 ## Context
 
@@ -63,11 +64,13 @@ Examine existing Python structure and patterns:
 - Document current design strengths and improvement opportunities
 
 ### 2. Interface Specification
-Define clean API boundaries and contracts:
-- Specify public interfaces using wide parameter, narrow return patterns
+Define clean API boundaries and contracts following practices guidelines:
+- All function and class signatures must follow @.auxiliary/instructions/practices.rst patterns exactly
+- Specify public interfaces using wide parameter, narrow return patterns (e.g., __.cabc.Sequence, __.cabc.Mapping for inputs)
+- Return narrow concrete types (list, dict, tuple, __.immut.Dictionary for outputs)
 - Design class hierarchies following Omniexception → Omnierror patterns
 - Apply appropriate naming conventions from nomenclature guidelines
-- Define type annotations using proper TypeAlias patterns
+- Define type annotations using proper TypeAlias patterns with __.typx.TypeAlias
 - Consider immutability preferences and container design patterns
 
 ### 3. Filesystem and Module Organization Design
@@ -80,20 +83,21 @@ Apply Python-specific organizational patterns and filesystem structure:
 - Plan type alias organization and dependency management
 
 ### 4. Class and Function Design
-Create maintainable Python structures:
-- Design class hierarchies with appropriate base classes and mixins
-- Specify function signatures with proper type annotations
-- Apply nomenclature patterns for methods, attributes, and functions
+Create maintainable Python structures following practices guide exactly:
+- Design class hierarchies with appropriate base classes and mixins (__.immut.Object, __.immut.Protocol, etc.)
+- Specify function signatures using practices guide patterns (wide inputs, narrow outputs, proper spacing)
+- Apply nomenclature patterns for methods, attributes, and functions from nomenclature guidelines
 - Design immutable data structures and container patterns
-- Plan dependency injection and configuration patterns
+- Plan dependency injection and configuration patterns with sensible defaults
 
 ### 5. Design Documentation
-Create comprehensive design specifications:
-- Document interface contracts and expected behaviors
-- Provide design examples following style guidelines
-- Specify exception handling patterns and error propagation
+Create comprehensive design specifications without implementations:
+- Provide only signatures, contracts, and interface specifications - no implementations
+- Do not provide exception class implementations, function bodies, or method implementations
+- Document interface contracts and expected behaviors (contracts only, not code)
+- Provide design examples using signatures and type annotations only
+- Specify exception handling patterns and error propagation (exception classes by name/signature only)
 - Document design rationale and trade-off decisions
-- Create interface specifications without implementation details
 
 ### 6. Design Validation
 Ensure design quality and consistency:

.auxiliary/configuration/conventions.md

@@ -15,9 +15,8 @@
 # Operation
 
 - Use `rg --line-number --column` to get precise coordinates for MCP tools that require line/column positions.
-- Prefer `text-editor` MCP tools over other text editing tools (line number-based edits are less error-prone).
-- Always reread files with `text-editor` tools after modifying files via other tools to avoid file hash conflicts.
-- Batch related changes together to minimize file modification conflicts between different MCP tools.
+- Choose appropriate editing tools based on the task complexity and your familiarity with the tools.
+- Batch related changes together when possible to maintain consistency.
 - Use relative paths rather than absolute paths when possible.
 - Do not write to paths outside the current project unless explicitly requested.
 - Use the `.auxiliary/scribbles` directory for scratch space instead of `/tmp`.

template/.auxiliary/configuration/claude/commands/cs-design-python.md

@@ -13,6 +13,7 @@ Stop and consult if:
 - Architectural decisions are needed instead of design specifications
 - Implementation details are requested instead of design specifications
 - Requirements analysis is needed instead of design specifications
+- User requests actual code implementations instead of specifications
 
 ## Context
 
@@ -63,11 +64,13 @@ Examine existing Python structure and patterns:
 - Document current design strengths and improvement opportunities
 
 ### 2. Interface Specification
-Define clean API boundaries and contracts:
-- Specify public interfaces using wide parameter, narrow return patterns
+Define clean API boundaries and contracts following practices guidelines:
+- All function and class signatures must follow @.auxiliary/instructions/practices.rst patterns exactly
+- Specify public interfaces using wide parameter, narrow return patterns (e.g., __.cabc.Sequence, __.cabc.Mapping for inputs)
+- Return narrow concrete types (list, dict, tuple, __.immut.Dictionary for outputs)
 - Design class hierarchies following Omniexception → Omnierror patterns
 - Apply appropriate naming conventions from nomenclature guidelines
-- Define type annotations using proper TypeAlias patterns
+- Define type annotations using proper TypeAlias patterns with __.typx.TypeAlias
 - Consider immutability preferences and container design patterns
 
 ### 3. Filesystem and Module Organization Design
@@ -80,20 +83,21 @@ Apply Python-specific organizational patterns and filesystem structure:
 - Plan type alias organization and dependency management
 
 ### 4. Class and Function Design
-Create maintainable Python structures:
-- Design class hierarchies with appropriate base classes and mixins
-- Specify function signatures with proper type annotations
-- Apply nomenclature patterns for methods, attributes, and functions
+Create maintainable Python structures following practices guide exactly:
+- Design class hierarchies with appropriate base classes and mixins (__.immut.Object, __.immut.Protocol, etc.)
+- Specify function signatures using practices guide patterns (wide inputs, narrow outputs, proper spacing)
+- Apply nomenclature patterns for methods, attributes, and functions from nomenclature guidelines
 - Design immutable data structures and container patterns
-- Plan dependency injection and configuration patterns
+- Plan dependency injection and configuration patterns with sensible defaults
 
 ### 5. Design Documentation
-Create comprehensive design specifications:
-- Document interface contracts and expected behaviors
-- Provide design examples following style guidelines
-- Specify exception handling patterns and error propagation
+Create comprehensive design specifications without implementations:
+- Provide only signatures, contracts, and interface specifications - no implementations
+- Do not provide exception class implementations, function bodies, or method implementations
+- Document interface contracts and expected behaviors (contracts only, not code)
+- Provide design examples using signatures and type annotations only
+- Specify exception handling patterns and error propagation (exception classes by name/signature only)
 - Document design rationale and trade-off decisions
-- Create interface specifications without implementation details
 
 ### 6. Design Validation
 Ensure design quality and consistency:

template/.auxiliary/configuration/conventions.md.jinja

@@ -15,9 +15,8 @@
 # Operation
 
 - Use `rg --line-number --column` to get precise coordinates for MCP tools that require line/column positions.
-- Prefer `text-editor` MCP tools over other text editing tools (line number-based edits are less error-prone).
-- Always reread files with `text-editor` tools after modifying files via other tools to avoid file hash conflicts.
-- Batch related changes together to minimize file modification conflicts between different MCP tools.
+- Choose appropriate editing tools based on the task complexity and your familiarity with the tools.
+- Batch related changes together when possible to maintain consistency.
 - Use relative paths rather than absolute paths when possible.
 - Do not write to paths outside the current project unless explicitly requested.
 - Use the `.auxiliary/scribbles` directory for scratch space instead of `/tmp`.