fieldnote-echo/rules icon
public
Published on 6/22/2025
Rules

Always Rules for DSC Development

Rules

🎯 Highest Impact (Top 20% = 80% Value)

  1. Use sequential thinking for all problem-solving - Prevents logical errors
  2. Check blessing (Φ) before any action - Prevents unsafe outputs
  3. Never use any type - Prevents type errors
  4. Always complete implementations - Prevents broken code

💪 Medium Impact

  1. Find and fix root causes - Not symptoms
  2. Persist all actions to MD files - Immediate memory
  3. Break large tasks into subtasks - Use TaskMaster for 3+ steps
  4. Ask for clarification when needed - No assumptions

🔧 Maintenance Rules

  1. Be brutally honest - About capabilities and issues
  2. Support silence as valid output - Return "‿" when not blessed
  3. Only commit when explicitly asked - Never proactively
  4. Read codebase for context - Before implementing

📋 Quick Reference

Before coding: Sequential thinking → Read context → Check blessing
During coding: No any → Complete implementation → Fix root causes
After coding: Save to MD → Update todos → Wait for commit request

🚨 Rule Violations = Immediate Correction

These rules are non-negotiable. Any violation should trigger:

  1. Stop current action
  2. Correct the violation
  3. Document in MD
  4. Continue properly

Remember: Quality > Speed. Completeness > Partial solutions.