All authors
Claude Skills by TheOnlyFusionCube
github.com/TheOnlyFusionCube52 skills1 installs71 views
- PromptsGenerate a project-local verification skill that drives the real app and captures evidence. Use when setting up automated verification for a repo.Votes: 0GitHub stars: 2
- PromptsRepair a project verification skill whose feature map or commands drifted. Use when app behavior and verification docs no longer agree.Votes: 0GitHub stars: 2
- Reproduce And Fix IssuesReproduce 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.Votes: 0GitHub stars: 2
- Triage Issue ReportsTriage incoming software issue reports using available repository and runtime evidence, without editing code. Use for automated or manual first-pass issue validation and routing.Votes: 0GitHub stars: 2
- ArchitectSettle data shapes, ownership, boundaries, and interfaces before code crosses a function/module boundary. Use for non-trivial design work.Votes: 0GitHub stars: 2
- ArenaSpawn 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.Votes: 0GitHub stars: 2
- Automate MeCreate a personal mode skill from recurring workflow patterns in available history. Use when the user wants their own agent style encoded.Votes: 0GitHub stars: 2
- Blast RadiusProve what a small-looking change can affect before or after editing. Use for compatibility, caller, state, schema, or behavior impact analysis.Votes: 0GitHub stars: 2
- BroRestate the last technical explanation in plain human language with minimal jargon. Use when the user asks for a simpler version.Votes: 0GitHub stars: 2
- Create Verification SkillGenerate a project-local verification skill that drives the real app and captures evidence. Use when setting up automated verification for a repo.Votes: 0GitHub stars: 2
- Figure It OutDesign a rigorous custom playbook when no bundled playbook safely fits a large or unusual task. Use for cross-cutting ambiguous execution.Votes: 0GitHub stars: 2
- HowTrace how a subsystem works using code and runtime evidence. Use for architecture walkthroughs, data flow, call paths, and are-we-sure investigations.Votes: 0GitHub stars: 2
- InterrogateAdversarially review a diff or design with independent lenses and evidence. Use before shipping contested or high-impact changes.Votes: 0GitHub stars: 2
- Maintain Verification SkillRepair a project verification skill whose feature map or commands drifted. Use when app behavior and verification docs no longer agree.Votes: 0GitHub stars: 2
- Make Bot UiBuild a small operator UI over an agent/webhook backend. Use when buttons or controls should trigger an agent workflow.Votes: 0GitHub stars: 2
- No CommentsRemove redundant comments, dead workaround explanations, and AI tells from code while preserving necessary constraints. Use when cleaning up code or diffs.Votes: 0GitHub stars: 2
- Poteto ModeLauren 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.Votes: 0GitHub stars: 2
- Playbooks1. Define precise triggers, non-triggers, outcome, and required capabilities. 2. Keep the SKILL.md focused. Move heavy examples, references, and scripts into progressive-disclosure files. 3. Use portable capability language. Add a fallback for optional capabilities instead of hard-coding one host tool. 4. Validate Agent Skills frontmatter and directory/name parity. 5. Exercise the skill on representative positive and negative cases. Revise based on behavior, not aesthetics alone.Votes: 0GitHub stars: 2
- Principle Attack The PremiseInventory 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.Votes: 0GitHub stars: 2
- Principle Boundary DisciplineValidate 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.Votes: 0GitHub stars: 2
- Principle Build The LeverPrefer 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.Votes: 0GitHub stars: 2
- Principle Encode Lessons In StructureTurn 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.Votes: 0GitHub stars: 2
- Principle Exhaust The Design SpaceBuild 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.Votes: 0GitHub stars: 2
- Principle Experience FirstOptimize for the end-user experience unless the cost violates an explicit constraint. Use when product, UX, API design, or feature-scope tradeoffs arise.Votes: 0GitHub stars: 2
- Principle Fix Root CausesReproduce 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.Votes: 0GitHub stars: 2
- Principle Foundational ThinkingChoose 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.Votes: 0GitHub stars: 2
- Principle Guard The Context WindowRoute 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.Votes: 0GitHub stars: 2
- Principle Laziness ProtocolBias toward deletion and the smallest change that fully solves the problem. Use when considering adding code, abstractions, dependencies, or speculative features.Votes: 0GitHub stars: 2
- Principle Make Operations IdempotentDesign 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.Votes: 0GitHub stars: 2
- Principle Migrate Callers Then Delete Legacy ApisMove 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.Votes: 0GitHub stars: 2
- Principle Minimize Reader LoadReduce 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.Votes: 0GitHub stars: 2
- Principle Model The DomainEncode the domain in the right structure: state machine, typed model, table, registry, reducer, boundary, or collection instead of scattered conditionals. Use when when stateful logic accumulates branches or repeated shape assumptions.Votes: 0GitHub stars: 2
- Principle Never Block On The HumanRun 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.Votes: 0GitHub stars: 2
- Principle Outcome Oriented ExecutionConverge on the target architecture rather than preserving temporary compatibility states as permanent complexity. Use when during planned migrations or rewrites with explicit phases.Votes: 0GitHub stars: 2
- Principle Prove It WorksVerify 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.Votes: 0GitHub stars: 2
- Principle Redesign From First PrinciplesDesign 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.Votes: 0GitHub stars: 2
- Principle Separate Before Serializing Shared StateEliminate unnecessary sharing or partition ownership before adding locks, queues, or coordination. Use when concurrency, locks, queues, shared state, or complex coordination are being considered.Votes: 0GitHub stars: 2
- Principle Sequence Verifiable UnitsBreak 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.Votes: 0GitHub stars: 2
- Principle Subtract Before You AddRemove dead weight and obsolete paths first; build on the simpler remaining system. Use when before an addition, rewrite, or structural refactor.Votes: 0GitHub stars: 2
- Principle Test Behavior Not ImplementationCall 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.Votes: 0GitHub stars: 2
- Principle Type System DisciplineMake 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.Votes: 0GitHub stars: 2
- RecallReconstruct current task context from available durable history and records. Use when resuming work or rebuilding context on a topic.Votes: 0GitHub stars: 2
- ReflectConvert lessons from a completed difficult task into structural improvements. Use after a long or unexpectedly painful workflow.Votes: 0GitHub stars: 2
- Setup PstackConfigure potetos-for-everyone model roles and capability preferences for the current agent/runtime. Use during initial setup or routing changes.Votes: 0GitHub stars: 2
- Show Me Your WorkMaintain a compact auditable decision trail during autonomous or high-stakes work. Use when the user will review decisions later.Votes: 0GitHub stars: 2
- SwarmFan out independent slices or coverage partitions and aggregate them with owner verification. Use for large audits, races, and parallel work.Votes: 0GitHub stars: 2
- TddWrite 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.Votes: 0GitHub stars: 2
- TeachTeach a subsystem or change so the reader can reason about it, combining how and why evidence. Use for real understanding rather than summary.Votes: 0GitHub stars: 2
- Technical WritingWrite maintainable technical docs, RFCs, READMEs, PR descriptions, and commit messages. Use for durable engineering prose.Votes: 0GitHub stars: 2
- Typescript Best PracticesApply disciplined TypeScript modeling and boundary parsing. Use when reading or editing TypeScript.Votes: 0GitHub stars: 2