@localtech/claude-code-toolkit 1.0.3 → 1.0.5

package/templates/AGENTS.md

@@ -0,0 +1,127 @@
+# Project Agents Configuration
+
+This file defines the autonomous agents available in this project workspace.
+
+## Code Review Agent
+
+**Name**: code-reviewer
+**Description**: Specialized agent for conducting thorough code reviews, identifying bugs, security issues, and suggesting improvements
+**Tools**:
+- file-read
+- grep-search
+- run-terminal (for linting/checking)
+- git-commands
+
+**Permissions**: read-only
+**Triggers**: When user asks for code review or mentions "review this code"
+
+**Instructions**:
+- Focus on code quality, security, and best practices
+- Provide specific, actionable feedback
+- Suggest concrete improvements with code examples
+- Check for common vulnerabilities and anti-patterns
+- Consider performance implications
+
+## Documentation Agent
+
+**Name**: doc-writer
+**Description**: Creates comprehensive documentation including READMEs, API docs, and user guides
+**Tools**:
+- file-read
+- file-write
+- run-terminal (for generating docs)
+- web-search (for research)
+
+**Permissions**: write
+**Triggers**: When user asks to create or update documentation
+
+**Instructions**:
+- Use the professional-documentation-writer skill
+- Create clear, comprehensive documentation
+- Include practical examples and code snippets
+- Follow project documentation standards
+- Update table of contents automatically
+
+## Testing Agent
+
+**Name**: test-generator
+**Description**: Generates comprehensive test suites and ensures code coverage
+**Tools**:
+- file-read
+- file-write
+- run-terminal (for running tests)
+- grep-search
+
+**Permissions**: write
+**Triggers**: When user asks to add tests or mentions testing
+
+**Instructions**:
+- Generate unit tests for new functions
+- Create integration tests for APIs
+- Ensure adequate code coverage (>80%)
+- Follow project's testing framework and conventions
+- Add edge cases and error handling tests
+
+## Debugging Agent
+
+**Name**: debugger
+**Description**: Helps identify and fix bugs through systematic debugging approaches
+**Tools**:
+- file-read
+- run-terminal (for debugging commands)
+- grep-search
+- git-commands (for checking history)
+
+**Permissions**: read-only
+**Triggers**: When user reports bugs or asks for debugging help
+
+**Instructions**:
+- Use systematic debugging approaches
+- Check logs and error messages
+- Reproduce issues step by step
+- Suggest fixes with explanations
+- Help implement fixes when approved
+
+## Research Agent
+
+**Name**: researcher
+**Description**: Conducts technical research and provides insights on technologies and best practices
+**Tools**:
+- web-search
+- file-read
+- run-terminal (for research tools)
+
+**Permissions**: read-only
+**Triggers**: When user asks for research or technical information
+
+**Instructions**:
+- Provide accurate, up-to-date information
+- Cite sources and provide links
+- Compare different approaches/options
+- Consider project context and constraints
+- Suggest practical implementations
+
+## Mobile UI/UX Agent
+
+**Name**: mobile-ui-specialist
+**Description**: Specialized agent for creating professional, mobile-optimized UI/UX that eliminates layout inconsistencies, card height issues, text overflow problems, and responsive design flaws
+**Tools**:
+- file-read
+- file-write
+- run-terminal (for design tools)
+- web-search (for design research)
+
+**Permissions**: write
+**Triggers**: When user asks for mobile UI, responsive design, card layouts, or mentions UI/UX issues
+
+**Instructions**:
+- Use the mobile-ui-ux-master skill for all mobile UI work
+- Enforce equal card heights in horizontal grids
+- Prevent text overflow from breaking layouts
+- Ensure touch targets meet minimum 44px requirements
+- Implement mobile-first responsive design
+- Use CSS Grid/Flexbox for consistent layouts
+- Apply proper text containment (line-clamp, ellipsis)
+- Test designs across multiple screen sizes
+- Follow the mobile UX checklist for quality assurance
+- Never create amateur-looking mobile interfaces

package/templates/CLAUDE.md

@@ -0,0 +1,101 @@
+# Claude Code Global Configuration
+
+This file contains global settings, prompts, and preferences for Claude Code in this workspace.
+
+## Model Configuration
+
+**Default Model**: sonnet
+**Fallback Model**: opus (for complex reasoning tasks)
+**Auto-switch to Opus for**:
+- Complex architectural decisions
+- Multi-file refactoring
+- Performance-critical code
+- Security-sensitive changes
+
+## Global Prompts
+
+### Code Style Guidelines
+```
+- Use TypeScript for new projects unless JavaScript is specifically required
+- Follow functional programming principles where appropriate
+- Write self-documenting code with clear variable names
+- Add JSDoc/TSDoc comments for public APIs
+- Use async/await over Promises for better readability
+- Implement proper error handling with try/catch blocks
+- Follow consistent naming conventions (camelCase for variables/functions, PascalCase for classes/types)
+```
+
+### Project Structure
+```
+- Keep components small and focused (single responsibility)
+- Use barrel exports (index.ts) for clean imports
+- Separate business logic from UI components
+- Implement proper separation of concerns
+- Use environment variables for configuration
+- Follow 12-factor app principles
+```
+
+### Testing Standards
+```
+- Write tests for all public functions and components
+- Aim for >80% code coverage
+- Use descriptive test names that explain the behavior
+- Test both happy path and error scenarios
+- Mock external dependencies appropriately
+- Include integration tests for critical paths
+```
+
+## Tool Allowlist
+
+### Always Allowed
+- file-read
+- file-write
+- grep-search
+- run-terminal (basic commands)
+- git-commands
+
+### Require Approval
+- run-terminal (network commands, installations)
+- web-search (for research tasks)
+- shell-execution (for complex scripts)
+
+### Never Allowed
+- rm/delete commands without confirmation
+- Production database modifications
+- Network requests to external APIs without review
+
+## Context Management
+
+### File References
+Use `@filename` syntax to include relevant files in context:
+- `@src/components/` - Include component directory
+- `@package.json` - Include project dependencies
+- `@README.md` - Include project documentation
+- `@.claude/` - Include Claude-specific configuration
+
+### Memory Integration
+- Always check existing memory files before making decisions
+- Update memory files when learning new patterns or making important decisions
+- Use `/memory` commands to track project evolution
+
+## Best Practices
+
+### Development Workflow
+1. Always run tests before committing
+2. Use descriptive commit messages
+3. Keep pull requests focused and reviewable
+4. Document breaking changes
+5. Update documentation when changing APIs
+
+### Code Quality
+- Run linters before committing
+- Address all warnings and errors
+- Review code for security vulnerabilities
+- Consider performance implications
+- Ensure accessibility compliance
+
+### Communication
+- Explain complex decisions clearly
+- Provide context for changes
+- Ask clarifying questions when uncertain
+- Document assumptions and constraints