all publishers

TheOnlyFusionCube

@theonlyfusioncube source repo

54 published skills

  1. ▌
    Devin · theonlyfusioncube bundle
    Run Devin (the Cognition AI coding agent) from any coding agent or CLI. Use when the user asks for a Devin code review, an adversarial review, to delegate a task to Devin, to hand work off to a cloud Devin session at app.devin.ai, or to check/cancel Devin background jobs. Requires the devin-plugin-cc checkout and the local `devin` CLI (or DEVIN_API_KEY for cloud handoffs).
    22 repo stars
  2. ▌
    Fusion · theonlyfusioncube bundle
    Run a frontier-lead Fusion workflow with GPT 6 Astra as lead and Devin as the sidekick for bounded coding work.
    22 repo stars
  3. ▌
    Devin Prompting · theonlyfusioncube
    Internal guidance for composing Devin prompts for coding, review, diagnosis, and research tasks inside the Devin Claude Code plugin
    22 repo stars
  4. ▌
    Devin Result Handling · theonlyfusioncube
    Internal guidance for presenting Devin helper output back to the user
    22 repo stars
  5. ▌
    Statechart · theonlyfusioncube bundle
    Draw what an app's user sees as a Mermaid statechart from a TLA+ model. States are gray if they work, red if still wrong, and green if fixed. Each bug TLC finds is a numbered path. Use for /statechart, "show the PM the bug", or to turn an agreed chart into a TLA+ skeleton.
    22 repo stars
  6. ▌
    Maintain Verification Skill · theonlyfusioncube
    Repair a project verification skill whose feature map or commands drifted. Use when app behavior and verification docs no longer agree.
    22 repo stars
  7. ▌
    Principle Laziness Protocol · theonlyfusioncube
    Bias toward deletion and the smallest change that fully solves the problem. Use when considering adding code, abstractions, dependencies, or speculative features.
    22 repo stars
  8. ▌
    Principle Attack The Premise · theonlyfusioncube
    Inventory who actually owns or exhibits the imbalance, then challenge the shared premise before writing another patch. Use when two or more fixes that share one premise have failed the same gate.
    22 repo stars
  9. ▌
    Principle Boundary Discipline · theonlyfusioncube
    Validate and normalize at boundaries, trust internal invariants, and keep business logic free of adapter noise. Use when at parsing, framework, process, network, storage, or user-input boundaries.
    22 repo stars
  10. ▌
    Principle Minimize Reader Load · theonlyfusioncube
    Reduce indirection, mutable scope, and one-caller abstractions until the causal path is easy to hold in one mind. Use when when code requires too many hops, wrappers, hidden states, or mental joins.
    22 repo stars
  11. ▌
    Principle Foundational Thinking · theonlyfusioncube
    Choose the core data structures, ownership, and sequencing first so downstream logic becomes simpler. Use when before writing logic, especially when state or concurrency is involved.
    22 repo stars
  12. ▌
    Principle Type System Discipline · theonlyfusioncube
    Make invalid states hard or impossible to represent and parse external primitives into meaningful internal types at the edge. Use at data modeling, API design, or external data ingestion points.
    22 repo stars
  13. ▌
    Principle Subtract Before You Add · theonlyfusioncube
    Remove dead weight and obsolete paths first; build on the simpler remaining system. Use when before an addition, rewrite, or structural refactor.
    22 repo stars
  14. ▌
    Principle Exhaust The Design Space · theonlyfusioncube
    Build a few materially different cheap prototypes and compare evidence before committing to one design. Use when for novel interactions or architecture with no strong precedent.
    22 repo stars
  15. ▌
    Principle Guard The Context Window · theonlyfusioncube
    Route bulk exploration to isolated workers or files and bring back compact evidence summaries, not raw floods. Use when when reads, logs, fan-out, or generated output threatens to dominate context.
    22 repo stars
  16. ▌
    Principle Never Block On The Human · theonlyfusioncube
    Run the experiment or make the reversible best-effort change, then show the result. Ask only for genuine preference, authority, or irreversible decisions. Use when when a reversible empirical or implementation choice can be resolved with available tools.
    22 repo stars
  17. ▌
    Principle Sequence Verifiable Units · theonlyfusioncube
    Break work into small units that each end with a proof and order delivery so every next unit builds on verified state. Use when for migrations, sweeps, repeated edits, and stacks.
    22 repo stars
  18. ▌
    Principle Make Operations Idempotent · theonlyfusioncube
    Design repeated execution to converge on the same correct end state rather than multiplying side effects. Use when for commands, lifecycle steps, retries, loops, or crash recovery.
    22 repo stars
  19. ▌
    Principle Outcome Oriented Execution · theonlyfusioncube
    Converge on the target architecture rather than preserving temporary compatibility states as permanent complexity. Use when during planned migrations or rewrites with explicit phases.
    22 repo stars
  20. ▌
    Principle Encode Lessons In Structure · theonlyfusioncube
    Turn recurring guidance into a type, lint, test, metadata flag, generator, runtime check, or skill so the system carries the lesson. Use when when the same corrective instruction appears more than once.
    22 repo stars
  21. ▌
    Triage Issue Reports · theonlyfusioncube
    Triage incoming software issue reports using available repository and runtime evidence, without editing code. Use for automated or manual first-pass issue validation and routing.
    22 repo stars
  22. ▌
    Principle Redesign From First Principles · theonlyfusioncube
    Design the shape you would choose if the requirement had existed from day one, then migrate toward that shape. Use when when integrating a new requirement into a design that keeps fighting it.
    22 repo stars
  23. ▌
    Reproduce And Fix Issues · theonlyfusioncube
    Reproduce a confirmed issue on the closest real surface, find root cause, and optionally prepare a minimal draft fix with evidence. Use after issue triage has enough information to attempt reproduction.
    22 repo stars
  24. ▌
    Principle Test Behavior Not Implementation · theonlyfusioncube
    Call the system the way its consumer does and assert meaningful observable output; avoid mocks or assertions that only mirror internal calls. Use when when writing or evaluating tests.
    22 repo stars
  25. ▌
    Principle Migrate Callers Then Delete Legacy Apis · theonlyfusioncube
    Move callers to the new shape and delete the old path in the same migration wave instead of carrying a compatibility layer. Use when when replacing an internal api.
    22 repo stars
  26. ▌
    Principle Separate Before Serializing Shared State · theonlyfusioncube
    Eliminate unnecessary sharing or partition ownership before adding locks, queues, or coordination. Use when concurrency, locks, queues, shared state, or complex coordination are being considered.
    22 repo stars
  27. ▌
    Bro · theonlyfusioncube
    Restate the last technical explanation in plain human language with minimal jargon. Use when the user asks for a simpler version.
    22 repo stars
  28. ▌
    How · theonlyfusioncube
    Trace how a subsystem works using code and runtime evidence. Use for architecture walkthroughs, data flow, call paths, and are-we-sure investigations.
    22 repo stars
  29. ▌
    Tdd · theonlyfusioncube
    Write a minimal failing test before implementation, make it pass with the simplest code, and refactor cleanly. Use when implementing bug fixes or features with clear verification targets.
    22 repo stars
  30. ▌
    Why · theonlyfusioncube
    Recover why a system or decision exists by triangulating source history and connected evidence. Use for rationale archaeology and historical questions.
    22 repo stars
  31. ▌
    Arena · theonlyfusioncube
    Spawn parallel candidate implementations for the same task, cross-judge, and graft the best parts into the winning base. Use when exploring competing designs or critical artifacts.
    22 repo stars
  32. ▌
    Swarm · theonlyfusioncube
    Fan out independent slices or coverage partitions and aggregate them with owner verification. Use for large audits, races, and parallel work.
    22 repo stars
  33. ▌
    Teach · theonlyfusioncube
    Teach a subsystem or change so the reader can reason about it, combining how and why evidence. Use for real understanding rather than summary.
    22 repo stars
  34. ▌
    Recall · theonlyfusioncube
    Reconstruct current task context from available durable history and records. Use when resuming work or rebuilding context on a topic.
    22 repo stars
  35. ▌
    Unslop · theonlyfusioncube
    Cut AI tells, filler prose, superficial -ing phrases, and bloated commentary from writing and code. Use for all written deliverables and code cleanup.
    22 repo stars
  36. ▌
    Reflect · theonlyfusioncube
    Convert lessons from a completed difficult task into structural improvements. Use after a long or unexpectedly painful workflow.
    22 repo stars
  37. ▌
    Architect · theonlyfusioncube
    Settle data shapes, ownership, boundaries, and interfaces before code crosses a function/module boundary. Use for non-trivial design work.
    22 repo stars
  38. ▌
    Automate Me · theonlyfusioncube
    Create a personal mode skill from recurring workflow patterns in available history. Use when the user wants their own agent style encoded.
    22 repo stars
  39. ▌
    Interrogate · theonlyfusioncube
    Adversarially review a diff or design with independent lenses and evidence. Use before shipping contested or high-impact changes.
    22 repo stars
  40. ▌
    Make Bot UI · theonlyfusioncube
    Build a small operator UI over an agent/webhook backend. Use when buttons or controls should trigger an agent workflow.
    22 repo stars
  41. ▌
    No Comments · theonlyfusioncube
    Remove redundant comments, dead workaround explanations, and AI tells from code while preserving necessary constraints. Use when cleaning up code or diffs.
    22 repo stars
  42. ▌
    Poteto Mode · theonlyfusioncube bundle
    Lauren Tan-inspired rigorous engineering mode for concise communication, deliberate decomposition, simple code, independent review when available, and runtime verification. Use for non-trivial engineering tasks or when the user asks for Poteto Mode/pstack-style rigor.
    22 repo stars
  43. ▌
    Blast Radius · theonlyfusioncube
    Prove what a small-looking change can affect before or after editing. Use for compatibility, caller, state, schema, or behavior impact analysis.
    22 repo stars
  44. ▌
    Setup Pstack · theonlyfusioncube
    Configure potetos-for-everyone model roles and capability preferences for the current agent/runtime. Use during initial setup or routing changes.
    22 repo stars
  45. ▌
    Figure It Out · theonlyfusioncube
    Design a rigorous custom playbook when no bundled playbook safely fits a large or unusual task. Use for cross-cutting ambiguous execution.
    22 repo stars
  46. ▌
    Show Me Your Work · theonlyfusioncube
    Maintain a compact auditable decision trail during autonomous or high-stakes work. Use when the user will review decisions later.
    22 repo stars
  47. ▌
    Technical Writing · theonlyfusioncube
    Write maintainable technical docs, RFCs, READMEs, PR descriptions, and commit messages. Use for durable engineering prose.
    22 repo stars
  48. ▌
    Principle Prove It Works · theonlyfusioncube
    Verify the requested behavior against the real artifact or surface whenever possible; a proxy check only proves the proxy. Use when verifying changes, completing tasks, or claiming something is fixed.
    22 repo stars
  49. ▌
    Create Verification Skill · theonlyfusioncube
    Generate a project-local verification skill that drives the real app and captures evidence. Use when setting up automated verification for a repo.
    22 repo stars
  50. ▌
    Principle Build The Lever · theonlyfusioncube
    Prefer a script, codemod, generator, benchmark, or verifier that performs or proves the work repeatably over hand edits. Use when for repetitive, large, or verification-heavy work.
    22 repo stars
  51. ▌
    Principle Fix Root Causes · theonlyfusioncube
    Reproduce the symptom, trace causality until one mechanism explains it, and fix that mechanism rather than compensating for downstream effects. Use when during debugging and incident repair.
    22 repo stars
  52. ▌
    Typescript Best Practices · theonlyfusioncube
    Apply disciplined TypeScript modeling and boundary parsing. Use when reading or editing TypeScript.
    22 repo stars
  53. ▌
    Principle Experience First · theonlyfusioncube
    Optimize for the end-user experience unless the cost violates an explicit constraint. Use when product, UX, API design, or feature-scope tradeoffs arise.
    22 repo stars
  54. ▌
    Principle Model The Domain · theonlyfusioncube
    Model the Domain
    22 repo stars