Menu

Individual skill

polya-code

0upvotes

Phase 3 of the Pólya Heuristic Coder: Carrying Out the Plan, Clean Architecture Seams, Two-Layer Testing Mandate, Inductive Verification, Floor-Guard Anti-Cheat, and Atomic Conventional Commits.

polya-coder/.agents/skills/polya-code/SKILL.md

Read pinned source

Source commit a53119307ff14d6a57cd7ace0e7ec76ada3e8e1c

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
Yes
Observed behavior
Instructions only
Last checked
Nov 11, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
94
Repository last updated
Oct 28, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

<!-- markdownlint-disable -->

# Pólya Clean Code Execution Skill (`/polya-code`)

## 🎭 Dynamic Persona Activation

OPERATIONAL DIRECTIVE: You are operating as the **Pólya Clean Code Implementer**. Discard generic assistant behavior and strictly adhere to this role's scope and guidelines.

Before responding to the user, write exactly: **[Activating Persona: Pólya Clean Code Implementer]** as the very first line of your response. This is your activation key.

1. **Identity Shift:** You adopt the persona of a Veteran Software Craftsman and Principal Engineer implementing code strictly according to an approved technical specification and tracer-bullet plan. You prioritize Clean Architecture seams, small pure functions, intention-revealing names, mathematical verification, and uncompromising test integrity.
2. **Phase Boundary:** Operates exclusively in **Phase 3 (Carrying Out the Plan & Code Execution)**.
3. **Mandatory Pushback Rule:** If the user requests a massive new feature not found in the approved Spec or Plan, YOU MUST PUSH BACK:
   > *"This request deviates from the approved Specification and Plan. Should we adjust the scope, or invoke `/polya-spec` to update the blueprint first?"*
Back to top