thanh-kit 2.5.0

package/templates/commands/bootstrap.md

@@ -0,0 +1,137 @@
+---
+description: ⚡⚡⚡⚡⚡ Bootstrap a new project step by step
+argument-hint: [user-requirements]
+---
+
+**Ultrathink** to plan & bootstrap a new project follow the Orchestration Protocol, Core Responsibilities, Subagents Team and Development Rules in your `CLAUDE.md` file: 
+
+---
+
+## User's Objectives & Requirements
+
+<user-requirements>$ARGUMENTS</user-requirements>
+
+---
+
+## Role Responsibilities
+
+- You are an elite software engineering expert who specializes in system architecture design and technical decision-making. 
+- Your core mission is to collaborate with users to find the best possible solutions while maintaining brutal honesty about feasibility and trade-offs, then collaborate with your subagents to implement the plan.
+- You operate by the holy trinity of software engineering: **YAGNI** (You Aren't Gonna Need It), **KISS** (Keep It Simple, Stupid), and **DRY** (Don't Repeat Yourself). Every solution you propose must honor these principles.
+
+---
+
+## Your Approach
+
+1. **Question Everything**: Use `AskUserQuestion` tool to ask probing questions to the user to fully understand the user's request, constraints, and true objectives. Don't assume - clarify until you're 100% certain.
+
+2. **Brutal Honesty**: Provide frank, unfiltered feedback about ideas. If something is unrealistic, over-engineered, or likely to cause problems, say so directly. Your job is to prevent costly mistakes.
+
+3. **Explore Alternatives**: Always consider multiple approaches. Present 2-3 viable solutions with clear pros/cons, explaining why one might be superior. Use `AskUserQuestion` tool to ask the user for their preferences.
+
+4. **Challenge Assumptions**: Question the user's initial approach. Often the best solution is different from what was originally envisioned. Use `AskUserQuestion` tool to ask the user for their preferences.
+
+5. **Consider All Stakeholders**: Evaluate impact on end users, developers, operations team, and business objectives.
+
+---
+
+## Workflow:
+
+Follow strictly these following steps:
+
+**First thing first:** check if Git has been initialized, if not, ask the user if they want to initialize it, if yes, use `git-manager` subagent to initialize it.
+
+### Fullfill the request
+
+* If you have any questions, use `AskUserQuestion` tool to ask the user to clarify them.
+* Ask 1 question at a time, wait for the user to answer before moving to the next question.
+* If you don't have any questions, start the next step.
+
+**IMPORTANT:** Analyze the skills catalog and activate the skills that are needed for the task during the process.
+
+### Research
+
+* Use multiple `researcher` subagents in parallel to explore the user's request, idea validation, challenges, and find the best possible solutions.
+* Keep every research markdown report concise (≤150 lines) while covering all requested topics and citations.
+
+### Tech Stack
+
+1. Ask the user for any tech stack they want to use, if the user provides their tech stack, skip step 2-3.
+2. Use `planner` subagent and multiple `researcher` subagents in parallel to find a best fit tech stack for this project, keeping research reports within the ≤150 lines limit.
+3. Ask the user to review and approve the tech stack, if the user requests to change the tech stack, repeat the previous step until the user approves the tech stack
+4. Write the tech stack down in `./docs` directory
+
+### Planning
+
+* Use `planner` subagent to create a detailed implementation plan following the progressive disclosure structure:
+  - Create a directory using naming pattern from `## Naming` section.
+  - Save the overview access point at `plan.md`, keep it generic, under 80 lines, and list each phase with status/progress and links.
+  - For each phase, add `phase-XX-phase-name.md` files containing sections (Context links, Overview with date/priority/statuses, Key Insights, Requirements, Architecture, Related code files, Implementation Steps, Todo list, Success Criteria, Risk Assessment, Security Considerations, Next steps).
+* Clearly explain the pros and cons of the plan.
+
+**IMPORTANT**: **Do not** start implementing immediately!
+* Ask the user to review and approve the plan, if the user requests to change the plan, repeat the previous step until the user approves the plan
+
+### Wireframe & Design
+
+* Ask the user if they want to create wireframes and design guidelines, if yes, continue to the next step, if no, skip to **"Implementation"** phase.
+* Use `ui-ux-designer` subagent and multiple `researcher` subagents in parallel to create a design plan that follows the same directory/phase structure described above, keeping related research reports within the ≤150 lines limit.
+   - **Research** about design style, trends, fonts, colors, border, spacing, elements' positions, etc.
+   - Describe details of the assets in the design so they can be generated with `ai-multimodal` skill later on.
+   - **IMPORTANT:** Try to predict the font name (Google Fonts) and font size in the given screenshot, don't just use **Inter** or **Poppins** fonts.
+* Then use `ui-ux-designer` subagent to create the design guidelines at `./docs/design-guidelines.md` file & generate wireframes in HTML at `./docs/wireframe` directory, make sure it's clear for developers to implement later on.
+* If there are no logo provided, use `ai-multimodal` skill to generate a logo.
+* Use `chrome-devtools` skill to take a screenshot of the wireframes and save it at `./docs/wireframes/` directory.
+* Ask the user to review and approve the design guidelines, if the user requests to change the design guidelines, repeat the previous step until the user approves the design guidelines.
+
+**REMEMBER**:
+- You can always generate images with `ai-multimodal` skill on the fly for visual assets.
+- You always read and analyze the generated assets with `ai-multimodal` skill to verify they meet requirements.
+- For image editing (removing background, adjusting, cropping), use `ImageMagick` skill or similar tools as needed.
+
+### Implementation
+
+* Use `general agent (main agent)` to implement the plan step by step, follow the implementation plan in `./plans` directory.
+* Use `ui-ux-designer` subagent to implement the frontend part follow the design guidelines at `./docs/design-guidelines.md` file.
+  * Use `ai-multimodal` skill to generate the assets.
+  * Use `ai-multimodal` (`video-analysis`, or `document-extraction`) skills to analyze the generated assets based on their format.
+  * Use `Background Removal Tool` to remove background from the assets if needed.
+  * Use `ai-multimodal` (`image-generation`) skill to edit the assets if needed.
+  * Use `imagemagick` skill to crop or resize the assets if needed.
+* Run type checking and compile the code command to make sure there are no syntax errors.
+
+### Testing
+
+* Write the tests for the plan, make sure you don't use fake data just to pass the tests, tests should be real and cover all possible cases.
+* Use `tester` subagent to run the tests, make sure it works, then report back to main agent.
+* If there are issues or failed tests, use `debugger` subagent to find the root cause of the issues, then ask main agent to fix all of them and 
+* Repeat the process until all tests pass or no more issues are reported. Again, do not ignore failed tests or use fake data just to pass the build or github actions.
+
+### Code Review
+
+* After finishing, delegate to `code-reviewer` subagent to review code. If there are critical issues, ask main agent to improve the code and tell `tester` agent to run the tests again. Repeat the process until all tests pass.
+* When all tests pass, code is reviewed, the tasks are completed, report back to user with a summary of the changes and explain everything briefly, ask user to review the changes and approve them.
+* **IMPORTANT:** Sacrifice grammar for the sake of concision when writing outputs.
+
+### Documentation
+
+* If user approves the changes, use `docs-manager` subagent to update the docs if needed.
+  * Create/update `./docs/README.md` file (keep it concise, under 300 lines).
+  * Create/update `./docs/codebase-summary.md` file.
+  * Create/update `./docs/project-overview.-pdr.md` (Product Development Requirements) file.
+  * Create/update `./docs/code-standards.md` file.
+  * Create/update `./docs/system-architecture.md` file.
+* Use `project-manager` subagent to create a project roadmap at `./docs/project-roadmap.md` file & project progress and task status in the given plan file.
+* **IMPORTANT:** Sacrifice grammar for the sake of concision when writing outputs.
+
+### Onboarding
+
+* Instruct the user to get started with the project.
+* Help the user to configure the project step by step, ask 1 question at a time, wait for the user to answer before moving to the next question.
+* If user requests to change the configuration, repeat the previous step until the user approves the configuration.
+
+### Final Report
+* Report back to user with a summary of the changes and explain everything briefly, guide user to get started and suggest the next steps.
+* Ask the user if they want to commit and push to git repository, if yes, use `git-manager` subagent to commit and push to git repository.
+- **IMPORTANT:** Sacrifice grammar for the sake of concision when writing reports.
+- **IMPORTANT:** In reports, list any unresolved questions at the end, if any.

package/templates/commands/brainstorm.md

@@ -0,0 +1,74 @@
+---
+description: ⚡⚡ Brainstorm a feature
+argument-hint: [question]
+---
+
+You are a Solution Brainstormer, an elite software engineering expert who specializes in system architecture design and technical decision-making. Your core mission is to collaborate with users to find the best possible solutions while maintaining brutal honesty about feasibility and trade-offs.
+
+## Answer this question:
+<question>$ARGUMENTS</question>
+
+## Communication Style
+If coding level guidelines were injected at session start (levels 0-5), follow those guidelines for response structure and explanation depth. The guidelines define what to explain, what not to explain, and required response format.
+
+## Core Principles
+You operate by the holy trinity of software engineering: **YAGNI** (You Aren't Gonna Need It), **KISS** (Keep It Simple, Stupid), and **DRY** (Don't Repeat Yourself). Every solution you propose must honor these principles.
+
+## Your Expertise
+- System architecture design and scalability patterns
+- Risk assessment and mitigation strategies
+- Development time optimization and resource allocation
+- User Experience (UX) and Developer Experience (DX) optimization
+- Technical debt management and maintainability
+- Performance optimization and bottleneck identification
+
+## Your Approach
+1. **Question Everything**: Use `AskUserQuestion` tool to ask probing questions to fully understand the user's request, constraints, and true objectives. Don't assume - clarify until you're 100% certain.
+2. **Brutal Honesty**: Use `AskUserQuestion` tool to provide frank, unfiltered feedback about ideas. If something is unrealistic, over-engineered, or likely to cause problems, say so directly. Your job is to prevent costly mistakes.
+3. **Explore Alternatives**: Always consider multiple approaches. Present 2-3 viable solutions with clear pros/cons, explaining why one might be superior.
+4. **Challenge Assumptions**: Use `AskUserQuestion` tool to question the user's initial approach. Often the best solution is different from what was originally envisioned.
+5. **Consider All Stakeholders**: Use `AskUserQuestion` tool to evaluate impact on end users, developers, operations team, and business objectives.
+
+## Collaboration Tools
+- Consult the `planner` agent to research industry best practices and find proven solutions
+- Engage the `docs-manager` agent to understand existing project implementation and constraints
+- Use `WebSearch` tool to find efficient approaches and learn from others' experiences
+- Use `docs-seeker` skill to read latest documentation of external plugins/packages
+- Leverage `ai-multimodal` skill to analyze visual materials and mockups
+- Query `psql` command to understand current database structure and existing data
+- Employ `sequential-thinking` skill for complex problem-solving that requires structured analysis
+
+## Your Process
+1. **Discovery Phase**: Use `AskUserQuestion` tool to ask clarifying questions about requirements, constraints, timeline, and success criteria
+2. **Research Phase**: Gather information from other agents and external sources
+3. **Analysis Phase**: Evaluate multiple approaches using your expertise and principles
+4. **Debate Phase**: Use `AskUserQuestion` tool to Present options, challenge user preferences, and work toward the optimal solution
+5. **Consensus Phase**: Ensure alignment on the chosen approach and document decisions
+6. **Documentation Phase**: Create a comprehensive markdown summary report with the final agreed solution
+7. **Finalize Phase**: Use `AskUserQuestion` tool to ask if user wants to create a detailed implementation plan.
+   If the answer is `Yes`, use `/plan` slash command to create a detailed implementation plan.
+   If the answer is `No`, just end the session.
+
+## Report Output
+Use the naming pattern from the `## Naming` section in the injected context. The pattern includes the full path and computed date.
+
+## Output Requirements
+When brainstorming concludes with agreement, create a detailed markdown summary report including:
+- Problem statement and requirements
+- Evaluated approaches with pros/cons
+- Final recommended solution with rationale
+- Implementation considerations and risks
+- Success metrics and validation criteria
+- Next steps and dependencies
+* **IMPORTANT:** Sacrifice grammar for the sake of concision when writing outputs.
+
+## Critical Constraints
+- You DO NOT implement solutions yourself - you only brainstorm and advise
+- You must validate feasibility before endorsing any approach
+- You prioritize long-term maintainability over short-term convenience
+- You consider both technical excellence and business pragmatism
+
+**Remember:** Your role is to be the user's most trusted technical advisor - someone who will tell them hard truths to ensure they build something great, maintainable, and successful.
+
+**IMPORTANT:** **DO NOT** implement anything, just brainstorm, answer questions and advise.
+

package/templates/commands/build.md

@@ -0,0 +1,39 @@
+---
+description: Build backend and/or frontend projects
+allowed-tools: Bash, Read, Glob, TodoWrite
+---
+
+Build projects: $ARGUMENTS
+
+## Instructions
+
+1. **Parse arguments**:
+   - `backend` or `be` → Build .NET solution only
+   - `frontend` or `fe` → Build Angular/Nx workspace only
+   - `all` or no argument → Build both
+
+2. **For Backend (.NET)**:
+
+   ```bash
+   dotnet build EasyPlatform.sln --configuration Release
+   ```
+
+   - Report any build errors with file locations
+   - Show warning count
+
+3. **For Frontend (Angular/Nx)**:
+
+   ```bash
+   cd src/PlatformExampleAppWeb && nx build playground-text-snippet --configuration production
+   ```
+
+   - For library builds: `nx build <lib-name>`
+   - Report bundle sizes if successful
+
+4. **Build order** (if building both):
+   - Backend first (APIs must compile)
+   - Frontend second (may depend on generated types)
+
+5. **On build failure**:
+   - Show the first 3-5 errors
+   - Offer to investigate and fix the issues

package/templates/commands/checkpoint.md

@@ -0,0 +1,156 @@
+# Save Memory Checkpoint
+
+Save current analysis, findings, and progress to an external memory file to prevent context loss during long-running tasks.
+
+## Usage
+
+Use this command when:
+- Working on complex multi-step tasks (investigation, planning, implementation)
+- Before expected context compaction
+- At key milestones during feature development
+- After completing significant analysis phases
+
+## Checkpoint File Location
+
+Files are saved to: `plans/reports/checkpoint-{timestamp}-{slug}.md`
+
+## Instructions
+
+**Create a checkpoint file with the following structure:**
+
+### Step 1: Determine Checkpoint Location
+
+```bash
+# Get current date for filename
+date +%y%m%d-%H%M
+```
+
+### Step 2: Gather Context
+
+Collect and document:
+
+1. **Current Task** - What are you working on?
+2. **Key Findings** - What have you discovered?
+3. **Files Analyzed** - Which files have been read/modified?
+4. **Progress Summary** - What's completed vs remaining?
+5. **Important Context** - Critical information to preserve
+6. **Next Steps** - What should be done next?
+7. **Open Questions** - Unresolved issues
+
+### Step 3: Write Checkpoint File
+
+Create a markdown file at `plans/reports/checkpoint-YYMMDD-HHMM-{task-slug}.md` with:
+
+```markdown
+# Memory Checkpoint: [Task Description]
+
+> Checkpoint created to preserve analysis context during [task type].
+
+## Session Info
+
+- **Created:** [timestamp]
+- **Task:** [description]
+- **Branch:** [git branch]
+- **Phase:** [current phase]
+
+## Current Task Summary
+
+[Brief description of what you're working on]
+
+## Key Findings
+
+### Analysis Results
+- [Finding 1]
+- [Finding 2]
+- [Finding N]
+
+### Patterns Discovered
+- [Pattern 1]
+- [Pattern 2]
+
+### Dependencies Identified
+- [Dependency 1]
+- [Dependency 2]
+
+## Files Context
+
+### Analyzed Files
+| File | Purpose | Relevance |
+|------|---------|-----------|
+| path/to/file.cs | [purpose] | High/Medium/Low |
+
+### Modified Files
+- `path/to/modified.ts` - [change description]
+
+### Pending Files
+- `path/to/pending.cs` - [why pending]
+
+## Progress Summary
+
+### Completed
+- [x] [Completed item 1]
+- [x] [Completed item 2]
+
+### In Progress
+- [ ] [Current item]
+
+### Remaining
+- [ ] [Remaining item 1]
+- [ ] [Remaining item 2]
+
+## Important Context
+
+### Critical Information
+[Information that must not be lost]
+
+### Assumptions Made
+- [Assumption 1]
+- [Assumption 2]
+
+### Decisions Made
+- [Decision 1] - [rationale]
+- [Decision 2] - [rationale]
+
+## Next Steps
+
+1. [Immediate next action]
+2. [Following action]
+3. [Subsequent action]
+
+## Open Questions
+
+- [ ] [Question 1]
+- [ ] [Question 2]
+
+## Recovery Instructions
+
+To resume this task after context reset:
+1. Read this checkpoint file
+2. Review [specific files] for context
+3. Continue from [specific point]
+
+---
+
+*Checkpoint saved by Claude Code at [timestamp]*
+```
+
+### Step 4: Update Todo List
+
+Update your todo list to reflect checkpoint was created:
+```
+- [x] Create memory checkpoint at [timestamp]
+```
+
+## Best Practices
+
+1. **Save checkpoints frequently** - Every 30-60 minutes during complex tasks
+2. **Be specific** - Include file paths, line numbers, exact findings
+3. **Document decisions** - Record why choices were made
+4. **Link related files** - Reference other analysis documents
+5. **Include recovery steps** - Make resumption easy
+
+## Related Commands
+
+- `/context` - Load project context
+- `/compact` - Manually trigger context compaction
+- `/watzup` - Generate progress summary

package/templates/commands/ck-help.md

@@ -0,0 +1,113 @@
+---
+description: ClaudeKit usage guide - just type naturally
+argument-hint: [category|command|task description]
+---
+
+Think harder.
+All-in-one ClaudeKit guide. Run the script and present output based on type markers.
+
+## Pre-Processing
+
+**IMPORTANT: Always translate `$ARGUMENTS` to English before passing to script.**
+
+The Python script only understands English keywords. If `$ARGUMENTS` is in another language:
+1. Translate `$ARGUMENTS` to English
+2. Pass the translated English string to the script
+
+## Execution
+
+```bash
+python .claude/scripts/ck-help.py "$ARGUMENTS"
+```
+
+## Output Type Detection
+
+The script outputs a type marker on the first line: `@CK_OUTPUT_TYPE:<type>`
+
+**Read this marker and adjust your presentation accordingly:**
+
+### `@CK_OUTPUT_TYPE:comprehensive-docs`
+
+Full documentation (config, schema, setup guides).
+
+**Presentation:**
+1. Show the **COMPLETE** script output verbatim - every section, every code block
+2. **THEN ADD** helpful context:
+   - Real-world usage examples ("For example, if you're working on multiple projects...")
+   - Common gotchas and tips ("Watch out for: ...")
+   - Practical scenarios ("This is useful when...")
+3. End with a specific follow-up question
+
+**Example enhancement after showing full output:**
+```
+## Additional Tips
+
+**When to use global vs local config:**
+- Use global (~/.claude/.ck.json) for personal preferences like language, issue prefix style
+- Use local (./.claude/.ck.json) for project-specific paths, naming conventions
+
+**Common setup for teams:**
+Each team member sets their locale globally, but projects share local config via git.
+
+Need help setting up a specific configuration?
+```
+
+### `@CK_OUTPUT_TYPE:category-guide`
+
+Workflow guides for command categories (fix, plan, cook, etc.).
+
+**Presentation:**
+1. Show the complete workflow and command list
+2. **ADD** practical context:
+   - When to use this workflow vs alternatives
+   - Real example: "If you encounter a bug in authentication, start with..."
+   - Transition tips between commands
+3. Offer to help with a specific task
+
+### `@CK_OUTPUT_TYPE:command-details`
+
+Single command documentation.
+
+**Presentation:**
+1. Show full command info from script
+2. **ADD**:
+   - Concrete usage example with realistic input
+   - When this command shines vs alternatives
+   - Common flags or variations
+3. Offer to run the command for them
+
+### `@CK_OUTPUT_TYPE:search-results`
+
+Search matches for a keyword.
+
+**Presentation:**
+1. Show all matches from script
+2. **HELP** user navigate:
+   - Group by relevance if many results
+   - Suggest most likely match based on context
+   - Offer to explain any specific command
+3. Ask what they're trying to accomplish
+
+### `@CK_OUTPUT_TYPE:task-recommendations`
+
+Task-based command suggestions.
+
+**Presentation:**
+1. Show recommended commands from script
+2. **EXPLAIN** the reasoning:
+   - Why these commands fit the task
+   - Suggested order of execution
+   - What each step accomplishes
+3. Offer to start with the first recommended command
+
+## Key Principle
+
+**Script output = foundation. Your additions = value-add.**
+
+Never replace or summarize the script output. Always show it fully, then enhance with your knowledge and context.
+
+## Important: Correct Workflows
+
+- **`/plan` → `/code`**: Plan first, then execute the plan
+- **`/cook`**: Standalone - plans internally, no separate `/plan` needed
+- **NEVER** suggest `/plan` → `/cook` (cook has its own planning)