thanh-kit 2.5.0

package/templates/skills/domain-name-brainstormer/SKILL.md

@@ -0,0 +1,212 @@
+---
+name: domain-name-brainstormer
+description: Generates creative domain name ideas for your project and checks availability across multiple TLDs (.com, .io, .dev, .ai, etc.). Saves hours of brainstorming and manual checking.
+---
+
+# Domain Name Brainstormer
+
+This skill helps you find the perfect domain name for your project by generating creative options and checking what's actually available to register.
+
+## When to Use This Skill
+
+- Starting a new project or company
+- Launching a product or service
+- Creating a personal brand or portfolio site
+- Rebranding an existing project
+- Registering a domain for a side project
+- Finding available alternatives when your first choice is taken
+
+## What This Skill Does
+
+1. **Understands Your Project**: Analyzes what you're building and who it's for
+2. **Generates Creative Names**: Creates relevant, memorable domain options
+3. **Checks Availability**: Verifies which domains are actually available across multiple TLDs
+4. **Multiple Extensions**: Suggests .com, .io, .dev, .ai, .app, and more
+5. **Provides Alternatives**: Offers variations if top choices are taken
+6. **Branding Insights**: Explains why certain names work well
+
+## How to Use
+
+### Basic Brainstorming
+
+```
+I'm building a project management tool for remote teams. 
+Suggest domain names.
+```
+
+```
+Help me brainstorm domain names for a personal finance app
+```
+
+### Specific Preferences
+
+```
+I need a domain name for my AI writing assistant. 
+Prefer short names with .ai or .io extension.
+```
+
+### With Keywords
+
+```
+Suggest domain names using the words "pixel" or "studio" 
+for my design agency
+```
+
+## Example
+
+**User**: "I'm building a tool for developers to share code snippets. Suggest creative domain names."
+
+**Output**:
+```
+Analyzing your project...
+Target audience: Developers
+Key features: Code sharing, snippets, collaboration
+
+🎯 Domain Name Suggestions
+
+## Available (.com)
+1. ✓ snippetbox.com - Clear, memorable, available!
+   Why: Directly describes the product, easy to remember
+
+2. ✓ codeclip.com - Short and snappy
+   Why: Implies quick code sharing, only 8 characters
+
+3. ✓ devpaste.com - Developer-focused
+   Why: Familiar to devs (like pastebin), clear purpose
+
+## Available (Alternative TLDs)
+4. ✓ snippet.dev - Perfect extension for developers
+   Why: .dev extension signals developer tool
+
+5. ✓ codebox.io - Tech-forward
+   Why: .io popular with tech startups, clean name
+
+6. ✓ sharecode.app - Descriptive
+   Why: .app extension, clearly states the action
+
+## Premium/Taken (.com)
+- codeshare.com (Taken, est. $2,500)
+- snippets.com (Taken, premium domain)
+
+## Recommendations
+
+🏆 Top Pick: snippet.dev
+- Perfect for developer audience
+- Short and memorable  
+- .dev extension adds credibility
+- Available now!
+
+🥈 Runner-up: snippetbox.com
+- .com is universally recognized
+- Slightly longer but descriptive
+- Great brandability
+
+Next steps:
+1. Register your favorite before someone else does!
+2. Want me to check more variations?
+3. Need help with logo ideas for these names?
+```
+
+**Inspired by:** Ben Aiad's use case from Lenny's Newsletter
+
+## Domain Naming Tips
+
+### What Makes a Good Domain
+
+✓ **Short**: Under 15 characters ideal
+✓ **Memorable**: Easy to recall and spell
+✓ **Pronounceable**: Can be said in conversation
+✓ **Descriptive**: Hints at what you do
+✓ **Brandable**: Unique enough to stand out
+✓ **No hyphens**: Easier to share verbally
+
+### TLD Guide
+
+- **.com**: Universal, trusted, great for businesses
+- **.io**: Tech startups, developer tools
+- **.dev**: Developer-focused products
+- **.ai**: AI/ML products
+- **.app**: Mobile or web applications
+- **.co**: Alternative to .com
+- **.xyz**: Modern, creative projects
+- **.design**: Creative/design agencies
+- **.tech**: Technology companies
+
+## Advanced Features
+
+### Check Similar Variations
+
+```
+Check availability for "codebase" and similar variations 
+across .com, .io, .dev
+```
+
+### Industry-Specific
+
+```
+Suggest domain names for a sustainable fashion brand, 
+checking .eco and .fashion TLDs
+```
+
+### Multilingual Options
+
+```
+Brainstorm domain names in English and Spanish for 
+a language learning app
+```
+
+### Competitor Analysis
+
+```
+Show me domain patterns used by successful project 
+management tools, then suggest similar available ones
+```
+
+## Example Workflows
+
+### Startup Launch
+1. Describe your startup idea
+2. Get 10-15 domain suggestions across TLDs
+3. Review availability and pricing
+4. Pick top 3 favorites
+5. Register immediately
+
+### Personal Brand
+1. Share your name and profession
+2. Get variations (firstname.com, firstnamelastname.dev, etc.)
+3. Check social media handle availability too
+4. Register consistent brand across platforms
+
+### Product Naming
+1. Describe product and target market
+2. Get creative, brandable names
+3. Check trademark conflicts
+4. Verify domain and social availability
+5. Test names with target audience
+
+## Tips for Success
+
+1. **Act Fast**: Good domains get taken quickly
+2. **Register Variations**: Get .com and .io to protect brand
+3. **Avoid Numbers**: Hard to communicate verbally
+4. **Check Social Media**: Make sure @username is available too
+5. **Say It Out Loud**: Test if it's easy to pronounce
+6. **Check Trademarks**: Ensure no legal conflicts
+7. **Think Long-term**: Will it still make sense in 5 years?
+
+## Pricing Context
+
+When suggesting domains, I'll note:
+- Standard domains: ~$10-15/year
+- Premium TLDs (.io, .ai): ~$30-50/year
+- Taken domains: Market price if listed
+- Premium domains: $hundreds to $thousands
+
+## Related Tools
+
+After picking a domain:
+- Check logo design options
+- Verify social media handles
+- Research trademark availability
+- Plan brand identity colors/fonts
+

package/templates/skills/dual-pass-review/SKILL.md

@@ -0,0 +1,249 @@
+---
+name: dual-pass-review
+description: Use AFTER any code changes (feature implementation, bug fix, refactor) to enforce mandatory dual-pass review. First pass reviews unstaged changes for correctness and convention compliance. Second pass ONLY executes if first pass made any corrections. Ensures work follows project conventions, development rules, and best practices before task completion.
+allowed-tools: Read, Write, Edit, Grep, Glob, Bash, Task
+---
+
+# Dual-Pass Code Review Workflow
+
+Mandatory review checkpoint that runs after any code changes to ensure quality and convention compliance.
+
+## Core Principle
+
+**Every code change requires verification before task completion.**
+
+Two review passes:
+1. **First Pass**: Review unstaged changes for correctness + convention compliance
+2. **Second Pass**: Conditional - ONLY if first pass made changes, review again
+
+## When to Use
+
+Trigger AUTOMATICALLY after:
+- Feature implementation (`/cook`, `/code`)
+- Bug fixes (`/fix`, `/debug`)
+- Refactoring (`/refactor`)
+- Any edit/write operations that modify code
+
+## Review Dimensions
+
+### 1. Task Correctness
+- [ ] Changes address the original task/requirement
+- [ ] No missing pieces or incomplete logic
+- [ ] Edge cases handled appropriately
+- [ ] No unintended side effects
+
+### 2. Project Conventions
+- [ ] Follows Clean Architecture layers
+- [ ] Uses correct repository pattern (service-specific, not generic)
+- [ ] CQRS patterns: Command + Handler + Result in ONE file
+- [ ] Entity patterns: static expressions, computed properties have empty `set { }`
+- [ ] Frontend: correct base class hierarchy
+- [ ] Frontend: BEM class naming on ALL elements
+
+### 3. Development Rules Compliance
+- [ ] YAGNI - No unnecessary features/abstractions
+- [ ] KISS - Simplest solution that works
+- [ ] DRY - No code duplication (search first, reuse existing)
+- [ ] Logic in LOWEST layer (Entity > Service > Component)
+- [ ] DTO mapping in DTO class, not handler
+- [ ] Side effects in event handlers, not command handlers
+
+### 4. Code Quality
+- [ ] No syntax errors, code compiles
+- [ ] Meaningful naming
+- [ ] Single Responsibility Principle
+- [ ] Proper error handling
+- [ ] No security vulnerabilities
+
+## Execution Protocol
+
+### Step 1: Get Unstaged Changes
+
+```bash
+# Check for unstaged changes
+git status --short
+
+# Get full diff of unstaged changes
+git diff
+
+# Get diff of staged changes (if any)
+git diff --staged
+```
+
+### Step 2: First Pass Review
+
+For EACH changed file, verify:
+
+```markdown
+## First Pass Review Checklist
+
+### File: [filename]
+
+**Task Correctness:**
+- [ ] Addresses original requirement
+- [ ] Logic is complete and correct
+- [ ] No missing edge cases
+
+**Convention Compliance:**
+- [ ] Follows platform patterns from CLAUDE.md
+- [ ] Uses correct base classes
+- [ ] Naming conventions followed
+- [ ] BEM classes on all template elements (frontend)
+
+**Development Rules:**
+- [ ] YAGNI/KISS/DRY compliance
+- [ ] Logic in correct layer
+- [ ] No anti-patterns (side effects in handlers, generic repos, etc.)
+
+**Quality:**
+- [ ] Compiles without errors
+- [ ] No security issues
+- [ ] Proper error handling
+```
+
+### Step 3: First Pass Corrections
+
+If issues found:
+1. Document each issue clearly
+2. Fix issues immediately
+3. Track that corrections were made
+
+```markdown
+## First Pass Corrections Made
+
+1. [File:Line] - [Issue] → [Fix Applied]
+2. [File:Line] - [Issue] → [Fix Applied]
+...
+```
+
+### Step 4: Conditional Second Pass
+
+**CRITICAL DECISION POINT:**
+
+```
+IF first_pass_made_changes == true:
+    EXECUTE full second pass review
+ELSE:
+    SKIP second pass, proceed to summary
+```
+
+### Step 5: Second Pass Review (If Needed)
+
+Re-run complete review on current unstaged changes:
+
+```bash
+# Get fresh diff after corrections
+git diff
+```
+
+Verify ALL checklist items again:
+- Task correctness
+- Convention compliance
+- Development rules
+- Code quality
+
+### Step 6: Generate Summary
+
+```markdown
+## Dual-Pass Review Summary
+
+**First Pass:**
+- Files reviewed: [count]
+- Issues found: [count]
+- Corrections made: [yes/no]
+
+**Second Pass:**
+- Executed: [yes/no]
+- Reason: [first pass made changes / first pass clean]
+- Additional issues: [count if executed]
+
+**Final Status:** [APPROVED / NEEDS ATTENTION]
+
+**Remaining Concerns:**
+- [List any minor items for future consideration]
+```
+
+## Common Issues to Check
+
+### Backend Anti-Patterns
+
+```csharp
+// Side effect in handler (WRONG)
+await notificationService.SendAsync(...);
+// → Move to UseCaseEvents/ event handler
+
+// Generic repository (WRONG)
+IPlatformRootRepository<Entity>
+// → Use service-specific: IMyServiceRootRepository<Entity>
+
+// Mapping in handler (WRONG)
+var entity = new Entity { Name = req.Name };
+// → Use DTO.MapToEntity() or Command.MapToNewEntity()
+
+// Missing eager loading (WRONG)
+await repo.GetAllAsync(...)
+// → Add: ct, e => e.Related
+```
+
+### Frontend Anti-Patterns
+
+```typescript
+// Missing BEM class (WRONG)
+<div><span>{{ name }}</span></div>
+// → <div class="user-card__content"><span class="user-card__name">{{ name }}</span></div>
+
+// Missing untilDestroyed (WRONG)
+this.data$.subscribe(...)
+// → this.data$.pipe(this.untilDestroyed()).subscribe(...)
+
+// Logic in component (WRONG)
+readonly types = [{ value: 1, label: 'Type A' }];
+// → Move to Entity: static readonly dropdownOptions = [...]
+
+// Direct HttpClient (WRONG)
+constructor(private http: HttpClient) {}
+// → Extend PlatformApiService
+```
+
+## Integration with Workflows
+
+This skill is the FINAL step before task completion in:
+
+| Workflow | Sequence (Updated) |
+|----------|-------------------|
+| Feature | plan → cook → test → **dual-pass-review** → docs-update → watzup |
+| Bug Fix | debug → plan → fix → test → **dual-pass-review** |
+| Refactor | plan → code → test → **dual-pass-review** |
+
+## Review Commands
+
+```bash
+# Quick convention check
+grep -r "IPlatformRootRepository" --include="*.cs"  # Should be service-specific
+grep -r "new Entity {" --include="*Handler.cs"  # Should be in DTO
+grep -r "SendAsync\|NotifyAsync" --include="*CommandHandler.cs"  # Should be in event handler
+
+# Frontend checks
+grep -r "class=\"\"" --include="*.html"  # Empty class (suspicious)
+grep -r "subscribe()" --include="*.ts" | grep -v "untilDestroyed"  # Missing cleanup
+```
+
+## Key Rules
+
+1. **NEVER skip first pass** - Always review unstaged changes
+2. **Second pass is CONDITIONAL** - Only if first pass made corrections
+3. **Be honest and brutal** - Flag all issues, don't be lenient
+4. **Evidence-based** - Cite specific files and lines
+5. **Follow project conventions** - Check CLAUDE.md patterns
+
+## Output Format
+
+Always end with clear status:
+
+```markdown
+---
+**Review Status:** [APPROVED / CORRECTIONS NEEDED]
+**Passes Executed:** [1 / 2]
+**Ready for Commit:** [Yes / No]
+---
+```