paddle

Use for rankingdepadel.club SDD planning interviews, "grill me" prompts, plan pressure-tests, unresolved product or architecture decisions, and pre-implementation planning that should end in a decision-complete proposed plan.

Use for rankingdepadel.club implementation handoffs, changelog and issue/spec reconciliation, commits, pushes, release consolidation, and ending a development cycle.

Use for rankingdepadel.club product/code work, active SDD specs, Codex planning, repository constraints, and deciding whether review or audit checkpoints apply.

Use for rankingdepadel.club governance edits, instruction version/date alignment, markdown rules, governance validation, changelog wording, and maintaining progressive disclosure between router docs and skills.

Audit Django views for project governance, security, reuse, and maintainability issues.

Review governance, skills, scripts, and repository files for context bloat, token-heavy workflows, and progressive-disclosure gaps. Use by default for conversations that are likely to be long or broad, and when the user asks to keep work under a context budget, reduce token consumption, or audit files for context efficiency.

Audit governance markdown and workflow skills for duplication, unclear ownership, coordination gaps, prose-only rules, and low-value SDD artifact overhead; export a reviewable governance audit report with prioritized findings and a consolidation-first rewrite plan.

Create persistent PRDs for complex rankingdepadel.club work that should later be split into approved implementation phases. Use when a requested feature, refactor, or process change is too large for one SDD spec, needs phased delivery, or should preserve product decisions before phase planning.

Break a phased PRD into vertical-slice SDD specs for rankingdepadel.club. Use when a PRD created with $phased-prd needs to become one or more implementation specs under specs/.

Audit a specific Django template's presentation for same-page UI coherence, CSS reuse, cascade conflicts, computed-style mismatches, and responsive layout risks. Use when the user asks to review or audit the presentation of one template, compare cards/controls/sections inside the same page, diagnose CSS cascade or inherited computed-style issues, or prevent visual inconsistencies before implementation.

Choose the correct rankingdepadel.club Codex workflow, source hierarchy, and next skill without loading every skill. Use when task routing, planning depth, source authority, ChatGPT handoff, pre-spec handling, audit choice, or workflow ownership is unclear.

Create or update rankingdepadel.club Codex skills with concise instructions, triggerable metadata, progressive disclosure, and repository validation. Use when the user asks to create, write, build, adapt, or revise a skill under .codex/skills.

Use for rankingdepadel.club test creation, TDD loops, test refactors, brittle assertion reviews, and choosing behavior-focused validation that avoids coupling tests to incidental copy, markup, CSS text, or implementation details.

Disciplined debugging loop for broken behavior, failing tests, exceptions, flaky failures, and performance regressions. Use when the user says "debug this", "diagnose this", "this is broken", "this is failing", or reports a reproducible or intermittent bug.