Every rule, and how hard it binds

228 rules match. Showing 151–175.

1. TEC-005 Prerequisites before steps IF a task requires permissions, state, tools, knowledge, inputs, or safety conditions, THEN list them before step 1 ELSE state that none are required only when useful. Hard constraint
2. TEC-006 Imperative starts the step IF the reader performs a procedural action, THEN start with a specific imperative verb and name the object ELSE name the actual actor. Context default
3. TEC-007 Expected result follows uncertain action IF a step’s success is not self-evident, THEN state the observable result immediately after it ELSE retain. Context default
4. TEC-008 Recovery follows known failure IF a step has a common or consequential failure mode, THEN provide symptom, cause or check, corrective action, and verification ELSE retain. Context default
5. TEC-009 Troubleshooting begins with observable symptom IF troubleshooting advice begins with an assumed cause, THEN reframe from the user-observable symptom and branch by tests ELSE retain. Hard constraint
6. TEC-010 Safety warning precedes the hazard IF an action can cause injury, loss, security exposure, or irreversible damage, THEN place a severity-labeled warning before the action and state avoidance ELSE block release. Hard constraint
7. TEC-011 UI verb works across input methods IF an instruction refers to a generic interface action, THEN prefer input-neutral verbs such as SELECT, OPEN, ENTER, or CHOOSE; use CLICK only for mouse-specific action ELSE retain. Context default
8. TEC-012 Interface labels match exactly IF documentation names a visible label, command, field, endpoint, or code identifier, THEN match its current spelling and capitalization exactly ELSE flag version mismatch. Hard constraint
9. TEC-013 Code examples are runnable or explicitly partial IF a code example is presented, THEN test it in the declared environment OR label omitted setup and placeholders ELSE do not imply it runs. Hard constraint
10. TEC-014 API reference exposes contract IF an endpoint, function, event, or schema is documented, THEN specify inputs, types, requiredness, constraints, outputs, errors, examples, and version ELSE mark incomplete. Hard constraint
11. TEC-015 Version-sensitive statement declares scope IF behavior varies by version, platform, plan, locale, or configuration, THEN state the applicable scope beside the claim ELSE retain. Hard constraint
12. TEC-016 Links describe destination or action IF link text is generic, duplicated, or meaningful only from surrounding visual position, THEN replace it with a concise destination or action ELSE retain. Hard constraint
13. TEC-017 Terms and examples globalize safely IF content will be translated or read globally, THEN avoid culture-bound idioms, ambiguous dates, concatenated fragments, and unstable synonyms ELSE retain. Context default
14. TEC-018 Document ownership and freshness IF technical content can change with the product or policy, THEN record owner, applicable version, review trigger, and last verified date ELSE retain. Context default
15. TEC-019 Reuse single-source facts IF the same volatile fact appears in multiple documents, THEN centralize it or generate references from one source ELSE retain independent stable statements. Heuristic
16. TEC-020 Validate documentation as a system IF a release changes interfaces, behavior, permissions, errors, or prerequisites, THEN run impact search and documentation regression checks ELSE retain. Hard constraint
17. CPY-001 Start from market awareness IF writing persuasive copy, THEN classify the audience as unaware, problem-aware, solution-aware, product-aware, or most-aware before choosing the message ELSE request research. Hard constraint
18. CPY-002 Match lead to awareness and evidence IF awareness is known, THEN select a lead type that bridges the reader’s current state to the offer ELSE do not default to a hype lead. Context default
19. CPY-003 Headline makes one credible promise IF a headline is used, THEN make its audience relevance, benefit or curiosity, and credible scope legible ELSE revise. Hard constraint
20. CPY-004 Mechanism explains the promise IF the promise is unfamiliar, counterintuitive, or in a sophisticated market, THEN explain why and how the offer produces the result ELSE keep the mechanism concise. Context default
21. CPY-005 Translate feature into buyer outcome IF copy names a feature, THEN connect it to functional benefit, practical outcome, and relevant emotional meaning when supported ELSE remove the feature. Context default
22. CPY-006 Specificity earns credibility IF a claim uses generic superiority language AND verifiable specifics exist, THEN replace the generic phrase with the relevant specific ELSE qualify or remove it. Heuristic
23. CPY-007 Proof appears after or near the claim IF a material sales claim is made, THEN attach the strongest appropriate proof close to it ELSE weaken or remove the claim. Hard constraint
24. CPY-008 Testimonial is real, typicality-aware, and specific IF a testimonial is used, THEN verify identity permission, authenticity, result context, and any required typicality disclosure ELSE remove it. Hard constraint
25. CPY-009 Objection response names the real risk IF research shows a recurring material objection, THEN acknowledge it, answer with proof or terms, and preserve any legitimate limitation ELSE do not invent objections. Context default