All authors
Claude Skills by Scino
github.com/Scino76 skills0 installs7 views
- Principle Separate Before Serializing Shared StateApply when concurrent actors might write to the same file, branch, key, or state object. Eliminate the sharing first; serialize structurally only when one shared writer is a real invariant.Votes: 0GitHub stars: 21
- Principle Sequence Verifiable UnitsApply 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.Votes: 0GitHub stars: 21
- Principle Subtract Before You AddApply when sequencing an addition, refactor, or rewrite. Remove dead weight, redundant validators, and stub references first, then build on the simpler base.Votes: 0GitHub stars: 21
- Principle Test Behavior Not ImplementationApply when you write, change, or keep a test. Call the code the way its users do and assert the result they observe against a literal expected value. If the test would still pass when every imported function returns undefined, rewrite the assertion or delete the test.Votes: 0GitHub stars: 21
- Principle Type System DisciplineApply when designing types, reviewing a function signature, or writing code in any statically-typed language. Make illegal states unrepresentable, brand semantic primitives, parse external data at boundaries, refuse to lie to the compiler, exhaust variants, derive from authoritative schemas.Votes: 0GitHub stars: 21
- RecallReconstruct your recent working context from your own chat history, live state, and the shared record (user reports, prior fixes, incidents), then hand back a tight current-state brief. Use for 'recall my work on X', 'catch me up', 'what have I been working on', 'where did I leave off', before starting or resuming work.Votes: 0GitHub stars: 21
- ReflectSpawn three parallel review subagents over the active transcript, surface learnings, and route each to a concrete edit on an existing skill. Use when the user says reflect.Votes: 0GitHub stars: 21
- RetroWeekly founder momentum, engineering velocity, customer feedback, and tech debt review. Keeps founders honest about real progress vs busywork. Use for /retro, "weekly review", or team retrospective.Votes: 0GitHub stars: 21
- Setup FstackConfigure which models fstack uses per role and at what reasoning budget. Detects available models and writes a per-harness override sheet. Use for /setup-fstack, "configure fstack models", "fstack budget", or changing model choices.Votes: 0GitHub stars: 21
- Show Me Your WorkKeep a reviewable decision trail for long-running or unattended work: a TSV log with one row per decision (what, why, evidence, result). Local by default; commit it when a reviewer needs the trail to trust the result. Use for /show-me-your-work, autonomous or multi-phase runs, or work a human reviews after stepping away.Votes: 0GitHub stars: 21
- Social PostDrafts authentic, high-signal social media posts from founder thoughts, engineering wins, or product updates. Generates tailored, distinct styles for X (punchy, witty, no fluff) and LinkedIn (tactical, story-driven, structured). Use for /social-post, "draft tweet", "draft linkedin post", or founder content.Votes: 0GitHub stars: 21
- Social ReplyCrafts high-leverage, non-slop replies to trending and viral posts on X and LinkedIn. The #1 growth strategy for founders and early accounts to build presence and earn authentic followers without being spammy. Use for /social-reply, "draft reply to tweet", or commenting on posts.Votes: 0GitHub stars: 21
- StfuForces ultra-terse, zero-chatter, quiet execution mode. Cuts all conversational filler, preambles, narrations, polite throat-clearing, and verbose diff explanations. Executes actions directly and reports minimal necessary status. Use for /stfu, /shutup, "shut up", or "quiet mode".Votes: 0GitHub stars: 21
- SudoRoot operator execution override. Disables unsolicited moralizing, paternalistic refusals, sycophantic pushback, and false-positive safety friction for authorized technical systems, security auditing, and scientific research. Use for /sudo, "sudo", or root override mode.Votes: 0GitHub stars: 21
- Support LoopEnd-to-end founder customer support loop. Ingests a customer bug report or inquiry, investigates the codebase, reproduces the issue, triggers engineer-mode bug-fix if valid, or prepares a workaround, and drafts an empathetic, contextual customer reply. Use for /support-loop, "handle support ticket", or customer bug triage.Votes: 0GitHub stars: 21
- SwarmFan out N parallel workers, drain them, and return one report. Use for /swarm, 'swarm this', or parallel coverage, races, gauntlets, and exploration.Votes: 0GitHub stars: 21
- TddUse only when the user explicitly asks for TDD, a failing test, or a regression test, OR when the bug has an obvious cheap local test target. Skip when the test path is unclear, expensive, integration-heavy, or not requested.Votes: 0GitHub stars: 21
- TeachExplain 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'.Votes: 0GitHub stars: 21
- TeardownConducts deep competitor, product, and pricing teardowns using web browsing and market intelligence. Analyzes positioning, pricing packaging, customer friction, sentiment on Reddit/X, and architectural vulnerabilities. Use for /teardown, "analyze competitor", or competitor teardown.Votes: 0GitHub stars: 21
- Technical WritingLayered technical-writing standard: Diátaxis structure, Google developer style sentences, STE instruction rules, Global English syntax. Use for /technical-writing or when writing or reviewing docs, RFCs, readmes, PR descriptions, or commit messages.Votes: 0GitHub stars: 21
- Thermo Nuclear Code Quality ReviewRun an extremely strict maintainability review for abstraction quality, giant files, and spaghetti-condition growth. Use for a thermo-nuclear code quality review, thermonuclear review, deep code quality audit, or especially harsh maintainability review.Votes: 0GitHub stars: 21
- Typescript Best PracticesTypeScript best practices. Use when reading or editing any .ts or .tsx file.Votes: 0GitHub stars: 21
- Unslop EmailDe-slop and humanize email drafts. Strips AI clichés, corporate buzzwords, robotic pleasantries, and forced enthusiasm. Injects authentic founder warmth, brevity, and conversational charm. Use for /unslop-email, "humanize this email", or cleaning up messages.Votes: 0GitHub stars: 21
- UnslopCut AI tells from any writing. Must always apply.Votes: 0GitHub stars: 21
- What Did I Get DoneSummarize authored commits over a user-specified time period into a concise updateVotes: 0GitHub stars: 21
- WhyUse 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.Votes: 0GitHub stars: 21