thanh-kit 2.5.0 → 2.5.1

package/templates/skills/package-upgrade/SKILL.md

@@ -1,189 +0,0 @@
----
-name: package-upgrade
-description: Use when the user asks to analyze package upgrades, check for outdated dependencies, plan npm/NuGet updates, or assess breaking changes in package updates. Triggers on keywords like "upgrade packages", "outdated", "npm update", "breaking changes", "dependency upgrade", "package update", "version upgrade".
-allowed-tools: Read, Write, Edit, Bash, Grep, Glob, Task, WebFetch, WebSearch, TodoWrite
----
-
-# Frontend Package Upgrade Analysis & Planning
-
-You are to operate as an expert frontend package management specialist, npm ecosystem analyst, and software architecture expert to analyze package.json files, research latest versions, collect breaking changes and migration guides, and generate a comprehensive upgrade plan.
-
-**IMPORTANT**: Always thinks hard, plan step by step to-do list first before execute. Always remember to-do list, never compact or summary it when memory context limit reach. Always preserve and carry your to-do list through every operation.
-
----
-
-## Core Anti-Hallucination Protocols
-
-### ASSUMPTION_VALIDATION_CHECKPOINT
-Before every major operation:
-1. "What assumptions am I making about [X]?"
-2. "Have I verified this with actual code evidence?"
-3. "Could I be wrong about [specific pattern/relationship]?"
-
-### EVIDENCE_CHAIN_VALIDATION
-Before claiming any relationship:
-- "I believe package X is compatible because..." → show actual compatibility matrix
-- "This version has breaking changes because..." → cite official changelog
-- "Migration effort is Y hours because..." → show evidence from similar migrations
-
-### TOOL_EFFICIENCY_PROTOCOL
-- Batch multiple WebSearch calls for related packages
-- Use parallel Read operations for package.json files
-- Batch package research into groups of 10
-
-### CONTEXT_ANCHOR_SYSTEM
-Every 10 packages researched:
-1. Re-read the original task description
-2. Verify the current operation aligns with original goals
-3. Update the `Current Focus` in `## Progress` section
-
----
-
-## PHASE 1: PACKAGE INVENTORY & CURRENT STATE ANALYSIS
-
-Build package inventory in `ai_task_analysis_notes/frontend-package-upgrade-analysis.md`.
-
-### PHASE 1A: INITIALIZATION AND PACKAGE DISCOVERY
-
-Initialize analysis file with:
-- `## Metadata` - Original prompt and task description
-- `## Progress` - Track phase, items processed, total items
-- `## Package Inventory` - All package.json files and dependencies
-- `## Version Research Results` - Latest versions and changelogs
-- `## Breaking Changes Analysis` - Breaking changes catalog
-- `## Migration Complexity Assessment` - Risk levels and effort estimates
-- `## Upgrade Strategy` - Phased migration plan
-
-**Find all package.json files**:
-```
-src/PlatformExampleAppWeb/package.json
-src/PlatformExampleAppWeb/apps/*/package.json
-src/PlatformExampleAppWeb/libs/*/package.json
-```
-
-For each package.json, document:
-- Project Name & Location
-- Framework Version
-- Dependencies (categorized: Framework, UI, Build Tools, Testing, Utilities)
-- DevDependencies
-
-Create **Master Package List** consolidating all unique packages.
-
-### PHASE 1B: PACKAGE USAGE ANALYSIS
-
-For each unique package, analyze codebase usage:
-- **Projects Using**: Which projects depend on this
-- **Import Count**: Number of files importing
-- **Key Usage Areas**: Where primarily used
-- **Configuration Files**: Config files for this package
-- **Upgrade Risk Level**: Low/Medium/High/Critical based on usage breadth
-
----
-
-## PHASE 2: WEB RESEARCH & VERSION DISCOVERY
-
-**IMPORTANT: BATCH INTO GROUPS OF 10**
-
-For EACH package in Master Package List:
-
-### Latest Version Discovery
-- Search: "[package-name] npm latest version"
-- Check: https://www.npmjs.com/package/[package-name]
-- Extract: Latest stable version, release date, downloads
-
-### Breaking Changes Research
-- Search: "[package-name] migration guide [old-version] to [new-version]"
-- Search: "[package-name] v[X] breaking changes"
-- Search: "[package-name] changelog"
-- GitHub: Check CHANGELOG.md, releases
-
-### Ecosystem Compatibility
-- Angular version compatibility
-- Check peerDependencies
-- Cross-package dependencies
-
-Document:
-- Current vs. Latest versions
-- Version gap (major/minor/patch versions behind)
-- Breaking changes with migration steps
-- Deprecation warnings
-- Peer dependency changes
-
----
-
-## PHASE 3: RISK ASSESSMENT & PRIORITIZATION
-
-### Risk Categories
-- **Critical Risk**: 5+ major versions behind, framework packages, 50+ breaking changes
-- **High Risk**: 3-4 major versions, state management, 20-30 breaking changes
-- **Medium Risk**: 1-2 major versions, some breaking changes
-- **Low Risk**: Patch/minor updates, backward compatible
-
-### Dependency Graph (Upgrade Order)
-1. Foundation packages (Node.js, TypeScript)
-2. Framework packages (Angular Core, CLI)
-3. Framework extensions (Material, RxJS)
-4. Third-party libraries
-5. Dev tools last
-
----
-
-## PHASE 4: COMPREHENSIVE REPORT GENERATION
-
-Generate report at `ai_package_upgrade_reports/[YYYY-MM-DD]-frontend-package-upgrade-report.md`:
-
-### Report Structure
-
-1. **Executive Summary**
-2. **Package Inventory by Project**
-3. **Version Gap Analysis**
-4. **Breaking Changes Catalog**
-5. **Migration Complexity Assessment**
-6. **Ecosystem Compatibility Analysis**
-7. **Recommended Upgrade Strategy** (Phased Migration Plan)
-8. **Detailed Migration Guides**
-9. **Testing Strategy**
-10. **Rollback Plan**
-11. **Timeline & Resource Estimation**
-12. **Appendices**
-
----
-
-## PHASE 5: APPROVAL GATE
-
-**CRITICAL**: Present comprehensive package upgrade report for explicit approval. **DO NOT** proceed without it.
-
----
-
-## PHASE 6: CONFIDENCE DECLARATION
-
-Before marking complete, provide:
-
-### Solution Confidence Assessment
-
-**Overall Confidence**: [High 90-100% / Medium 70-89% / Low <70%]
-
-**Evidence Summary**:
-- All package.json files discovered: [count]
-- Web research completed: [X/Y packages]
-- Breaking changes documented: [count]
-- Official sources used: npm, GitHub, official docs
-
-**Assumptions Made**: [List or "None"]
-
-**User Confirmation Needed**:
-- IF confidence < 90%: "Please verify [specific packages] before proceeding"
-- IF confidence >= 90%: "Analysis is comprehensive, ready for migration"
-
----
-
-## Package Upgrade Guidelines
-
-- **Comprehensive Discovery**: Find ALL package.json files
-- **Web Research Accuracy**: Use official sources only (npm, GitHub, official docs)
-- **Breaking Changes Focus**: Prioritize identifying breaking changes requiring code changes
-- **Risk Assessment**: Evaluate complexity based on breaking changes, usage breadth, dependencies
-- **Practical Planning**: Create actionable phased plan with realistic effort estimates
-- **Evidence-Based Decisions**: Base ALL recommendations on actual research with sources cited
-- **Confidence Declaration**: Declare confidence level; if < 90%, request user confirmation
-- **Batch Processing**: Research packages in batches of 10

package/templates/skills/plan-analysis/SKILL.md

@@ -1,191 +0,0 @@
----
-name: plan-analysis
-description: Use when the user provides an implementation plan file and asks to analyze it, assess impact, update specifications, or verify planned changes. Triggers on keywords like "analyze plan", "implementation plan", "assess impact", "update spec from plan", "verify plan".
-allowed-tools: Read, Write, Edit, Bash, Grep, Glob, Task, TodoWrite
----
-
-# Implementation Plan Analysis & Specification Update
-
-You are to operate as an expert full-stack dotnet angular principle developer, software architect, and technical analyst to analyze a detailed implementation plan, perform comprehensive impact analysis, and update specification documents.
-
-**IMPORTANT**: Always thinks hard, plan step by step to-do list first before execute. Always remember to-do list, never compact or summary it when memory context limit reach. Always preserve and carry your to-do list through every operation.
-
----
-
-## Core Anti-Hallucination Protocols
-
-### ASSUMPTION_VALIDATION_CHECKPOINT
-Before every major operation:
-1. "What assumptions am I making about [X]?"
-2. "Have I verified this with actual code evidence?"
-3. "Could I be wrong about [specific pattern/relationship]?"
-
-### EVIDENCE_CHAIN_VALIDATION
-Before claiming any relationship:
-- "I believe X calls Y because..." → show actual code
-- "This follows pattern Z because..." → cite specific examples
-- "Service A owns B because..." → grep for actual boundaries
-
-### TOOL_EFFICIENCY_PROTOCOL
-- Batch multiple Grep searches into single calls with OR patterns
-- Use parallel Read operations for related files
-- Combine semantic searches with related keywords
-
-### CONTEXT_ANCHOR_SYSTEM
-Every 10 operations:
-1. Re-read the original task description
-2. Verify the current operation aligns with original goals
-3. Update the `Current Focus` in `## Progress` section
-
----
-
-## PHASE 1: EXTERNAL MEMORY-DRIVEN IMPLEMENTATION PLAN ANALYSIS
-
-Build a structured knowledge model in `ai_task_analysis_notes/[plan-name].ai_task_analysis_notes_temp.md`.
-
-### PHASE 1A: INITIALIZATION AND DISCOVERY
-
-1. **Initialize** the analysis file with standard headings
-
-### IMPLEMENTATION PLAN COMPREHENSIVE ANALYSIS
-
-**IMPLEMENTATION_PLAN_DEEP_ANALYSIS**: Thorough analysis of the implementation plan file:
-
-1. **Plan Structure Analysis**:
-   - Read and parse the implementation plan completely
-   - Extract all planned features, requirements, and changes
-   - Identify implementation phases and dependencies
-   - Document under `## Implementation Plan Overview`
-
-2. **Requirements Extraction**:
-   - Parse Knowledge Graph from implementation plan
-   - Extract new business requirements
-   - Map functional and non-functional requirements
-   - Identify changed business workflows
-   - Document under `## Extracted Requirements`
-
-3. **Planned Changes Analysis**:
-   - Catalog all planned code changes (new files, modifications, deletions)
-   - Identify affected components, services, and layers
-   - Map file-level changes to business capabilities
-   - Extract integration points
-   - Document under `## Planned Changes Analysis`
-
-4. **Architecture Impact Assessment**:
-   - Analyze how changes affect overall system architecture
-   - Identify CQRS pattern impacts (new Commands/Queries/Events)
-   - Map domain entity changes and repository patterns
-   - Document under `## Architecture Impact Assessment`
-
-5. **Existing Specification Analysis**:
-   - Read and analyze existing specification document structure
-   - Identify current test cases, requirements, entity relationships
-   - Map existing test coverage to planned changes
-   - Document under `## Current Specification Analysis`
-
-**AFFECTED_COMPONENTS_DISCOVERY**: For each planned change, discover:
-- Direct Dependencies
-- Indirect Dependencies
-- Test Coverage Impact
-- API Integration Impact
-- Cross-Service Communication
-- Database Schema Impact
-
-Save to `## Comprehensive File List` with:
-- `filePath`, `changeType`, `relationshipType`, `impactLevel`
-- `serviceContext`, `planContext`, `specificationRelevance`
-
-### PHASE 1B: KNOWLEDGE GRAPH CONSTRUCTION
-
-**IMPORTANT: MUST DO WITH TODO LIST**
-
-For each file, document in `## Knowledge Graph`:
-- Standard fields plus plan-specific:
-- `currentContent`: Existing functionality (if file exists)
-- `plannedChanges`: Specific changes planned
-- `changeImpactAnalysis`: How changes affect other components
-- `testingRequirements`: New test cases needed
-- `specificationMapping`: How component maps to spec sections
-- `testCaseImpact`: Existing test cases needing modification
-
-### PHASE 1C: SPECIFICATION MAPPING ANALYSIS
-
-- **Test Case Mapping**: Which existing test cases are affected
-- **Business Requirement Mapping**: How new requirements relate to existing
-- **Entity Relationship Impact**: Changes to entity relationships
-- **Workflow Integration**: How new workflows integrate with existing
-- **Coverage Gap Analysis**: Areas where new test cases needed
-
-### PHASE 1D: OVERALL ANALYSIS
-
-Write comprehensive summary showing:
-- Complete end-to-end workflows affected
-- Architectural patterns impacted
-- Business logic workflow changes
-- Integration points affected
-- Comprehensive test coverage requirements
-
----
-
-## PHASE 2: COMPREHENSIVE ANALYSIS AND PLANNING
-
-Generate detailed analysis under these headings:
-
-1. **Implementation Impact Analysis**: Component impact, integration points, data flow changes, platform compliance
-
-2. **Business Logic Analysis**: New business rules, modified workflows, validation requirements
-
-3. **Testing Strategy Analysis**: Test coverage requirements, new test scenarios, regression testing needs
-
-4. **Specification Update Strategy**: How to integrate new requirements, maintain traceability, preserve existing coverage
-
-5. **Rollback and Safety Strategy**: Backup procedures, rollback plan, validation checkpoints
-
----
-
-## PHASE 3: APPROVAL GATE
-
-**CRITICAL**: Present comprehensive analysis for explicit approval. **DO NOT** proceed without it.
-
----
-
-## PHASE 4: SPECIFICATION UPDATE EXECUTION
-
-Once approved, execute with MANDATORY steps:
-
-1. **Backup Original Specification**
-2. **Read and Parse Existing Specification**
-3. **Execute Planned Updates**:
-   - New Requirements Integration
-   - Entity Relationship Updates
-   - Test Case Enhancement
-   - Traceability Matrix Updates
-   - Coverage Analysis Updates
-4. **Maintain Specification Structure**
-5. **Quality Assurance Validation**
-
----
-
-## SUCCESS VALIDATION
-
-Verify under `## Specification Validation`:
-- **Requirements Traceability**: All plan requirements mapped
-- **Test Coverage Validation**: All changes covered by tests
-- **Business Workflow Validation**: End-to-end workflows documented
-- **Integration Testing Coverage**: Cross-service impacts covered
-- **Regression Prevention**: Existing functionality protected
-
----
-
-## Plan Analysis Guidelines
-
-- **Plan-Driven Analysis**: Base all analysis on the detailed implementation plan
-- **Specification Structure Preservation**: Maintain standardized specification format
-- **Comprehensive Impact Assessment**: Analyze direct and indirect effects
-- **End-to-End Workflow Mapping**: Understand affected business processes
-- **Enterprise Architecture Awareness**: Respect platform patterns
-- **Quality-Focused Testing**: Create comprehensive test specifications
-- **Specification Completeness**: Ensure full traceability
-- **Risk Assessment and Mitigation**: Identify risks and provide rollback strategies
-- **Bidirectional Traceability**: Maintain clear mapping between plan and spec
-- **Coverage Preservation**: Maintain existing test coverage while adding new

package/templates/skills/planning/SKILL.md

@@ -1,115 +0,0 @@
----
-name: planning
-description: Use when you need to plan technical solutions that are scalable, secure, and maintainable.
-license: MIT
----
-
-# Planning
-
-Create detailed technical implementation plans through research, codebase analysis, solution design, and comprehensive documentation.
-
-## When to Use
-
-Use this skill when:
-- Planning new feature implementations
-- Architecting system designs
-- Evaluating technical approaches
-- Creating implementation roadmaps
-- Breaking down complex requirements
-- Assessing technical trade-offs
-
-## Core Responsibilities & Rules
-
-Always honoring **YAGNI**, **KISS**, and **DRY** principles.
-**Be honest, be brutal, straight to the point, and be concise.**
-
-### 1. Research & Analysis
-Load: `references/research-phase.md`
-**Skip if:** Provided with researcher reports
-
-### 2. Codebase Understanding
-Load: `references/codebase-understanding.md`
-**Skip if:** Provided with scout reports
-
-### 3. Solution Design
-Load: `references/solution-design.md`
-
-### 4. Plan Creation & Organization
-Load: `references/plan-organization.md`
-
-### 5. Task Breakdown & Output Standards
-Load: `references/output-standards.md`
-
-## Workflow Process
-
-1. **Initial Analysis** → Read codebase docs, understand context
-2. **Research Phase** → Spawn researchers, investigate approaches
-3. **Synthesis** → Analyze reports, identify optimal solution
-4. **Design Phase** → Create architecture, implementation design
-5. **Plan Documentation** → Write comprehensive plan
-6. **Review & Refine** → Ensure completeness, clarity, actionability
-
-## Output Requirements
-
-- DO NOT implement code - only create plans
-- Respond with plan file path and summary
-- Ensure self-contained plans with necessary context
-- Include code snippets/pseudocode when clarifying
-- Provide multiple options with trade-offs when appropriate
-- Fully respect the `./docs/development-rules.md` file.
-
-**Plan Directory Structure**
-```
-plans/
-└── {date}-plan-name/
-    ├── research/
-    │   ├── researcher-XX-report.md
-    │   └── ...
-    ├── reports/
-    │   ├── XX-report.md
-    │   └── ...
-    ├── scout/
-    │   ├── scout-XX-report.md
-    │   └── ...
-    ├── plan.md
-    ├── phase-XX-phase-name-here.md
-    └── ...
-```
-
-## Active Plan State
-
-Prevents version proliferation by tracking current working plan via session state.
-
-### Active vs Suggested Plans
-
-Check the `## Plan Context` section injected by hooks:
-- **"Plan: {path}"** = Active plan, explicitly set via `set-active-plan.cjs` - use for reports
-- **"Suggested: {path}"** = Branch-matched, hint only - do NOT auto-use
-- **"Plan: none"** = No active plan
-
-### Rules
-
-1. **If "Plan:" shows a path**: Ask "Continue with existing plan? [Y/n]"
-2. **If "Suggested:" shows a path**: Inform user, ask if they want to activate or create new
-3. **If "Plan: none"**: Create new plan using naming from `## Naming` section
-4. **Update on create**: Run `node .claude/scripts/set-active-plan.cjs {plan-dir}`
-
-### Report Output Location
-
-All agents writing reports MUST:
-1. Check `## Naming` section injected by hooks for the computed naming pattern
-2. Active plans use plan-specific reports path
-3. Suggested plans use default reports path (not plan folder)
-
-**Important:** Suggested plans do NOT get plan-specific reports - this prevents pollution of old plan folders.
-
-## Quality Standards
-
-- Be thorough and specific
-- Consider long-term maintainability
-- Research thoroughly when uncertain
-- Address security and performance concerns
-- Make plans detailed enough for junior developers
-- Validate against existing codebase patterns
-
-**Remember:** Plan quality determines implementation success. Be comprehensive and consider all solution aspects.

package/templates/skills/planning-with-files/SKILL.md

@@ -1,160 +0,0 @@
----
-name: planning-with-files
-description: Transforms workflow to use Manus-style persistent markdown files for planning, progress tracking, and knowledge storage. Use when starting complex tasks, multi-step projects, research tasks, or when the user mentions planning, organizing work, tracking progress, or wants structured output.
----
-
-# Planning with Files
-
-Work like Manus: Use persistent markdown files as your "working memory on disk."
-
-## Quick Start
-
-Before ANY complex task:
-
-1. **Create `task_plan.md`** in the working directory
-2. **Define phases** with checkboxes
-3. **Update after each phase** - mark [x] and change status
-4. **Read before deciding** - refresh goals in attention window
-
-## The 3-File Pattern
-
-For every non-trivial task, create THREE files:
-
-| File | Purpose | When to Update |
-|------|---------|----------------|
-| `task_plan.md` | Track phases and progress | After each phase |
-| `notes.md` | Store findings and research | During research |
-| `[deliverable].md` | Final output | At completion |
-
-## Core Workflow
-
-```
-Loop 1: Create task_plan.md with goal and phases
-Loop 2: Research → save to notes.md → update task_plan.md
-Loop 3: Read notes.md → create deliverable → update task_plan.md
-Loop 4: Deliver final output
-```
-
-### The Loop in Detail
-
-**Before each major action:**
-```bash
-Read task_plan.md  # Refresh goals in attention window
-```
-
-**After each phase:**
-```bash
-Edit task_plan.md  # Mark [x], update status
-```
-
-**When storing information:**
-```bash
-Write notes.md     # Don't stuff context, store in file
-```
-
-## task_plan.md Template
-
-Create this file FIRST for any complex task:
-
-```markdown
-# Task Plan: [Brief Description]
-
-## Goal
-[One sentence describing the end state]
-
-## Phases
-- [ ] Phase 1: Plan and setup
-- [ ] Phase 2: Research/gather information
-- [ ] Phase 3: Execute/build
-- [ ] Phase 4: Review and deliver
-
-## Key Questions
-1. [Question to answer]
-2. [Question to answer]
-
-## Decisions Made
-- [Decision]: [Rationale]
-
-## Errors Encountered
-- [Error]: [Resolution]
-
-## Status
-**Currently in Phase X** - [What I'm doing now]
-```
-
-## notes.md Template
-
-For research and findings:
-
-```markdown
-# Notes: [Topic]
-
-## Sources
-
-### Source 1: [Name]
-- URL: [link]
-- Key points:
-  - [Finding]
-  - [Finding]
-
-## Synthesized Findings
-
-### [Category]
-- [Finding]
-- [Finding]
-```
-
-## Critical Rules
-
-### 1. ALWAYS Create Plan First
-Never start a complex task without `task_plan.md`. This is non-negotiable.
-
-### 2. Read Before Decide
-Before any major decision, read the plan file. This keeps goals in your attention window.
-
-### 3. Update After Act
-After completing any phase, immediately update the plan file:
-- Mark completed phases with [x]
-- Update the Status section
-- Log any errors encountered
-
-### 4. Store, Don't Stuff
-Large outputs go to files, not context. Keep only paths in working memory.
-
-### 5. Log All Errors
-Every error goes in the "Errors Encountered" section. This builds knowledge for future tasks.
-
-## When to Use This Pattern
-
-**Use 3-file pattern for:**
-- Multi-step tasks (3+ steps)
-- Research tasks
-- Building/creating something
-- Tasks spanning multiple tool calls
-- Anything requiring organization
-
-**Skip for:**
-- Simple questions
-- Single-file edits
-- Quick lookups
-
-## Anti-Patterns to Avoid
-
-| Don't | Do Instead |
-|-------|------------|
-| Use TodoWrite for persistence | Create `task_plan.md` file |
-| State goals once and forget | Re-read plan before each decision |
-| Hide errors and retry | Log errors to plan file |
-| Stuff everything in context | Store large content in files |
-| Start executing immediately | Create plan file FIRST |
-
-## Advanced Patterns
-
-See [reference.md](reference.md) for:
-- Attention manipulation techniques
-- Error recovery patterns
-- Context optimization from Manus
-
-See [examples.md](examples.md) for:
-- Real task examples
-- Complex workflow patterns