@remits/remits-cli 0.1.84 → 0.1.85
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/package.json +1 -1
- package/skills/remits-cli/SKILL.md +13 -0
package/package.json
CHANGED
|
@@ -698,6 +698,19 @@ Both are valid. Use Test components when the behavior can be asserted programmat
|
|
|
698
698
|
|
|
699
699
|
**Never skip verification.** If the user says "just do it" or "that's fine, commit it" — verify anyway. Silent bugs erode trust. If you can't verify because there's no Test component and no relevant embeddable, tell the user what you'd need to verify and ask how they'd like to proceed.
|
|
700
700
|
|
|
701
|
+
### Avoid Brittle Front-Stage Intelligence
|
|
702
|
+
|
|
703
|
+
When a Remits component must interpret, classify, extract, reconcile, route, match, or otherwise make judgment calls over variable real-world data, do not implement that intelligence as hard-coded helper methods, regex cascades, keyword lists, filename/layout assumptions, or overly specific branching.
|
|
704
|
+
|
|
705
|
+
Use the platform's AI-first pattern instead:
|
|
706
|
+
- deterministic code bounds inputs, normalizes obvious protocol details, validates schema shape, performs math, and persists authoritative results
|
|
707
|
+
- `ai()`, agents, tools, prompts, and `index_search()` handle fuzzy interpretation and variable document/data understanding
|
|
708
|
+
- prompts live in Prompt files when non-trivial and are explicit, schema-grounded, and testable
|
|
709
|
+
- tool calls are preferred over scraping JSON out of model text when state needs to change
|
|
710
|
+
- deterministic validation checks AI output before writes and provides safe fallbacks
|
|
711
|
+
|
|
712
|
+
Regex and narrow helper methods are acceptable for mechanical parsing, exact validation, stable protocol handling, and guardrails. They are not acceptable as the primary strategy for messy document understanding, classification, matching, or other intelligence-like behavior. If a component guide and `docs/guides/features/ai-support.md` point to an AI-supported capability, follow that surface before inventing brittle code.
|
|
713
|
+
|
|
701
714
|
### The Development Fast Loop
|
|
702
715
|
|
|
703
716
|
This is how every development task should flow:
|