zhongwei/gh-cskiro-claudex-meta-tools
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Initial commit

Browse Source
This commit is contained in:
Zhongwei Li
2025-11-29 18:16:56 +08:00
commit 8a3d331e04
61 changed files with 11808 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

169
skills/insight-skill-generator/docs/lessons-learned/configuration/2025-11-16-configuration-driven-design-pattern.md Normal file
View File

@@ -0,0 +1,169 @@
# Configuration Insights - November 16, 2025
Auto-generated lessons learned from Claude Code Explanatory insights.
**Session**: 79b654b6-10f8-4c3c-92e1-a3535644366c
**Generated**: 2025-11-16 09:57:31
---
larity thresholds without editing code
2. Add new categories and keywords as their projects evolve
3. Customize skill generation patterns for their domain
This approach follows the "data over code" principle from the skill-creator research, making the skill more maintainable and adaptable.
---
## Configuration-Driven Design Pattern
**Configuration-Driven Design Pattern**
Rather than hardcoding clustering logic, we're externalizing it to YAML configuration files. This allows users to:
1. Tune similarity thresholds without editing code
2. Add new categories and keywords as their projects evolve
3. Customize skill generation patterns for their domain
This approach follows the "data over code" principle from the skill-creator research, making the skill more maintainable and adaptable.
---
## Configuration-Driven Design Pattern
**Configuration-Driven Design Pattern**
Rather than hardcoding clustering logic, we're externalizing it to YAML configuration files. This allows users to:
1. Tune similarity thresholds without editing code
2. Add new categories and keywords as their projects evolve
3. Customize skill generation patterns for their domain
This approach follows the "data over code" principle from the skill-creator research, making the skill more maintainable and adaptable.
---
## Configuration-Driven Design Pattern
**Configuration-Driven Design Pattern**
Rather than hardcoding clustering logic, we're externalizing it to YAML configuration files. This allows users to:
1. Tune similarity thresholds without editing code
2. Add new categories and keywords as their projects evolve
3. Customize skill generation patterns for their domain
This approach follows the "data over code" principle from the skill-creator research, making the skill more maintainable and adaptable.
---
## Template-Based Documentation vs. Executable Logic
**Template-Based Documentation vs. Executable Logic**
Notice that our templates use Jinja2-style syntax (`{{ variable }}`), but this is for documentation and reference only. In Claude Code skills, the actual logic is expressed as clear, step-by-step instructions in SKILL.md that I (Claude) interpret and execute. The templates serve as:
1. **Consistency guides** - showing expected output structure
2. **Reference patterns** - documenting best practices
3. **Quality standards** - setting expectations for generated content
This is different from traditional code generation where templates are programmatically rendered. Here, I read the templates as examples and generate similar output naturally.
---
## Template-Based Documentation vs. Executable Logic
**Template-Based Documentation vs. Executable Logic**
Notice that our templates use Jinja2-style syntax (`{{ variable }}`), but this is for documentation and reference only. In Claude Code skills, the actual logic is expressed as clear, step-by-step instructions in SKILL.md that I (Claude) interpret and execute. The templates serve as:
1. **Consistency guides** - showing expected output structure
2. **Reference patterns** - documenting best practices
3. **Quality standards** - setting expectations for generated content
This is different from traditional code generation where templates are programmatically rendered. Here, I read the templates as examples and generate similar output naturally.
---
## Template-Based Documentation vs. Executable Logic
**Template-Based Documentation vs. Executable Logic**
Notice that our templates use Jinja2-style syntax (`{{ variable }}`), but this is for documentation and reference only. In Claude Code skills, the actual logic is expressed as clear, step-by-step instructions in SKILL.md that I (Claude) interpret and execute. The templates serve as:
1. **Consistency guides** - showing expected output structure
2. **Reference patterns** - documenting best practices
3. **Quality standards** - setting expectations for generated content
This is different from traditional code generation where templates are programmatically rendered. Here, I read the templates as examples and generate similar output naturally.
---
## Template-Based Documentation vs. Executable Logic
**Template-Based Documentation vs. Executable Logic**
Notice that our templates use Jinja2-style syntax (`{{ variable }}`), but this is for documentation and reference only. In Claude Code skills, the actual logic is expressed as clear, step-by-step instructions in SKILL.md that I (Claude) interpret and execute. The templates serve as:
1. **Consistency guides** - showing expected output structure
2. **Reference patterns** - documenting best practices
3. **Quality standards** - setting expectations for generated content
This is different from traditional code generation where templates are programmatically rendered. Here, I read the templates as examples and generate similar output naturally.
---
## Template-Based Documentation vs. Executable Logic
**Template-Based Documentation vs. Executable Logic**
Notice that our templates use Jinja2-style syntax (`{{ variable }}`), but this is for documentation and reference only. In Claude Code skills, the actual logic is expressed as clear, step-by-step instructions in SKILL.md that I (Claude) interpret and execute. The templates serve as:
1. **Consistency guides** - showing expected output structure
2. **Reference patterns** - documenting best practices
3. **Quality standards** - setting expectations for generated content
This is different from traditional code generation where templates are programmatically rendered. Here, I read the templates as examples and generate similar output naturally.
---
## Template-Based Documentation vs. Executable Logic
**Template-Based Documentation vs. Executable Logic**
Notice that our templates use Jinja2-style syntax (`{{ variable }}`), but this is for documentation and reference only. In Claude Code skills, the actual logic is expressed as clear, step-by-step instructions in SKILL.md that I (Claude) interpret and execute. The templates serve as:
1. **Consistency guides** - showing expected output structure
2. **Reference patterns** - documenting best practices
3. **Quality standards** - setting expectations for generated content
This is different from traditional code generation where templates are programmatically rendered. Here, I read the templates as examples and generate similar output naturally.
---
## Template-Based Documentation vs. Executable Logic
**Template-Based Documentation vs. Executable Logic**
Notice that our templates use Jinja2-style syntax (`{{ variable }}`), but this is for documentation and reference only. In Claude Code skills, the actual logic is expressed as clear, step-by-step instructions in SKILL.md that I (Claude) interpret and execute. The templates serve as:
1. **Consistency guides** - showing expected output structure
2. **Reference patterns** - documenting best practices
3. **Quality standards** - setting expectations for generated content
This is different from traditional code generation where templates are programmatically rendered. Here, I read the templates as examples and generate similar output naturally.
---