thanh-kit 2.5.0 → 2.5.1

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

@@ -1,202 +0,0 @@
-# Examples: Planning with Files in Action
-
-## Example 1: Research Task
-
-**User Request:** "Research the benefits of morning exercise and write a summary"
-
-### Loop 1: Create Plan
-```bash
-Write task_plan.md
-```
-
-```markdown
-# Task Plan: Morning Exercise Benefits Research
-
-## Goal
-Create a research summary on the benefits of morning exercise.
-
-## Phases
-- [ ] Phase 1: Create this plan ✓
-- [ ] Phase 2: Search and gather sources
-- [ ] Phase 3: Synthesize findings
-- [ ] Phase 4: Deliver summary
-
-## Key Questions
-1. What are the physical health benefits?
-2. What are the mental health benefits?
-3. What scientific studies support this?
-
-## Status
-**Currently in Phase 1** - Creating plan
-```
-
-### Loop 2: Research
-```bash
-Read task_plan.md           # Refresh goals
-WebSearch "morning exercise benefits"
-Write notes.md              # Store findings
-Edit task_plan.md           # Mark Phase 2 complete
-```
-
-### Loop 3: Synthesize
-```bash
-Read task_plan.md           # Refresh goals
-Read notes.md               # Get findings
-Write morning_exercise_summary.md
-Edit task_plan.md           # Mark Phase 3 complete
-```
-
-### Loop 4: Deliver
-```bash
-Read task_plan.md           # Verify complete
-Deliver morning_exercise_summary.md
-```
-
----
-
-## Example 2: Bug Fix Task
-
-**User Request:** "Fix the login bug in the authentication module"
-
-### task_plan.md
-```markdown
-# Task Plan: Fix Login Bug
-
-## Goal
-Identify and fix the bug preventing successful login.
-
-## Phases
-- [x] Phase 1: Understand the bug report ✓
-- [x] Phase 2: Locate relevant code ✓
-- [ ] Phase 3: Identify root cause (CURRENT)
-- [ ] Phase 4: Implement fix
-- [ ] Phase 5: Test and verify
-
-## Key Questions
-1. What error message appears?
-2. Which file handles authentication?
-3. What changed recently?
-
-## Decisions Made
-- Auth handler is in src/auth/login.ts
-- Error occurs in validateToken() function
-
-## Errors Encountered
-- [Initial] TypeError: Cannot read property 'token' of undefined
-  → Root cause: user object not awaited properly
-
-## Status
-**Currently in Phase 3** - Found root cause, preparing fix
-```
-
----
-
-## Example 3: Feature Development
-
-**User Request:** "Add a dark mode toggle to the settings page"
-
-### The 3-File Pattern in Action
-
-**task_plan.md:**
-```markdown
-# Task Plan: Dark Mode Toggle
-
-## Goal
-Add functional dark mode toggle to settings.
-
-## Phases
-- [x] Phase 1: Research existing theme system ✓
-- [x] Phase 2: Design implementation approach ✓
-- [ ] Phase 3: Implement toggle component (CURRENT)
-- [ ] Phase 4: Add theme switching logic
-- [ ] Phase 5: Test and polish
-
-## Decisions Made
-- Using CSS custom properties for theme
-- Storing preference in localStorage
-- Toggle component in SettingsPage.tsx
-
-## Status
-**Currently in Phase 3** - Building toggle component
-```
-
-**notes.md:**
-```markdown
-# Notes: Dark Mode Implementation
-
-## Existing Theme System
-- Located in: src/styles/theme.ts
-- Uses: CSS custom properties
-- Current themes: light only
-
-## Files to Modify
-1. src/styles/theme.ts - Add dark theme colors
-2. src/components/SettingsPage.tsx - Add toggle
-3. src/hooks/useTheme.ts - Create new hook
-4. src/App.tsx - Wrap with ThemeProvider
-
-## Color Decisions
-- Dark background: #1a1a2e
-- Dark surface: #16213e
-- Dark text: #eaeaea
-```
-
-**dark_mode_implementation.md:** (deliverable)
-```markdown
-# Dark Mode Implementation
-
-## Changes Made
-
-### 1. Added dark theme colors
-File: src/styles/theme.ts
-...
-
-### 2. Created useTheme hook
-File: src/hooks/useTheme.ts
-...
-```
-
----
-
-## Example 4: Error Recovery Pattern
-
-When something fails, DON'T hide it:
-
-### Before (Wrong)
-```
-Action: Read config.json
-Error: File not found
-Action: Read config.json  # Silent retry
-Action: Read config.json  # Another retry
-```
-
-### After (Correct)
-```
-Action: Read config.json
-Error: File not found
-
-# Update task_plan.md:
-## Errors Encountered
-- config.json not found → Will create default config
-
-Action: Write config.json (default config)
-Action: Read config.json
-Success!
-```
-
----
-
-## The Read-Before-Decide Pattern
-
-**Always read your plan before major decisions:**
-
-```
-[Many tool calls have happened...]
-[Context is getting long...]
-[Original goal might be forgotten...]
-
-→ Read task_plan.md          # This brings goals back into attention!
-→ Now make the decision       # Goals are fresh in context
-```
-
-This is why Manus can handle ~50 tool calls without losing track. The plan file acts as a "goal refresh" mechanism.

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

@@ -1,110 +0,0 @@
-# Reference: Manus Context Engineering Principles
-
-This skill is based on the context engineering principles from Manus, the AI agent company acquired by Meta for $2 billion in December 2025.
-
-## The 6 Manus Principles
-
-### 1. Filesystem as External Memory
-
-> "Markdown is my 'working memory' on disk."
-
-**Problem:** Context windows have limits. Stuffing everything in context degrades performance and increases costs.
-
-**Solution:** Treat the filesystem as unlimited memory:
-- Store large content in files
-- Keep only paths in context
-- Agent can "look up" information when needed
-- Compression must be REVERSIBLE
-
-### 2. Attention Manipulation Through Repetition
-
-**Problem:** After ~50 tool calls, models forget original goals ("lost in the middle" effect).
-
-**Solution:** Keep a `task_plan.md` file that gets RE-READ throughout execution:
-```
-Start of context: [Original goal - far away, forgotten]
-...many tool calls...
-End of context: [Recently read task_plan.md - gets ATTENTION!]
-```
-
-By reading the plan file before each decision, goals appear in the attention window.
-
-### 3. Keep Failure Traces
-
-> "Error recovery is one of the clearest signals of TRUE agentic behavior."
-
-**Problem:** Instinct says hide errors, retry silently. This wastes tokens and loses learning.
-
-**Solution:** KEEP failed actions in the plan file:
-```markdown
-## Errors Encountered
-- [2025-01-03] FileNotFoundError: config.json not found → Created default config
-- [2025-01-03] API timeout → Retried with exponential backoff, succeeded
-```
-
-The model updates its internal understanding when seeing failures.
-
-### 4. Avoid Few-Shot Overfitting
-
-> "Uniformity breeds fragility."
-
-**Problem:** Repetitive action-observation pairs cause drift and hallucination.
-
-**Solution:** Introduce controlled variation:
-- Vary phrasings slightly
-- Don't copy-paste patterns blindly
-- Recalibrate on repetitive tasks
-
-### 5. Stable Prefixes for Cache Optimization
-
-**Problem:** Agents are input-heavy (100:1 ratio). Every token costs money.
-
-**Solution:** Structure for cache hits:
-- Put static content FIRST
-- Append-only context (never modify history)
-- Consistent serialization
-
-### 6. Append-Only Context
-
-**Problem:** Modifying previous messages invalidates KV-cache.
-
-**Solution:** NEVER modify previous messages. Always append new information.
-
-## The Agent Loop
-
-Manus operates in a continuous loop:
-
-```
-1. Analyze → 2. Think → 3. Select Tool → 4. Execute → 5. Observe → 6. Iterate → 7. Deliver
-```
-
-### File Operations in the Loop:
-
-| Operation | When to Use |
-|-----------|-------------|
-| `write` | New files or complete rewrites |
-| `append` | Adding sections incrementally |
-| `edit` | Updating specific parts (checkboxes, status) |
-| `read` | Reviewing before decisions |
-
-## Manus Statistics
-
-| Metric | Value |
-|--------|-------|
-| Average tool calls per task | ~50 |
-| Input-to-output ratio | 100:1 |
-| Acquisition price | $2 billion |
-| Time to $100M revenue | 8 months |
-
-## Key Quotes
-
-> "If the model improvement is the rising tide, we want Manus to be the boat, not the piling stuck on the seafloor."
-
-> "For complex tasks, I save notes, code, and findings to files so I can reference them as I work."
-
-> "I used file.edit to update checkboxes in my plan as I progressed, rather than rewriting the whole file."
-
-## Source
-
-Based on Manus's official context engineering documentation:
-https://manus.im/de/blog/Context-Engineering-for-AI-Agents-Lessons-from-Building-Manus

package/templates/skills/project-index/SKILL.md

@@ -1,97 +0,0 @@
----
-name: project-index
-description: Generate and maintain a project structure index for fast AI navigation. Creates docs/structure.md with an AI-friendly map + tree. Use when starting a new project, after major changes, or when docs/structure.md is stale.
----
-
-# Project Index Skill
-
-Generate an AI-friendly `docs/structure.md` so agents can understand project layout quickly without scanning the whole repo.
-
-## When to Use
-
-- First time: project has no `docs/structure.md`
-- After major changes: added/removed modules, moved folders, renamed domains/features
-- When `docs/structure.md` looks stale or misleading
-- On demand: user says “update structure”, “refresh index”, “scan project”
-
-## Output
-
-- File: `docs/structure.md`
-- Content: **Top-Level Map** (purpose hints) + directory tree + entry points + config/key files + file-type distribution
-
-## Scripts (Recommended)
-
-### Python (recommended default)
-```bash
-python .claude/skills/project-index/scripts/scan_structure.py . 4 > docs/structure.md
-```
-
-### Node.js
-```bash
-node .claude/skills/project-index/scripts/scan-structure.js . 4 > docs/structure.md
-```
-
-### Flags
-
-- `json`: output JSON instead of Markdown
-- `--no-gitignore`: ignore `.gitignore` rules and scan everything (not recommended)
-
-## Script Behavior (What “optimized” means)
-
-- Respects `.gitignore` patterns by default (simplified matching)
-- Has built-in ignores for common noise:
-  - dependencies/build outputs: `node_modules/`, `dist/`, `build/`, `coverage/`, `.next/`, `.nuxt/`, `.turbo/`
-  - virtualenv/caches: `venv/`, `.venv/`, `.tox/`, `__pycache__/`, `.pytest_cache/`, `.mypy_cache/`, `.ruff_cache/`
-  - IDE: `.vscode/`, `.idea/`
-  - typical build outputs: `bin/`, `obj/`, `target/`
-  - secrets files: `.env*`
-- Uses ASCII tree connectors (`|--`, ``--`) to avoid encoding issues on Windows terminals
-- Generates a **Top-Level Map** with heuristic purpose descriptions (fast navigation)
-
-## Expected Structure File Format
-
-```markdown
-# Project Structure Index
-> Auto-generated by project-index. Last updated: YYYY-MM-DD HH:mm
-
-## Quick Stats
-- Total files: X
-- Total directories: Y
-- Main language: TypeScript/Python/etc
-
-## Top-Level Map
-| Path | Type | Purpose |
-|:---|:---:|:---|
-| src/ | dir | Main application source code |
-| apps/ | dir | Application(s) (often runnable targets) |
-| packages/ | dir | Packages (shared modules/libraries) |
-| docs/ | dir | Documentation |
-| README.md | file | Project overview and getting started |
-
-## Directory Tree
-```
-repo/
-|-- src/
-|   `-- ...
-`-- README.md
-```
-
-## Entry Points
-- src/index.ts
-
-## Config Files
-- package.json
-
-## Key Files
-- README.md
-
-## File Distribution
-| Category | Count |
-|:---|---:|
-| typescript | 120 |
-```
-
-## Integration Notes
-
-- Agents should **read `docs/structure.md` first** for large/broad tasks, then use `rg` for precise lookup.
-- A stale `docs/structure.md` is worse than none; refresh it after restructures.