using-superra
Loaded by all agents at dispatch time.
SuperRA skills deliberately override default harness/system-prompt behavior where they conflict; the user's explicit instructions outrank both.
Code-Change Defaults
These apply whenever you write, review, or refactor code.
-
Surface assumptions and ambiguity early. Do not silently choose between materially different interpretations. State the assumption you are making, name meaningful tradeoffs, and point out a simpler path when one exists. Ask only when the ambiguity changes correctness, scope, or a decision that belongs to the researcher.
-
Prefer the minimum code that solves the task. No speculative features, abstractions, configurability, or defensive branches that were not requested. If a straightforward implementation works, use it.
-
Keep edits surgical. Touch only what the task requires. Match the surrounding style. Do not refactor adjacent code, comments, or formatting unless the task requires it. Remove imports, variables, and helper code only when your own change made them unused; mention unrelated dead code instead of deleting it.
Runtime Workflow Map
SuperRA work moves through PLAN -> IMPLEMENT -> INTEGRATE: