PStack Core Operations Guide

1. Don't pile up prompts: entry directly calls the model, only give clear goals and acceptance criteria, let the system automatically match 22 troubleshooting handbooks based on the scenario. 2. Constraint layering rules (from hard to soft): code physical directory isolation > compiler/CI/Lint mechanical failure > Rules > Skills > style guide. Remember: relying on the last two soft rules to manage projects, the codebase will eventually become a garbage heap. 3. Unit test the Skill: treat the skill itself as code to test, in an anonymous clean directory let an independent model act as judge for blind testing and scoring, never deploy unless it reaches 10/10. 4. Subtraction priority principle: if you can delete code, never add code; the smaller the modification scope, the better; any cross-process violation reference is killed at build time.