Skip to main content
Use these ready-made blocks to move fast while keeping quality and safety.

​
Feature build

  • Good: “Build <feature>. Goals: <outcome>. Scope: <areas/files>. Constraints: <perf/security/UX>. Output: code + brief summary. Tests: <cases>. Iterate back with plan and risks before edits.”
  • Bad: “Build the feature.”

​
Bug investigation

  • Good: “Bug: <symptom>. Repro: <steps>. Suspected areas: <files>. Ask clarifying questions. Do a context sweep, list hypotheses, propose minimal fixes with tests. No edits until I approve.”
  • Bad: “Fix it.”

​
Performance audit

  • Good: “Audit <page/service> for perf. Map calls, rendering hotspots, and asset sizes. Prioritize issues by impact/effort. Propose fixes and tests. No code changes.”
  • Bad: “Make it faster.”

​
UX redesign

  • Good: “Redesign <page/flow>. Keep: <must-keep>. Change: <problems>. Components: <list>. Style: <direction>. Use real copy: <text>. Show before/after rationale. Provide mobile + desktop guidance.”
  • Bad: “Make it look nicer.”

​
Guarded change

  • Good: “Critical area. Edit only <files>. Restate current behavior, intended change, risks, and tests. Make smallest change. Stop if scope expands.”
  • Bad: “Update auth quickly.”

​
Option set

  • Good: “Give 3 options for <goal>. For each: approach, pros/cons, effort, risks, validation. Recommend one and what would change your pick.”
  • Bad: “What should we do?”