claude-code-plugin-ref…
Explain plugin, skill, command, agent, and hook mechanics used here. Use when authoring or debugging plugins. Do not use for ops; use night-market-operations.
Polishes working code through successive quality passes in fresh subagents. Use after tests pass when code needs multi-dimension refinement before release.
$ npx -y skills add athola/claude-night-market --skill dorodango --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/dorodangoContext preview
The summary Claude sees to decide when to auto-load this skill.
Polishes working code through successive quality passes in fresh subagents. Use after tests pass when code needs multi-dimension refinement before release.
name: dorodango
description: Polishes working code through successive quality passes in fresh subagents. Use after tests pass when code needs multi-dimension refinement before release.
alwaysApply: false
category: workflow
tags:
- polishing
- iterative-refinement
- code-quality
- convergence
progressive_loading: true
dependencies:
hub: []
modules:
- modules/pass-definitions.md
complexity: intermediate
model_hint: standard
estimated_tokens: 400Named after the Japanese art of polishing a ball of dirt into a high-gloss sphere. Applied to code: take the initial implementation (the "mud ball") and refine it through successive quality passes until it shines.
pass
quality dimensions
skill directly: pensive:code-refinement, etc.)
Four quality dimensions, each a self-contained pass:
1. **Correctness** - run tests, fix failures 2. **Clarity** - code readability and structure 3. **Consistency** - naming, patterns, style alignment 4. **Polish** - documentation, error messages, edges
See `modules/pass-definitions.md` for detailed scope of each pass type.
dimension as **converged**
dimension is not re-run
human with recommendation to split into smaller units
State tracked in `.attune/dorodango-state.json`:
{
"target": "plugins/foo",
"started_at": "2026-03-18T12:00:00Z",
"pass_count": 3,
"passes": [
{
"type": "correctness",
"issues_found": 2,
"issues_fixed": 2
},
{
"type": "clarity",
"issues_found": 5,
"issues_fixed": 5
},
{
"type": "consistency",
"issues_found": 0
}
],
"converged_dimensions": ["consistency"],
"converged": false
}This file enables resume across sessions. On resume, skip converged dimensions and continue from the next unconverged dimension.
Each pass dispatches a self-contained subagent to prevent context accumulation. The subagent receives:
Subagent dispatch is optional for targets under 100 lines of code; in-session review is sufficient for small files.
1. Initialize state file (or load existing) 2. Determine next unconverged dimension 3. Dispatch subagent for that dimension 4. Record results in state file 5. If dimension converged (0 issues), mark it 6. If all dimensions converged or 10 passes reached, stop 7. Otherwise, proceed to next dimension
with emotional framing for better results
(`correctness`, `clarity`, `consistency`, `polish`) listed under `converged_dimensions`.
convergence, the skill surfaces the unconverged dimensions to the user with a recommendation to split the target into smaller units.
correctness pass that finds failing tests never marks the dimension as converged.
the state file recording individual pass results rather than a single bulk entry.
A plugin marketplace for Claude Code. Install only the plugins you need to run git workflows, code review, spec-driven development, and autonomous agents from inside your Claude Code session.
Explain plugin, skill, command, agent, and hook mechanics used here. Use when authoring or debugging plugins. Do not use for ops; use night-market-operations.
States load-bearing decisions, invariants, and weak points. Use when judging a design change. Do not use for gating; use night-market-change-control.
Rebuild the dev environment: uv, Python tiers, pins, traps. Use when onboarding or toolchain breaks. Do not use for daily commands; use night-market-operations.
Classify, gate, and review changes. Use when landing a PR, releasing, or amending rules. Do not use for failure triage; use night-market-debugging-playbook.
Search and record project memory (Discussions, journal, ADRs). Use before re-investigating anything. Do not use for settled battles; see failure-archaeology.
Bind loop 'done' to unfakeable gates. Use to harden egregore/herald loops or promote completion_integrity. Not for QA gates; use night-market-validation-and-qa.