code-craft

Enforce fixed coding thresholds and governance checks for production code.

Updated Jan 24, 2026
One-click install
npx skills add https://github.com/pikakit/agent-skills --skill code-craft
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-craft
Source: https://github.com/pikakit/agent-skills/tree/main/.agent/skills/code-craft
Command: npx skills add https://github.com/pikakit/agent-skills --skill code-craft

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Pragmatic coding standards provide a concise, predictable baseline for producing high-quality software, reducing over-engineering and inconsistency across teams.

Core Features & Use Cases

  • Enforces SRP, DRY, KISS, YAGNI, and Boy Scout principles to keep code readable and maintainable.
  • Defines fixed thresholds such as 20 lines per function, 3 arguments, and 2 levels of nesting, plus naming guidelines.
  • Serves as a governance reference for code reviews, refactoring planning, and architecture discussions.

Quick Start

Run Code Craft guidelines on your current task to assess naming, structure, and dependency considerations.

Frequently Asked Questions about code-craft

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I enforce coding standards for function length and arguments during code review?

To enforce coding standards during code review, apply fixed thresholds such as a maximum of 20 lines per function, 3 arguments, and 2 levels of nesting. These predictable baselines reduce inconsistency and over-engineering across teams.

What is the best way to plan legacy modernization and refactoring tasks?

The best way to plan legacy modernization is by applying pragmatic principles like SRP, DRY, KISS, YAGNI, and Boy Scout rules. This governance baseline tracks dependencies and structures predictable refactoring steps.

How do I apply naming conventions and architecture constraints across development teams?

You can apply naming conventions and architecture constraints by using a shared governance reference for code reviews and architecture discussions. This ensures consistent, readable, and maintainable code production across teams.

Why does code review fail to prevent over-engineering and inconsistent code quality?

Code review fails to prevent over-engineering when lacking concise, predictable baselines. Enforcing explicit thresholds like 3 arguments per function and KISS principles reduces inconsistency and ensures reliable code quality.

Can I use fixed coding thresholds for complex architecture decisions?

You can use fixed coding thresholds for architecture decisions by tracking dependencies and applying SRP and YAGNI principles. These rules serve as a governance reference to keep complex systems maintainable.

When should I not use strict line limits and nesting thresholds for code quality?

Strict line limits and nesting thresholds may not suit contexts requiring deep architectural flexibility. If code reviews demand highly specialized patterns, these fixed thresholds might over-constrain complex domain logic.