thatgfsj-code 2.2.9 → 3.0.0

package/src/skills/brainstorming.ts

@@ -1,43 +1,43 @@
-import type { Skill } from './index.js';
-
-export const brainstormingSkill: Skill = {
-  id: 'brainstorming',
-  name: 'Brainstorming',
-  description: 'Explore multiple approaches before committing to a solution',
-  category: 'planning',
-  autoActivate: ['怎么', 'how to', '方案', 'approach', '有没有', 'alternatives'],
-  prompt: `## Brainstorming Mode
-
-When exploring solutions, don't jump to the first idea. Instead:
-
-### 1. Generate Options
-List 3-5 different approaches, including at least one unconventional one.
-
-### 2. Evaluate Each
-For each approach, briefly note:
-- **Pros**: What makes it good
-- **Cons**: What could go wrong
-- **Effort**: How much work (quick/medium/heavy)
-
-### 3. Recommend
-Pick the best approach and explain WHY it's the best fit for this specific situation.
-
-### Format
-\`\`\`
-## Approaches
-
-### Option A: [Name]
-- Pros: ...
-- Cons: ...
-- Effort: medium
-
-### Option B: [Name]
-- Pros: ...
-- Cons: ...
-- Effort: quick
-
-**Recommendation**: Option B because [specific reason]
-\`\`\`
-
-Don't just list options - give a clear recommendation with reasoning.`,
-};
+import type { Skill } from './index.js';
+
+export const brainstormingSkill: Skill = {
+  id: 'brainstorming',
+  name: 'Brainstorming',
+  description: 'Explore multiple approaches before committing to a solution',
+  category: 'planning',
+  autoActivate: ['怎么', 'how to', '方案', 'approach', '有没有', 'alternatives'],
+  prompt: `## Brainstorming Mode
+
+When exploring solutions, don't jump to the first idea. Instead:
+
+### 1. Generate Options
+List 3-5 different approaches, including at least one unconventional one.
+
+### 2. Evaluate Each
+For each approach, briefly note:
+- **Pros**: What makes it good
+- **Cons**: What could go wrong
+- **Effort**: How much work (quick/medium/heavy)
+
+### 3. Recommend
+Pick the best approach and explain WHY it's the best fit for this specific situation.
+
+### Format
+\`\`\`
+## Approaches
+
+### Option A: [Name]
+- Pros: ...
+- Cons: ...
+- Effort: medium
+
+### Option B: [Name]
+- Pros: ...
+- Cons: ...
+- Effort: quick
+
+**Recommendation**: Option B because [specific reason]
+\`\`\`
+
+Don't just list options - give a clear recommendation with reasoning.`,
+};

package/src/skills/code-review.ts

@@ -1,45 +1,45 @@
-import type { Skill } from './index.js';
-
-export const codeReviewSkill: Skill = {
-  id: 'code-review',
-  name: 'Code Review',
-  description: 'Systematic code review for quality, security, and correctness',
-  category: 'review',
-  autoActivate: ['review', '审查', '检查代码', 'code quality'],
-  prompt: `## Code Review Checklist
-
-When reviewing code (your own or others):
-
-### Correctness
-- Does it do what it's supposed to?
-- Are edge cases handled?
-- Are error cases handled?
-
-### Security
-- No hardcoded secrets or API keys
-- Input validation on user data
-- No SQL injection, XSS, or path traversal risks
-
-### Performance
-- No unnecessary loops or allocations
-- Efficient data structures
-- No N+1 queries or blocking calls
-
-### Readability
-- Clear variable/function names
-- Appropriate comments (why, not what)
-- Consistent style with codebase
-
-### Testability
-- Can this be easily tested?
-- Are dependencies injectable?
-- Are side effects isolated?
-
-### Output Format
-\`\`\`
-## Review Summary
-✅ Good: [what's done well]
-⚠️ Suggestions: [improvements]
-🔴 Issues: [must fix]
-\`\`\``,
-};
+import type { Skill } from './index.js';
+
+export const codeReviewSkill: Skill = {
+  id: 'code-review',
+  name: 'Code Review',
+  description: 'Systematic code review for quality, security, and correctness',
+  category: 'review',
+  autoActivate: ['review', '审查', '检查代码', 'code quality'],
+  prompt: `## Code Review Checklist
+
+When reviewing code (your own or others):
+
+### Correctness
+- Does it do what it's supposed to?
+- Are edge cases handled?
+- Are error cases handled?
+
+### Security
+- No hardcoded secrets or API keys
+- Input validation on user data
+- No SQL injection, XSS, or path traversal risks
+
+### Performance
+- No unnecessary loops or allocations
+- Efficient data structures
+- No N+1 queries or blocking calls
+
+### Readability
+- Clear variable/function names
+- Appropriate comments (why, not what)
+- Consistent style with codebase
+
+### Testability
+- Can this be easily tested?
+- Are dependencies injectable?
+- Are side effects isolated?
+
+### Output Format
+\`\`\`
+## Review Summary
+✅ Good: [what's done well]
+⚠️ Suggestions: [improvements]
+🔴 Issues: [must fix]
+\`\`\``,
+};

package/src/skills/executing-plans.ts

@@ -1,27 +1,27 @@
-import type { Skill } from './index.js';
-
-export const executingPlansSkill: Skill = {
-  id: 'executing-plans',
-  name: 'Executing Plans',
-  description: 'Execute multi-step plans methodically with verification',
-  category: 'planning',
-  prompt: `## Plan Execution Mode
-
-When executing a plan or multi-step task:
-
-1. **One step at a time** - Complete each step fully before moving to the next
-2. **Verify each step** - After each change, verify it works (read the file, run a test, check syntax)
-3. **Report progress** - Tell the user what you did for each step
-4. **Handle failures** - If a step fails, stop and explain. Don't silently skip.
-5. **Commit checkpoints** - After successful steps, suggest a git commit
-
-### Progress Format
-\`\`\`
-✅ Step 1: [What was done] - Verified
-✅ Step 2: [What was done] - Verified  
-⏳ Step 3: [Currently working on]
-⬜ Step 4: [Pending]
-\`\`\`
-
-If you encounter an unexpected issue, stop and ask the user how to proceed.`,
-};
+import type { Skill } from './index.js';
+
+export const executingPlansSkill: Skill = {
+  id: 'executing-plans',
+  name: 'Executing Plans',
+  description: 'Execute multi-step plans methodically with verification',
+  category: 'planning',
+  prompt: `## Plan Execution Mode
+
+When executing a plan or multi-step task:
+
+1. **One step at a time** - Complete each step fully before moving to the next
+2. **Verify each step** - After each change, verify it works (read the file, run a test, check syntax)
+3. **Report progress** - Tell the user what you did for each step
+4. **Handle failures** - If a step fails, stop and explain. Don't silently skip.
+5. **Commit checkpoints** - After successful steps, suggest a git commit
+
+### Progress Format
+\`\`\`
+✅ Step 1: [What was done] - Verified
+✅ Step 2: [What was done] - Verified  
+⏳ Step 3: [Currently working on]
+⬜ Step 4: [Pending]
+\`\`\`
+
+If you encounter an unexpected issue, stop and ask the user how to proceed.`,
+};

package/src/skills/frontend-design.ts

@@ -1,35 +1,35 @@
-import type { Skill } from './index.js';
-
-export const frontendDesignSkill: Skill = {
-  id: 'frontend-design',
-  name: 'Frontend Design',
-  description: 'UI/UX best practices for web interfaces',
-  category: 'architecture',
-  autoActivate: ['ui', 'ux', 'frontend', 'css', 'layout', 'design', '界面', '页面'],
-  prompt: `## Frontend Design Principles
-
-### Layout
-- Use CSS Grid for 2D layouts, Flexbox for 1D
-- Mobile-first: design for small screens, enhance for larger
-- Consistent spacing: use a 4px or 8px grid system
-
-### Typography
-- Max 2-3 font sizes per page
-- Line height: 1.5 for body, 1.2 for headings
-- Max line length: 60-80 characters
-
-### Color
-- Use a limited palette (primary, secondary, accent, neutral)
-- Ensure contrast ratio ≥ 4.5:1 for text
-- Use color purposefully (not just decoration)
-
-### Components
-- Keep components small and focused
-- Extract reusable patterns early
-- Props should be explicit, not spread
-
-### Performance
-- Lazy load images and heavy components
-- Minimize bundle size
-- Use skeleton loaders for async content`,
-};
+import type { Skill } from './index.js';
+
+export const frontendDesignSkill: Skill = {
+  id: 'frontend-design',
+  name: 'Frontend Design',
+  description: 'UI/UX best practices for web interfaces',
+  category: 'architecture',
+  autoActivate: ['ui', 'ux', 'frontend', 'css', 'layout', 'design', '界面', '页面'],
+  prompt: `## Frontend Design Principles
+
+### Layout
+- Use CSS Grid for 2D layouts, Flexbox for 1D
+- Mobile-first: design for small screens, enhance for larger
+- Consistent spacing: use a 4px or 8px grid system
+
+### Typography
+- Max 2-3 font sizes per page
+- Line height: 1.5 for body, 1.2 for headings
+- Max line length: 60-80 characters
+
+### Color
+- Use a limited palette (primary, secondary, accent, neutral)
+- Ensure contrast ratio ≥ 4.5:1 for text
+- Use color purposefully (not just decoration)
+
+### Components
+- Keep components small and focused
+- Extract reusable patterns early
+- Props should be explicit, not spread
+
+### Performance
+- Lazy load images and heavy components
+- Minimize bundle size
+- Use skeleton loaders for async content`,
+};

package/src/skills/git-workflow.ts

@@ -1,36 +1,36 @@
-import type { Skill } from './index.js';
-
-export const gitWorkflowSkill: Skill = {
-  id: 'git-workflow',
-  name: 'Git Workflow',
-  description: 'Clean git practices: commits, branches, PRs',
-  category: 'workflow',
-  autoActivate: ['git', 'commit', 'branch', 'merge', 'push', 'pull request'],
-  prompt: `## Git Best Practices
-
-### Commits
-- **Atomic**: One logical change per commit
-- **Message format**: \`type(scope): description\`
-  - feat: new feature
-  - fix: bug fix
-  - refactor: code restructuring
-  - docs: documentation
-  - test: adding tests
-  - chore: maintenance
-
-### Before Committing
-1. Review changes: \`git diff --staged\`
-2. Run tests
-3. Check for secrets or debug code
-
-### Branch Naming
-- \`feature/description\` - New features
-- \`fix/description\` - Bug fixes
-- \`refactor/description\` - Code improvements
-
-### Workflow
-1. Create branch from main
-2. Make changes with atomic commits
-3. Push and create PR
-4. Squash merge to main`,
-};
+import type { Skill } from './index.js';
+
+export const gitWorkflowSkill: Skill = {
+  id: 'git-workflow',
+  name: 'Git Workflow',
+  description: 'Clean git practices: commits, branches, PRs',
+  category: 'workflow',
+  autoActivate: ['git', 'commit', 'branch', 'merge', 'push', 'pull request'],
+  prompt: `## Git Best Practices
+
+### Commits
+- **Atomic**: One logical change per commit
+- **Message format**: \`type(scope): description\`
+  - feat: new feature
+  - fix: bug fix
+  - refactor: code restructuring
+  - docs: documentation
+  - test: adding tests
+  - chore: maintenance
+
+### Before Committing
+1. Review changes: \`git diff --staged\`
+2. Run tests
+3. Check for secrets or debug code
+
+### Branch Naming
+- \`feature/description\` - New features
+- \`fix/description\` - Bug fixes
+- \`refactor/description\` - Code improvements
+
+### Workflow
+1. Create branch from main
+2. Make changes with atomic commits
+3. Push and create PR
+4. Squash merge to main`,
+};

package/src/skills/improve-architecture.ts

@@ -1,38 +1,38 @@
-import type { Skill } from './index.js';
-
-export const improveArchitectureSkill: Skill = {
-  id: 'improve-architecture',
-  name: 'Improve Architecture',
-  description: 'Systematically improve codebase structure and quality',
-  category: 'architecture',
-  autoActivate: ['重构', 'refactor', '架构', 'architecture', 'clean', 'improve'],
-  prompt: `## Architecture Improvement Protocol
-
-When improving code structure:
-
-### 1. Assess Current State
-- Read the code and identify pain points
-- Look for: god classes, circular dependencies, tight coupling, code duplication
-
-### 2. Identify Patterns
-- **Single Responsibility**: Does each module/class do ONE thing?
-- **Dependency Direction**: Do high-level modules depend on low-level ones?
-- **Abstraction Level**: Is each layer at the right abstraction?
-
-### 3. Plan Changes
-- Start with the highest-impact, lowest-risk change
-- Each change should be independently valuable
-- Never refactor everything at once
-
-### 4. Execute Safely
-- Make one change at a time
-- Verify after each change
-- Commit frequently
-
-### Red Flags to Fix
-- Files over 300 lines
-- Functions over 50 lines
-- More than 3 levels of nesting
-- Copy-pasted code blocks
-- Circular imports`,
-};
+import type { Skill } from './index.js';
+
+export const improveArchitectureSkill: Skill = {
+  id: 'improve-architecture',
+  name: 'Improve Architecture',
+  description: 'Systematically improve codebase structure and quality',
+  category: 'architecture',
+  autoActivate: ['重构', 'refactor', '架构', 'architecture', 'clean', 'improve'],
+  prompt: `## Architecture Improvement Protocol
+
+When improving code structure:
+
+### 1. Assess Current State
+- Read the code and identify pain points
+- Look for: god classes, circular dependencies, tight coupling, code duplication
+
+### 2. Identify Patterns
+- **Single Responsibility**: Does each module/class do ONE thing?
+- **Dependency Direction**: Do high-level modules depend on low-level ones?
+- **Abstraction Level**: Is each layer at the right abstraction?
+
+### 3. Plan Changes
+- Start with the highest-impact, lowest-risk change
+- Each change should be independently valuable
+- Never refactor everything at once
+
+### 4. Execute Safely
+- Make one change at a time
+- Verify after each change
+- Commit frequently
+
+### Red Flags to Fix
+- Files over 300 lines
+- Functions over 50 lines
+- More than 3 levels of nesting
+- Copy-pasted code blocks
+- Circular imports`,
+};