mariusflores
15 skills with substantive source documentation and an official publisher or observed installation demand. Read each skill’s original documentation through its card.
mariusflorescubenchmark-checklist
Vet a perf measurement (limiter, tuning, limits, errors, repeatability, relevance, and whether the work happened) before you report or act on it. Use when you run a benchmark or report a speedup or regression you measured.
- 설치 수
- 1
- GitHub Stars
- 13
- 업데이트
- 10월 20일
mariusflorescublast-radius
Find what a change could break somewhere else before it ships, beyond the diff, and prove the one fact it's safe because of by running real code instead of writing it up. Use for 'blast radius of X', 'what could this break', or reviewing a small diff you don't trust.
- 설치 수
- 1
- GitHub Stars
- 13
- 업데이트
- 10월 20일
mariusflorescucorrect
Find the mistakes agents keep repeating in this repo and make each one impossible. Try architecture first, then types, then a lint whose error names the fix, then a test, and write docs last. Prove each check fails on a real past mistake. Repeat this each time the operator corrects you. Use for /correct.
- 설치 수
- 1
- GitHub Stars
- 13
- 업데이트
- 10월 20일
mariusflorescumaintain-formal-verification-skill
Bring a project's formal verification back in line with the code after the code changes: find the commits that touched verified code, update the model, harness, or properties to describe the code as it is now, rerun, and say whether each failure is drift in the verification or a bug in the code. Use for /maintain-formal-verification-skill, \"is the model still true to the code\", or after merges and refactors that touched verified code without rechecking it.
- 설치 수
- 1
- GitHub Stars
- 13
- 업데이트
- 10월 20일
mariusflorescuno-comments
Spawn Comment Sicko, fix accepted findings, and offer encodings for claimed constraints.
- 설치 수
- 1
- GitHub Stars
- 13
- 업데이트
- 10월 20일
mariusflorescupoteto-mode
poteto's agent style for concise, detailed responses, deliberate subagents, unslopped prose, simple code, and verified work. Use for poteto, /poteto-mode, or requests to work in this style.
- 설치 수
- 1
- GitHub Stars
- 13
- 업데이트
- 10월 20일
mariusflorescuprinciple-boundary-discipline
Apply when wiring validation, error handling, or framework adapters. Concentrate guards at system boundaries (CLI, config, network, external APIs); trust internal types and keep business logic in pure functions.
- 설치 수
- 1
- GitHub Stars
- 13
- 업데이트
- 10월 20일
mariusflorescuprinciple-make-operations-idempotent
Apply when designing commands, lifecycle steps, or processing loops that run amid crashes, restarts, and retries. Converge to the same end state regardless of partial prior runs.
- 설치 수
- 1
- GitHub Stars
- 13
- 업데이트
- 10월 20일
mariusflorescuprinciple-model-the-domain
Apply when writing stateful logic, or when code branches a lot or repeats a shape assumption across files.
- 설치 수
- 1
- GitHub Stars
- 13
- 업데이트
- 10월 20일
mariusflorescuprinciple-prove-it-works
Apply after completing a task, before declaring done. Verify against the real artifact (run the feature, read the actual value, inspect the diff), not a proxy, self-report, or 'it compiles.'
- 설치 수
- 1
- GitHub Stars
- 13
- 업데이트
- 10월 20일
mariusflorescuprinciple-sequence-verifiable-units
Apply to multi-step work (sweeps, migrations, runs of similar edits) and to how you stack commits and PRs. Break work into small units that each end in a verifiable state, check each before the next, and order delivery so the sequence proves itself to a reviewer.
- 설치 수
- 1
- GitHub Stars
- 13
- 업데이트
- 10월 20일
mariusflorescusharpen
Make a task deeper, not bigger, then rewrite the prompt. Use for /sharpen.
- 설치 수
- 1
- GitHub Stars
- 13
- 업데이트
- 10월 20일
mariusflorescuteach
Explain a body of work plainly so a person actually understands it. Runs the how and why skills and weaves what they find into one clear explanation. Use for 'teach me this', 'help me really understand X', 'explain this change or subsystem to me'.
- 설치 수
- 1
- GitHub Stars
- 13
- 업데이트
- 10월 20일
mariusflorescuwhy
Use for 'why does X work this way', 'why we picked Y', design rationale, regressions, postmortems, or data-backed thresholds. Discovers available MCPs and queries each evidence category (source control, issue tracker, long-form docs, real-time chat, infrastructure observability, error tracking, product analytics warehouse) in parallel, then returns a cited read on decisions and tradeoffs. Use how for runtime behavior.
- 설치 수
- 1
- GitHub Stars
- 13
- 업데이트
- 10월 20일
mariusflorescuthermos
Launch both thermo-nuclear review subagents in parallel, then synthesize their findings. Use for thermos, double thermo review, or combined bug/security and code-quality branch audits.
- 설치 수
- 1
- GitHub Stars
- 0
- 업데이트
- 10월 10일