Update framework configuration and clean up obsolete specs

Configuration updates:
- Added .env.example template for environment variables
- Updated README.md with better setup instructions (.env usage)
- Enhanced .claude/settings.local.json with additional Bash permissions
- Added .claude/CLAUDE.md framework documentation

Spec cleanup:
- Removed obsolete spec files (language_selection, mistral_extensible, template, theme_customization)
- Consolidated app_spec.txt (Claude Clone example)
- Added app_spec_model.txt as reference template
- Added app_spec_library_rag_types_docs.txt
- Added coding_prompt_library.md

Framework improvements:
- Updated agent.py, autonomous_agent_demo.py, client.py with minor fixes
- Enhanced dockerize_my_project.py
- Updated prompts (initializer, initializer_bis) with better guidance
- Added docker-compose.my_project.yml example

This commit consolidates improvements made during development sessions.

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

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

prompts/initializer_prompt.md

@@ -30,9 +30,16 @@ Before creating issues, you need to set up Linear:
 
 ### CRITICAL TASK: Create Linear Issues
 
+**IMPORTANT - Issue Count:**
+Create EXACTLY ONE issue per feature listed in the `<implementation_steps>` section of app_spec.txt.
+- Count the `<feature_N>` tags in the spec file
+- If the spec has 8 features → create 8 issues
+- If the spec has 50 features → create 50 issues
+- Do NOT create a fixed arbitrary number
+- Each `<feature_N>` in `<implementation_steps>` = 1 Linear issue
+
 Based on `app_spec.txt`, create Linear issues for each feature using the
-`mcp__linear__create_issue` tool. Create 50 detailed issues that
-comprehensively cover all features in the spec.
+`mcp__linear__create_issue` tool.
 
 **For each feature, create an issue with:**
 
@@ -66,7 +73,7 @@ priority: 1-4 based on importance (1=urgent/foundational, 4=low/polish)
 ```
 
 **Requirements for Linear Issues:**
-- Create 50 issues total covering all features in the spec
+- Create ONE issue per `<feature_N>` tag in `<implementation_steps>`
 - Mix of functional and style features (note category in description)
 - Order by priority: foundational features get priority 1-2, polish features get 3-4
 - Include detailed test steps in each issue description