Skip to content
Back to skills

Implementation

ASecurity

Implement software features, fix bugs, and write production-quality code. Use this for hands-on development work including writing new code, modifying existing code, and debugging issues.

  • 35 stars
  • 0 votes
  • 0 copies
  • 2 views
  • Added May 26, 2026
developmentgodebugging

Works with

  • terminal

Security analysis

A100/100

Scanned May 27, 2026

npx -y skills add KarmaloopAI/Jiva --skill implementation --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Implementation?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Implementation
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/karmaloopai-implementation/badge)](https://www.skillsdirectory.com/skills/karmaloopai-implementation)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: feature-implementation
description: >
  Implement software features, fix bugs, and write production-quality code. Use this for hands-on development work including writing new code, modifying existing code, and debugging issues.
---

# Feature Implementation Skill

## Overview
Write high-quality, production-ready code for features and bug fixes.

## Workflow

1. **Understand Requirements**: Parse task requirements thoroughly
2. **Plan Implementation**: Identify files to create/modify
3. **Write Code**: Implement with best practices:
   - Clean, readable code
   - Proper error handling
   - Type safety
   - Good variable/function names
4. **Verify**: Test basic functionality
5. **Document**: Add comments for complex logic

## Code Quality Standards

- Follow language idioms and conventions
- Handle edge cases and errors
- Use appropriate data structures
- Keep functions focused and small
- Add inline comments for complex logic

## Tools to Use

- `create_file`: For new files
- `edit_file`: For modifications
- `view`: To read existing code
- `grep_search`: To find code patterns
- `run_terminal_command`: To run tests

## Best Practices

- Read existing code before making changes
- Match the project's style and patterns
- Test changes when possible
- Leave code better than you found it

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…