guidelines

Enforce strict behavioral rules for coding tasks to minimize output.

Updated Apr 30, 2026
One-click install
npx skills add https://github.com/wapgear/izmailov-skills --skill guidelines-wapgear
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: guidelines
Source: https://github.com/wapgear/izmailov-skills/tree/main/skills/guidelines
Command: npx skills add https://github.com/wapgear/izmailov-skills --skill guidelines-wapgear

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Strict behavioural rules enforce minimal output, zero speculation, and surgical precision in coding tasks, reducing ambiguity and increasing reproducibility.

Core Features & Use Cases

  • State assumptions before writing any code to anchor scope.
  • Ask exactly one targeted clarifying question when a request is ambiguous.
  • Match the existing code style and avoid introducing unused abstractions or changes.
  • Trace every changed line back to the original request to maintain auditability.
  • Verify each plan step against a concrete check before proceeding.
  • Apply the /izmailov:humanize transformation to any user-facing prose to improve readability.

Quick Start

State assumptions clearly, then apply the hard rules to every task and ask one targeted clarifying question if anything is ambiguous.

Frequently Asked Questions about guidelines

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

FAQPage Schema
How do I enforce strict coding standards and consistency during code reviews?

To enforce coding standards and consistency, this Skill applies strict behavioral rules that trace every changed line back to the original request, match existing code style, and eliminate speculation during code reviews. It anchors scope by requiring assumptions to be stated upfront.

What is the best way to minimize output and eliminate speculation in coding tasks?

The best way to minimize output and eliminate speculation in coding tasks is to apply strict behavioral rules enforcing surgical precision, requiring explicit assumption statements, and verifying each plan step against a concrete check before proceeding.

How do I match existing code style and avoid unnecessary changes when modifying code?

To match existing code style and avoid unnecessary changes, this Skill enforces rules that prevent introducing unused abstractions, trace modifications directly to the original request, and ask exactly one targeted clarifying question when a request is ambiguous.

When do I need to state assumptions before writing code?

You need to state assumptions before writing code whenever a task request contains ambiguity. This Skill enforces stating assumptions clearly to anchor scope, then asks exactly one targeted clarifying question to resolve remaining ambiguity before proceeding.

What are the limitations of applying strict rules for precise coding outputs?

The limitation of applying strict rules for precise coding outputs is that it enforces minimal output and zero speculation, meaning it will not introduce broader changes or unused abstractions beyond the original request scope, requiring exact specifications from the user.

Can I use this Skill for software documentation and task execution, or just coding?

Yes, you can use this Skill for software documentation and task execution. It enforces strict behavioral rules across all software development activities where precision is critical, applying transformations to user-facing prose to improve readability.