A skill should do its work and stop, avoiding performative complexity and multi-stage flows when single-pass suffices.

Entities in the same semantic neighborhood but without a typed relation to this one — candidates for new edges or unrecognized duplicates.

• Skills should interconnect with each other rather than operate independently; output of one feeds another.claim0.826
• Parallel sub-tasks within skills and across skill families should produce parallel outputs for legibility.claim0.804
• A skill works at multiple reinforcing scales: individual command, skill invocation, and user project.claim0.800
• Single-process, non-interruptible task switching at command boundaries is sufficient for responsive single-user systems; avoids complexity of multiprocess synchronization.hypothesis0.799
  Design hypothesis that coarse-grained task switching (at commands only) eliminates need for protection mechanisms while maintaining usability.
• If we do one thing at a time, and if what we do is wholesome and sound, then whatever comes next will work.hypothesis0.792
  A predictive statement encapsulating the confidence of living process.
• Skills that occasionally produce unexpected output may be more useful than perfectly predictable skills.claim0.791
• Everything should be made as simple as possible, but not simpler.quote0.790
  Einstein's assertion invoked to explain why BMR preserves accuracy while reducing complexity
• Every skill should have one unmistakable thing it does; sprawling skills violate the Strong Centers principle.claim0.788