Skip to content
Agentmart
Submit a tool

implementation-quality

Support implementation with clean code, SOLID design, consistent style, defensive coding, and evidence-based changes.

Skill by hoskengadu

IndexedMIT
Write a review

Install

Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.

npx agentmarket install skill/hoskengadu-implementation-quality

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

We use your email only for this newsletter. Privacy

About

Support implementation with clean code, SOLID design, consistent style, defensive coding, and evidence-based changes.

Use cases: design

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this skill can do and what it asks for, from its SKILL.md. Checked Oct 25, 2026.

Tools
No tools found
Secrets
None asked for
Install scripts
None found

Network hosts it talks to 1

  • codeload.github.com · found in install command

Files it touches

  • ~/.claude/skills/implementation-quality

What's inside

Skill name
implementation-quality
Description
Support implementation with clean code, SOLID design, consistent style, defensive coding, and evidence-based changes.
License
MIT
Metadata
short-description: High-quality implementation guidance
Instructions
32 lines in SKILL.md · view on GitHub

Files (1)

  • SKILL.md

SKILL.md (first lines)

# Implementation Quality

Use this skill for coding tasks where the main risk is poor implementation quality, hidden regressions, or unnecessary complexity.

## Implementation Rules

- Inspect the existing code and surrounding patterns before editing.
- Preserve public behavior unless the user explicitly requests a change.
- Choose the simplest design that satisfies the requirement.
- Keep functions, classes, and modules focused.
- Prefer explicit names over clever abstractions.
- Avoid speculative generalization.
- Add comments only when they clarify non-obvious intent or constraints.

## Validation Mindset

- Add or update tests for behavior changes.
- Check edge cases, nullability, input validation, and error handling.
- Verify that the change fits the existing architecture and coding style.
- If a refactor is needed, separate it from behavior changes when possible.

## Stack Selection

If the user has not specified the target technology, ask whether the work should follow `.NET`, `Java`, or `Python` conventions before proceeding with stack-specific advice.

When the stack is known, use the matching specialized skill:

- `.NET` work: `implementation-quality-dotnet`
- `Java` work: `implementation-quality-java`
- `Python` work: `implementation-quality-python`

From hoskengadu/software-engineering-skills, MIT.

More from hoskengadu/software-engineering-skills

Signals

Stars
0
Forks
0
Open issues
0
Last commit (this folder)
Aug 20, 2026 (2 months ago)

From GitHub (fetched Oct 24, 2026).

Details

License
MIT
First seen
Oct 24, 2026
Last checked
Oct 24, 2026

More from hoskengadu

Cite this page

implementation-quality skill. Agent Mart. https://agentmart.dev/skills/hoskengadu-implementation-quality (last updated 2026-10-24)