← all publishers

denizaslan36

@denizaslan36 source repo

Report this profile Claim this profile

• 6 skills
• 0 followers
• 5 hours ago last updated

1. ▌
   Scope Lock · denizaslan36

   Keep implementation or review work inside the user's authorized outcome and protect unrelated work. Use when requirements are sprawling, the repository is dirty, a change risks expanding into refactoring, or the user asks to prevent scope creep. Do not use for open-ended exploration where discovering a wider scope is the goal.
   0 installs
2. ▌
   Debug Reset · denizaslan36

   Reset a stalled debugging attempt and replace repeated guesswork with one discriminating investigation. Use after multiple failed fixes, recurring errors, contradictory symptoms, or when the user says the debugging process is stuck. Do not use for a first simple error with an obvious verified cause.
   0 installs
3. ▌
   Brutal Review · denizaslan36

   Adversarially review an idea, plan, design, implementation, or draft before commitment. Use when the user asks for a brutal review, stress test, pre-mortem, hostile reviewer, failure analysis, or a candid go/no-go judgment. Do not use for ordinary proofreading or when the user only wants implementation.
   0 installs
4. ▌
   Release Ready · denizaslan36

   Perform a final readiness audit of a repository, package, tool, model, dataset, or public artifact before release. Use when the user asks whether work is ready to publish, open-source, tag, package, or hand off. Do not use for ordinary feature completion or to publish anything without explicit authorization.
   0 installs
5. ▌
   Evidence Audit · denizaslan36

   Audit claims in a technical, scientific, analytical, or research document for evidentiary strength and calibrated wording. Use for report review, source-to-claim checking, uncertainty review, citation support, or distinguishing measurements from inference. Do not use for ordinary copyediting or to begin new research unless the user requests it.
   0 installs
6. ▌
   Verification Gate · denizaslan36

   Audit whether completed work actually supports its success claims. Use before saying a change is complete, fixed, passing, compliant, or ready when those claims can be checked. Do not use for early exploration, ideation, or requests that only ask for a plan.
   0 installs