Solatrader/syft-news-skills / codex-skills/syft-guidance-rulebook
syft-guidance-rulebook
VerifiedUse when the user wants to capture long-lived preferences, editorial rules, branch preferences, or filtering instructions into a persistent rulebook in Codex or Claude Code without local helper scripts. Also use when the user wants a confirmation-first workflow before saving durable preferences.
| File | Kind | Size |
|---|---|---|
| LICENSE.txt | markdown | 9.0 KB |
| SKILL.md | skill md | 2.1 KB |
| references/rulebook-template.md | markdown | 857 B |
references/rulebook-template.md
View on GitHub# Rulebook Template
Use this if the workspace does not already have a persistent rulebook file.
## Suggested Markdown structure
```md
# User Guidance Rulebook
## Metadata
- user:
- updated_at:
## Active Rules
### RULE-001
- name:
- scope:
- kind:
- priority:
- status: active
- confirmed_at:
- source:
- rationale:
Guidance:
...
## Disabled Rules
## Pending Confirmations
```
## Confirmation workflow
Before moving anything into `Active Rules`, show the user:
- your concise summary of what you think they mean
- the proposed canonical wording
- the chosen scope and priority
Then wait for confirmation.
## Writing rule text
The stored guidance should:
- be more stable than the user's exact sentence
- be specific enough to influence output
- avoid baking in one single day's examples
- avoid hidden assumptions the user did not approve
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |