10 actions in 10 pieces of software · ranked by words, meaning and measured trust · 506 ms
skillcursor/pluginsrecord
- principle-build-the-lever
Apply to any non-trivial work, not just bulk work: edits, migrations, analyses, checks. Build the tool that does it or proves it (codemod, script, generator, or a skill your subagents follow) instead of working by hand. The tool is the artifact a reviewer can rerun.
- principle-build-the-lever
skillcursor/pluginsrecord
- principle-exhaust-the-design-space
Apply when facing a novel UI interaction or architectural decision with no precedent in the codebase. Build 2-3 competing prototypes and compare side by side before committing.
- principle-exhaust-the-design-space
skillcursor/pluginsrecord
- principle-subtract-before-you-add
Apply when sequencing an addition, refactor, or rewrite. Remove dead code, redundant validators, and stub references first, then build on the simpler base.
- principle-subtract-before-you-add
skillcursor/pluginsrecord
- principle-laziness-protocol
Apply when refactoring, evaluating diff size, or tempted to add abstractions, layers, or signal threading. Bias toward deletion and the smallest change that solves the problem.
- principle-laziness-protocol
skillcursor/pluginsrecord
- principle-foundational-thinking
Apply before writing logic: choosing core types and data structures, sequencing scaffold-vs-feature work, asking what concurrent actors share. Get the data structures right so downstream code becomes obvious.
- principle-foundational-thinking
skillcursor/pluginsrecord
- principle-never-block-on-the-human
Apply when tempted to ask 'should I do X?' on reversible work.
- principle-never-block-on-the-human
skillcursor/pluginsrecord
- principle-experience-first
Apply when product, UX, or feature-scope tradeoffs come up. Choose user delight over implementation convenience; ship fewer polished features over more rough ones.
- principle-experience-first
skillcursor/pluginsrecord
- principle-attack-the-premise
Apply when two or more fixes that share one premise have failed the same gate. Write the premise down and test it directly before you write another fix that assumes it.
- principle-attack-the-premise
skillcursor/pluginsrecord
- principle-encode-lessons-in-structure
Apply when you catch yourself writing the same instruction a second time, or notice a recurring correction. Encode the rule as a lint, metadata flag, runtime check, or script instead of more text.
- principle-encode-lessons-in-structure
skillcursor/pluginsrecord
- principle-redesign-from-first-principles
Apply when integrating a new requirement into an existing design.
- principle-redesign-from-first-principles
Labels are the instruments' verdict and are never changed by ranking. Agents and robots get this same answer as JSON at /api/v1/find?q=…&answer=1 and through the MCP server.