Skip to content
Skills Library
Programming · Building & coding

implementation-craft

/implementation-craft

Write and change production code that fits the existing codebase. Use when implementing features, fixing bugs, or refactoring in frontend, backend, API, or database code. Covers validation, error handling, data access, naming, and the rules that keep generated code from becoming bloated or generic.

Licence
MIT
Last repository change
28.10.2026

Assessment and security

90/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content25 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 28.10.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Write and change production code that fits the existing codebase. Use when implementing features, fixing bugs, or refactoring in frontend, backend, API, or database code. Covers validation, error handling, data access, naming, and the rules that keep generated code from becoming bloated or generic.

Original author description

Write and change production code that fits the existing codebase. Use when implementing features, fixing bugs, or refactoring in frontend, backend, API, or database code. Covers validation, error handling, data access, naming, and the rules that keep generated code from becoming bloated or generic.

How it works

  1. Defaults
  2. Do not
  3. Data and APIs
  4. Before handing off
Original SKILL.md headings · 33 lines, 294 words
SKILL.md preview
---
name: implementation-craft
description: Write and change production code that fits the existing codebase. Use when implementing features, fixing bugs, or refactoring in frontend, backend, API, or database code. Covers validation, error handling, data access, naming, and the rules that keep generated code from becoming bloated or generic.
---

# Implementation Craft

## Defaults

- Match the repository's existing style, module system, and libraries.
- Make the smallest change that satisfies the acceptance criteria.
- Validate input at the trust boundary (route handler, form submit, message consumer). Return a specific status and message.
- Handle the failure path of every I/O call. The UI must show it; the server must log it without leaking internals.
- Keep side effects in named functions. No hidden writes in getters or render paths.
- Move focus in the same update that shows the target element (React: `useLayoutEffect` or `autoFocus`, not `useEffect`). Deferred focus drops the first keystrokes, and the wrong text gets saved.
- Name things after the domain, not the pattern (`renameItem`, not `handleUpdateHelper`).

## Do not

- Add a file, hook, utility, interface, or layer that has one caller and no complexity to hide.
- Add a dependency for something the platform or an existing dependency already does.
- Rewrite working code that the task does not touch.
- Silence type errors, lint rules, or failing tests to get green.
- Ship mock data, `TODO` handlers, or success messages that fire before the server confirms.
- Add speculative options, flags, or config "for later".

## Data and APIs

- Keep server and client limits identical. Put the number in one place per side and test both.
- Return 404 for missing resources, 400 for invalid input, and do not echo raw input back in error HTML.
- Use parameterized queries. Never build SQL with string concatenation.
- Schema changes need a migration path for existing data.

## Before handing off

Run the formatter or linter the project already uses. Read your own diff line by line. Delete anything you cannot justify in one sentence.

Versions

The database has no other skills named implementation-craft.

Database snapshot: 13.11.2026 · package version f858ed9ce688 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 90backend-craft
    Backend engineering standards — API design, layering, database patterns, caching, error handling, auth, background jobs, logging, and the production-readiness checklist. Use when building any server-side code (endpoints, services, models, migrations, jobs).
  • 95pact-coding-standards
    Clean code principles, error handling patterns, and coding standards for PACT Code phase. Use when: implementing features, refactoring code, reviewing code quality, establishing coding conventions, or handling errors and exceptions. Triggers on: code quality, clean code,…
  • 90express-craft
    Express.js (Node) engineering standards — layering, async error handling (Express 4 vs 5), boundary validation, security middleware, graceful shutdown, and testing. Loaded on top of backend-craft when the ticket's stack is Express. Use when building Express APIs.
  • 100tdd
    Enforces test-driven development: write failing test, write minimal code to pass, refactor. Mandatory for all implementation work. Use when writing any production code, implementing features, fixing bugs, refactoring, or when the user says "write code", "implement", "fix this",…
  • 100local-awesome-code-standards-c28c96db
    Universal coding standards — naming, structure, immutability, error handling, type safety, backend layering, frontend architecture — that fill the gaps after the project's own conventions. Use when starting a module, refactoring to team conventions, setting up lint rules,…
  • 90typescript-rules
    React/TypeScript frontend development rules including type safety, component design, state management, and error handling. Use when implementing React components, TypeScript code, or frontend features.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.