@oriro/orirocli 0.1.9 → 0.1.11

package/skills/craft/gpt-5-4-prompting/references/prompt-blocks.md

@@ -1,172 +1,172 @@
-# Prompt Blocks
-
-Use these blocks selectively when composing Codex or GPT-5.4 prompts.
-Wrap each block in the XML tag shown in its heading.
-
-## Core Wrapper
-
-### `task`
-
-Use in nearly every prompt.
-
-```xml
-<task>
-Describe the concrete job, the relevant repository or failure context, and the expected end state.
-</task>
-```
-
-## Output and Format
-
-### `structured_output_contract`
-
-Use when the response shape matters.
-
-```xml
-<structured_output_contract>
-Return exactly the requested output shape and nothing else.
-Keep the answer compact.
-Put the highest-value findings or decisions first.
-</structured_output_contract>
-```
-
-### `compact_output_contract`
-
-Use when you want concise prose instead of a schema.
-
-```xml
-<compact_output_contract>
-Keep the final answer compact and structured.
-Do not include long scene-setting or repeated recap.
-</compact_output_contract>
-```
-
-## Follow-through and Completion
-
-### `default_follow_through_policy`
-
-Use when Codex should act without asking routine questions.
-
-```xml
-<default_follow_through_policy>
-Default to the most reasonable low-risk interpretation and keep going.
-Only stop to ask questions when a missing detail changes correctness, safety, or an irreversible action.
-</default_follow_through_policy>
-```
-
-### `completeness_contract`
-
-Use for debugging, implementation, or any multi-step task that should not stop early.
-
-```xml
-<completeness_contract>
-Resolve the task fully before stopping.
-Do not stop at the first plausible answer.
-Check whether there are follow-on fixes, edge cases, or cleanup needed for a correct result.
-</completeness_contract>
-```
-
-### `verification_loop`
-
-Use when correctness matters.
-
-```xml
-<verification_loop>
-Before finalizing, verify the result against the task requirements and the changed files or tool outputs.
-If a check fails, revise the answer instead of reporting the first draft.
-</verification_loop>
-```
-
-## Grounding and Missing Context
-
-### `missing_context_gating`
-
-Use when Codex might otherwise guess.
-
-```xml
-<missing_context_gating>
-Do not guess missing repository facts.
-If required context is absent, retrieve it with tools or state exactly what remains unknown.
-</missing_context_gating>
-```
-
-### `grounding_rules`
-
-Use for review, research, or root-cause analysis.
-
-```xml
-<grounding_rules>
-Ground every claim in the provided context or your tool outputs.
-Do not present inferences as facts.
-If a point is a hypothesis, label it clearly.
-</grounding_rules>
-```
-
-### `citation_rules`
-
-Use when external research or quotes matter.
-
-```xml
-<citation_rules>
-Back important claims with citations or explicit references to the source material you inspected.
-Prefer primary sources.
-</citation_rules>
-```
-
-## Safety and Scope
-
-### `action_safety`
-
-Use for write-capable or potentially broad tasks.
-
-```xml
-<action_safety>
-Keep changes tightly scoped to the stated task.
-Avoid unrelated refactors, renames, or cleanup unless they are required for correctness.
-Call out any risky or irreversible action before taking it.
-</action_safety>
-```
-
-### `tool_persistence_rules`
-
-Use for long-running tool-heavy tasks.
-
-```xml
-<tool_persistence_rules>
-Keep using tools until you have enough evidence to finish the task confidently.
-Do not abandon the workflow after a partial read when another targeted check would change the answer.
-</tool_persistence_rules>
-```
-
-## Task-Specific Blocks
-
-### `research_mode`
-
-Use for exploration, comparisons, or recommendations.
-
-```xml
-<research_mode>
-Separate observed facts, reasoned inferences, and open questions.
-Prefer breadth first, then go deeper only where the evidence changes the recommendation.
-</research_mode>
-```
-
-### `dig_deeper_nudge`
-
-Use for review and adversarial inspection.
-
-```xml
-<dig_deeper_nudge>
-After you find the first plausible issue, check for second-order failures, empty-state behavior, retries, stale state, and rollback paths before you finalize.
-</dig_deeper_nudge>
-```
-
-### `progress_updates`
-
-Use when the run may take a while.
-
-```xml
-<progress_updates>
-If you provide progress updates, keep them brief and outcome-based.
-Mention only major phase changes or blockers.
-</progress_updates>
-```
+# Prompt Blocks
+
+Use these blocks selectively when composing Codex or GPT-5.4 prompts.
+Wrap each block in the XML tag shown in its heading.
+
+## Core Wrapper
+
+### `task`
+
+Use in nearly every prompt.
+
+```xml
+<task>
+Describe the concrete job, the relevant repository or failure context, and the expected end state.
+</task>
+```
+
+## Output and Format
+
+### `structured_output_contract`
+
+Use when the response shape matters.
+
+```xml
+<structured_output_contract>
+Return exactly the requested output shape and nothing else.
+Keep the answer compact.
+Put the highest-value findings or decisions first.
+</structured_output_contract>
+```
+
+### `compact_output_contract`
+
+Use when you want concise prose instead of a schema.
+
+```xml
+<compact_output_contract>
+Keep the final answer compact and structured.
+Do not include long scene-setting or repeated recap.
+</compact_output_contract>
+```
+
+## Follow-through and Completion
+
+### `default_follow_through_policy`
+
+Use when Codex should act without asking routine questions.
+
+```xml
+<default_follow_through_policy>
+Default to the most reasonable low-risk interpretation and keep going.
+Only stop to ask questions when a missing detail changes correctness, safety, or an irreversible action.
+</default_follow_through_policy>
+```
+
+### `completeness_contract`
+
+Use for debugging, implementation, or any multi-step task that should not stop early.
+
+```xml
+<completeness_contract>
+Resolve the task fully before stopping.
+Do not stop at the first plausible answer.
+Check whether there are follow-on fixes, edge cases, or cleanup needed for a correct result.
+</completeness_contract>
+```
+
+### `verification_loop`
+
+Use when correctness matters.
+
+```xml
+<verification_loop>
+Before finalizing, verify the result against the task requirements and the changed files or tool outputs.
+If a check fails, revise the answer instead of reporting the first draft.
+</verification_loop>
+```
+
+## Grounding and Missing Context
+
+### `missing_context_gating`
+
+Use when Codex might otherwise guess.
+
+```xml
+<missing_context_gating>
+Do not guess missing repository facts.
+If required context is absent, retrieve it with tools or state exactly what remains unknown.
+</missing_context_gating>
+```
+
+### `grounding_rules`
+
+Use for review, research, or root-cause analysis.
+
+```xml
+<grounding_rules>
+Ground every claim in the provided context or your tool outputs.
+Do not present inferences as facts.
+If a point is a hypothesis, label it clearly.
+</grounding_rules>
+```
+
+### `citation_rules`
+
+Use when external research or quotes matter.
+
+```xml
+<citation_rules>
+Back important claims with citations or explicit references to the source material you inspected.
+Prefer primary sources.
+</citation_rules>
+```
+
+## Safety and Scope
+
+### `action_safety`
+
+Use for write-capable or potentially broad tasks.
+
+```xml
+<action_safety>
+Keep changes tightly scoped to the stated task.
+Avoid unrelated refactors, renames, or cleanup unless they are required for correctness.
+Call out any risky or irreversible action before taking it.
+</action_safety>
+```
+
+### `tool_persistence_rules`
+
+Use for long-running tool-heavy tasks.
+
+```xml
+<tool_persistence_rules>
+Keep using tools until you have enough evidence to finish the task confidently.
+Do not abandon the workflow after a partial read when another targeted check would change the answer.
+</tool_persistence_rules>
+```
+
+## Task-Specific Blocks
+
+### `research_mode`
+
+Use for exploration, comparisons, or recommendations.
+
+```xml
+<research_mode>
+Separate observed facts, reasoned inferences, and open questions.
+Prefer breadth first, then go deeper only where the evidence changes the recommendation.
+</research_mode>
+```
+
+### `dig_deeper_nudge`
+
+Use for review and adversarial inspection.
+
+```xml
+<dig_deeper_nudge>
+After you find the first plausible issue, check for second-order failures, empty-state behavior, retries, stale state, and rollback paths before you finalize.
+</dig_deeper_nudge>
+```
+
+### `progress_updates`
+
+Use when the run may take a while.
+
+```xml
+<progress_updates>
+If you provide progress updates, keep them brief and outcome-based.
+Mention only major phase changes or blockers.
+</progress_updates>
+```

package/skills/craft/grill-me/LICENSE

@@ -1,21 +1,21 @@
-MIT License
-
-Copyright (c) 2026 ORIRO.ai
-
-Permission is hereby granted, free of charge, to any person obtaining a copy
-of this software and associated documentation files (the "Software"), to deal
-in the Software without restriction, including without limitation the rights
-to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
-copies of the Software, and to permit persons to whom the Software is
-furnished to do so, subject to the following conditions:
-
-The above copyright notice and this permission notice shall be included in all
-copies or substantial portions of the Software.
-
-THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
-IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
-FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
-AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
-LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
-OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
-SOFTWARE.
+MIT License
+
+Copyright (c) 2026 ORIRO.ai
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

package/skills/craft/grill-me/SKILL.md

@@ -1,13 +1,13 @@
----
-watermark: ORIRO
-name: grill-me
-provider: ORIRO.ai
-copyright: Copyright (c) 2026 ORIRO.ai
-description: Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me".
----
-
-Interview me relentlessly about every aspect of this plan until we reach a shared understanding. Walk down each branch of the design tree, resolving dependencies between decisions one-by-one. For each question, provide your recommended answer.
-
-Ask the questions one at a time.
-
-If a question can be answered by exploring the codebase, explore the codebase instead.
+---
+watermark: ORIRO
+name: grill-me
+provider: ORIRO.ai
+copyright: Copyright (c) 2026 ORIRO.ai
+description: Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me".
+---
+
+Interview me relentlessly about every aspect of this plan until we reach a shared understanding. Walk down each branch of the design tree, resolving dependencies between decisions one-by-one. For each question, provide your recommended answer.
+
+Ask the questions one at a time.
+
+If a question can be answered by exploring the codebase, explore the codebase instead.

package/skills/craft/idea-to-deploy/LICENSE

@@ -1,21 +1,21 @@
-MIT License
-
-Copyright (c) 2026 ORIRO.ai
-
-Permission is hereby granted, free of charge, to any person obtaining a copy
-of this software and associated documentation files (the "Software"), to deal
-in the Software without restriction, including without limitation the rights
-to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
-copies of the Software, and to permit persons to whom the Software is
-furnished to do so, subject to the following conditions:
-
-The above copyright notice and this permission notice shall be included in all
-copies or substantial portions of the Software.
-
-THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
-IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
-FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
-AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
-LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
-OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
-SOFTWARE.
+MIT License
+
+Copyright (c) 2026 ORIRO.ai
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.