All authors
Claude Skills by v1truv1us
github.com/v1truv1us276 skills4 installs410 views
- Pr Review CanvasGenerate an interactive PR review walkthrough as an HTML page. Fetches PR data via gh API, categorizes files into core vs mechanical changes, adds reviewer annotations, and renders diffs with moved-code detection. Use when the user pastes a GitHub PR URL and asks for a review, walkthrough, or summary, or says \\\"review this PR\\\".Votes: 0GitHub stars: 8
- Prompt EngineeringComprehensive prompt engineering for coding agents covering structured instruction design, few-shot prompting, chain-of-thought, decomposition, agent workflow patterns, and reliability techniques for multi-step pipelines.Votes: 0GitHub stars: 8
- Prompt RefinementTransform prompts into structured TCRO format with phase-specific clarification. Automatically invoked by /ai-eng/research, /ai-eng/plan, /ai-eng/work, and /ai-eng/specify commands. Use when refining vague prompts, structuring requirements, or enhancing user input quality before execution.Votes: 0GitHub stars: 8
- 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: 8
- 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: 8
- 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 create-skill + unslop, optionally pulling fresh evidence from recent transcripts.Votes: 0GitHub stars: 8
- 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: 8
- InterrogateUse for \"interrogate\", \"adversarial review\", \"multi-model review\", \"challenge this\", \"stress test this code\", \"find blind spots\", or \"tear this apart\". Four LLM reviewers challenge changes from independent angles.Votes: 0GitHub stars: 8
- Poteto Modepoteto'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.Votes: 0GitHub stars: 8
- 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: 8
- 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: 8
- 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: 8
- 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: 8
- 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: 8
- 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: 8
- 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: 8
- Principle Laziness ProtocolApply when refactoring, evaluating diff size, or tempted to add abstractions, layers, or signal threading. Bias toward deletion and the smallest change that solves the problem.Votes: 0GitHub stars: 8
- 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: 8
- 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: 8
- 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: 8
- 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: 8
- 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: 8
- 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: 8
- 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: 8
- 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: 8
- 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: 8
- 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: 8
- 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: 8
- 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: 8
- Typescript Best PracticesTypeScript best practices. Use when reading or editing any .ts or .tsx file.Votes: 0GitHub stars: 8
- UnslopCut AI tells from any writing. Must always apply.Votes: 0GitHub stars: 8
- 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: 8
- RepurposeAdapt existing content into new formats for different channels. Use for \"repurpose this\", \"turn this into\", \"adapt for\", or /repurpose.Votes: 0GitHub stars: 8
- Research DeepMulti-source deep research with confidence-rated synthesis. Use for \"research deeply\", \"deep dive on\", \"comprehensive research\", or /research-deep.Votes: 0GitHub stars: 8
- Run Learning RetrospectiveEvaluate learning progress, identify blockers, and adjust the learning planVotes: 0GitHub stars: 8
- Run Smoke TestsRun Playwright smoke tests, debug failures, and verify fixesVotes: 0GitHub stars: 8
- Security And HardeningOWASP Top 10 prevention, auth patterns, secrets management, dependency auditing, three-tier boundary system. Use when handling user input, auth, data storage, or external integrations.Votes: 0GitHub stars: 8
- Shipping And LaunchReview changes, open PRs, run pre-launch checks, staged rollouts, and rollback. Use when preparing to ship to production or closing out a branch.Votes: 0GitHub stars: 8
- Source Driven DevelopmentGround every framework decision in official documentation. Use when you want authoritative, source-cited code for any framework or library.Votes: 0GitHub stars: 8
- Spec Driven DevelopmentWrite a structured specification before writing code. Use when starting a new project, feature, or significant change. Defines objectives, commands, structure, code style, testing strategy, and boundaries.Votes: 0GitHub stars: 8
- Test Driven DevelopmentRed-Green-Refactor workflow. Write tests before implementation, maintain 80%+ coverage. Use when implementing logic, fixing bugs, or changing behavior.Votes: 0GitHub stars: 8
- Text CleanupComprehensive patterns and techniques for removing AI-generated verbosity and slopVotes: 0GitHub stars: 8
- Thermo Nuclear Architecture ReviewRun an extremely strict architecture and system design review for coupling, boundary violations, dependency direction, layering, and structural decay. Use for a thermo-nuclear architecture review, thermonuclear system design audit, or especially harsh architecture review.Votes: 0GitHub stars: 8
- Thermo Nuclear Performance ReviewRun an extremely strict performance review for runtime efficiency, memory usage, bundle size, database query patterns, and scalability limits. Use for a thermo-nuclear performance review, thermonuclear performance audit, or especially harsh performance review.Votes: 0GitHub stars: 8
- Using Agent SkillsDiscovery and invocation of all skills, commands, and agents. Decision tree for task-to-skill mapping. Core operating behaviors for agents. Use when unsure which skill or agent to use.Votes: 0GitHub stars: 8
- Verification LoopContinuous verification after every change, plus claim-based proof when evidence is required. Use when implementing, fixing bugs, refactoring, or when asked to verify a specific claim.Votes: 0GitHub stars: 8
- Weekly ReviewProduce a weekly synthesis of authored commits with highlights by bugfix, tech debt, and net-new workVotes: 0GitHub stars: 8
- What Did I Get DoneSummarize authored commits over a user-specified time period into a concise updateVotes: 0GitHub stars: 8
- Workflow From ChatsExtract durable working preferences from recent Cursor chats and convert them into skills, rules, or workflow docs. Use when asked to learn preferences, mine feedback, personalize workflows, or generate team/person-specific agent guidance.Votes: 0GitHub stars: 8
- Ralph WiggumContinuous iteration loop pattern for well-defined tasks with clear completion criteria. Use when getting tests to pass, implementing features with automatic verification, bug fixing with clear success conditions, or running automated development overnight. Provides prompt templates, safety guidelines, and integration patterns for ai-eng-system workflows.Votes: 0GitHub stars: 8