build-core

Codifies software craftsmanship principles to guide code reviews and refactoring with actionable steps.

7|3|Updated Dec 1, 2025
One-click install
npx skills add https://github.com/yzavyas/claude-1337 --skill build-core
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: build-core
Source: https://github.com/yzavyas/claude-1337/tree/main/plugins/core-1337/skills/build-core
Command: npx skills add https://github.com/yzavyas/claude-1337 --skill build-core

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill codifies software craftsmanship principles to help builders improve code quality, facilitate disciplined refactoring, and elevate collaboration around a codebase.

Core Features & Use Cases

  • Craft-focused guidance for code reviews, design decisions, and incremental improvements.
  • Concrete next steps that guide engineers to actionable changes.
  • Use Case: When reviewing or refactoring, the skill provides a framework to ensure long-term maintainability.

Quick Start

Propose to review a sample function and output a minimal, testable refactor plan.

Frequently Asked Questions about build-core

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

FAQPage Schema
How do I enforce software craftsmanship principles during a code review?

To enforce craftsmanship during a code review, apply actionable guidance that codifies incremental changes, testability, and clear next steps to ensure long-term maintainability without external tools.

What is the best way to plan a testable refactoring task for an existing codebase?

The best way to plan a testable refactoring task is to generate a minimal, incremental refactor plan that ensures testability and provides concrete next steps for architectural improvements.

Can I improve code quality and maintainability without using external linting tools?

Yes, you can improve code quality without external tools by applying codified craftsmanship principles that enforce disciplined, incremental changes and testability during architectural decisions.

How do I guide engineers to make incremental architectural decisions for better code quality?

You guide engineers by providing craft-focused guidance that outputs concrete next steps, ensuring architectural decisions prioritize incremental changes and long-term code maintainability.

Does this approach to code refactoring work for standard software projects without dependencies?

Yes, this refactoring approach works for standard software projects without dependencies by codifying craftsmanship principles into actionable guidance for code reviews and design decisions.