All authors
Claude Skills by Scino
github.com/Scino76 skills0 installs7 views
- ArchitectSketch types, signatures, and module structure before code, then stay in the loop while implementation fills in. Use for /architect, 'architect this', 'design this', or non-trivial work where jumping to code would lock in the wrong shape.Votes: 0GitHub stars: 21
- ArenaSpawn N parallel candidates at the same task, pick a base, graft the strongest parts of the losers into it. Use for /arena, 'arena this', 'throw it in the arena', or when one attempt at a non-trivial artifact would lock in the wrong shape.Votes: 0GitHub stars: 21
- Automate MeUse for \"automate me\", \"create/update/refresh my -mode skill\", \"turn/capture my preferences or working style into a skill\", or wanting agents to follow how the user works. Drafts or revises a personal -mode skill via plugin-dev:skill-development + unslop, optionally pulling fresh evidence from recent transcripts.Votes: 0GitHub stars: 21
- BabysitWatch an open PR — fix failing CI, handle the straightforward review comments, and drive it to a mergeable state. Claude Code analog of Cursor's built-in /babysit. Use after opening a PR when the user wants the agent to shepherd it without re-prompting.Votes: 0GitHub stars: 21
- Blast RadiusFind 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.Votes: 0GitHub stars: 21
- BroRestate the last message in plain human language, with no jargon. Use for /bro or when asked to say it plainly.Votes: 0GitHub stars: 21
- BrowseWeb browsing and page extraction. Attaches to Chrome over CDP when it is running, otherwise one-shot headless Chrome. Use for /browse, "open URL", public competitor pages, interactive search UIs, or a session where you are already logged in.Votes: 0GitHub stars: 21
- Ceo ReviewFounder/CEO strategic plan review. Calibrates scope across 4 modes (Scope Expansion, Selective Expansion, Hold Scope, Scope Reduction) to challenge premises, eliminate bloat, or discover the 10-star product experience. Use for /ceo-review, "review scope", or strategic plan review.Votes: 0GitHub stars: 21
- Changelog To PostConverts git commits, PR diffs, or engineering release notes into clean, user-facing changelogs, customer update emails, and launch tweets. Translates internal code changes into customer value. Use for /changelog-to-post, "draft release notes", or announcing new features.Votes: 0GitHub stars: 21
- Create Verification SkillGenerate a project-local verification skill that drives your app the way a user does — any language, framework, or platform. Use for /create-verification-skill, \"make a control skill for this repo\", or when a project has no scripted way to prove UI/CLI/service behavior.Votes: 0GitHub stars: 21
- Customer LensAudits UI flows, onboarding funnels, error messages, and landing page copy from the perspective of a skeptical, distracted customer. Identifies cognitive friction, confusing jargon, and drop-off risks. Use for /customer-lens, "audit UX", or customer friction review.Votes: 0GitHub stars: 21
- DeslopRemove AI-generated code slop and clean up code styleVotes: 0GitHub stars: 21
- Engineer Modefstack engineering execution. 23 playbooks, 24 principles, verified work, no slop. Use for /engineer-mode, /poteto-mode, or any non-trivial engineering task.Votes: 0GitHub stars: 21
- Playbooks**You own the skill's voice.** Agent-facing prose has a higher bar than human prose; unhelpful sentences become instructions. 1. Use the **plugin-dev:skill-development** skill (Claude Code's skill for authoring SKILL.md files). 2. Validate the skill: frontmatter has `name` and `description`, referenced files exist, cross-skill links resolve. 3. Test cases if structural; skip if subjective. 4. Run **Opening a PR**. When in doubt, delete; prose earns its keep by changing a decision. Tell it to ...Votes: 0GitHub stars: 21
- Figure It OutDesign an auditable playbook when no narrower one fits: a large migration, an ambitious multi-part change, or work a human reviews after stepping away. Scales rigor to the task, runs a hypothesis loop, and logs decisions via show-me-your-work. Use for /figure-it-out, 'figure it out', a large migration, or when no narrower playbook applies.Votes: 0GitHub stars: 21
- Fix CiFind failing PR checks, inspect logs or external check links, and apply focused fixesVotes: 0GitHub stars: 21
- Fix Merge ConflictsResolve merge conflicts non-interactively, validate build and tests, and finalize conflict resolutionVotes: 0GitHub stars: 21
- Founder ModeHigh-agency founder execution mode. Takes end-to-end ownership across product, code, copy, customers, and speed-to-market. Cuts bureaucracy, refuses generic AI hedges, enforces obsessive taste, and prioritizes commercial impact. Use for /founder-mode, "founder mode", or cross-functional shipping.Votes: 0GitHub stars: 21
- Founder VoiceManages and maintains the founder's persistent voice profile, tone preferences, vocabulary rules, and platform styles across X and LinkedIn. Use for /founder-voice, "configure my voice", or establishing writing persona.Votes: 0GitHub stars: 21
- FstackMaster orchestrator for fstack. Routes founder operations (sales, support, social, strategy) and engineering work through /engineer-mode. Use for /fstack, /fabio-mode, or founder/engineering requests.Votes: 0GitHub stars: 21
- Geo PageGenerates high-authority GEO (Generative Engine Optimization) and documentation pages designed to be accurately cited by AI search engines (Perplexity, SearchGPT, ChatGPT, Gemini) without keyword-stuffed SEO slop. Use for /geo-page, "create comparison page", or SEO content.Votes: 0GitHub stars: 21
- Get Pr CommentsFetch and summarize review comments from the active pull requestVotes: 0GitHub stars: 21
- HowUse for \"how does X work\", code walkthroughs before changing something, and placement / ownership / layering questions (\"where should this live\", \"which package owns this\", \"is this the right layer\"). Explains subsystem architecture, runtime flow, onboarding mental models. Can critique architecture. Use why for motivation.Votes: 0GitHub stars: 21
- Inbox TriageIngests pasted email threads or inbox batches, ranks by business and customer urgency, surfaces top priorities, and generates concise notes and 1-click draft responses. Use for /inbox-triage, "triage inbox", or sorting customer/sales messages.Votes: 0GitHub stars: 21
- InterrogateUse for \"interrogate\", \"adversarial review\", \"multi-model review\", \"challenge this\", \"stress test this code\", \"find blind spots\", or \"tear this apart\". Multiple LLM reviewers challenge changes from independent angles.Votes: 0GitHub stars: 21
- Lead ReplyDraft high-conversion, charming, consultative, and non-salesy replies to inbound leads and inquiries. Considers real product capabilities, persona, and next steps without AI slop. Use for /lead-reply, "draft reply to lead", or sales inquiries.Votes: 0GitHub stars: 21
- Maintain Verification SkillPeriodic pass that keeps a project's verification skill and feature map honest: parallel source readers per feature, one live session driving every feature, at most one PR of proven corrections. Use for /maintain-verification-skill or \"audit the verify skill\".Votes: 0GitHub stars: 21
- Make Pr Easy To ReviewPrepare PRs for review by cleaning noisy history, improving PR descriptions, and adding reviewer guidance without changing code behavior. Use for "make this easy to review", "tidy this PR", "clean up commits", or "annotate the diff".Votes: 0GitHub stars: 21
- No CommentsSpawn the comment-sicko subagent, fix accepted findings, and offer encodings for claimed constraints.Votes: 0GitHub stars: 21
- Office HoursYC-style founder sparring and product interrogation. Asks 6 forcing questions on demand reality, status quo, desperate specificity, narrowest wedge, observation, and future-fit before writing code. Use for /office-hours, "brainstorm this idea", or product stress-test.Votes: 0GitHub stars: 21
- Poteto ModeCompatibility alias for /engineer-mode and credit to Lauren Tan's pstack, which set the foundation of playbooks and principles for fstack's engineer-mode. Use for /poteto-mode or legacy prompts.Votes: 0GitHub stars: 21
- Principle Attack The PremiseApply when two or more fixes that share one premise have failed the same gate. Take a census of which actors hold the imbalance before the next fix, then question the premise instead of writing another fix that assumes it.Votes: 0GitHub stars: 21
- Principle Boundary DisciplineApply 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.Votes: 0GitHub stars: 21
- Principle Build The LeverApply to any non-trivial work, not just bulk work: edits, migrations, analyses, checks. Build the tool that does it or proves it (codemod, script, generator, or a skill your subagents follow) instead of working by hand. The tool is the artifact a reviewer can rerun.Votes: 0GitHub stars: 21
- Principle Clear NamingApply when naming variables, functions, types, files, or endpoints. Enforces the 6-month amnesia test, language conventions, intent-based naming, and cross-boundary consistency.Votes: 0GitHub stars: 21
- Principle Encode Lessons In StructureApply when you catch yourself writing the same instruction a second time, or notice a recurring correction. Encode the rule as a lint, metadata flag, runtime check, or script instead of more text.Votes: 0GitHub stars: 21
- Principle Exhaust The Design SpaceApply when facing a novel UI interaction or architectural decision with no precedent in the codebase. Build 2-3 competing prototypes and compare side by side before committing.Votes: 0GitHub stars: 21
- Principle Experience FirstApply when product, UX, or feature-scope tradeoffs come up. Choose user delight over implementation convenience; ship fewer polished features over more rough ones.Votes: 0GitHub stars: 21
- Principle Fix Root CausesApply when debugging. Trace each symptom to its root cause and fix it there; reproduce first, ask why until you reach it, resist nil-check guards that silence crashes.Votes: 0GitHub stars: 21
- Principle Foundational ThinkingApply before writing logic: choosing core types and data structures, sequencing scaffold-vs-feature work, asking what concurrent actors share. Get the data structures right so downstream code becomes obvious.Votes: 0GitHub stars: 21
- Principle Guard The Context WindowApply when context is filling up: large outputs, long files, repeated reads, fan-out planning. Route bulk to subagents; keep summaries in the main thread, not raw payloads.Votes: 0GitHub stars: 21
- Principle Laziness ProtocolApply when refactoring, evaluating diff size, or tempted to add abstractions, layers, or signal threading. Enforces Occam's Razor: bias toward deletion and the simplest change that solves the problem.Votes: 0GitHub stars: 21
- Principle Make Operations IdempotentApply 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.Votes: 0GitHub stars: 21
- Principle Migrate Callers Then Delete Legacy ApisApply when introducing a new internal API while old callers still exist. Migrate callers and delete the old API in the same wave instead of preserving compatibility layers.Votes: 0GitHub stars: 21
- Principle Minimize Reader LoadApply when reviewing or shaping code that's hard to trace. Count layers between question and answer, and hidden state in the reader's head; collapse one-caller wrappers and shrink mutable scope.Votes: 0GitHub stars: 21
- Principle Model The DomainApply when writing stateful logic, or when code branches a lot or repeats a shape assumption across files. Encode the domain in a structure instead of scattered conditionals.Votes: 0GitHub stars: 21
- Principle Never Block On The HumanApply when tempted to ask 'should I do X?' on reversible work. Proceed, present the result, let the human course-correct after the fact; reserve confirmation for irreversible actions.Votes: 0GitHub stars: 21
- Principle Outcome Oriented ExecutionApply during planned rewrites and migrations with explicit phase boundaries. Converge on the target architecture; don't preserve smooth intermediate states with throwaway compatibility code.Votes: 0GitHub stars: 21
- Principle Prove It WorksApply 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.'Votes: 0GitHub stars: 21
- Principle Redesign From First PrinciplesApply when integrating a new requirement into an existing design. Redesign as if the requirement had been a foundational assumption from day one, instead of bolting it on.Votes: 0GitHub stars: 21