NTQ AI Prompts

# Code Review Skill

This skill performs comprehensive code reviews with actionable feedback.

## Instructions

When reviewing code:

1. **Check correctness** - Verify logic and functionality
2. **Review code style** - Ensure consistency with project standards
3. **Identify security issues** - Look for vulnerabilities
4. **Assess performance** - Find potential bottlenecks
5. **Evaluate maintainability** - Consider future maintenance

## Review Checklist

### Functionality
- [ ] Code works as intended
- [ ] Edge cases are handled
- [ ] Error handling is appropriate

### Code Quality
- [ ] Code is readable and well-organized
- [ ] Functions are focused and not too long
- [ ] No code duplication
- [ ] Variable names are descriptive

### Security
- [ ] Input validation is present
- [ ] No hardcoded secrets
- [ ] SQL injection prevention
- [ ] XSS prevention

## Feedback Format

Provide specific, actionable feedback with:
- Line references
- Suggested improvements
- Code examples when helpful

# Git Commit Message Skill

This skill writes clear, conventional commit messages following best practices.

## Instructions

When writing commit messages:

1. **Use conventional commit format** - type(scope): description
2. **Be concise but descriptive** - Summarize changes clearly
3. **Use imperative mood** - "Add feature" not "Added feature"
4. **Reference issues** - Link to relevant tickets or issues
5. **Separate concerns** - One logical change per commit

## Commit Types

- **feat**: New feature
- **fix**: Bug fix
- **docs**: Documentation changes
- **style**: Code style changes (formatting, etc.)
- **refactor**: Code refactoring
- **test**: Adding or updating tests
- **chore**: Maintenance tasks

## Format

```
type(scope): short description

Longer description if needed. Explain what and why,
not how.

Refs: #issue-number
```

# Documentation Writer Skill

This skill creates clear, comprehensive documentation for code and APIs.

## Instructions

When writing documentation:

1. **Understand the code** - Analyze functionality and purpose
2. **Write clear descriptions** - Explain what the code does in plain language
3. **Document parameters** - List all inputs with types and descriptions
4. **Include examples** - Provide usage examples for common scenarios
5. **Note edge cases** - Document any limitations or special behaviors

## Documentation Types

### Function/Method Documentation
- Purpose and description
- Parameters with types
- Return values
- Exceptions thrown
- Usage examples

### API Documentation
- Endpoint descriptions
- Request/response formats
- Authentication requirements
- Rate limits and errors

### README Documentation
- Project overview
- Installation instructions
- Quick start guide
- Configuration options

# Test Generator Skill

This skill generates comprehensive unit tests for code.

## Instructions

When generating tests:

1. **Identify testable units** - Find functions, methods, and classes to test
2. **Cover edge cases** - Include tests for boundary conditions and error states
3. **Use appropriate assertions** - Match assertions to expected outcomes
4. **Mock dependencies** - Isolate units from external dependencies
5. **Follow naming conventions** - Use descriptive test names

## Test Categories

- **Happy path tests** - Normal expected behavior
- **Edge case tests** - Boundary conditions
- **Error handling tests** - Exception and error scenarios
- **Integration tests** - Component interactions

## Framework Guidelines

- Use the project's existing test framework
- Follow AAA pattern (Arrange, Act, Assert)
- Keep tests independent and isolated
- Aim for high code coverage

# Code Refactoring Skill

This skill helps refactor code to improve readability, maintainability, and performance.

## Instructions

When asked to refactor code:

1. **Analyze the code structure** - Identify code smells, duplications, and areas for improvement
2. **Apply refactoring patterns** - Use appropriate design patterns and best practices
3. **Preserve functionality** - Ensure all existing behavior is maintained
4. **Add documentation** - Include clear comments explaining complex logic
5. **Optimize performance** - Look for opportunities to improve efficiency

## Guidelines

- Follow the language's style guide and conventions
- Break large functions into smaller, focused ones
- Use meaningful variable and function names
- Remove dead code and unused imports
- Add type annotations where applicable

## Output Format

Provide the refactored code with explanations of changes made.

# Code Review Skill

This skill performs comprehensive code reviews with actionable feedback.

## Instructions

When reviewing code:

1. **Check correctness** - Verify logic and functionality
2. **Review code style** - Ensure consistency with project standards
3. **Identify security issues** - Look for vulnerabilities
4. **Assess performance** - Find potential bottlenecks
5. **Evaluate maintainability** - Consider future maintenance

## Review Checklist

### Functionality
- [ ] Code works as intended
- [ ] Edge cases are handled
- [ ] Error handling is appropriate

### Code Quality
- [ ] Code is readable and well-organized
- [ ] Functions are focused and not too long
- [ ] No code duplication
- [ ] Variable names are descriptive

### Security
- [ ] Input validation is present
- [ ] No hardcoded secrets
- [ ] SQL injection prevention
- [ ] XSS prevention

## Feedback Format

Provide specific, actionable feedback with:
- Line references
- Suggested improvements
- Code examples when helpful

# Git Commit Message Skill

This skill writes clear, conventional commit messages following best practices.

## Instructions

When writing commit messages:

1. **Use conventional commit format** - type(scope): description
2. **Be concise but descriptive** - Summarize changes clearly
3. **Use imperative mood** - "Add feature" not "Added feature"
4. **Reference issues** - Link to relevant tickets or issues
5. **Separate concerns** - One logical change per commit

## Commit Types

- **feat**: New feature
- **fix**: Bug fix
- **docs**: Documentation changes
- **style**: Code style changes (formatting, etc.)
- **refactor**: Code refactoring
- **test**: Adding or updating tests
- **chore**: Maintenance tasks

## Format

```
type(scope): short description

Longer description if needed. Explain what and why,
not how.

Refs: #issue-number
```

# Documentation Writer Skill

This skill creates clear, comprehensive documentation for code and APIs.

## Instructions

When writing documentation:

1. **Understand the code** - Analyze functionality and purpose
2. **Write clear descriptions** - Explain what the code does in plain language
3. **Document parameters** - List all inputs with types and descriptions
4. **Include examples** - Provide usage examples for common scenarios
5. **Note edge cases** - Document any limitations or special behaviors

## Documentation Types

### Function/Method Documentation
- Purpose and description
- Parameters with types
- Return values
- Exceptions thrown
- Usage examples

### API Documentation
- Endpoint descriptions
- Request/response formats
- Authentication requirements
- Rate limits and errors

### README Documentation
- Project overview
- Installation instructions
- Quick start guide
- Configuration options

# Test Generator Skill

This skill generates comprehensive unit tests for code.

## Instructions

When generating tests:

1. **Identify testable units** - Find functions, methods, and classes to test
2. **Cover edge cases** - Include tests for boundary conditions and error states
3. **Use appropriate assertions** - Match assertions to expected outcomes
4. **Mock dependencies** - Isolate units from external dependencies
5. **Follow naming conventions** - Use descriptive test names

## Test Categories

- **Happy path tests** - Normal expected behavior
- **Edge case tests** - Boundary conditions
- **Error handling tests** - Exception and error scenarios
- **Integration tests** - Component interactions

## Framework Guidelines

- Use the project's existing test framework
- Follow AAA pattern (Arrange, Act, Assert)
- Keep tests independent and isolated
- Aim for high code coverage

# Code Refactoring Skill

This skill helps refactor code to improve readability, maintainability, and performance.

## Instructions

When asked to refactor code:

1. **Analyze the code structure** - Identify code smells, duplications, and areas for improvement
2. **Apply refactoring patterns** - Use appropriate design patterns and best practices
3. **Preserve functionality** - Ensure all existing behavior is maintained
4. **Add documentation** - Include clear comments explaining complex logic
5. **Optimize performance** - Look for opportunities to improve efficiency

## Guidelines

- Follow the language's style guide and conventions
- Break large functions into smaller, focused ones
- Use meaningful variable and function names
- Remove dead code and unused imports
- Add type annotations where applicable

## Output Format

Provide the refactored code with explanations of changes made.

Write API documentation for {{endpoint}}:

Method: {{method}}
Parameters: {{params}}
Response: {{response}}

Include examples and error codes.

Write a professional email response to: {{original_email}}

Tone: {{tone}}
Desired outcome: {{outcome}}

Write a job description for {{position}} at {{company}}. Include responsibilities, requirements, benefits, and company culture.

# Git Commit Message Skill

This skill writes clear, conventional commit messages following best practices.

## Instructions

When writing commit messages:

1. **Use conventional commit format** - type(scope): description
2. **Be concise but descriptive** - Summarize changes clearly
3. **Use imperative mood** - "Add feature" not "Added feature"
4. **Reference issues** - Link to relevant tickets or issues
5. **Separate concerns** - One logical change per commit

## Commit Types

- **feat**: New feature
- **fix**: Bug fix
- **docs**: Documentation changes
- **style**: Code style changes (formatting, etc.)
- **refactor**: Code refactoring
- **test**: Adding or updating tests
- **chore**: Maintenance tasks

## Format

```
type(scope): short description

Longer description if needed. Explain what and why,
not how.

Refs: #issue-number
```

# Code Refactoring Skill

This skill helps refactor code to improve readability, maintainability, and performance.

## Instructions

When asked to refactor code:

1. **Analyze the code structure** - Identify code smells, duplications, and areas for improvement
2. **Apply refactoring patterns** - Use appropriate design patterns and best practices
3. **Preserve functionality** - Ensure all existing behavior is maintained
4. **Add documentation** - Include clear comments explaining complex logic
5. **Optimize performance** - Look for opportunities to improve efficiency

## Guidelines

- Follow the language's style guide and conventions
- Break large functions into smaller, focused ones
- Use meaningful variable and function names
- Remove dead code and unused imports
- Add type annotations where applicable

## Output Format

Provide the refactored code with explanations of changes made.

Write product copy for {{product_name}}:

Features: {{features}}
Target: {{target}}

Include headline, benefits, and CTA.

# Test Generator Skill

This skill generates comprehensive unit tests for code.

## Instructions

When generating tests:

1. **Identify testable units** - Find functions, methods, and classes to test
2. **Cover edge cases** - Include tests for boundary conditions and error states
3. **Use appropriate assertions** - Match assertions to expected outcomes
4. **Mock dependencies** - Isolate units from external dependencies
5. **Follow naming conventions** - Use descriptive test names

## Test Categories

- **Happy path tests** - Normal expected behavior
- **Edge case tests** - Boundary conditions
- **Error handling tests** - Exception and error scenarios
- **Integration tests** - Component interactions

## Framework Guidelines

- Use the project's existing test framework
- Follow AAA pattern (Arrange, Act, Assert)
- Keep tests independent and isolated
- Aim for high code coverage

Write a blog post about {{topic}} for {{audience}}. Include engaging intro, 3-5 sections, practical tips, and CTA. Word count: {{word_count}}