skills.rest
DeevsDeevs
DeevsDeevsCOMMUNITY
Explore all skills by this author →
GitHub

97-dev

Apply programming principles from 97 Things Every Programmer Should Know to coding and reviews.

40|6|Updated Nov 23, 2025
Search Tags:#refactoring#code-quality#workflow-optimization#design-decision#professional-development#programming-wisdom
One-click install
npx skills add https://github.com/DeevsDeevs/agent-system --skill 97-dev
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: 97-dev
Source: https://github.com/DeevsDeevs/agent-system/tree/main/97-dev
Command: npx skills add https://github.com/DeevsDeevs/agent-system --skill 97-dev

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Distilled guidance from 97 Things Every Programmer Should Know to improve design decisions, code quality, testing discipline, and professional growth across projects.

Core Features & Use Cases

  • Apply timeless principles (DRY, SRP, Boy Scout Rule, code is design) to daily coding, reviews, and refactoring.
  • Use the referenced material to guide architecture, testing strategies, and maintenance decisions.
  • Integrate these guidelines into workflows and mentorship to elevate engineering practices.

Quick Start

Identify a relevant principle from 97 Things and apply it to the current task with a brief justification.

Frequently Asked Questions about 97-dev

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

FAQPage Schema
What programming wisdom helps improve code quality and design decisions?▼

Programming wisdom from 97 Things Every Programmer Should Know improves code quality by applying principles like DRY, SRP, and the Boy Scout Rule to daily coding, reviews, and refactoring tasks.

How do I apply the Boy Scout Rule during code refactoring?▼

Apply the Boy Scout Rule during refactoring by selecting the principle from 97 Things, leaving the code cleaner than you found it, and justifying the design decision briefly within your current workflow.

When should I use DRY and SRP principles in software engineering workflows?▼

Use DRY and SRP principles in software engineering workflows when writing code, planning architecture, and performing reviews to simplify maintenance and communicate technical trade-offs effectively.

Does this guidance apply to maintenance-first testing strategies?▼

Yes, this guidance applies to maintenance-first testing strategies by leveraging timeless programming principles to guide architecture, testing discipline, and long-term maintenance decisions across real-world projects.

What are the limitations of using timeless programming wisdom for workflow optimization?▼

The limitation of timeless programming wisdom for workflow optimization is that it provides high-level design guidance and trade-off communication rather than automated code fixes or direct architectural enforcement.

Related Skills

Explore More Software Engineering Skills→
bailynlovebailynlove
1

claude-code

Automate coding tasks using the Claude Code CLI agent.

Community
Advanced
VuNguyenVietTienVuNguyenVietTien

brainstorm

Generate and evaluate system architecture designs with trade-off analysis.

Community
Advanced
luongnv89luongnv89
104

devops-pipeline

Automate pre-commit hooks and GitHub Actions for code quality.

Community
Advanced
mafvietnammafvietnam

ck:mobile-development

Guide iOS and Android mobile development with framework selection and architecture patterns.

Community
Advanced