skills.rest
Anders-planck
Anders-planckCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

coding-rules

Enforce TDD, comment standards, and safe changes during coding tasks.

Updated Apr 20, 2026
Search Tags:#testing#tdd#coding#code-quality#guidelines#code-review
One-click install
npx skills add https://github.com/Anders-planck/opencode-config --skill coding-rules-anders-planck
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: coding-rules
Source: https://github.com/Anders-planck/opencode-config/tree/main/skills/coding-rules
Command: npx skills add https://github.com/Anders-planck/opencode-config --skill coding-rules-anders-planck

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Inconsistent code quality and undefined coding practices across teams lead to bugs, maintenance burdens, and slow delivery.

Core Features & Use Cases

  • Code Quality: Establishes consistent quality standards, guardrails, and non-regressive rules to prevent regressive changes.
  • Problem-Solving: Provides a structured approach to debugging and refactoring with explicit guidelines.
  • Mock Data Policy: Enforces real data usage and discourages mock modes to ensure realism and safety.
  • Testing & Use: Stresses writing tests first, maintaining testable code, and ensuring tests pass before merges.
  • Template & Error Handling: Promotes evergreen templates and robust error handling strategies.
  • Code Search — ast-grep: Mandates AST-based code search and structural checks to reduce brittle changes.
  • Library Documentation — Context7: Recommends up-to-date docs usage before integrations.

Quick Start

Follow these coding guidelines when writing or updating code to ensure consistency, testability, and maintainable software.

Frequently Asked Questions about coding-rules

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

FAQPage Schema
How do I enforce consistent code quality and TDD practices across my software projects?▼

Enforce consistent code quality by applying structured coding guidelines during development, code reviews, and refactoring. This ensures test-driven development, standard comments, and safe, non-regressive changes across the entire project workflow.

What is the best way to prevent regressive changes during code refactoring?▼

Prevent regressive changes during refactoring by mandating AST-based code search for structural checks and enforcing strict non-regressive guardrails. This structured approach reduces brittle modifications and maintains safe code transitions.

Should I use mock data for testing, or does real data provide better safety?▼

Real data provides better safety than mock data. A strict mock data policy enforces real data usage and discourages mock modes to ensure realism, robust error handling, and reliable test outcomes before merges.

Can I integrate new libraries without checking up-to-date documentation?▼

Integrating new libraries requires checking up-to-date documentation first. Following recommended documentation practices before integration ensures compatibility and prevents deprecated or unsafe code dependencies.

How do I establish coding standards for reliable software?▼

Establish coding standards for reliable software by specifying mandatory metadata structures, guardrails, and error handling strategies. This enforces testable code, evergreen templates, and passing tests before merges.

Related Skills

Explore More Software Engineering Skills→
mcj-codermcj-coder
1

greenfield-baseline

Automate project scaffolding with quality gates, CI/CD, and repository structure.

Community
Advanced
mishahaninmishahanin
10

ast-grep

Translate natural language queries into structural AST patterns for code search.

Community
Advanced
thktthkt
11

test

Execute project tests and analyze code coverage with package managers and linters.

Community
Intermediate
tkgallytkgally
8

example-sentences

Codify rules for creating and revising dictionary example sentences.

Community
Intermediate